Choosing internal verification software for your department

Most "IV software" is a folder with signatures. What a BTEC department actually needs is a system that makes per-criterion decisions and their evidence trail the default output of marking — so the verification log, the sampling pack and the standards-verification file are exports, not projects. Here's the buying guide.

Must-have #1 — Criteria are the data model

If the product's central object is a "submission" or a "file", everything criterion-shaped will be a text field someone types into. If its central object is a criterion with a verdict and cited evidence, then the unit grade computes itself (band rule), sampling lists build themselves, and gaps surface before IV instead of during it. Ask for a live demo on a real unit's grid: A.P1 through C.D3, verdicts visible.

Must-have #2 — The evidence trail is native

Every verdict must point at the evidence that justified it — location or quote — or you're rebuilding the audit trail by hand. This is also what makes IV log entries one-click instead of one-evening.

Must-have #3 — Exports your verifier will actually accept

• Per-learner assessment records, per criterion, with evidence locations.
• A sampling pack: chosen learners × full paper trail (brief, evidence, records, IV log, resubmission papers — see the SV guide).
• Something exportable and durable — PDF/CSV out, not a login the Standards Verifier doesn't have.

Must-have #4 — Assessment-aware, not storage-agnostic

Drop-boxes don't know a resubmission from a first attempt, a Merit criterion from a Pass one, or an expired brief from a live one. The product should encode the workflow: brief versions, resubmission authorisation with Lead IV sign-off, deadline tracking, and criterion coverage per unit.

Must-have #5 — Data protection that survives an inspection

• Written no-training-on-learner-data confirmation.
• UK/EU data residency or clear GDPR posture; retention rules you control.
• Tenant isolation if you're a multi-centre trust.
• An honest answer on AI: does anything in the pipeline emit grades to learners, or does every output land with the teacher first? (The wrong answer here is a compliance problem — see the AI tools guide.)

Red flags

• "Powered by AI" with no evidence citation anywhere in the demo.
• Records that only exist inside the product (lock-in meets audit risk).
• IV workflow modelled as "upload, then email" with signature images.

Where checkb.tech fits

It's deliberately the criteria-first version of this list: verdicts per criterion with cited evidence, deterministic re-checks, brief-version handling, resubmission awareness, exports shaped for verification paperwork, and the teacher-decides boundary built into every screen — triage, exports and cohort analytics. Start on the free tier with one unit's next batch and compare the export against your current IV log — that comparison is the whole evaluation.

FAQ

Do we need software at all?

Small centres run fine on documents if the discipline is there. Software earns its keep at scale — multiple assessors, resubmission volume, or SV sampling pressure — by making the good records the lazy path.

Can IV software double as our malpractice tracker?

Partly — authentication evidence (drafts, versions, observation records) can live in the same trail. Malpractice cases still run through your centre's policy process.