Resources & Guides for IQA Teams

EQA visit preparation · external quality assurance visit checklist · EQA evidence FE college

EQA Visit Ready: A Pre-Visit Checklist for FE Colleges

You've had the email. An EQA visit is confirmed, or an Ofsted deep dive has just landed on a curriculum area, and now someone is asking whether "everything's ready." The honest answer, most of the time, is: mostly, but it's scattered across three drives, two inboxes and one colleague's memory.

This isn't a generic compliance checklist. It's written from inside the process — the same evidence gathering, sampling checks and standardisation questions that come up on the inside of an actual IQA cycle, not from a compliance consultancy's template library. If you run IQA for a curriculum area, a department, or a whole centre, this is what actually gets checked, what actually goes wrong, and what to do about it in the time you've got left.

What EQAs actually ask for first

Most colleges over-prepare the wrong things. EQAs don't start by asking to see your policy documents — they start by asking to see evidence that the policy is actually happening. In practice, that means:

• The sampling plan itself, not a description of your sampling strategy. They want to see it as a live document: who's been sampled, when, against what risk rating.
• A sample of IQA records, usually across more than one assessor, so they can check for consistency rather than reading one well-written example.
• Evidence of standardisation activity — not just meeting minutes that say "standardisation took place," but what was actually discussed and what changed as a result.
• Traceability from a learner's assessment decision back to the IQA sign-off that checked it. This is the single most common point where colleges scramble, because it means pulling evidence from two or three different systems and lining up dates.

If you can produce these four things inside the first ten minutes of a request, the rest of the visit tends to go well. If it takes an hour to assemble them, the EQA has already learned something about your quality assurance process — regardless of how good the underlying judgements were.

The evidence pack: what "EQA-ready" really means

"EQA-ready" doesn't mean a folder that exists. It means a folder (physical or digital) that is structured the way an EQA actually reads it, not the way it was convenient to file it.

A genuinely EQA-ready evidence pack, per curriculum area, typically includes:

1. The current sampling plan, with risk ratings and rationale
2. Completed IQA records for the sampled learners, in date order
3. Observation records, where observation of practice forms part of the sampling method
4. Standardisation meeting evidence, tied to the assessors covered by that sampling plan
5. Any actions raised at the last EQA visit, and evidence they were closed out — not just noted, closed out
6. A short summary of anything that changed in the delivery team, the qualification specification, or awarding body requirements since the last visit

The colleges that struggle here aren't the ones with bad IQA judgements. They're the ones where this evidence exists but lives in six places, so "EQA-ready" in practice means someone spending two days the week before the visit reconstructing a pack that should already exist.

Sampling plan coverage — checking you've covered what you say you have

This is the gap that catches even experienced quality teams out, because it's invisible until someone actually checks. A sampling plan can look complete on paper — every assessor listed, every unit covered — while the actual sampling that happened drifted from the plan months ago.

Before a visit, check:

• Does the sampling that's actually happened match the plan's stated frequency and risk rating, or has "high risk = sampled every submission" quietly slipped to "high risk = sampled most of the time"?
• Are there curriculum areas, units, or assessors that haven't been sampled at all in the current cycle, even though the plan says they should have been?
• Where risk ratings have changed (a new assessor, a unit with previous EQA action points, a qualification recently updated by the awarding body), has the sampling frequency actually changed with it, or just the paperwork?

The honest way to check this is to cross-reference the plan against the actual IQA records, unit by unit, assessor by assessor — not to re-read the plan and assume compliance. This is exactly the kind of coverage check that's fast when the records live in one system and genuinely painful when they're spread across spreadsheets, shared drives and personal folders.

Standardisation evidence — proving consistency, not describing it

Every centre says standardisation happens. What separates a strong evidence base from a weak one is whether you can prove what changed as a result, not just that a meeting took place.

Look for:

• Specific examples discussed at standardisation (anonymised work, borderline judgements, differing interpretations between assessors) rather than generic minutes
• Evidence that a disagreement in judgement was actually resolved — what the resolution was, and whether it was fed back to the assessor(s) involved
• A link between standardisation findings and subsequent IQA activity — if standardisation identified an assessor applying criteria inconsistently, is there a sampling record afterwards showing that was checked and improved?

A policy document describing your standardisation process is not evidence that standardisation is working. An EQA has read hundreds of standardisation policies; they're checking whether yours produces anything that changes practice.

Common gaps that trigger follow-up actions

These show up repeatedly enough to be worth naming directly:

