Specification changes in BTEC Business: what to track and when
Two different clocks run inside "BTEC Business", and conflating them causes most change-management chaos: the specification issue clock (rare, structural) and the brief cycle clock (annual, cosmetic). Here's how to tell them apart and what to do when either ticks.
The two clocks
| Specification issue | Brief cycle (PSA) | |
|---|---|---|
| How often | Years apart — e.g. International L3 Business is on Issue 4 | Annually — issued around June, valid to end of the following August |
| What changes | Can change anything: criteria wording, unit lists, grading rules, controls | Scenario and data rotate; criteria identical across V1/V2 (PSA guide) |
| Response needed | Full re-plan: grids, resources, thresholds, tooling pinned to the new issue | Refresh briefs and scenario data; teaching continuity preserved |
When an issue bump lands, the checklist
- Diff the criteria grids, unit by unit. Not the whole spec — the grids are the assessment law. Any criterion whose code, band or verb changed is a marking-standard change; everything else is editorial.
- Check the grading rules section — the band rules rarely move, but an issue is the only place they could.
- Re-pin your tools and templates. Threshold documents, checking tools, criteria libraries — anything calibrated to the old issue must be updated, or your per-criterion work is against stale law. (The criteria library pins to the current International L2/L3 Business issues; a new issue is a re-distillation event.)
- Re-run standardisation early on a script marked under the old issue, against the new grid — the disagreements are your change log (the method).
- Brief audit: centre-devised briefs validated against the old issue need re-checking against the new — coverage, sufficiency, the stage-1 IV checks.
The brief-cycle non-event (say this to the team)
"New briefs" each June are not specification changes. The June cycle rotates scenarios and data tables; the criteria grid on the final page is identical. The three things that genuinely need June attention: use the new briefs' actual scenario data (old scenarios in new-year evidence is a validity problem), version control per cohort (versions guide), and expiry dates in the calendar (the calendar guide).
FAQ
How do I know which issue we're on?
The spec's cover page states the issue number and date; briefs state their version and validity window. Pin your working documents to those printed facts — never to filenames or folklore.
Do criteria ever change mid-issue?
No — within an issue, the grids are stable. Anything that looks like a mid-year criteria change is almost always a brief-cycle misunderstanding or an erratum notice worth reading carefully.