Core Component

Employer Set Project (ESP)

Controlled assessment worth 100 marks (40% of Core Component). Students complete 5 tasks across multiple supervised sessions totaling up to 14 hours 30 minutes. No internet or AI tools permitted.

100 marks
Total Assessment
40% of Core Component
Core Component
Up to 14 hours 30 minutes
Assessment Time

ESP Assessment Details

ComponentAssessment MethodDurationMarksWeightingTimetableAvailability
Employer Set ProjectExternally set project14 hours 30 minutes100
40%
Set date/time
May/November

ESP Assessment Notes

  • • The ESP is externally set and marked by Pearson
  • • Forms 40% of the Core Component (20% of total T Level grade)
  • • Students complete 5 tasks across multiple supervised sessions
  • • No internet access or AI tools permitted during assessment
  • • Pre-release materials may include industry context for familiarisation

ESP At a Glance

Assessment Conditions

  • Up to 14 hours 30 minutes total
  • Multiple supervised sessions
  • No internet access permitted
  • No AI or response-preparation tools

Portfolio Submission

  • Planning documents
  • Annotated digital portfolio
  • Working prototype
  • Testing evidence
  • Reflective evaluation

Assessment Objectives (100 marks total)

AO1

Planning

12% weighting

12 marks
available
AO2

Application

41% weighting

41 marks
available
AO3

Selecting techniques and resources

9% weighting

9 marks
available
AO4

English, maths, digital

6% weighting

6 marks
available
AO5

Outcomes and review

32% weighting

32 marks
available

Task-by-Task Requirements

Task 1: Planning a project

Produce a project plan using the Pearson template with a Gantt chart plus a resource and cost plan. Schedule to a defined deadline, prioritise activities, assign resources and align to an appropriate development lifecycle.

Provide a rationale that justifies key planning decisions including task order, allocation, benefits, risks, timing and costs.

Expected Evidence:

Gantt chart
Resource and cost plan
Written rationale

Task 2: Identifying and fixing defects in existing code

Assess given code against stated requirements. Design and run tests with clearly identified test data: valid, valid extreme, invalid, invalid extreme, erroneous and record expected versus actual results.

Correct errors and adjust the code so it meets the brief while following sound programming conventions.

Expected Evidence:

Annotated test records
Corrected code

Task 3: Designing a solution

Decompose the problem with clear abstraction and refinement, show reusable components and communicate algorithms using appropriate tools (flowcharts or code).

Apply logical thinking with well-defined steps and use consistent structure and naming conventions. Communicate the design so a client can make decisions and a third party could implement the solution.

Expected Evidence:

Design pack with algorithms and diagrams
Explanation of structures and processes

Task 4a: Developing a solution

Implement the solution to the brief using appropriate programming techniques and both pre-written and user-written modules. Organise code clearly: avoid deep nesting, use clear indentation, precise logic, functions or classes, comments, mostly local variables and constants.

Testing is expected implicitly through a working product that meets requirements. User experience should show consistency, simplified inputs, meaningful messages and where relevant data visualisation (e.g. with Matplotlib).

Expected Evidence:

Working prototype
Well-structured codebase

Task 4b: Reflective evaluation

Apply reflective evaluation. Demonstrate that the product meets the success criteria and user needs using evidence from testing.

Discuss realistic improvements you would make if revisiting the problem.

Expected Evidence:

Concise reflective report linked to the brief and criteria

Learning Time & Delivery Conditions

Assessment Time

  • • Total supervised assessment: up to 14 hours 30 minutes
  • • Multiple sessions scheduled by the centre
  • • Pre-release familiarisation with industry context allowed

Conditions

  • • Supervised sessions only
  • • No internet access
  • • No AI or similar tools for any assessed task

Core Component Context

  • • Total Core: 630 guided learning hours
  • • ESP: Controlled project element within Core
  • • Worth 40% of Core marks

Required Software & Resources

Software Requirements:

  • Diagramming or flowcharting software for algorithms and system diagrams
  • Python 3.10 or later with appropriate IDE plus libraries (Pandas and Matplotlib)
  • Spreadsheet software for data handling, dashboards, Gantt chart and costings
  • Word processor, presentation tool, project management tool
  • Image editor, programming editor, database tools
  • Web browsers, web server

Note: All items listed are explicitly required in the Core resources section of the Pearson specification for ESP delivery.

Student ESP Brief

Would you like a printable one-page brief for students with tick-box checklist for evidence per task and session-by-session running order for the 14 hours 30 minutes?

Back to T-Level Overview