• Audit trail gaps — an IQA record with no clear trail of who made a decision, when, and what evidence they reviewed to make it.
• Missing sign-off dates, or sign-off dates that don't line up with when the underlying assessment was actually completed (a common tell that IQA happened well after the assessment, not alongside it).
• Inconsistent risk-rating rationale — two assessors rated as the same risk level for very different reasons, or risk ratings that were set once and never revisited.
• Actions from the previous visit that were "actioned" verbally but have no evidence trail showing what was actually done.

Every one of these is a documentation and traceability problem, not a quality-of-teaching problem. That's the frustrating part — the underlying IQA judgements are often sound, but if the evidence trail can't demonstrate it in the room, the visit records it as a gap anyway.

A one-week pre-visit checklist

If the visit is confirmed for next week, here's a realistic day-by-day approach:

Day 1 — Take stock. Pull the current sampling plan and check it against what's actually been sampled. Identify any curriculum areas or assessors with a coverage gap.

Day 2 — Close the coverage gaps you can. Where sampling has fallen behind, prioritise the highest-risk areas first. You won't close every gap in a week — be honest about what's realistic, and be ready to explain the plan for the rest.

Day 3 — Assemble the evidence packs. One per curriculum area: sampling plan, IQA records in date order, observation records, standardisation evidence, previous action closure.

Day 4 — Check standardisation evidence specifically. Make sure it shows discussion and outcome, not just attendance. If recent standardisation was thin, a short written summary now of what was actually covered is better than nothing — but don't backdate it as something it wasn't.

Day 5 — Cross-check previous action points. For every action raised at the last visit, confirm there's evidence it was closed, not just remembered as closed.

Day 6 — Brief the team. Make sure assessors and IQAs involved know what's being sampled and can speak to their own records if asked directly — an EQA will sometimes talk to the assessor, not just review the paperwork.

Day 7 — Dry run. Pick one curriculum area and time how long it actually takes to produce the full evidence pack from a standing start. If it takes longer than ten minutes, that's the thing to fix before the next cycle, not before this visit.

How colleges running IQA Manager prepare for this differently

The colleges and training providers who find this least stressful aren't the ones scrambling less at the last minute — they're the ones who were never doing the scrambling in the first place, because EQA Evidence Packs are assembled continuously as IQA activity happens, not reconstructed the week before a visit. If you're running IQA across multiple curriculum areas, see what EQA visit readiness looks like built in. It's a question worth comparing against other options too — see how IQA software stacks up against a spreadsheet more broadly.

Practically, that means:

• Sampling plans and actual sampling activity live in the same system, so coverage gaps show up as they happen, not six months later.
• IQA records, standardisation evidence and previous action closures are already linked together, rather than living in separate folders that need reassembling.
• An EQA can be given direct, read-only access to the evidence for their visit, instead of receiving an evidence email chain assembled under time pressure.

None of this changes the judgements you make as an IQA — that's still down to professional expertise, not software. What changes is whether the evidence of those judgements is ready in ten minutes or two days.

IQA spreadsheet alternative · internal quality assurance spreadsheet template · IQA tracker software

IQA Manager vs Spreadsheets: What Actually Changes When You Switch

If you searched for an IQA spreadsheet template, you're not alone — it's how almost every IQA process in the UK starts. This article won't pretend that's a mistake. But if you're at the point of looking for a better template, the actual problem usually isn't the template. It's the spreadsheet.

Why almost every IQA team starts on spreadsheets

There's nothing wrong with starting here. When you're a small team, sampling a manageable number of learners across one or two awarding bodies, a spreadsheet is fast to set up, free, and familiar. Everyone can open it. Nobody needs training. For a single quality nominee running IQA across a handful of assessors, it genuinely works.

The problem isn't the starting point. It's that most teams never consciously decide to move on — the spreadsheet just keeps getting patched, tab by tab, until it's doing a job it was never designed for.

The exact moment spreadsheets stop working

There's rarely one dramatic failure. It's a gradual accumulation of small frictions that eventually add up to real risk:

• More assessors join, and now the sampling plan needs to track individual assessor risk ratings, not just unit coverage.
• More curriculum areas or awarding bodies come on board, each with slightly different sampling requirements, and the one master spreadsheet either forks into several inconsistent versions or becomes an unmanageable tab-per-area structure.
• An EQA visit or Ofsted deep dive lands with short notice, and someone spends two days reconstructing evidence that technically "exists" but isn't assembled anywhere.

None of these individually feels like a crisis. Together, they're the reason quality teams end up firefighting instead of doing IQA.

Five specific failure modes

These are the concrete ways spreadsheet-based IQA breaks down in practice, not abstract risks:

