How much time do site managers lose to paperwork?

Ask a site manager how much of their day goes on RAMS review, inductions, inspection records and subcontractor paperwork rather than actually managing the site, and you'll get a confident answer fast. Ask for a number backed by real tracking, and most can't produce one.

We won't invent a specific figure here — reliable, sector-wide data on this exact question is thin, and quoting an unverified percentage wouldn't tell you anything useful about your own site.

Why this is genuinely hard to measure honestly

Part of the reason nobody has a solid number is that admin time on a construction site doesn't happen in one identifiable block — it's scattered across the day in five-minute interruptions between genuinely operational tasks. A site manager fielding a phone call about a missing RAMS while walking between two areas of the site isn't going to log that as "eleven minutes of admin" afterwards. It happens, it gets absorbed into the general noise of the day, and by the end of the week nobody can say with confidence how much of it there actually was. That's not a criticism of site managers — it's a genuine measurement problem, and it's exactly why a confident-sounding sector-wide percentage should be treated with real scepticism rather than repeated as fact.

Where the time genuinely goes

What's easier to say with confidence is where the time tends to go: chasing subcontractors for RAMS or accreditation evidence that should have been submitted before they arrived, re-checking site inspection records that were captured on paper and need transcribing, and managing the same compliance information separately across multiple sites rather than in one place.

• –Chasing paperwork that should have arrived before a subcontractor turned up, rather than being on file already
• –Manually cross-checking accreditation status that's changed since it was last looked at
• –Transcribing inspection notes taken on paper or in a notebook into whatever system the record actually needs to live in
• –Re-answering the same compliance question for the same subcontractor across separate sites, because there's no shared view
• –Reconstructing what happened in the run-up to an incident from memory, because the daily record wasn't detailed enough at the time

What's worth tracking locally

Rather than looking for a sector-wide benchmark that doesn't reliably exist, it's more useful to track your own site's pattern for a couple of weeks: how often does a subcontractor turn up without the right paperwork already on file, how much time goes into producing inspection records versus actually inspecting, and how many compliance questions get asked more than once because the answer wasn't recorded anywhere accessible the first time. Those specific, locally observed patterns are the ones worth acting on — they tell you where your actual site is losing time, rather than how a hypothetical average site compares to another.

A practical starting point

If a pattern does emerge — say, the same three or four subcontractors always turning up without current accreditation on file — that's worth treating as a specific, fixable problem rather than an inevitable cost of running a site. It connects directly to the kind of leading-indicator tracking that catches a compliance gap before it becomes a delay or, worse, an incident, rather than a general sense that "there's too much paperwork" without a clear picture of which paperwork and why.

Asking the question of the people actually doing the admin

One of the more useful, and most overlooked, ways to find out where admin time genuinely goes is simply to ask the people doing it — a site manager can usually describe, off the top of their head, the two or three recurring tasks that eat the most of their week, even without a precise number attached. That qualitative answer, gathered consistently across a handful of sites, tends to be more useful than trying to build a formal time-tracking exercise from scratch, and it has the advantage of coming with the context of why each task is time-consuming, not just how long it takes.

It's also worth asking the same question of subcontractors, not just your own site managers — they're often the ones chasing paperwork requests from multiple principal contractors at once, and their frustration with a slow or duplicated process is a useful signal too, not just an inconvenience to be managed.

The difference between necessary admin and duplicated admin

Not all of this time is genuinely wasted — reviewing a RAMS properly, running a thorough induction, writing a detailed inspection record are all admin in the sense that they're not physically building anything, but they're doing real work. The time worth targeting is the duplicated kind: re-checking something that was already verified, re-entering data that already exists somewhere else, chasing a document that should have arrived automatically rather than needing a phone call. Distinguishing between the two matters, because trying to cut admin time indiscriminately risks cutting the genuinely useful checks along with the wasteful repetition.

Why this compounds across a busy project

A single instance of chasing a missing document costs a few minutes. Across a project with a dozen active subcontractors, several of whom turn over their own workforce weekly, those few-minute instances happen constantly, and the cumulative effect on a site manager's week is real even without a precise figure attached to it. This is also where the problem tends to compound across multiple concurrent sites — the same duplicated admin repeated site by site, rather than solved once for the whole organisation.