AI Field Manual
FM-PM-04 · Guide

Project Management  ·  Fundamentals

Convert a vague request into a scope statement

The email says: "Can you just set up a portal so clients can see their project documents? Ideally before the end of the quarter." It's three lines long. Behind it are a dozen decisions nobody has made: which clients, which documents, who uploads them, what "see" means, and what happens when someone sees the wrong thing. This guide turns the request into a scope statement before it turns into a project nobody can finish.

Status
Published
Reading time
About 12 minutes
You'll need
The original request (email, message or notes), anything you know about constraints, and an approved AI assistant
Last reviewed
November 2026
Before you start

What AI is for here, and what it isn't

Scope problems rarely come from bad requests. They come from requests that are reasonable but incomplete, accepted before anyone has asked what they actually include. Every unasked question becomes an assumption, and every assumption becomes a disagreement later.

AI is good at the first half of the fix: reading a short request and listing everything it leaves undefined, drafting objectives and deliverables, and proposing sensible exclusions. It's fast at producing a structured first draft you can take to the sponsor.

It can't know what the sponsor actually wants, what the organization can support, or what you're willing to commit to. Its draft is a list of questions in the shape of an answer. The scope statement only becomes real when the sponsor has read it and agreed, including to the exclusions.

Step 1

Capture the request exactly

Copy the request word for word, including who sent it, when, and any context you have about why. Don't paraphrase it yet. The original wording matters: "set up a portal" and "give clients access to their documents" lead to very different projects, and you'll want to show the sponsor exactly how you interpreted their words.

Add what you already know: the deadline and whether it's fixed, the budget if any, systems that already exist, and who else might have a stake.

Step 2

Find what the request leaves undefined

The request-analysis prompt
You are helping a project manager scope an informal request before
committing to it. Do not design a solution.

REQUEST (verbatim): [paste]
FROM: [role]     CONTEXT: [why it was asked, if known]
KNOWN CONSTRAINTS: [deadline, budget, existing systems, policies]

PRODUCE:
1. THE UNDERLYING NEED: two or three possible business problems this
   request could be solving. Mark which one the wording most supports.
2. UNDEFINED TERMS: every word or phrase that could reasonably mean
   different things (e.g., "portal", "clients", "see", "documents").
3. MISSING DECISIONS: grouped as who (users, owners), what (content,
   features), how (security, support), and when (deadline flexibility).
4. HIDDEN WORK: tasks the request implies but doesn't mention
   (migration, permissions, training, support, ongoing maintenance).
5. QUESTIONS FOR THE SPONSOR: no more than 10, ordered by how much
   the answer changes the size of the work.

RULES: Do not assume answers. Do not estimate effort or cost.

The "hidden work" list is often the most eye-opening part for the sponsor. A document portal implies deciding who uploads documents, how permissions are maintained when client contacts change, and who answers when a client can't log in, none of which appears in the three-line request.

Step 3

Draft the scope statement

Once you have some answers, or your best assumptions clearly labelled, draft the scope statement.

The scope statement prompt
Draft a one-page scope statement from the request and answers below.

REQUEST: [verbatim]
ANSWERS FROM SPONSOR: [what you've learned]
ASSUMPTIONS I'M MAKING: [where you don't have answers yet]

SECTIONS:
- Objective: the business outcome, in one or two measurable sentences.
- Deliverables: what will exist at the end, concretely.
- In scope: the work included.
- Out of scope: work that someone might reasonably expect but that is
  NOT included. Be explicit; at least five items.
- Assumptions: each one stated so the sponsor can confirm or reject it.
- Constraints: deadline, budget, policies, systems.
- Acceptance criteria: how the sponsor will decide it's done.
- Open questions: anything still unanswered.

RULES: Keep every assumption visible; do not fold assumptions into
deliverables. Use plain language a non-technical sponsor can approve.

The out of scope list does more work than any other section. Every item on it is a conversation you won't have to have in month three. "Out of scope: integration with the billing system" costs nothing to write now and saves an argument later.

Step 4

Review it with the sponsor

Send the draft with the open questions first. Then go through it together, ideally live: sponsors skim documents, but they engage with conversations.

Pay attention to three reactions:

  • "That's obviously included." An item they expected is in your out-of-scope list. That's the point of the list: decide now whether it moves into scope, and if so, whether the deadline or budget moves too.
  • "Just make a sensible assumption." Fine for small things. For anything that changes the size of the work, write down the assumption and get a yes.
  • Silence on the acceptance criteria. If the sponsor can't say how they'll judge it done, you can't finish it. Keep asking.

When it's agreed, record the agreement: an email reply saying "Approved" is enough for small pieces of work. Larger ones may need your organization's formal change or project approval process.

Step 5

Worked example: the client document portal

Fictional request. "Can you just set up a portal so clients can see their project documents? Ideally before the end of the quarter." From the operations director, six weeks before quarter end.

The request analysis surfaces, among others:

  • Undefined terms: "clients" (all 140, or the 12 on active projects?), "documents" (final deliverables only, or drafts and contracts too?), "see" (view, download, upload, comment?).
  • Missing decisions: who uploads documents, who grants and removes access, what happens when a client contact leaves their company.
  • Hidden work: an access review process, a support route for login problems, a policy on what may be shared, and moving existing documents.

The operations director answers four of the questions in a fifteen-minute call. The scope statement that comes out of it:

Objective: Give the 12 clients with active projects self-service access to their final deliverables, reducing document requests to project managers.

In scope: a client area in the existing document platform; one site per active client; read and download access to a "Final deliverables" folder; access granted and removed by the project manager; a one-page client guide.

Out of scope: clients uploading files; drafts and contracts; the other 128 clients; single sign-on with client systems; a branded custom web portal; migration of past projects' documents; integration with billing.

Assumptions: the existing document platform's licensing allows external sharing (confirm with IT); each client nominates up to three contacts.

Acceptance criteria: all 12 clients can sign in and download a test document; access removal tested for one contact; the client guide is approved by operations.

"A portal" became a well-bounded piece of work that fits the quarter. And the director now knows that rolling it out to all 140 clients is a separate decision.

Step 6

Record the agreed scope

Scope statement template
[Request name] — Scope statement v[number], [date]
Requested by: [name, role]        Prepared by: [your name]

OBJECTIVE
[Business outcome, measurable, one or two sentences]

DELIVERABLES
- [concrete thing that will exist]

IN SCOPE
- [work included]

OUT OF SCOPE
- [plausible expectation that is NOT included]

ASSUMPTIONS (confirm or correct)
- [assumption] — confirmed by [name] on [date] / open

CONSTRAINTS
- Deadline: [date, fixed or flexible]   Budget: [amount or none]
- Systems and policies: [items]

ACCEPTANCE CRITERIA
- [observable check]

OPEN QUESTIONS
- [question] — owner [name] — by [date]

Approved by: [sponsor name], [date], [how: email / meeting / signature]

What stays with you: what you commit to, what you push back on, and the conversation with the sponsor that turns a draft into an agreement.

Esc

Saved in this browser

Reading list

Contents

Reference

Keyboard shortcuts

/ or Ctrl K
Search the manual
↑ ↓
Move through search results and index entries
Enter
Open the selected result
← →
Switch discipline tabs; previous / next entry in a workflow card
Esc
Close any dialog
?
Show this list