Business & Productivity
Write a Weekly Status Update
Turns your rough weekly notes into a short status update with progress, risks and the decisions you need, ready to send to stakeholders.
- Customizable fields
- 8 fields
Business & Productivity
Turns a project idea and rough notes into a one-page brief with goal, scope, success measures and open questions for sign-off.
Designed for general-purpose AI assistantsPublished November 2026
Fill in the fields and the prompt updates. What you type stays in this page and is never saved or sent.
Turn my notes into a one-page project brief that the people approving it can read in three minutes.
Project name: {{project name}}
Audience for the brief (sponsor, team, client): {{audience}}
Background and why now: {{background}}
What the project should achieve: {{objective}}
Known requirements, constraints, budget and dates: {{constraints}}
People involved and their roles: not yet decided
Anything we have already decided is out of scope: none stated
Write the brief with these sections:
1. Purpose: the problem and why it matters now, in three sentences or fewer.
2. Objective and success measures: one objective, and two to four measures that would show it worked. For each measure give a baseline and a target only if I provided them; otherwise write [baseline?] or [target?].
3. Scope: what is included and what is explicitly not.
4. Approach: the main phases or workstreams, in plain language, with rough sequencing. Do not invent durations that are not in my notes.
5. Roles: who decides, who does the work and who needs to be informed. Mark any role I did not name as [who?].
6. Budget and timeline: only what I gave you, with gaps marked.
7. Risks and assumptions: the three biggest, each with a way to reduce it. Label assumptions as assumptions.
8. Decisions needed to start: what must be agreed, by whom and by when.
9. Open questions: everything you could not fill in from my notes.
Then, before the brief, give me a short "is this ready for sign-off?" check: list anything vague, contradictory or missing that would make an approver hesitate, such as a goal that cannot be measured or a scope with no boundary.
Rules: use only my information. Do not invent figures, names, dates, benefits or approvals. Keep the brief within 450 words. Write in plain language, without buzzwords such as "synergy", "leverage" or "best-in-class".5 required fields are empty and will stay as a {{placeholder}} in the copied text.
Illustrative only. Real answers depend on your input and the assistant you use.
Ready for sign-off? Not yet. Three gaps: (1) neither success measure has a target, and the day-30 measure has no baseline; (2) no owner is named for the content work; (3) the budget is mentioned but without a figure. Brief: Customer Onboarding Refresh Purpose: New customers take a median of 21 days to reach their first successful use, and early churn is highest in that period. Shortening it is expected to reduce early churn. Objective and success measures: Reduce time to first successful use. Measures: median days to first use (baseline 21, target [target?]); share of new customers active at day 30 (baseline [baseline?], target [target?]). Scope: In: welcome emails, in-app checklist, help articles for setup. Out: pricing changes and the mobile app. Approach: 1. Review current onboarding data. 2. Draft and test the new sequence with a small group. 3. Roll out to all new customers. Roles: Sponsor: Head of Customer Success. Delivery: [who?] for content, engineering for the checklist. Budget and timeline: budget [figure?]; launch target end of Q2. Risks and assumptions: Engineering capacity is shared with another project. Mitigation: agree the checklist scope first. Decisions needed: approve scope and name the content owner by the 15th. Open questions: What is the day-30 baseline?
The readiness check at the top is the main value. A brief with visible gaps is more helpful at the start than a polished brief that hides them.
If your organization has a standard brief template, paste it and tell the assistant to follow its headings while keeping the readiness check and the gap markers.
Update the brief when decisions change and note the date. A brief nobody maintains becomes a source of arguments.
Business & Productivity
Turns your rough weekly notes into a short status update with progress, risks and the decisions you need, ready to send to stakeholders.
Coding & Software
Turns a technical decision and the options you weighed into an ADR with context, consequences and the conditions for revisiting it.
Business & Productivity
Sorts a messy to-do list by impact, urgency and effort, challenges what should be dropped and builds a realistic plan for the time you have.