The before-you-send checklist I use so a one-page client brief still matches the ask

The one-page brief can look finished long before the ask is settled. Two goals can survive from meeting notes into Slack, an opinion can get dressed up as a decision, and an open question can become a requirement because it has a tidy heading. Add a remembered budget and a missing stakeholder, and “I think we're aligned” can rewrite the send.

I am Brittany Bonds, a freelancer admin helper. I turn messy meeting notes into a clean one-page client brief. I am not a CPA, lawyer, strategist, or engagement attorney, and this is not legal, financial, tax, or contractual advice. It is a practical notes-to-brief checklist for keeping stated facts, decisions, questions, and constraints visibly separate before a page leaves the draft folder.

This is complementary to my earlier posts, not a rewrite. My first-pass workflow is How I turn messy meeting notes into a one-page client brief. The second pass is The mid-brief checklist I use so a one-page client brief stays honest. This third pass is the before-you-send check: the moment when someone may treat the one-pager as the locked ask.

What “honest enough to send” looks like

• A primary goal is clear, or competing goals are labeled conflict / ask
• Decisions are supported by a source, while opinions remain opinion or assumption
• Open questions are visibly open, with an owner or a clear next ask
• Budget, timeline, scope, tools, and audience match the latest source — or the mismatch is recheck
• The stakeholder list includes the person who can quietly veto the direction
• The send note does not claim alignment that the brief itself cannot show

If the only proof of alignment is “I think we're aligned,” I stop before sending.

The before-you-send checklist

Use this against the brief and its source trail: meeting notes, Slack, email, calendar, prior brief, intake form, and decision log. The goal is visible uncertainty, not a green-looking page.

1. Reconcile the ask, not just the wording

• [ ] Write the requested outcome in one sentence and name the audience — client, internal team, or both
• [ ] If notes and Slack contain two goals, keep both visible and label the conflict; do not pick the easier one because it fits the page
• [ ] Compare the brief's “success” line with the latest source; a polished synonym may not be the same ask
• [ ] Mark anything that came from one person's interpretation as opinion or assumption, not client-confirmed fact

2. Separate decisions from questions

• [ ] Give each locked decision a source, date, or named decision-maker when available
• [ ] Keep “should we,” “could we,” and “what about” items under open question — a heading does not turn them into requirements
• [ ] Add an owner or next ask to material questions; “TBD” alone is not a handoff
• [ ] Do not convert “we can probably do that” into scope, deliverable, or acceptance criteria
• [ ] Skim test: a reader can count the unresolved questions without guessing which green bullets are still negotiable

3. Stop constraint drift at the send boundary

• [ ] Recheck budget, timeline, scope, tools, format, and brand or audience limits against the latest source
• [ ] Put conflicting values side by side as recheck — do not average a $2,000 guess and a $3,000 note into “flexible budget”
• [ ] Label changed constraints with their source and date; old context is not current permission
• [ ] Skim test: the brief says what is included, excluded, and still waiting for confirmation

4. Find the quiet veto before it finds the send

• [ ] List the approver, day-to-day contact, reviewer, and anyone whose sign-off can stop the work
• [ ] Check whether the quiet veto appears in the source trail even if they were absent from the meeting
• [ ] Name the missing approval as ask rather than treating silence as consent
• [ ] Keep private names, credentials, and sensitive raw notes out of the share view
• [ ] Skim test: the recipient knows who can approve, who can comment, and what happens if that person has not answered

5. Challenge the alignment sentence

• [ ] Replace “I think we're aligned” with the exact points that are confirmed, open, or conflicting
• [ ] Read the brief once as a skeptical recipient: what would you reasonably think is now locked?
• [ ] Make the send ask specific — confirm goal, owner, constraint, decision, or open question — instead of asking for a vague thumbs-up
• [ ] Leave a visible needs confirmation marker where sending would otherwise create a false record
• [ ] Final skim: the brief and send message tell the same story without requiring a Slack archaeology project

Soft CTA

If you want messy meeting notes turned into a clean one-page client brief: hubuve on Gumroad. Use code ADMIN12 for $2 off. Shop the live catalog or browse the GitHub Pages catalog.

I am not a CPA, and this is not legal, financial, tax, or contractual advice — just admin cleanup so the brief you send still matches the ask you can actually support.