Newsletter
Why Project Handoffs Fail (And the Fix That Takes 10 Minutes) | MES
Most project handoffs move folders but leave context behind. Here's the one document every approved project should generate before your PM opens anything else.
Modern Engineering Solutions
Engineer Your Freedom
The Modern PE
September 2026
Your project manager inherits the files. Everything that actually matters stays with whoever sold the work.
A handoff that only moves folders leaves the whole pursuit inside one person's head.
A deal gets signed on a Friday. Somewhere in your firm, Monday morning belongs to whoever stands the project up.
Create the customer in your accounting software, then the estimate underneath it. Build the project folder from the template, if the person remembers. Copy the site plan and the survey where delivery can reach them. Open a Teams channel. Tell the project manager any of this happened.
Standing a project up: five systems, none of them engineering
1
Create the customer in accounting
2
Build the estimate underneath it
3
Build the project folder from template
4
Copy the site plan and survey over
5
Open a Teams channel
At most firms none of it sits in anybody's job description
It gets done by whoever notices, one way in one office and another way two states over, and on a heavy week it gets done halfway.
That is the version everybody complains about, and it is the smaller half of the problem. The files move. The context does not. Your project manager inherits a folder and a proposal PDF, and the rest stays in the head of whoever ran the pursuit.
What Stays In One Person's Head
Think about what that person knows the day the deal closes. Who actually pays the invoice, and who only sounds like they do. Which consultant coordinates every decision. Which outside firm drew the concept the whole schedule now depends on. What the client is really trying to decide, which is almost never the same as the list of tasks you priced. And every single thing you promised you would not do.
None of that is in the plan set, and all of it decides how the project goes.
The Document That Should Get Written At Approval
So the document that should get written at approval, automatically, is a project brief, and it should land in the project folder before the project manager opens anything else. Read the signed proposal. Write down the understanding, the scope numbered task for task with a timeline on each, and the exclusions. Route it to that division's own site and its own team, so one standard does not force every office into one place.
We generate one on every approval now. A due diligence brief from last month opens by naming the ownership group and where they sit, the development consultant who runs all coordination, the outside studio that drew the concept plan, the water provider, and the county holding entitlement authority. Then it states the four questions the client is actually paying to answer:
The four questions the client is actually paying to answer
1
What the treatment system costs
2
How big it has to be
3
How long the permit really takes
4
Whether the current layout is leaving lots on the table
A project manager who reads that page knows who to call and what winning looks like before touching a drawing.
The Exclusions Are The Point
On hourly work a missed exclusion becomes a change order somebody eventually writes. On lump sum it comes straight out of margin, and it leaves quietly.
On hourly
A missed exclusion becomes a change order somebody eventually writes
On lump sum
It comes straight out of margin, and it leaves quietly
The scope tells your project manager what to build. The exclusions tell them when to stop.
That one brief carried twenty three of them, from geotechnical to construction observation, sitting in the folder on day one instead of surfacing in month two as a favor somebody already did.
It will not guess, either. When there is no signed scope it can read, it writes nothing and flags the project rather than producing a confident brief nobody can trace back to a document.
One Honest Limit
It does not sit in on the calls or read the email threads. What reaches the delivery team is whatever somebody wrote down in the proposal, which moves the discipline upstream where it belongs. A proposal that skips the context stops costing sales an hour and starts costing the project manager a week.
The Rules That Keep It Safe
✓
Deliverables arrive as suggestions. Deliverables drafted off that scope arrive as suggestions, and a person confirms each one.
✓
The task board is created empty. The board belongs to the project manager.
✓
Nothing invoices on its own. Billing is a decision, and decisions stay with people.
Automation you can run twice is worse than the checklist it replaced.
Everything is created at approval and nowhere else. Approving the same project twice, or retrying one that died halfway, finishes the missing pieces instead of creating a second folder and a second estimate.
The Test I Would Run In Your Chair
Pull a project that closed sixty days ago and ask the project manager to name four things that were excluded from the scope. If they cannot, the handoff at your firm is a folder, and the context is still sitting with whoever sold the work.
Reply and tell me what they said.
I read every one.
Next letter goes back to plan review and the piece I promised last month: teaching the tool to see the drawing itself, not just the text behind it.
Michael Groselle, PE
Founder and CEO, Modern Engineering Solutions
mod-eng.com | Mike@mod-eng.com | (214) 833-6748
Talk to an engineer
Tell us about your project.
An engineer reads it
Not a salesperson. Someone who can tell you whether the pathway is real.
You get a first answer
Your options, the agencies involved and the questions that decide cost and schedule.
You decide
No commitment to have the first call.
Prefer the phone? (214) 833-6748