Situation brief ready to review.
Situation brief
Written · 11/12/2026, 1:56:22 PM
Illustrative example — a fictional client and project, written for this demo. Not a real customer, not a real case, and not a claim about results.
What you reported
Only what your own words support. Mark anything that is not accurate.
- told to youThe client requested adding a spring menu and a booking page.
- told to youThe client asked if the delivery can be on the 31st.
- told to youNothing is signed off, and Marcus is the person who signs.
- you stated thisThe proposal includes $6,800 fee and three rounds of revisions.
- your experienceI feel worried about being perceived as inflexible versus working for free.
Tentative readings
Rapport's hypotheses, not facts. Mark any that do not fit.
- The client may be treating the project as open-ended until signed.
- The client's timeline appears to be based on internal team expectations rather than the project proposal.
Conflicts and gaps
What does not line up, and what is simply missing.
- conflictsThe requested delivery date (31st) conflicts with the proposal date (24th).
- missingThe scope for the booking page (simple form vs. full system) is unknown.
- missingThe status of the project fee given the new additions is unknown.
The one question
The smallest question whose answer could change what you do next.
Does the client acknowledge that these new requests fall outside the initial project scope?
Next step
You decide. Nothing is committed by reading this.
Draft a response acknowledging the requests while outlining that these additions require a revised scope and timeline estimate for Marcus to review.
Optional — help judge this brief
Clarify
What do you need most right now?
Whether the client understands the impact of their new requests on the current scope and project delivery timeline.
Your corrections are kept beside what Rapport proposed. Nothing here is sent to anyone, and nothing is decided for you.