Guide · Updated 2026-10-02
How to Keep a Gap Log with Your Training Matrix
A gap log turns red cells into owned actions. List each missing or expired requirement with a person responsible and a target date. Close the line only when the matrix evidence is updated — not when someone “said they’d book it”.
Quick answer
Run a short open-actions list (sheet tab, tracker or software tasks) filtered from matrix gaps. Review it in the same meeting as Monday mobilisation. Archive closed gaps with the date evidence landed.
Minimum gap-log fields
| Field | Purpose |
|---|---|
| Worker | Who is blocked |
| Requirement | What is missing or expired |
| Risk / site impact | Why it matters this week |
| Owner | Who chases training or evidence |
| Target date | When it must close |
| Status | Open / booked / closed |
Cadence
- Filter the matrix for missing and expired on a fixed day.
- Add new gaps to the log; do not rely on memory.
- Chase owners mid-week.
- Close only after the matrix date and file are updated.
- Prioritise names on near-term packages first
- Separate “booked” from “closed”
- Keep the log short — dump noise into archive
Honest limits
FieldClear surfaces gaps from assigned requirements and dates. A gap log is your management process around that view. The tool does not close commercial or competence decisions for you. Not legal advice.
Already have a spreadsheet?
Upload your existing matrix and see who’s current, what’s expiring and what’s missing.
14-day free trial. No card required.