Write Scope-of-Work Documents from Meeting Notes

1. Open https://claude.ai and start a **new chat** (keep everything in this single thread through Order 4). 2. Paste this prompt and fill in the brackets: "I need to turn rough meeting notes into a scope of work — but do NOT draft an SOW yet. Only extract structure. Project / client name: [...] My role (implementation / advisory / creative): [...] Fee model hint (fixed phases / hourly bucket / retainer / unknown): [...] Hard deadlines or phases already discussed: [...] Raw notes or transcript excerpt: [paste everything] Reply with ONLY four labeled sections — no document headings, no legalese: (a) Decisions — bullets for what both sides already agreed. (b) Open questions — bullets for anything ambiguous or unresolved. (c) Constraints — budget, tech stack, stakeholders, approvals, access. (d) Risks — what could blow scope, timeline, or budget. Do not write 'Scope of Work' prose yet." 3. Read Claude's output. If it sneaks in draft sentences that sound like contract language, reply: "Remove all SOW-style wording — bullets only under the four sections above." 4. If your notes were fuzzy, insist until you see **at least three** open questions called out (or an explicit line that the notes are complete — then add your own questions as bullets).

1. In the **same chat**, paste: "Using ONLY the extraction you just produced (decisions / open questions / constraints / risks), build an SOW **skeleton** — still no detailed deliverables table yet. Use these section headings (rename slightly if the project is tiny): Overview & objectives; Scope & deliverables (placeholder subsection); Timeline & milestones (placeholder); Client responsibilities; Assumptions; Out of scope; Changes & re-estimation; Acceptance. Under **In scope**, bullet only concrete work implied by the extraction — each bullet must trace to a phrase in Step 1. Under **Out of scope**, bullets for what you will **not** do unless separately agreed — aim for **at least three** bullets unless you explain why fewer apply. If out-of-scope is genuinely unknown, write one line 'none yet — to be agreed' plus **one** specific question to ask the client next. Keep tone professional but plain — no marketing fluff." 2. Scan in-scope bullets for hedge words like "etc." — if you see them, ask Claude to replace each with named categories. 3. If out-of-scope is empty while in-scope reads like marketing hype, prompt: "Add boundaries implied by budget, constraints, and risks from Step 1."

1. In the **same chat**, paste: "Now draft the **Scope & deliverables** and **Timeline & milestones** sections using the skeleton and extraction above. Produce: (A) A **markdown table** with columns: Deliverable | Acceptance criteria (observable) | Owner (Client / Provider — use Provider for yourself) | Target date or phase. Rules: - Every acceptance criterion must describe something **observable** — a file delivered, a metric hit, a workshop held, a signed approval — not vibes. - Ban rows where acceptance is only subjective unless you add a proxy (replace "client happy" with "signed PDF delivered" or "≤2 revision rounds on wireframes"). - Merge duplicate rows. (B) A **milestone list** — either calendar dates from the notes or Phase 1 / 2 / 3 with what completes each phase. (C) Under **Acceptance**, 3–5 bullets on how sign-off works (e.g., written approval email, review window in business days). Flag any date as **TBD + blocker** when Step 1 didn't supply it." 2. If you see "ongoing support" without hours or cadence, prompt: "Either split into concrete recurring artifacts or cap hours per month." 3. Verify each row names **who proves done** and **what artifact proves it**.

1. In the **same chat**, paste: "Append the remaining sections as plain text I can paste into a doc: **Assumptions** — bullets for inputs the client must provide (content, access, approvals, stakeholders). Focus on dependencies that usually blow deadlines. **Change requests** — **3–6 sentences** describing process only (how the client requests extra work, how you respond with estimated timeline and fee impact, what happens if they decline). **Not** legal language — business-process clarity. **Fees & invoicing** — use bracket placeholders copied from my notes only: [FEE STRUCTURE], [PAYMENT SCHEDULE], [DEPOSIT]. If I didn't give numbers in prior messages, **do not invent dollar amounts** — keep brackets. **Term** — [START DATE], [END DATE or ongoing], aligned with what we discussed. **Disclaimer** — one short line: this is a business scope summary for discussion, not legal advice; high-stakes deals should involve counsel. Compile everything **above** this message (skeleton, table, milestones) into one continuous markdown draft in logical section order." 2. Scan for hallucinated prices — if you see numbers you never typed in this chat, reply: "Strip all dollar amounts; use bracket placeholders only." 3. Confirm the change path reads actionable in under six sentences.

1. Open https://docs.google.com → **Blank** document. 2. Title it `[Client] — Scope of Work — [DATE]` using your real client name and today's date. 3. Paste the **full markdown draft** from Claude (Orders 1–4). 4. Apply **Heading 1 / Heading 2** styles to section titles; convert the deliverables table using Docs' **Table** tool if the paste breaks alignment. 5. Skim for **[brackets]**, **TBD**, mismatched dates, or duplicate sections — fix typos; don't rewrite scope without re-running Step 3 in Claude. 6. If the table is unreadable after one paste, go back to Claude **once** with: "Re-output **only** the markdown table from Step 3 as clean GitHub-flavored markdown" — then re-paste the repaired table. 7. Optional: **File → Download → PDF** if you need an attachment for email or e-sign prep.