1. Version conflicts. Two people editing the same sampling plan, on a shared drive, without knowing the other has an unsaved change open. Whoever saves last wins — and nobody notices what was overwritten.
2. No audit trail. A cell changes. There's no record of who changed it, when, or why — which matters enormously when an EQA asks who made a specific judgement call and on what date.
3. Sampling coverage gaps nobody notices. The plan says every high-risk assessor gets sampled monthly. Nobody's actually checking whether that's still true six months in, because checking means manually cross-referencing multiple tabs.
4. Evidence scattered across personal drives. The spreadsheet tracks that sampling happened. The actual evidence — the marked work, the observation notes — lives wherever the assessor or IQA happened to save it. Reconstructing the link between the two, under time pressure, is where most pre-visit stress comes from.
5. Standardisation notes that live in someone's inbox. Standardisation happened, an email went round, and six months later nobody can produce it as evidence because it was never filed anywhere searchable.

Individually, these are inconvenient. Together, in front of an EQA, they read as a quality assurance process without a reliable audit trail — regardless of how sound the actual IQA judgements were.

What a dedicated platform actually replaces, module by module

This is usually the point people expect a hard sell. It's actually a fairly mechanical mapping:

• Sampling plans — the master tab that's usually the first thing to fork into inconsistent copies becomes one live plan, with risk ratings that update coverage automatically rather than needing manual cross-checking.
• IQA records — instead of a row in a spreadsheet referencing a file somewhere else, the record and the evidence sit together.
• Observations — tracked against the same sampling plan, rather than in a separate document nobody remembers to cross-reference.
• EQA evidence packs — assembled continuously as IQA activity happens, so there's no reconstruction exercise the week before a visit.
• Policies library — a single current version, rather than "final_v3_ACTUAL_final.docx" living in four different people's inboxes.

What doesn't change

This is worth being honest about, because it's easy to oversell software as replacing professional judgement — it doesn't. You still make the same IQA decisions: whether a piece of work meets the standard, whether an assessor's judgement is consistent, what risk rating a curriculum area deserves. A platform doesn't make any of those calls for you.

What changes is whether the evidence of those judgements is reliably captured, linked, and retrievable — instead of technically existing somewhere but taking two days to reassemble under pressure.

Migration reality check

Moving off a spreadsheet system is rarely the multi-month project people fear. The core work is:

• Importing or re-entering the current sampling plan and mapping existing risk ratings across
• Bringing across recent IQA records so there's continuity rather than a hard cutover with no history
• A short onboarding period where the team gets used to entering records directly rather than emailing evidence and someone else filing it

For a small-to-mid-sized centre, this is realistically a matter of weeks, not months — and it can be timed to start after a busy EQA period rather than during one.

Is it worth it at your size?

The honest answer: not always, not immediately. A single-team provider with a handful of assessors and low sampling volume may genuinely be fine on a well-organised spreadsheet for a while yet — see the note on this in Best IQA Software for FE Colleges in 2026 for where that line tends to sit.

But if any of the five failure modes above are already showing up — version conflicts, sampling gaps nobody's checking, evidence you'd struggle to produce inside ten minutes — that's usually the signal, regardless of centre size. IQA Manager's Starter, Standard and Plus tiers are priced by user count specifically so a small provider isn't paying college-scale fees to solve a college-scale problem they don't have.

If you're a college running IQA across multiple curriculum teams, the coverage and audit-trail problems tend to show up earliest and hardest — worth checking the homepage for what that looks like at scale.

Built by an active IQA practitioner, IQA Manager exists because the person who built it hit these exact five failure modes first-hand, not because a compliance vendor spotted a market gap.

Best IQA software for FE colleges · IQA software UK · internal quality assurance software further education

Best IQA Software for FE Colleges in 2026 (And When a Spreadsheet Still Wins)

If you're reading this, something has probably just happened: an EQA visit that went worse than it should have, a new academic year with more assessors than last year's spreadsheet was built for, or an Ofsted deep dive that made the gaps in your evidence trail uncomfortably visible. This is a look at what "IQA software" actually means, what to look for, and — importantly — when it's genuinely not worth switching yet.

What actually counts as "IQA software"

Worth being precise here, because the category gets muddied. Generic compliance or QA tools built for broad regulatory tracking aren't the same thing as software built specifically for the internal quality assurance cycle in a learning and skills context. IQA software, properly defined, needs to handle:

