HAWKEYE SYSTEMS

Training Compliance Tracking for Field Crews: What to Record

How to track training compliance for field crews: which records to keep, what US rules require, how to catch expirations by site, and what software must do.

Plan a walkthrough

Training compliance tracking means knowing, at any moment and for every worker, which training they need, which they have finished, and which is about to lapse, with a record you can hand to an inspector. For crews spread across job sites, the hard part is not assigning courses. It is keeping completion records, certification dates and site assignments in one place so that a supervisor can answer a simple question before a crew mobilizes: is everyone on this job cleared to be here?

This guide covers what to record, what US rules say about those records, how to track by role and site, and what to demand from software.

Hefieldops

Connect Training Status to Fieldwork

Hefieldops connects field activity with office management, helping construction teams document site work and review field records more efficiently.

Visit Hefieldops

TL;DR

Track three things together: training completions, certifications with expiry dates, and evidence of competency. Each needs a name, a date, a trainer or issuer and proof.
Federal and state rules set the minimum record content for specific topics, and they differ. OSHA’s construction confined-space rule, for example, requires employee names, trainers’ names and training dates.
Tie requirements to role, site and job, not to a single company-wide course list, so that the right people are flagged at the right time.
Choose software that keeps change history, sends renewal alerts, and connects training status to crew scheduling and field records.
Start small: one high-risk training category, one clean register, one weekly review.

What training compliance tracking actually covers
The records worth keeping for every training event
What US rules say about training records
When crews work in more than one country
How tracking works across roles, sites and projects
Why spreadsheets fail on a job site
What to look for in training tracking software
Our perspective: training status belongs in the same record as the work
How Hawkeye Workforce Readiness fits
A 30-day plan to get a clean register
FAQ
Sources

What training compliance tracking actually covers

There is a difference between knowing that someone clicked through a course and being able to show that the right person completed the right training by the required date. The first is activity. The second is compliance. An auditor, an insurer or a safety officer after an incident asks for the second.

In practice, tracking covers three kinds of data that many companies keep in separate places:

Training completions: safety orientations, toolbox talks, equipment instruction, hazard communication, and company policy courses.
Certifications and licenses: operator cards, crane or lift credentials, first aid, confined-space entry, and anything issued by an outside body with an expiry date.
Competency evidence: a supervisor’s sign-off, a practical assessment, a test result, or a record that a worker was observed doing the task correctly.

When these live in a binder, a payroll folder and a supervisor’s phone, nobody sees the whole picture. The goal of tracking is one view where a manager can filter by person, crew, site or requirement and see who is current, who is expiring and who has lapsed.

Tracking also has limits. It does not replace training quality, and it is not employee monitoring. A record that says a worker finished a course tells you nothing about whether they understood it, which is why assessments and practical sign-offs belong in the record too.

The records worth keeping for every training event

The safest habit is to capture more than the minimum, in a consistent format, from the first day. A good record answers five questions: who, what, when, under which requirement, and with what proof.

Field | What to capture | Why it matters

Worker | Full name and a unique ID | Prevents mix-ups between workers with similar names

Training or credential | Exact course or credential name and version | Shows which standard or revision the worker met

Date | Completion date, and expiry or next-due date | Drives renewal alerts and overdue lists

Trainer or issuer | Trainer’s name, or issuing organization | Required by several regulations and needed to verify authenticity

Proof | Certificate, signed roster, test score or sign-off | Turns a claim into evidence

Scope | Equipment, task, site or role the training covers | A forklift card does not cover a boom lift

Review | Who verified the record, how, and when | Shows the entry was checked, not just typed

If a credential has restrictions, such as a limit on equipment type, record them. A card that looks valid but covers a different machine is one of the most common gaps a supervisor finds only after the work has started.

What US rules say about training records

There is no single federal rule for training records. Requirements attach to specific topics, and each states what the record must contain. These examples show how varied they are.

Construction confined spaces. OSHA’s rule at 29 CFR 1926.1207 requires employers to keep records showing that required training was accomplished. The records must contain each employee’s name, the trainers’ names and the training dates, and the training must establish that the employee is proficient in the duties assigned.

