Module 4 of 12 · Illustrated Walkthrough
The Project Becomes Yours at the Handoff
The illustrated walkthrough — how a sold pursuit becomes a project you own, and how curiosity beyond the contract finds what the client will actually call success.
Module 4 throughline — The project becomes yours when you can explain what was promised, what was assumed, what is at risk, and what the client will actually judge as success.In Modules 2 and 3 you learned the project’s economics — the fee, the multiplier, backlog turning into cash. Before you can protect a dollar of it, one moment has to go right. Which moment — and what has to transfer in it?
The moment
The project becomes yours at the handoff
Picture a PM handed a project the week construction documents begin. They inherit a fee they didn’t price, a scope they didn’t write, and promises they never heard made. Weeks later a roughly $40,000 change surfaces — work everyone assumed was in scope, that nobody had actually logged. So here is the question the whole module turns on: when does a project actually become yours?
The handoff is not a calendar event. It is the latest acceptable moment to take ownership — by the time you’re assigned, most of the risk is already baked in.
The handoff transfers two things at once: knowledge and accountability. The contract is the written half — scope, fee, terms. The pursuit team carries the rest: the verbal promises, the fee assumptions, the priorities the client only said out loud. Both halves must be actively pulled. One lives on the server; the other walks out the door when the pursuit team moves on.
?You’re assigned a project. The signed contract is on the server, and the pursuit team is still down the hall. Is reading the contract enough to take ownership?
Before it was yours
Every project clears a gate before it reaches you
That decision has a name at Grace — the Go / No-Go. It’s the gate every opportunity must pass through during Pursuit, well upstream of Contracting and your Handoff. Clear the gate and the firm commits real time and money to winning the work. Don’t, and we walk away — on purpose — to spend that energy where we’re stronger. A “No-Go” isn’t a loss; it’s a discipline.
The Go/No-Go is a gate inside the Pursuit stage. Only opportunities that clear it advance to Contracting, your Handoff, and Delivery.
Here’s what matters for you as PM: you don’t own this decision — but you inherit its result. The Go/No-Go is led by the Principal in Charge, working in concert with Business Development — the Pursuit Manager and BD leadership. You may be invited to the table to weigh the delivery reality: can we staff it, schedule it, win it? When you are, give an honest read. But the call sits with the PIC and BD. Your job is to be aware and contributing, not to cast the deciding vote.
The gate scores an opportunity on three honest questions.
Relationship strength
Are we known to the owner / decision-maker — or walking in cold as a stranger?
Preparedness
Did we see this coming? Was it on our Top 10 list with a capture plan — or news to us when the RFQ dropped?
Qualifications & timing
Are we technically competitive for this work, and is there real time to prepare a tailored submission?
Here’s the actual tool, filled in as a worked example — the simulated Oakhaven pursuit. Notice how the three factors above map to its rows.
| Relevant Factors | Factoring Scoring Scale | Score | |||
|---|---|---|---|---|---|
| NEGATIVE (0–1 POINTS) |
NEUTRAL (2 POINTS) |
POSITIVE (3 POINTS) |
|||
| Factor 1 Relationship strength |
Are we known by the Owner / Decision-Maker? | Unknown to this Owner / Decision-Maker (0) | Known, but not fully cultivated | Well-developed working relationship | 2 |
| Factor 2 Preparedness |
Is this the first we’ve heard of it? Was it on our “Top 10” List? | Didn’t know until the RFQ/RFP came out; unprepared (0) | Known or on Top 10 List, but no pre-sale meeting | On Top 10 List; capture plan completed | 3 |
| Factor 3 Qualifications & timing |
Do we meet the RFQ qualifications for portfolio and team? | Capable (1) | Can meet or exceed every requirement | Technically superior — our sweet spot | 3 |
| Does marketing have adequate time for a tailored submission? | One week or less to due date (0) | Two weeks or less to due date | Over 2 weeks to due date | 3 | |
| Total score | 11 | ||||
?You’re asked to sit in on the Go/No-Go for a project your team might deliver. Does that make the decision yours?
The Pursuit-stage process steps and the “who leads / your role” breakdown live in the Quick Reference, Card 1.
The output
What a clean handoff leaves you holding
You prove the handoff happened by producing one thing — a Handoff Ownership Brief. Six fields. Fill them and you own the project. Leave them blank and you’re still guessing.
What was promised
The scope and deliverables you’re now on the hook for.
What was assumed
The fee basis, staffing, and scope assumptions the price depends on.
What was priced
The fee — and where the margin actually sits.
What the client values most
The priorities carried out of pursuit, in the client’s own words.
What’s unclear or at risk
The gaps you can already see from where you stand.
What must be resolved first
The short list that has to close before planning advances.
A handoff is complete when you can explain what was sold, why it was sold that way, what assumptions the fee depends on, what the client expects, where the risk sits, and what must be clarified before planning advances.
Notice fields 5 and 6. Readiness isn’t knowing every answer — it’s naming the unknowns and owning their closure. The strongest PMs would rather pause a day at the handoff than spend a month unwinding a misunderstanding in design.
The principle
Lead the judgment. Verify the process.
As owner you carry two kinds of work, and confusing them is expensive. You LEAD the substance — the calls only judgment can make. You VERIFY the process — formatting, signatures, logs, standard Grace language — prepared and finalized with Admin. Hand the judgment to process and you’ve delegated the part that was yours. Drown in the process and you’ve stopped leading.
| Situation | You LEAD (judgment) | Verify / Admin (process) |
|---|---|---|
| Contract handoff | Confirm what was promised, what is unclear, what needs follow-up. | Confirm file location, executed agreement, naming, version control. |
| Scope assumptions | Determine what must be clarified before planning advances. | Maintain the checklist / handoff record. |
| Additional-service risk | Identify where sold scope may not match the expected effort. | Confirm template, log entry, approval path. |
| Client communication | Decide what the client needs to see, and when. | Format the update or meeting record consistently. |
| Fee / staffing | Interpret what the fee allows and where the risk sits. | Confirm the budget is loaded in BST. |
The full construction-phase version of this table — pay applications, change orders, closeout — is drilled in Module 11, where it lives in the Quick Reference. Here, the principle is the point.
?A scope item looks like it may exceed the effort that was sold. Admin offers to log it and move on. Is logging it enough?
Beyond the contract
The contract is the floor, not the finish line
Imagine a PM who delivered every line of the signed scope — on time, on budget, technically clean — and the client was lukewarm. The thing they cared about most never appeared in the contract, so it never got managed. That’s the trap: meet the floor and miss the point.
The signed scope — the minimum you must deliver. Manage only to this and you’ve achieved compliance.
The client’s real definition of success — usually higher than the contract, and never fully written in it. Reaching it is value creation.
The space between floor and finish line gets filled one of two ways. You presume — quietly steering value toward your own assumptions, often wrong. Or you get curious and ask.
?Your client is a hospital, so obviously infection control is their top priority. Do you still need to ask?
The tool
Six questions that find the finish line
Discovery isn’t a soft chat. It’s a deliberate set of questions, each built to surface a different driver of value — grounded in how Grace clients actually define success.
“A year after these doors open, what has to be true for the people who use this space — and how will you know?”
“Who lives, works, heals, learns, or gathers here every day — and what do they need that they’d never put in a brief?”
“Where would ‘good enough’ be a failure — the few things we must protect at all costs?”
“When scope, schedule, and budget collide, which do you most want us to protect?”
“Beyond you, who has to believe this succeeded — and what will they judge it on?”
“How, and how often, do you want to hear from us — and what does a great update look like?”
Curiosity over presumption. Ask, then go quiet. The answer you didn’t expect is usually the one that matters most.
The payoff
Same scope, different value
At the Oakhaven Public Safety Campus (a simulated project), two PMs ran the same signed scope. One asked, early, what mattered most. The dispatch center’s real priority — zero downtime for 911 during cutover — was never in the contract. The curious PM surfaced it and planned the phasing around it. The other met it as a late-stage crisis. Same paperwork. Very different value. The whole difference was a question.
Discovery is where you stop managing the document and start managing the outcome.
And the answers don’t stay in a notebook. Your planning work begins with three inputs — what was promised, what was assumed, and what the client values most. That is the raw material for Planning, and it’s where this module hands off. The contribution loop continues: value → outcomes → money → capacity → the firm’s future.
Module 4 · Taking Ownership
You took the baton, you know what you own, and you know how to find what winning means to this client.
Carry the three inputs forward into the plan.