Reading a BTEC assignment brief, page by page

The assignment brief is the most-read, least-understood document in BTEC delivery — learners skim it for the task list, teachers check it once at authorisation. Read properly, it tells you exactly what to write, how deep to write it, and how your work will be judged. Here's the anatomy.

The parts of a brief (and what each is for)

1. Cover / issue details: unit, title, version (V1/V2), issue dates and the validity window. The version is printed here — trust it over any filename (why versions matter).
2. The scenario: the business/case your evidence lives in, usually with data tables. Read this as assessment material — the figures feed calculations, the context anchors analysis. A brief without its data used is a brief only half-read.
3. The tasks/activities: each lists the learning aims and the criteria codes it covers — Pearson prints the mapping ("This activity covers learning aims A and B; A.P1, A.M2…"). That mapping is the spine of your evidence: work through it and every criterion has a home.
4. Assessment controls: time allowed, supervision level, permitted resources, whether drafts/feedback are allowed. These are rules of validity — break them and the evidence isn't assessable, regardless of quality. They also define what teacher feedback is permitted mid-process; respect the boundary.
5. The final-page criteria grid: the whole assessment, verbatim, in one table. This is the page the entire marking hangs on — the same grid as the criteria library and the spec.

Read the brief as an assessor would

1. Grid first, scenario second. Know what's assessed before you know what it's about — verbs and all (grid literacy).
2. Map tasks to criteria — every grid criterion should appear in at least one task; if a criterion has no task home, that's a brief problem your IV should catch (that's stage-1 internal verification).
3. Inventory the data. List every table/figure and predict which criteria will need it. Learners who do this write scenario-anchored evidence naturally.

For brief authors: the three checks before a brief goes live

• Coverage: every criterion has a task that generates evidence for it — and no task demands work the grid doesn't assess.
• Sufficiency: the scenario actually contains what the Merit/Distinction criteria need to analyse and evaluate. A bland scenario quietly converts all criteria to Pass-level writing.
• Controls are realistic: supervision and resource rules your centre can actually run.

The one-sentence version

A brief is not a worksheet; it's a criteria grid wearing a scenario — read the grid, live in the scenario, and honour the controls.

FAQ

Are brief versions the same as criteria versions?

No — V1/V2 rotate the scenario; the criteria grid is identical across versions. Criteria change only with a new specification issue, which is a different event entirely.

Can I use a past brief for practice?

Excellent idea — expired briefs are perfect rehearsal material. Label them clearly so they never mix with live assessment (validity windows again).