Hazardous materials. In Interpretation 10-0170, dated December 6, 2010, PHMSA said hazmat employee records must include the employee’s name, most recent training completion date, a description, copy or location of the training materials, the trainer’s name and address, and certification that the employee was trained and tested. The same interpretation says the rule does not require keeping the exam or score itself, though keeping it is still sensible if you want to show understanding.

Aerial work platforms in California. Under Title 8, Section 3298, employers must certify that employees were trained to operate and inspect a working platform. The record carries the trained person’s identity, the employer’s or trainer’s signature and the completion date, and it is kept for the duration of employment.

Washington State. For the program it covers, WAC 296-823-12015 requires training records to be kept for three years. They must include training dates, contents or a summary, trainers’ names and qualifications, and attendees’ names and job titles. That is a state rule for a specific program, not a national standard.

Federal records schedules. The National Archives’ General Records Schedule 2.6, updated May 2024, lists employee training records such as completion certificates, rosters of required attendees, training plans and course materials, with retention instructions that vary by category. It governs federal agencies, but it is a useful picture of which documents count as training records.

The pattern is clear. Names, dates and trainers appear in nearly every rule. Retention periods, signature requirements and the level of detail change by topic and by state. Check the rule for each topic you train on, and when in doubt ask your safety consultant or counsel which retention period applies to you.

When crews work in more than one country

If you operate outside the US, record-keeping duties change. A few examples from official sources show how much:

In the United Kingdom, CITB’s Requirements for Approved Training Organisations, April 2024 edition, calls for a reliable, auditable system of training, testing and assessment records kept for at least three years.
In South Africa, the Department of Employment and Labour’s 2024 code for lifting machinery operator training providers requires accredited providers to keep learner records for a minimum of five years.
In Taiwan, training units must keep implementation data such as plans, course content, rosters and attendance records for three years under the Occupational Safety and Health Education and Training Rules.

Note that several of these apply to training providers rather than to the employers who send workers to them. The practical lesson is to store records in a system where retention can be set per requirement and per jurisdiction, instead of one blanket period.

How tracking works across roles, sites and projects

A flat list of courses that everyone must take produces noise. Field work needs requirements that depend on context.

By role. An equipment operator, a flagger, a foreman and an estimator need different things. Define a requirement set per role, and attach it when a person is hired or promoted.

By site. A refinery turnaround, a utility right-of-way and a downtown high-rise each carry their own orientations and permits. When a site adds a requirement, everyone assigned there should see the gap right away.

By task. Work in a trench, on a lift or in a confined space triggers specific training. The cleanest approach is to link the requirement to the job or work order, so that scheduling a crew to that task checks their status first.

By change. New hires, role changes, transfers between sites and contractors joining a job all create gaps. Offboarding matters too: a departing worker’s access and records should be closed out deliberately.

Whatever the structure, each person’s status should resolve to one of four states: not started, in progress, current, or overdue, plus an expiring-soon flag with a lead time that fits the credential. A 30-day warning is fine for a course you can finish in an hour. A certification that needs a scheduled exam or a seat in a class needs far more notice.

Why spreadsheets fail on a job site

A spreadsheet works for a crew of ten in one yard. It starts to fail when:

The person who maintains it is not the person who sees the site. Supervisors learn a worker’s card expired when an inspector asks, not when the date passes.
Corrections overwrite history. If someone changes a date, nothing shows who changed it or why.
Evidence lives elsewhere. The cell says current, and the certificate is in a truck, a text thread or nowhere.
It does not talk to scheduling. Nothing stops a lapsed worker from being put on tomorrow’s crew.
It cannot answer by site. Pulling every credential for one project means filtering several tabs by hand.

None of this means abandoning simple tools on day one. It means knowing which failure you are living with and what it costs when a record is missing at the wrong moment.

What to look for in training tracking software

Whether you are comparing platforms or building requirements for a pilot, test them against the way field work actually happens.

One live view. Training completions, certifications and competency evidence should be filterable by person, crew, site and requirement.
Requirement rules. Assignments by role, location, hire date and expiry, not only manual enrollment.
Alerts and escalation. Configurable reminders by role and lead time, and escalation to a supervisor when a deadline passes.
Evidence and history. Attached proof, verification status, and an audit trail that shows who changed a record and when. Software that only displays a green check is a liability the day someone asks how you know.
Exports auditors accept. Reports for a worker, a site or a requirement in a format you can hand over.
Field access. Supervisors need status on a phone, at the gate or in the truck, not only at a desk.
Connection to the work. Training status should feed scheduling and crew assignment, and field records should reference it. If training data sits in a separate tool, someone has to reconcile it by hand.
Access controls. Workers, supervisors and administrators should see only what their role needs.

