Newsletter
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. What to write down at approval, copied from the signed contract.
For engineering firm owners
A handoff that only moves folders leaves the whole pursuit inside one person's head.
Updated November 2026 from my September letter. What changed: the page we write at approval now copies the signed contract, and the client example is gone.

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.
Five systems, none of them engineering, and 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.
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. 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 cost isn't the start date. It's month two
Our own numbers say handoffs aren't slow. They say something else.
I assumed handoff was where our jobs lost time, so I checked before rewriting this letter. On 88 jobs we won since June, the first hour landed a median of two days after the win, and 84 of the 88 started within a week. Our waiting happens in the middle and at the end of a job, not at the start.
So the case for a better handoff isn't speed. It's what the project manager knows on day one. Gabriel Szulanski studied 122 transfers of best practice inside eight companies. The biggest barriers were about the knowledge itself, not whether people wanted to help. He studied practices moving between units, not deals moving to delivery, but the lesson carries: willing people still drop what was never written down.
Write it down at approval, from the contract
The scope tells your project manager what to build. The exclusions tell them when to stop.
So the document that should get written at approval, automatically, is a scope and summary, and it should land in the project folder before the project manager opens anything else. This fall we changed how ours is written. The understanding, the scope and the exclusions are copied from the signed contract word for word, not rewritten, so an exclusion can't drift between what we signed and what the project manager reads. The rest is drawn from the deal record, and the deal's contacts move onto the project with it. It carries no fee. If a dollar figure shows up, it refuses to save.
A good one opens with who pays, who coordinates, who drew the concept, who supplies the water and who holds approval authority. A project manager who reads that page knows who to call before touching a drawing.
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.
Ten of our saved documents carry an exclusions list copied from a signed scope. The lists ran from 3 items to 16, and a typical one had about 11. That is 11 things sitting in the folder on day one instead of surfacing in month two as a favor somebody already did.

It can't read what nobody wrote down
A draft that says it's a draft beats a confident page nobody can trace.
Since early October, nine projects outside our one repeat site program were approved, and all nine got a scope and summary. Four of the nine had no signed scope it could read, so it labeled the second half a draft pending the final proposal. What reaches delivery is whatever made it into the signed document. That moves the discipline upstream, where it belongs.
The rules that keep it safe are short. Nothing goes to a client on its own: the kickoff email waits in the approver's drafts, and a retainer invoice waits for one click. The folder, the estimate and the channel are created at approval, and a retry finishes the missing pieces instead of making a second folder and a second estimate. Automation you can run twice is worse than the checklist it replaced.
Here is the test I would run in your chair. Pull a project you won sixty days ago and ask the project manager to name four things that were excluded from the scope. Then check them against the signed proposal. If they cannot, the handoff at your firm is a folder, and the context is still sitting with whoever sold the work. I haven't run this on our own team yet, so I don't have our answer to give you.

Tell me what they said through our contact page. I read every one.
Michael Groselle, PE
Founder and CEO
Modern Engineering Solutions
mod-eng.com
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