Drafting an Agreement
Mia guides Leo and Jack in drafting a specific agreement, including who owns each task, how handoffs will be documented, and when they will raise concerns. They confirm that the commitments are realistic and mutual.
Dialogue12

We’ve identified the main friction points. Let’s turn them into a working agreement: specific responsibilities, a reliable handoff, and a clear way to flag concerns before they escalate.
I’m comfortable owning the initial analysis and the first draft. What I need is a firm deadline for Jack’s review, so I’m not left guessing whether the work is ready to move forward.
That seems reasonable, provided the draft includes the assumptions and any unresolved questions. I can own the technical review, but I can’t reliably sign off on work when key context is missing.
So Leo owns the analysis and draft, including assumptions and open questions; Jack owns the technical review. What turnaround can you both meet consistently, not just on an unusually quiet week?
If I send the complete draft by noon Tuesday, I can give Jack two full working days. That should work unless the source data arrives late, which I’ll flag as soon as I know.
I can return comments by Thursday at noon, as long as I receive the draft and supporting material together. If the review requires substantial rework, I’ll say so rather than silently slipping the deadline.
Let’s document each handoff in the project tracker: owner, date sent, requested response date, and a link to the current version. That gives you both a shared record without adding another meeting.
Agreed. I’ll mark the draft as ready for review only when the supporting material is attached. If something is incomplete, I’ll label it clearly instead of assuming Jack knows what’s missing.
And I’ll raise concerns in the tracker as soon as I see a risk to the deadline or the quality of the analysis. If it’s genuinely urgent, I’ll message Leo directly and explain why it can’t wait.
Before we settle this, is either commitment unrealistic given your current workload? I’d rather adjust the process now than have a polished agreement neither of you can actually follow.
Tuesday and Thursday are realistic for me. If an unexpected priority threatens my draft deadline, I’ll tell Jack and update the tracker by Monday afternoon, not after the deadline has passed.
Those deadlines work for me too. I’ll commit to the Thursday review, and if I need clarification, I’ll ask promptly rather than letting uncertainty stall the handoff. We can try this for the next project cycle.
Vocabulary8
- working agreement
A practical set of commitments about how people will work together. Here, it covers responsibilities, handoffs, and how to raise concerns.
- owning
Taking responsibility for a task and seeing it through. You can say, “I’ll own the initial analysis,” to make your role clear.
- sign off on
To formally approve something or confirm that it is acceptable. In this context, Jack needs enough information before he can approve the work.
- turnaround
The time needed to complete a task or respond to a request. You can ask, “What turnaround can you commit to?” when setting a deadline.
- supporting material
Documents or other information that help explain or verify a piece of work. Providing it with a draft can make a review more efficient.
- flag concerns
To draw attention to problems or risks so they can be addressed. The phrase is useful in professional settings when you want to raise an issue early.
- substantial rework
A significant amount of work needed to revise or redo something. It helps distinguish major revisions from minor edits.
- by Monday afternoon
A specific time frame for completing an action. Giving a clear point by which you will update others makes a commitment easier to follow.
Key Sentences8
- 1
Let’s turn them into a working agreement: specific responsibilities, a reliable handoff, and a clear way to flag concerns before they escalate.
This sentence moves a discussion from identifying problems to agreeing on practical steps. Reuse “Let’s turn this into…” to propose a concrete plan.
- 2
I’m comfortable owning the initial analysis and the first draft.
This is a clear way to state which tasks you are willing to take responsibility for. Replace the tasks with your own, such as “the client follow-up and the summary.”
- 3
What turnaround can you both meet consistently, not just on an unusually quiet week?
This question checks that a deadline is sustainable rather than overly optimistic. Use “What turnaround can you meet consistently?” when setting realistic expectations.
- 4
If I send the complete draft by noon Tuesday, I can give Jack two full working days.
This links one person’s delivery time to another person’s review period. Reuse the conditional structure “If I send [item] by [time], I can give you [period] to review it.”
- 5
Let’s document each handoff in the project tracker: owner, date sent, requested response date, and a link to the current version.
This sentence specifies what information to record so everyone can follow the progress of a task. Adapt the list to the details your team needs to track.
- 6
If the review requires substantial rework, I’ll say so rather than silently slipping the deadline.
This communicates a commitment to raise problems instead of missing a deadline without warning. Use “I’ll say so rather than…” to contrast proactive communication with an unhelpful alternative.
- 7
If an unexpected priority threatens my draft deadline, I’ll tell Jack and update the tracker by Monday afternoon, not after the deadline has passed.
This sets out what you will do if circumstances put a commitment at risk, including when you will communicate. Reuse the pattern “If [risk] threatens [commitment], I’ll [action] by [time].”
- 8
I’ll commit to the Thursday review, and if I need clarification, I’ll ask promptly rather than letting uncertainty stall the handoff.
This combines a firm commitment with a plan for handling uncertainty. Use “I’ll ask promptly rather than…” to show that you will address a potential delay directly.