• Sampling plans tied to individual assessor and unit risk ratings, not generic task tracking
• IQA records that link directly to the assessment evidence being checked, not a separate reference to where that evidence lives
• Observations as a distinct, trackable activity within the sampling plan
• EQA evidence packs that can be assembled or accessed on demand, not reconstructed under pressure
• Awarding body-specific requirements, since sampling and evidence expectations differ meaningfully between, for example, City & Guilds and Pearson

A generic project-management or compliance tool can be bent into approximating some of this. None of it is what those tools were actually designed for.

What FE colleges should look for

At college scale, a few things matter more than they do for a small provider:

• Sampling at scale — coverage across multiple curriculum areas, dozens of assessors, and several awarding bodies simultaneously, without the plan itself becoming unmanageable.
• EQA evidence packs that can be handed to an external verifier directly, rather than assembled into an email chain under time pressure — see the pre-visit checklist for what "EQA-ready" actually needs to look like.
• Role-based access — an IQA coordinator, a curriculum-area IQA, and an external EQA all need different views of the same underlying data, not one shared spreadsheet with everyone's edits mixed together.
• A genuine audit trail — not just a version history, but a clear record of who made which judgement, when, against what evidence.
• Awarding-body coverage that actually matches your provision, rather than generic "compliance" fields that don't map to how City & Guilds or NCFE actually expect sampling to be evidenced.

The honest case for staying on spreadsheets

This is the part vendors usually skip, so it's worth saying plainly: if you're a small provider, one team, low sampling volume, and nobody's currently finding it difficult to produce evidence on request, a well-organised spreadsheet may genuinely still be the right tool. The switch isn't worth the time or cost until the coordination problem — multiple assessors, multiple curriculum areas, coverage nobody's actively checking — actually exists for you. For a longer look at exactly where that line tends to sit and the specific failure modes that signal you've crossed it, see IQA Manager vs Spreadsheets: What Actually Changes When You Switch.

Comparison: spreadsheets vs. repurposed project tools vs. purpose-built platforms

Spreadsheets and shared drives — free, familiar, fast to start. Break down as assessor count, curriculum areas, or awarding bodies multiply, because coverage checking and evidence linking become manual cross-referencing exercises. See the five specific failure modes in the piece linked above.

Repurposed project-management tools (Trello, Asana, and similar) — better at task tracking and deadlines than a spreadsheet, but built for generic workflow, not for sampling-plan logic, risk ratings, or awarding-body-specific evidence requirements. Usually ends up needing as much manual workaround as a spreadsheet, just with a nicer interface.

Purpose-built IQA platforms — designed around the actual sampling-plan-to-evidence-pack cycle from the outset. The trade-off is cost and a short onboarding period, against a genuinely lower risk of the coverage and audit-trail gaps that spreadsheets and generic tools both struggle with at scale.

Where IQA Manager fits

IQA Manager is a multi-role portal — coordinator, curriculum IQA, assessor and EQA views of the same live data — built by a practising IQA, not a generic compliance vendor entering the sector. It's built for college-scale sampling as much as for a single-centre training provider. Pricing is published outright: Starter, Standard and Plus tiers by user count, no VAT (EdTech Assurance isn't VAT-registered), and no "book a demo to see pricing" gate — unusual in this category, where most comparable tools keep pricing behind a sales conversation. There's a live, no-signup demo rather than a scripted sales walkthrough, and coverage across 13 built-in awarding bodies including City & Guilds, Pearson, NCFE, TQUK, CACHE, VTCT, Focus Awards, BIIAB, Qualsafe, CMI, ILM, Agored Cymru and IMI Awards.

Questions to ask any vendor before you buy

Whichever platform you're evaluating — IQA Manager included — these are worth asking directly:

1. Where is our data actually held, and does that meet our data residency requirements?
2. What does the audit trail actually capture — every field change, or just a version number?
3. How does an external EQA get access — a proper read-only role, or a workaround involving exports and email?
4. Is pricing published, or gated behind a sales call? If it's gated, ask why directly.
5. What's the actual contract length and exit process — can you get your data out cleanly if you leave?

If a vendor won't answer the pricing and data-export questions plainly, that's informative in itself.

Verdict / decision checklist

Before switching from a spreadsheet, check:

• Are you regularly finding sampling coverage gaps only when someone happens to check, rather than being flagged automatically?
• Has a version conflict or missing audit trail entry caused a real problem at an EQA visit or Ofsted deep dive in the last year?
• Would producing a full evidence pack for one curriculum area, right now, take longer than ten minutes?
• Are you managing more than one awarding body's sampling requirements in the same spreadsheet?

Two or more "yes" answers is usually the point where the switch pays for itself well within a year, not just in stress avoided but in evidence you can actually stand behind when it's checked.