Here's a scene you've probably lived. It's Tuesday morning, the mason's crew is staged up to run scaffold on the north elevation, and the competent person who's supposed to sign off on that scaffold called in sick. His backup's card expired last month and nobody caught it. So now you've got a five-man crew standing around at $60-plus a head, burning a morning, because a single certification lapsed and lived only in a manila folder in somebody's truck.
Training and certification tracking is the kind of thing that never shows up on a schedule until it stops the schedule. It's invisible right up until an inspector asks for the aerial-lift card, the GC's safety guy pulls a random audit, or a worker gets hurt doing a task he was never qualified to do. This article is about how you keep that from happening — the actual mechanics of tracking who's qualified for what, and how tying training to your look-ahead turns it from a paperwork chore into a live part of how you plan work.
Why the manila folder fails
Most jobs still manage competency the same way: a binder in the trailer, a shared spreadsheet somebody updates when they remember, and the foreman's memory. That works until the workforce moves. On a multi-family or commercial job, your headcount can swing from 40 to 200 and back down again over the course of a year, and a big chunk of those bodies are subs' guys you've never met. The binder can't keep up with that churn, and the spreadsheet is only as current as the last time someone bothered to open it.
The failure mode is always the same. Nobody knows a certification is expiring until it's already expired — usually the morning you need it. The fix isn't more diligence from an already-buried super. It's making the data live somewhere that surfaces problems before they hit the field, and connecting that data to the schedule so the right question gets asked while there's still time to answer it.
Build the requirement matrix first
Before any software helps you, you need to know what each activity actually requires. This is a one-time exercise that pays off for the life of the project. Walk your scope and, activity by activity, write down the competencies gate it:
- Site-wide baseline — OSHA 10 for laborers, OSHA 30 for foremen and supers, plus your project's site-specific orientation. Nobody past the gate without it.
- Equipment operation — aerial/scissor lift (the ANSI A92 standard changed the game here, so verify it's current training, not a 2015 card), forklift/telehandler, crane operator certification, rigging and signal person qualification.
- High-hazard tasks — scaffold competent person, confined space entry and attendant, fall-protection competent person, trenching/excavation competent person, hot-work and fire-watch, silica-exposure competent person for anyone cutting concrete or masonry.
- Trade licenses and certs — welder qualifications tied to a specific procedure (a 6G cert doesn't cover every joint), journeyman/master electrical, backflow, and any state-specific licensing your work touches.
Notice something: most of these attach to a task, not a person's job title. A guy can be a great carpenter and still not be your scaffold competent person. The matrix forces you to separate "who's here" from "who's qualified for this specific work," and that distinction is exactly what keeps you out of trouble.
Track the expiration date, not just the card
The single most useful piece of data you can hold isn't whether someone has a certification — it's when it dies. Cards expire on wildly different cycles. OSHA course completion doesn't technically expire but many owners and GCs treat it as five-year, aerial-lift retraining runs on a three-year cycle, first aid/CPR is typically two years, and crane operator certifications and welder qualifications have their own clocks (a welder qual can lapse if the procedure sits unused past six months, depending on the code).
What you want is a rolling view of what's expiring in the next 30, 60, and 90 days. Ninety days out is your comfortable window — plenty of time to book a class or a testing appointment. Sixty is when it should be scheduled. Thirty days out and still open means it's now a real risk to the work. If you're managing this by hand, put a recurring calendar reminder to review the expiration list every Monday. If you're using field management or scheduling software that stores these dates, the tool should be throwing the flag at you, not waiting for you to go look.
Treat missing training as a constraint — because it is
This is where scheduling and competency tracking actually connect, and it's the part most people miss. In short-interval and look-ahead planning, a constraint is anything that has to be true before an activity can start: material on site, prior work complete, permit in hand, inspection passed. A missing certification is a constraint in exactly the same way. If Thursday's task needs a certified operator and you don't have one lined up, that task is not ready to be committed — full stop.
The whole point of pulling work into a three- to six-week look-ahead is to see problems early enough to solve them. Training is one of the constraints that benefits most from lead time, because you usually can't fix it same-day. You can expedite a material delivery. You cannot conjure a scaffold class the morning you need it. So when you're screening the activities coming into your window, "is everyone who touches this qualified, and are their cards current through the work?" belongs on the checklist next to material and access.
A good look-ahead tool like LookAheadWall makes this natural because you're already laying out the coming weeks by location and trade flow. When you can see that the lift work on Level 3 lands in two weeks, the question "do we have a current operator for it?" surfaces while there's still runway to send someone to training or bring in a qualified body. The schedule becomes the thing that asks the question at the right moment, instead of the field asking it too late.
The gotchas that actually bite you
A few things go wrong over and over, regardless of how you're tracking:
- The backup nobody verified. You confirm your primary competent person is current and stop there. Then he takes a Friday off and the whole task stalls. Every gating role needs at least two qualified bodies, and both cards need to be live.
- Subs who self-certify verbally. "Yeah, all my guys are trained" is not documentation. If it isn't on paper — card, roster, or upload — it doesn't exist when the inspector or the injury lawyer asks. Collect the actual records at onboarding and make it a condition of gate access.
- Orientation that lags the ramp-up. When a sub surges 20 new bodies to hit a milestone, orientation becomes the bottleneck. If your look-ahead shows the manpower spike coming, you can schedule the orientation sessions ahead of it instead of doing them in a chaotic Monday-morning huddle while the clock runs.
- The card that expires mid-task. A cert current on the start date but expiring three days into a two-week pour is a problem you created by only checking the start date. Verify coverage through the duration of the work.
- Stale course versions. When a standard changes — as the aerial-lift rules did — an old completion card may no longer satisfy the requirement. "He has a card" isn't the same as "he has the current card."
A weekly rhythm that keeps you honest
Systems only work if there's a cadence behind them. Here's a rhythm that holds up on a busy job:
- Onboarding: No badge without documented orientation plus whatever certs the person's role requires. Capture expiration dates at intake, not later.
- Weekly look-ahead review: When you screen next week's committed work and the weeks behind it, run every activity against the requirement matrix. Any gap becomes a tracked constraint with a name and a date attached.
- Monday expiration sweep: Review everything expiring in the next 90 days. Anything inside 60 gets a class or test booked. Anything inside 30 that's still open gets escalated as a live risk to the work it gates.
- Task assignment check: Before a foreman assigns a gated task, the answer to "is this person qualified and current?" is a yes you can point to, not a shrug.
None of this requires heroics. It requires that the information lives somewhere current and that it gets looked at on a schedule. That's the whole trick.
Where the software earns its keep
Software doesn't replace judgment here — it replaces the manila folder and the failing memory. The value is boring and enormous: one current record of who's qualified for what, expiration dates that raise their hand before they lapse, documentation you can produce in ten seconds when an inspector asks, and a link between those competencies and the work you're about to commit.
That last link is the one worth chasing. Tracking certifications in isolation is just tidier paperwork. Tying them into your weekly work plan and look-ahead is what changes outcomes, because it puts the qualification question in front of you at the moment you're deciding whether a task is truly ready to go. When your planning surface and your competency data talk to each other, "we don't have a current operator" shows up two weeks out as a solvable problem — not Tuesday morning, with a crew standing around and the day already gone.
Do the matrix once. Capture the expiration dates. Screen training as a constraint in every look-ahead. Sweep the expiring list every Monday. Do those four things consistently and the whole category quietly stops being something that bites you — which, on a jobsite, is about the highest praise a system can earn.