What you can prove a contractor actually did

For a lot of operations, the honest answer is "not much". The visit was taken on trust. The paperwork, if it exists, is an email attachment or a signed sheet in a drawer. The proof that the contractor was competent to do the work, that the right controls were in place before they started, and that the job was finished properly before they left, is scattered or simply absent. The work was probably fine. But "probably" is a weak position to be in when something goes wrong, or when an auditor asks you to demonstrate control of the people working on your site.

This is a visibility gap with real exposure attached. When a contractor works on your assets, your responsibility doesn't leave the building with them. Clients and contractors both have responsibilities, as HSE's guidance on using contractors sets out: the contractor for doing the work safely, and you for choosing a competent contractor, agreeing the controls and managing the work on your site. If the controls weren't in place, or can't be shown to have been in place, that's still yours to answer for. And the moment to capture that proof is at the time of the work, not three months later when you're trying to reconstruct who did what from a thread of emails.

Key takeaways

• Clients and contractors both have responsibilities, and yours doesn't end when the contractor leaves site, so the evidence of what they did matters.
• The time to capture proof of a contractor visit is while the work happens, not months later from a thread of emails.
• Apply permits where the work and site procedures require them; assess competence, agree controls, supervise appropriately and verify handback. In ocapii, any required permit and RAMS sign-off are completed before work starts, so controls are evidenced up front rather than assumed.
• Evidence of the work is captured on site by photo and record before the contractor leaves, and held against the asset they worked on. It supports your checks; it doesn't replace them.
• Keeping the permit, controls and completed job together against the asset gives the next engineer, manager or auditor the full history.

ocapii captures the whole visit as a connected record. Where the work and your site procedures call for a permit-to-work, the permit and RAMS sign-off are completed before work starts, so the controls are agreed and evidenced up front rather than assumed. Evidence of the work is captured on site, by photo and record, before the contractor leaves, and held against the asset they worked on. The certificate, the permit, the sign-off and the completed job all sit together, against the right asset, in one view, instead of living in four different places and one person's memory. A photo or a signature isn't proof of competence or of safe execution on its own: you still need to assess competence, agree controls, supervise appropriately and verify handback. The recorded evidence supports those controls rather than replacing them.

The change is from a visit you took on trust to a visit you can prove. Before, the record of a contractor's work was whatever happened to get filed. After, the permit, the controls and the proof of completion are captured as the work happens and attached to the asset, so the evidence you need to answer "what did they actually do, and was it safe" is already there.

That has a quiet operational payoff beyond the audit. When proof of work is captured before a contractor leaves site, disputes tend to be shorter, recalls can become rarer, and the asset history tells you what's been touched and by whom. The next decision about that asset is made with a full picture rather than a guess.

It also tightens the handover that usually goes missing. A contractor finishes, and the knowledge of what they did walks out with them, until you need it. Capturing the permit, the controls and the completed work against the asset means the record stays on site even when the people don't. The next engineer, the next manager, the next auditor inherits the full story rather than starting from scratch. Over time, that turns a stack of one-off visits into a continuous account of how an asset has been looked after, which is exactly the kind of intelligence that's usually lost the moment a van pulls away.

Controlling contractors well isn't about more paperwork. It's about capturing the right evidence at the right moment, once, and being able to see it when it counts. The operations that master it are the ones who rarely have to wonder what a contractor actually did, because the evidence is already against the asset and the right checks were made at the time.

FAQs

What should contractor management software record?

It should record any permit to work the job requires, the RAMS sign-off, the certificate and evidence that the job was completed and handed back, all held against the asset the contractor worked on. Keeping these together in one view means you are not relying on email attachments or signed sheets in a drawer.

When should proof of contractor work be captured?

Evidence of the work should be captured on site, before the contractor leaves, as part of a proper handback check. Trying to reconstruct who did what months later from emails leaves gaps that are hard to close.

Why does contractor evidence matter if the work was probably fine?

Because clients and contractors both have responsibilities, and yours does not leave with the contractor. If the controls cannot be shown to have been in place, that is yours to answer for, including when an auditor asks you to demonstrate control of the people working on your site.

How does ocapii help with permits to work and RAMS sign-off?

Where the work and site procedures require a permit, the permit to work and RAMS sign-off are completed in ocapii before work starts, so the controls are agreed and evidenced up front. Evidence of the work is then captured on site and held against the asset alongside the permit and sign-off. That supports, rather than replaces, assessing competence, supervising appropriately and verifying handback, and helps you show what a contractor did and how it was controlled.