The Work That Cannot Be Missed
Mitzi Orkus
The Work That Cannot Be Missed
8:39
Authored by Mitzi Orkus, Director of Strategic Growth, KAStrack
One of our clients, an industrial contractor, had a person who kept impeccable training records for the whole staff. The records were open to the people who needed them, but the system was his own, and nobody else could read it. Then a Fortune 50 company the contractor does work for showed up for a surprise audit, and he was out.
The audit didn't go well. The training had happened, the documentation existed, and the right people could open it. But his colleagues couldn't interpret his system, and neither could the auditors. Afterward the client had to turn in a large volume of paperwork to show that everything had been identified and documented properly and to satisfy the contract.
That one stays with me because nobody was careless. The work got done, and someone kept excellent records. What the contractor lacked was records anyone else could read, and that audit is what led them to start using KAStrack.
Most operations have work like this, work that can't be missed: inspections before equipment goes back into service, certifications that have to stay current, corrective actions that have to be verified. It doesn't bring in revenue, but when it slips, the operation can stop. Spread it across several sites, supervisors, and crews, and leaders need to know it's happening, that the records match what actually happened, and that someone will notice when something falls through. Another checklist doesn't answer that.
When the process doesn't grow with the operation
The process that worked when a company was smaller often stays the same while the operation doesn't. A supervisor who handled inspections, certifications, and follow-ups for one site ends up responsible for several, and the system still runs on what a few people remember. One knows which inspections are due. Another keeps the certification spreadsheet. A third chases corrective actions.
When any of them leaves or changes roles, the gap shows up in the work, usually at a bad time. The contractor's records manager was the extreme version: excellent at the job, and the only one who could make sense of his own system. Individual diligence carries an operation a long way, but it can't be handed off.
Doing the work and proving it
Two problems look identical in an executive report. In one, the work wasn't done: an inspection was missed, or a corrective action sat open because nobody followed through. In the other, the work was done and the organization can't show it. The inspection happened but the record never got submitted. A supervisor verified a repair in the field and the evidence stayed in an email. The contractor's audit was this second kind.
The fixes are different. A missed inspection points to scheduling, ownership, and escalation. A completed inspection nobody can document points to how the record gets captured and where it goes, and more reminders won't help. Then there's the record that says complete with no evidence behind it, which leaves leadership guessing what the status means.
A missing record doesn't prove the work wasn't done, and a completed record doesn't prove it was done correctly. So I ask both questions: is the work happening, and can the organization show it?
What has to be in place
Consistent execution needs four things. Someone defines what's required and where it applies. The person responsible knows the work is theirs and has what they need to do it. Completion gets captured, with evidence when the work calls for it. And someone finds out when an item is overdue or waiting for review. None of that is hard to describe. Keeping it going across locations and recurring schedules is where it breaks.
A certification shows how. The renewal requirements are documented and a spreadsheet shows the expiration date, but nobody is assigned to start the renewal, nobody is notified when it's due, and nobody confirms the employee is still qualified for the assignment on the calendar. The organization is keeping a record of the requirement without managing it.
Making the Work Visible and Assured
“When work that cannot be missed isn’t prioritized and built into everyday operations, people end up spending extra time catching up and chasing paperwork, especially when an audit or inspection is coming. That work should be part of how the operation runs, not a separate effort people scramble to reconstruct later.
KAStrack helps organize that work so the operation can keep its attention on the work itself instead of using extra resources to prepare for an audit. The assurance comes from making the required tasks clear, easy to complete, and visible to leadership.
Frontline crews often have competing priorities. They know the job has to get done, and they also have a responsibility to do it safely. When leadership supports them with the right planning, certifications, and equipment readiness, crews are better positioned to complete the job without avoidable accidents or setbacks. Safety and compliance are not separate from getting the work done. Done well and done safely are not a tradeoff. They are the same. KAStrack makes that visible.
That is one reason KAStrack is built around configurable modules rather than a single pre-packaged setup. Each module can be configured to the customer’s workflow. It takes more effort from our back office to get that configuration right, but the payoff is a system that fits the organization and can be adopted by the frontline. A system that people use is more valuable than one that only looks complete in a demo.
There are many regulations and company requirements that define work that must be done. Often, the task has been completed, but the complexity of showing that completion leaves leadership without assurance. KAStrack is designed to make it easier for frontline teams to complete and record the work, while giving leaders reports and oversight across the operation. The goal is not simply to do the work. It is to make completion clear and dependable.”
Robert Claypool, Founder, KAStrack
What changes for leadership
When required work is tied to named owners, schedules, and records, managers spend less time working out what happened. An operations leader can review what's overdue and what needs approval instead of calling site managers. A compliance leader finds missing documentation while there's still time to fix it. A training manager sees certifications coming up for expiration before the employee is unavailable. Follow-up and judgment still fall to managers. They just have the time to use them.
Try this on your own operation. Could you name the inspections due this week, the certifications expiring next month, and the corrective actions waiting for review, across every location, without asking supervisors for reports? And for the items showing complete, could you say what evidence backs the status? If getting those answers takes several spreadsheets, a few phone calls, and a search through old email, the organization is relying on effort where it needs a process.
Where to start
You don't need every location to operate identically or every task to go through the same approval. You do need clear owners, a way to capture completion, and reliable information about what's done and what isn't.
At KAStrack, we start by learning how your organization manages the work that can't be missed, where responsibility sits, and what leadership needs to see. A Needs Assessment shows where responsibilities, records, or follow-up have become disconnected. If your team spends too much time chasing work that should already be visible, start there.
Have a question about this? Email Mitzi directly at morkus@kastrack.com.
About the author: Mitzi Orkus, a petroleum engineer turned growth strategist, is the Director of Strategic Growth at KAStrack. Before joining the company, she was a client for six years, using KAStrack to improve the way she ran her own business. Today, she helps other organizations move from chasing proof to producing it as part of how work is done.
Read the earlier articles in this series:
