What to Do When a Client Rejects Your Training Matrix

Find out what was actually rejected

Ask for the rejection in writing: population expected, requirements in scope, file format, and examples of failing rows. Some clients want supervisors only; others want every person on next week’s programme; others want evidence files rather than a spreadsheet. Do not rebuild everything until you know which failure modes they hit. If the rejection is verbal, confirm it by email so your revision addresses the same points.

Recovery checklist

• Original request wording pasted into the revision cover note
• Population re-agreed (project, dates, employers included)
• Expired, missing and not-required statuses made explicit
• Illegible or mismatched evidence replaced
• Subcontract employer names shown where the client asked for supply-chain visibility
• Personal data minimised to what the client needs
• Version number and ISO date on the reissued pack

Step-by-step reissue

Treat the response like a controlled document change, not a frantic overwrite of a shared link.

1. Log the rejection reason and owner internally.
2. Filter the live matrix to the agreed population and requirement set.
3. Close or document gaps the client called out; do not hide them with colour alone.
4. Export a fresh snapshot and attach evidence in the format requested.
5. Spot-check the previously failing rows plus five random others.
6. Send the revision with a short change note and archive the identical pack.

Prevent the next rejection

Recurring rejections often mean your live data is fine but your export discipline is not—or the reverse. Run a dry-run client pack quarterly. Standardise requirement names so “CSCS skilled” and “skilled worker card” do not appear as different columns across projects. Brief commercial teams not to promise matrix formats you cannot produce. When a principal contractor issues a template, map your fields to theirs once and keep the mapping with the project file.

If the client rejects because they wanted competence assessments rather than training dates, say so clearly and supply the correct artefact from document control. Do not relabel training RAG as competence to smooth the conversation. Where accreditation evidence was expected alongside workforce extracts, send both with distinct labels. After acceptance, keep the live matrix aligned so mobilisation does not contradict the pack that cleared prequalification.

Scope of any reissue

FieldClear helps you organise and export assigned training evidence. A clean revision does not guarantee client acceptance, accreditation or legal compliance. This guide is not legal advice.