Training Records vs Competence

Training Records Answer

• Who attended which session, and when
• What curriculum or topic was covered
• Expiry or refresh dates where required
• Trainer or provider identity

Competence Answers

• Can this person do this task, on this equipment, in these conditions?
• What evidence shows that (assessment, observed task, supervised hours)?
• Who authorised them, and when should they be reassessed?
• What happens if they fail or the process changes?

A Simple Verification Loop

1. Define the task and the standard (what “good” looks like).
2. Train or brief to that standard.
3. Assess — written, practical, or observed performance.
4. Authorise — only then assign unsupervised work where required.
5. Refresh — after time, incidents, or MOC that changes the task.

Supervisor Checklist

Task Matrices

training records vs competence guide works only when ownership is visible and routines are boringly consistent. Write who does what by weekday, not only in emergencies. When the process depends on heroics, it will fail on a quiet Tuesday.

Use real examples from your site when training. Abstract principles do not survive shift handover. Keep records short enough that people complete them under time pressure without inventing fiction.

Leaders should sample quality monthly and ask what would break if a key person were absent for two weeks. Absence is a predictable stress test.

Assessment Methods

Field verification beats desk approval. Walk the job, watch the interface, and listen for workarounds. Workarounds are data about process friction — fix the friction rather than only punishing the workaround.

When findings repeat, escalate from local fixes to system fixes. Repeating the same corrective action wording without addressing capacity, design, or scheduling is how chronic issues age into incidents.

Share lessons across shifts and sister sites in plain language within a week, while context is fresh.

Authorisation Gates

Close the loop with dates, owners, and verification. Open actions without verification are wishes. Build a habit of showing evidence: photo, signature, measurement, or witnessed retest as applicable to the finding.

Retire obsolete controls and documents so people are not obeying ghosts. Confusion between old and new expectations is itself a hazard.

Finally, measure a few leading indicators that match this process and review them without blame theatre. Learning cultures still keep standards; they simply refuse to hide bad news.

Putting This Into Practice on a Real Site

Start where risk and friction are highest, not where paperwork is easiest. Choose one area, one crew, or one job type and run the process properly for thirty days. During the pilot, capture every point of confusion: unclear ownership, missing inputs, forms that take too long, and steps people skip under time pressure. Those friction points are design requirements for the next revision.

Train with stories from your own workplace rather than generic slides alone. Walk the physical locations where controls must appear. Ask new supervisors to explain the process back to you in their own words before they authorise live work. If they cannot explain it simply, the process is not yet ready for unsupervised use.

Build a weekly fifteen-minute review: what was opened, what closed, what blocked progress, and what nearly went wrong. Keep the conversation factual and free of humiliation. The goal is faster learning, not theatre. Escalate chronic blockers to someone who can change resources, scheduling, or design — local owners cannot fix capacity problems with better handwriting.

Define what “good” looks like with three to five leading indicators that match this process. Examples include on-time close-out, percentage of jobs with a completed walk-down where required, reopen rate after near misses, and sample quality scores from leadership walkarounds. Review indicators without turning them into a blame scoreboard. If numbers improve while field reality worsens, your measures are wrong.

After ninety days, decide deliberately: standardise, adjust, or stop. Write the minimum standard on a single page so contractors and new starters can follow it. Keep deeper annexes available without forcing every user through every detail every time. Consistency across shifts matters more than ornamental complexity.

Finally, connect this process to its neighbours. Change control should reopen risk assessments. Permits should reflect real isolations. Emergency plans should match headcount methods. Incident learning should update procedures and briefings. A strong site is a network of simple processes that talk to each other, not a collection of isolated campaigns that fade after the launch poster comes down.

Supervision, Handover, and Fatigue

Many failures occur at boundaries: shift handover, crew change, contractor swap, or the moment a temporary control is left “for the next person.” Write handover expectations into the process. What must be said out loud? What must be shown in the field? What must be signed or logged before responsibility transfers?

Fatigue and unfamiliarity deserve explicit attention. If a control only works when people are fresh and experienced, it will fail during overtime, shutdowns, and peak seasons. Consider additional checks, simpler steps, or staffing rules when those conditions are present. Do not rely on slogans about staying alert as the primary control.

Supervisors need time and skill to verify, not only to sign. If the schedule assumes zero verification time, the organisation has designed verification out of existence. Protect a small amount of time for walks, sampling, and coaching — it is cheaper than investigation after harm.

Minimum Standard Checklist

Write a one-page minimum standard that answers four questions: when is this process required, who can authorise or approve, what must be recorded before work proceeds, and how is completion verified. Keep the page visible to supervisors and contractors.

Anything beyond the minimum belongs in annexes for specialists. Most users should succeed with the one-pager plus a short field walk. If people need a full day of classroom training before they can start a simple job gate, the design is too heavy for daily use.

Revisit the one-pager after each serious near miss related to the process. If the event revealed ambiguity, fix the wording while memory is fresh. Stable standards still improve; they simply improve on purpose.