What Engineers Actually Spend Their Time On

If you asked a room full of licensed engineers what they went to school to do, most of them would say some version of "solve hard problems." If you then followed them around for a week with a stopwatch, the stopwatch would tell a different story.

This is not a new complaint. Engineers have been writing bitter memos about paperwork since the profession existed. What has changed is that the administrative load has grown faster than the technical work, and the tools that were supposed to help — document management systems, cloud storage, email threads — have mostly shifted the burden rather than reducing it.

We want to be specific about where the time actually goes, because vague complaints do not design products.

The taxonomy

After hundreds of conversations with working engineers, the non-engineering time on a typical week falls into four buckets.

Searching for references. An engineer needs a figure from a report they wrote in 2021. They know it exists. They do not remember which project, which version, or which folder. They search by filename, by client, by a keyword they think appeared in the title. They find three candidates. Two of them are drafts. One is final. None of them match the page number they remembered. Total time to find one figure: twenty minutes on a good day, two hours on a bad one.

Rebuilding documents. A scope calls for a type of report the firm has produced before — dozens of times, maybe hundreds. The engineer starts from a template, or from the most recent similar project, or from a blank page because finding the template would take longer than retyping. The report is 70% common language across all instances and 30% project-specific. Every engineer rebuilds both halves every time.

Tracking specifications. A design references a product, a standard, or a client-specific spec. The engineer needs to confirm the current version. The spec might be a PDF on the client's FTP, an email attachment from 2019, a page in a binder, or a revision on the manufacturer's website. Some combination of those. The engineer picks one and hopes.

Coordinating records. A review comment comes back. The engineer needs to respond, update the drawing, update the calc, update the report narrative, update the project memo, and note the change in the correspondence log. Five surfaces, one change. The coordination is the job.

None of these are skilled engineering. All of them are necessary. And they compound: a week lost to searching, rebuilding, tracking, and coordinating is a week not spent on the thing the client is actually paying for.

The real numbers

Independent industry studies have put administrative and non-billable time in professional services between 30% and 50% of a working week, depending on the firm, the role, and how generously you define "administrative." Our own conversations with early-access firms put it closer to the high end for senior engineers and toward the middle for juniors — not because juniors are more efficient, but because their time is cheaper to burn on filing and searching, and it gets burned.

Pick the middle. Call it 40%. For a firm of thirty engineers, that is the equivalent of twelve full-time positions spent on work that is not what the firm sells. Rebuild the economics of a design-build project in that light and the margins are not particularly encouraging.

What can actually move

We are not claiming to eliminate administrative work. Some of it — client-facing correspondence, project accounting, QA signoffs — is the job and should stay with the humans. The goal is narrower: return the time that is currently lost to searching, rebuilding, tracking, and coordinating that the firm already has answers to, somewhere, if it could only find them.

Here is the specific version.

• Search. Nexus indexes your full corpus. Asking "where is the pump curve from the 2022 utilities job?" returns a citation in seconds. The twenty-minute hunt becomes a five-second query. This is not a modest efficiency gain. It changes how people do their jobs.
• Reuse. When a new report starts from a similar past report, the AI drafts the common 70% with citations into your own prior work. The engineer edits the project-specific 30%. Review takes minutes.
• Tracking. Ingested specs and standards are versioned in the index. Querying "what is the current version of the client spec for storm drainage?" returns the latest, with an audit trail of when it changed.
• Coordination. A change request surfaces the other places in the project record that reference the same element. The engineer updates what needs updating, with a prompt for the rest.

The sum of those four is a real, measurable reduction in non-engineering time. We aim for 30-50% of the administrative load, based on what we have seen in pilot deployments. The exact number depends on the firm, the quality of the existing archive, and how honestly people track their time in the first place.

What you do with the hours back

An engineer with five extra hours a week does not answer five more emails. They do the thing they were hired to do: think about the problem, look at the site, check the calculation, review the junior's work, talk to the client. The technical quality of the firm goes up. The career satisfaction of the engineers goes up. The firm bills the same or more, on better work, with less overtime.

This is what we mean by "be an engineer again." Not nostalgia for a past that never existed, but a practical re-centering of the professional's time on the thing that requires a license in the first place.

Worth measuring honestly

If you are evaluating Gradeum for your firm, the single most valuable thing you can do before the demo is track your own time for a week. Count the minutes spent searching. Count the minutes spent rebuilding. Count the coordination passes. The numbers are almost always worse than people expect — and the upside is almost always larger than the pitch.

Request a demo and bring your week of notes. We will walk the specific scenarios.

— Gradeum Technologies