A practical test during a demo: pick a worker with an expiring card, a site with a new requirement and an inspector’s request for last quarter’s records. Ask the vendor to walk each case live.

Our perspective: training status belongs in the same record as the work

We build field operations software, and the pattern we see most is this: training lives in one system, scheduling in another, and the daily record of who actually did the work in a third. Each handoff is a place where a gap can hide. A worker can be scheduled onto a task they are not cleared for, and nobody finds out until the paperwork is reviewed, if then.

Our view is that readiness should be part of the same connected record that runs from assignment through billing. When a foreman builds a crew, the question of who is qualified should be answered at that moment. When the daily record is filed, it should show who was on site and what they did. When the office reviews it, each handoff should be clear and traceable. That is what we mean by an audit-ready record: not a folder assembled in a panic, but a trail created as the work happens.

We also think compliance is not a checkbox. Assignment, deadlines, evidence, exceptions and retraining all keep moving as crews change. A tracking process that treats completion as a single event will always be behind.

— Client

How Hawkeye Workforce Readiness fits

If your crews are the reason tracking is hard, Hawkeye Workforce Readiness is built for that case. It brings workforce learning and readiness tracking into the same platform as crew scheduling, labor and equipment tracking, and daily work records, so training status is not a separate system to reconcile. Construction teams can see how it connects to the rest of the field workflow on our construction page, and a product walkthrough is the best way to test it against your own requirements.

A 30-day plan to get a clean register

You do not need to track everything at once. This sequence works for most contractors and field service firms.

Week 1: pick the scope. Choose the highest-risk training category, for example the credentials that gate access to your most hazardous task. List the people and sites it touches.
Week 1: define the record. Use the field table above. Decide who owns each field and where proof is stored.
Week 2: load what exists. Gather certificates, rosters and sign-offs. Mark each entry verified or unverified, and list what is missing.
Week 3: set alert rules. Set lead times by credential type and a named person who gets each escalation.
Week 3: link to scheduling. Decide the rule: no assignment to a task without current status, and who may grant a documented exception.
Week 4: review weekly. Hold a fifteen-minute review of expiring and overdue items per site. Add the next training category only when this one runs cleanly.

The same discipline helps elsewhere in the field record. Labor hours feed payroll, so see our guide to construction labor tracking. Daily records are where site attendance is proven, so a daily construction report built on mobile templates closes the loop. If you work on public projects, field records also support certified payroll reporting.

FAQ

What does compliance tracking mean for employee training?

It is the systematic monitoring of training so you can show that required people completed required training by the required date. It goes beyond activity such as logins. The output is a record, with names, dates, trainers and proof, that stands up to an auditor or inspector.

What employee training records should I keep?

At a minimum, keep the worker’s name, the training or credential, the completion and expiry dates, the trainer or issuer, and proof such as a certificate or signed roster. Specific rules add detail. OSHA’s construction confined-space rule, for instance, requires names, trainers’ names and dates, and some states add signatures or retention periods.

How long do I have to keep training records?

It depends on the topic and the jurisdiction. Washington’s WAC 296-823-12015 sets three years for the program it covers, and California’s aerial platform rule keeps the record for the duration of employment. Check the rule for each training topic, and ask your safety consultant or attorney if you are unsure.

How can I track training across remote job sites?

Assign requirements by role, site and task, and review status by site on a regular schedule. Use alerts with lead times matched to each credential, and give supervisors mobile access to status. Linking training status to crew scheduling prevents a lapsed worker from being assigned in the first place.

What should training tracking software include?

Look for one filterable view of training, certifications and competency evidence, rule-based assignments, configurable alerts and escalation, attached evidence with change history, and exportable reports. For field teams, add mobile access and a connection to scheduling and daily records.

Sources

See your operations in action.

Walk through the handoffs that slow your team down—and see where a connected record can help.