BTEC verification: the 15 recurring questions, answered

Verification conversations repeat. Collect the questions that come back every cycle — internal and standards — and the answers hold still. Here are the fifteen that matter, answered once.

1. How big should my IV sample be?

Risk-based, recorded, and always including every resubmission, borderline scripts and at least one the assessor found hard. New assessors get heavy sampling until trust exists — the IV guide.

2. What does the verifier ask for first?

The assessment record: per-criterion decisions with evidence locations. Everything else — IV log, resubmission papers — hangs off it (records guide).

3. What's the most common finding?

Records that summarise instead of decide: "strong work, Merit" verifies nothing. Per-criterion verdicts with locations are the fix.

4. Can I verify my own assessments?

No — a different person verifies. Structural independence, not personal integrity.

5. What if the IV disagrees with my verdict?

The decision returns to you with reasons; you re-examine the evidence. The IV checks your judgements against the criteria; they don't re-mark on opinion.

6. How does the SV differ from my IV?

Sample size and authority: the SV compares your centre's standard against the national one and can require re-assessment — the three-gate map.

7. What paperwork must accompany a resubmission?

Lead IV authorisation before the learner restarts, the first attempt's record, the resubmitted evidence, the fresh assessment — rules.

8. Is "partly met" a valid decision on the record?

Formally, decisions are met / not met; "partly met" is working language that makes the gap precise — write it in comments, decide met / not met in the verdict column (vocabulary).

9. How do verifiers treat verb-level issues?

Seriously and every time: described work recorded against analyse criteria is the classic leniency finding — the ladder.

10. Do verifiers check authentication in the AI era?

Increasingly, yes — expect to show the trail: drafts, versions, observation records, in-class production (the guide).

11. What makes a brief fail verification?

Coverage gaps (criteria without tasks), sufficiency failures (scenario can't evidence the criteria), wrong version/expired window — stage-1 IV catches all three cheaply.

12. How far back can records be demanded?

Per your centre's retention policy and Pearson's requirements — the operational answer is "further than your current filing system assumes". Durable, retrievable, per learner per unit.

13. Can tool-assisted verdicts survive verification?

Yes, when the tool's role is checking and the teacher's role is deciding: verdicts with cited evidence, one-click override, teacher decisions on the record — the compliance frame.

14. What if our standard disagrees with the SV's?

Required actions follow, and there's an appeals route through Pearson's process — appeals map. Complete records are what make that conversation winnable.

15. What single improvement most raises verification outcomes?

Per-criterion records with cited evidence, written at marking time. Every answer above eventually routes back to it — which is why checkb.tech produces exactly that as its primary output (export).