
How to Find the Work Your Firm Keeps Doing Twice
Ask the owner of almost any growing firm on Long Island how many hours went to doing work twice last month, and the honest answer is a guess. Firms from Hauppauge to the East End give the same answer, and it is clearest at Engineering firms, where a sheet issued from a superseded model or a timesheet typed into two systems passes for an ordinary Tuesday. Rework rarely shows up on a report, so it rarely gets fixed.
That matters more now than it did a few years ago. Architecture and Engineering firms in Deltek's 2026 Clarity study reported staff growth of just 1.2% and turnover of 13.8%, while forecasting 9.5% net revenue growth for 2026. If growth is not coming from new hires, it has to come from the hours you already have. The biggest pool of hours nobody measures is the work your team does twice.
This post walks through a two-week count any firm can run, how to sort what you find, and which causes technology can fix.
Why rework stays invisible
Rework hides because it looks like work. It is billed to the same project, done by the same people, in the same hours. Nobody opens a ticket that says "redid the duct layout because the architectural background changed." The fix happens, the deadline holds, and the cost disappears into the week.
We have written about how rework quietly becomes part of the process. The next step is to stop estimating it and start counting it.
Run a two-week rework count
For two weeks, ask everyone on the team to log each time they redo, re-check, re-send, or rebuild something. Keep it light enough that people do it:
- One line per redo. What was redone, roughly how long it took, and what caused it.
- One shared place. A simple form or a shared spreadsheet is enough. If logging takes more than 30 seconds, people stop logging.
- No blame. The goal is to find broken processes, not careless people. Say so up front, and mean it.
- No fixing yet. Count first. Fixing things halfway through hides the pattern you are trying to see.
Two weeks is long enough to catch a deadline cycle and short enough that people keep logging. Include the owners and project managers. Their rework is often the most expensive kind.
Sort every entry by cause
At the end of the two weeks, put each entry into one of five buckets. Most entries will fit one of these:
- Wrong version. Someone worked from a superseded drawing, model, or spec, usually because a copy lived on a desktop or in an email attachment instead of one shared location.
- Double entry. The same information typed into two or three systems: hours into a timesheet and again into project accounting, a client's details into the CRM and again into a proposal. Every retype is a chance for a mismatch that someone has to chase later.
- Missing information. Someone could not find the answer, made a reasonable guess, and redid the work when the real answer turned up.
- Lost work. A crash, a sync conflict, or a file overwritten with no version history to restore from.
- Handoff gaps. A step was skipped because the process lives in one person's head. With turnover at 13.8% a year across the firms in Deltek's study, that knowledge walks out the door more often than most firms plan for.
Add up the hours in each bucket. The two or three biggest are where you start.
Put a number on it
Dollars get more attention than hours, so convert them. Picture a 25-person MEP firm with 18 billable people, and treat every number here as an assumption for illustration, not a survey result. Say the count shows each of them losing about two hours a week to rework. That is 36 hours a week. Over 48 working weeks, it comes to roughly 1,700 hours a year, more than the roughly 1,300 hours we assume one full-time Engineer bills in a year.
At an assumed $150 an hour, that is about $259,000 of capacity a year spent doing things twice. Your own count will give you your own numbers, and those will persuade your partners more than any benchmark can.
Hiring is the usual fix, but it takes months, and a new hire inherits the same broken handoffs.
Which causes technology fixes, and which it does not
Some rework is a technology problem and some is not. Sort out which is which before anyone buys anything.
- Wrong version: fixable. One shared location for current project files, with permissions and version history, so there is no second copy to work from. For teams working in shared models, that includes setting up syncing and file access properly instead of leaving it to habit.
- Double entry: often fixable. Connect the systems you already own, so information is entered once and flows to the rest. Here is what a connected Engineering firm looks like.
- Lost work: fixable. Monitored backups that someone tests, version history on shared files, and workstations that are maintained before they fail.
- Missing information: partly. A searchable home for standards, templates, and how-tos helps. AI search tools can help people find what is already written down, but only if someone wrote it down first.
- Handoff gaps: mostly a process problem. Technology can enforce a checklist once it exists. It cannot decide what the checklist should say.
Scope changes and client revisions will show up in your count too. Those are a contract and project management question, not an IT one. Count them anyway, so you can see how much of your rework is within your control.
Start with the top three
Take the three causes with the most hours and fix one a month. Then run the count again in 90 days with the same form. If the hours did not drop, the fix did not work, and you know it before you spend more.
If you have an internal IT person, this is a natural fit for co-managed IT: they keep the day-to-day, and an outside team takes on the file structure, integrations, and backups that clear the biggest buckets.
Want help reading your rework count? New Edge IT Services works with firms across Long Island, and with Engineering firms nationwide. Book a 30-minute review, bring your numbers or just your hunch, and we will show you which causes technology can fix and which it cannot. No pitch, just a clear picture. Book your review.


