Scope, Assumptions, and Exclusions Section Writer
Prevent misunderstandings before they cost money.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Write the scope section of a proposal. Project description: [PROJECT_DESCRIPTION]. Deliverables: [DELIVERABLES]. Client responsibilities: [CLIENT_RESPONSIBILITIES]. Known risks and unknowns: [RISKS_AND_UNKNOWNS]. Timeline and review rounds: [TIMELINE_AND_REVISIONS]. Return, in plain language: 1. In scope: each deliverable with a measurable description (quantities, formats, versions, review rounds, turnaround time). 2. Out of scope: things clients often assume are included (extra revisions, content writing, third-party costs, training, ongoing support), written explicitly. 3. Assumptions: conditions that must be true (access by a date, timely feedback within three working days, a single point of contact, content supplied in a format), and what happens if they are not (timeline moves, change order). 4. Dependencies and risks, with the owner of each. 5. Change process: how changes are requested, priced, approved, and recorded. 6. Acceptance: what counts as done, who signs off, and how long they have to review. 7. A plain-language summary box of five bullets. Provide an example of one vague sentence and its precise rewrite. Note that binding terms should be reviewed by a lawyer who knows [JURISDICTION] [VERIFY]. Use only the details I gave.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.