A useful project brief names the result, the people involved, the limits and what “finished” means. Ask AI to expose missing decisions before it creates a detailed plan.
When a project feels vague, a structured brief can help you make the next decision. AI can organise the information you supply, but it cannot confirm another person’s agreement or know constraints you have not described.
A practical workflow.
Define the result
Describe the deliverable and who will use it. Add a practical completion test: for example, a draft approved by the project owner rather than “improve communication.”
Separate facts from assumptions
List the confirmed deadline, resources and responsibilities. Put unresolved details in an assumptions list and ask which need an answer before planning.
Break the work into outputs
Request a short sequence of milestones, each with an output and a dependency. Ask for an initial task small enough to complete in one work session.
Review with the people involved
Check the plan with the people responsible for the work. Update dates and owners only after agreement; an AI-generated plan does not assign anyone a commitment.
READY TO MAKE YOURS
Start with this prompt.
Turn these project notes into a brief: [notes]. Include objective, audience, deliverables, scope exclusions, dependencies and acceptance criteria. Label unknown budget, dates and approvals as questions. Explain conflicts in the notes and do not silently resolve them. End with the essential decisions needed to start.
Replace the brackets. Leave out private details. Check the response.
ILLUSTRATIVE EXAMPLE
A clearer request.
A VAGUE STARTPlan our website project.
A CLEARER BRIEFDraft a one-page brief for updating five support pages. The owner is our support lead; the deadline is not confirmed. List deliverables, approval questions and the first three actions.
The prompt makes missing decisions visible instead of inventing a complete schedule.
Before you use the result.
- Every milestone has an output.
- Dates and owners are confirmed or clearly provisional.
- The completion test is observable.
- Dependencies and unresolved questions are visible.
A few useful answers.
Should I ask for a full plan immediately?
If the goal or constraints are unclear, start with questions and a short brief. A detailed plan becomes useful after the important decisions are made.
Can AI estimate the timeline?
It can propose a rough sequence from your information. Check estimates against the team’s availability and experience before treating them as commitments.
PUT THE GUIDE TO WORK
ChatGPT for project management: build a plan people can confirm
Use ChatGPT for project management tasks such as clarifying scope, organising dependencies and drafting a status update. Begin with a small project brief and confirmed constraints. A plan is ready to use when the people doing the work can recognise their tasks and agreements in it.
Define done before dividing the work
A list of activities is easier to make than a usable definition of done. For a tutorial page, “write content” could mean an outline, a reviewed draft or a published page. State the deliverable, who accepts it and what the acceptance check involves. Then list the work needed to reach that point. Keep optional additions in a separate list so they cannot quietly expand the first release. If acceptance is unknown, the next action is a question, not a longer task list.
Plan dependencies instead of filling every date
A review cannot finish before the reviewer receives the draft. A handover can wait on access or an approval even when the file itself is ready. Mark those dependencies before choosing dates. Ask each owner to confirm the work and capacity; distinguish their commitment from your estimate. When a dependency slips, show the affected tasks and the decision needed. That makes the plan easier to update without pretending the original timetable was certain.
Open a card, copy the prompt and replace the brackets with your own details. Each card includes a follow-up and a check before you use the answer.
SITUATION 01 ↗
Turn a vague request into scope
Define the deliverable before committing to the work.
Open the prompt +
Turn [request] into a project brief. Confirmed constraints: [constraints]. Known acceptance requirements: [requirements]. Separate deliverable, included work, excluded work and unresolved questions. Do not invent an approver or assume optional features are required. Ask for the missing information that would change the scope.
Refine the next draft
Give me a smaller first version that still meets the stated acceptance requirements. Explain what is deferred.
Before you use it
Have the requester confirm the boundaries before treating the brief as agreed.
SITUATION 02 ↗
Map the work in a useful order
Make blockers visible before choosing dates.
Open the prompt +
Arrange [work items] into a dependency map for [deliverable]. Available people and capacity: [facts]. Identify which tasks can run independently and which need another output or approval first. Keep owners proposed unless my notes show agreement. Do not assign calendar dates I have not supplied.
Refine the next draft
Which single unresolved dependency is most likely to stop the next step? Draft a question to clarify it.
Before you use it
Check the sequence with the people who know the work.
SITUATION 03 ↗
Write an honest project status update
Give the reader progress, a blocker and a decision.
Open the prompt +
Write a project update from [finished work], [remaining work] and [blocker]. State what changed since the last update, the effect on the deliverable and the decision or input needed. Distinguish confirmed dates from estimates. Do not translate tasks started into tasks finished or invent a percentage complete.
Refine the next draft
Reduce it to a short summary and three bullet points without losing the decision needed.
Before you use it
The recipient should be able to tell what action, if any, you need from them.
SITUATION 04 ↗
Assess a new request
Show what extra work changes before agreeing to it.
Open the prompt +
Compare [new request] with [agreed scope]. Known effort and dependencies: [facts]. Identify additions, affected tasks and unresolved estimates. Draft two options: keep the current release focused or include the change after confirming its effect. Do not approve the change, set a price or promise a new date.
Refine the next draft
Draft a neutral message asking the requester to choose between those options once the missing estimates are confirmed.
Before you use it
A useful change note explains the trade-off; it does not silently rewrite the agreement.
The examples below are original, illustrative edits using fictional situations. They show the checks to make, rather than promising what an AI tool will produce.
Copy a small project brief
Deliverable: [one outcome] Definition of done: [observable acceptance check] Approver: [confirmed person or not yet confirmed] Included / excluded: [scope] Work items: [task | output | proposed owner | dependency] Confirmed constraints: [dates, access and capacity] Estimates: [duration + assumptions] Risks: [uncertainty | signal | response] Next decision: [what must be confirmed before starting]
WORKED EXAMPLE
An activity is not a finished deliverable
Illustrative task: publish one tutorial page after content review and a mobile check. The first plan ends when writing is complete.
FIRST DRAFTWrite the tutorial. Done.
AFTER CHECKINGDraft the tutorial → content review → address confirmed edits → check the mobile page → receive approval → publish. Done means the approved page is available at the agreed URL.
What changed
The revision identifies the acceptance path. Each stage still needs a confirmed owner and any required access.
WORKED EXAMPLE
Protect the first release when a request grows
Illustrative change: a requester adds a downloadable workbook to a single-page tutorial project.
FIRST DRAFTAdd the workbook and keep the same delivery date.
AFTER CHECKINGThe workbook adds writing, layout and download testing. Keep the page-only release, or confirm the extra work and dependencies before agreeing a revised release plan.
What changed
The plan makes the new work visible instead of assuming it has no effect. It gives the requester a concrete choice.
Try it with your own task.
Use the brief to confirm one scope boundary, one owner and the next dependency. Then turn the confirmed work into a realistic weekly plan.
GO DEEPER / 4 FREE TEMPLATES
Prompts for this part of the task.
Use a template for the step you are working on. Add the required inputs, then check the result against your source material.
Browse the task-guide directory ↗
Use a small workflow that you can repeat.
- Choose the decision or action the output should support.
- Remove confidential details and provide the approved source material.
- Ask for a draft with uncertainties separated from confirmed facts.
- Review owners, dates, calculations and commitments before sharing or acting.
Keep in mind: Do not paste client secrets, credentials or restricted internal documents. A clear-looking table does not make its numbers or ownership assignments correct.
A concise status update
Make progress and blockers easy to scan.You get: Short progress update with blockers+
COPY. PERSONALISE. CHECK.
Turn these project notes into a weekly update for [audience]: [notes]. Use four headings: completed, next, blockers and decisions needed. Keep it under [length] words. Preserve dates and evidence. Distinguish work in progress from finished work and label estimates. Do not invent progress percentages or imply approval. End with the one decision that most affects the next step.
Example input
Testing has started, one dependency is blocked and the launch date is still an estimate.
Illustrative scenario, not a generated or verified AI result.
Then ask
Rewrite for a manager who has one minute to read it.
Before using the answer
Check that completion claims, risks and decision requests are accurate.
Clarify a vague work request
Turn an unclear brief into a decision-ready scope.You get: Scope, completion criteria and questions+
COPY. PERSONALISE. CHECK.
I received this request: [request]. My role is [role], the intended reader or user is [audience], and the known constraints are [time, resources and limits]. Separate what is explicitly requested from what is still undefined. Draft a short scope with the deliverable, what completion means and what is outside scope. Ask at most three questions that would change the work. Mark proposed assumptions for approval; do not treat them as agreements.
Example input
Request: 'Refresh our onboarding document.' Audience: new support staff. Available: two hours. The approved source is last month's checklist.
Illustrative scenario, not a generated or verified AI result.
Then ask
Use my answers to write a five-line confirmation message I can send before starting.
Before using the answer
Check that the scope fits the available time and does not add unapproved deliverables.
Prepare a useful handover
Give the next person enough context to continue.You get: Task-by-task handover and return checklist+
COPY. PERSONALISE. CHECK.
Build a handover from my notes: [notes]. The cover period is [dates] and the person taking over knows [background]. Group the handover by active task. For each, show current state, next action, named owner if supplied, deadline if confirmed and a link placeholder for the source. Put blocked work and decisions needing approval first. Label absent details 'not provided'. Finish with a short return-to-work checklist.
Example input
Notes: draft guide sent to Jo; waiting for review. Webinar slides due 18 October; Priya owns design. Cover period: 12–16 October.
Illustrative scenario, not a generated or verified AI result.
Then ask
Read this as the covering colleague. List the three missing details most likely to stop you making progress.
Before using the answer
Verify access to linked documents and confirm that each named person has agreed to the responsibility.
Turn a routine into a usable checklist
Make a recurring process easier to follow.You get: Ordered process checklist with checks+
COPY. PERSONALISE. CHECK.
Convert this process into a checklist for [reader]: [process notes]. Include prerequisites, ordered actions and a visible completion check for each action. Mark decision points and explain what to do when a required input is missing. Separate actions explicitly described from suggestions that need review. Do not invent access, software controls or organisational policies. End with questions that a first-time user would need answered.
Example input
Process: collect approved event title and date, duplicate last week's email draft, replace details, ask the editor to review, schedule only after approval.
Illustrative scenario, not a generated or verified AI result.
Then ask
Walk through the checklist using a missing event date. Show where the process pauses and whom the notes say to ask.
Before using the answer
Try the checklist once against the actual tools and confirm approval steps are accurate.
Keep learning from original sources.
These sources inform the workflow and checks; the templates above are original LifestyleGlide prompts.
