A practical internal verification log template
The IV log is the one document a Standards Verifier, an appeals panel and an auditor will all read the same way. It answers, per verification: who checked what, against what, finding what, and who agreed. Free of narrative, rich in names and dates. Here's the anatomy and a template.
What each entry must capture
- Header: unit, learning aims covered, qualification, cohort, assessor, internal verifier, date of verification.
- The brief: title/version (V1/V2), date approved for use, who approved it — stage-1 IV evidence.
- The sample: which learners were sampled and why (random, borderline, first round, all-resubmissions) — the "why" is what makes the sample defensible.
- Per-criterion findings: criterion code, assessor's decision, IV's agreement or disagreement, the evidence location examined.
- Actions: what returns to the assessor, what changes in records, deadlines.
- Sign-off: both signatures and dates; Lead IV countersignature where required.
A copy-paste entry template
Unit: 3 Business Finance (L3) · Assessor: [Name] · IV: [Name] · Date: [dd/mm/yyyy]
Brief: "Local bakery expansion" PSA V2, approved [date] by [Lead IV]
Sample: Learners A, F, K (borderline Merit), R (all-D) + 1 resubmission — selected as [first round with new assessor]
Findings: A.P1 met — evidence p.1 ¶2, agreed. A.P2 partly met per assessor, evidence p.3 ¶1 lacks suitability link — agreed, returned. B.P4 not met (no calculations from brief data) — agreed; resubmission authorised [date] by [Lead IV], due [date]. C.D3 met — evidence p.11, judgement supported by ratio data, agreed.
Actions: Assessor to amend A.P2 record and confirm resubmission window; IV re-check [date].
Signatures: [Assessor] [IV] [Lead IV]
Notice what it has that most logs don't: the disagreements. A log with no disagreements ever is not a strong log — it's an unused one. IVs who find nothing across a whole year either aren't sampling hard enough or aren't recording honestly.
Three habits that make logs audit-proof
- Log at verification time, not before an audit. Reconstructed logs have a smell — consistent handwriting, consistent dates, no gaps.
- Reference evidence by location, not opinion. "p.3 ¶1" can be checked by anyone in 2028. "The finance section" cannot.
- Close every action. Open actions from last round showing up open in this round is a self-inflicted finding.
If verification records are generated alongside marking rather than after it, the log almost writes itself — checkb.tech's per-criterion output means every "agreed" in the template above is a citation that already exists. The verification export formats it for the log.
FAQ
Where should logs live?
Anywhere durable and retrievable per learner per unit — a shared drive folder structure is fine. What matters is that the SV can get the complete set for any sampled learner in minutes.
Do logs differ per qualification size?
No — the entry anatomy is the same whether it's a Certificate or an Extended Diploma. Volume differs; content doesn't.