From project notes to the next decision

Make this week’s next decision clear.

A weekly status report summarizes progress, risks, and next actions for a defined period—so your team or client knows what changed and which decisions need help.

Make this with my agent

Bring your notes. Review a draft before sharing.

Explore the method

01
Lead with the decision.
Two extra QA days are proposed, not approved.
02
Show progress honestly.
9 of 12 tasks is 75% of tasks—not launch readiness.
03
Name the open gates.
At risk is not delayed. QA and Legal still need follow-through.

THE REAL HTML · FICTIONAL EXAMPLEView on its own

A worked example, not a customer result. September 2026 dates are sample facts.

Now make it about your work

Your week. Your agent. Your report.

Bring this week’s notes, last week’s update, and the decisions your reader owns.

Start with three things

The audience and reporting period.
Dated progress notes and the previous update.
Open risks, owners, and decisions that need help.

Make this with my agent

You review the facts and access. Nothing is published without your approval.

The method behind the reportFrom activity notes to owned next actions

How do I create a useful weekly status report with an AI agent?

Give your agent dated project notes, the previous update, and the decisions your audience owns. Ask it to separate completed work from expected work, show what changed, and name the next action for each risk. Review the evidence, then share one readable HTML briefing.

What to give your agent

Dated ticket excerpts with an owner and a clear status; omit private comments your audience should not see.
The previous weekly update, so changes are measured against what readers already heard.
Milestones, dependencies, and confirmed dates, including where a date is still only an estimate.
Open questions and decisions, with the person who can resolve each one and the deadline for an answer.
For a client update: agreed scope, acceptance criteria, delivery evidence, and the client's approval contact. Include only authorized source material.

Choose the reader's decision
Start with who needs this update and what they can do with it. A sponsor may need to approve a tradeoff; a delivery team may need a dependency resolved. Tell the agent that purpose before supplying notes. It gives the report a useful filter for deciding what deserves space.
Compare this week with last week
Ask for a short change summary before drafting the report. A ticket moving between internal stages may not matter to a sponsor; a milestone changing from likely to uncertain does. Require the agent to distinguish source-backed changes from its interpretation and flag any conflicting dates.
Turn blockers into actionable requests
For every material risk, include the consequence, owner, next action, and when help is needed. Keep an unresolved decision separate from a general concern. If an owner is absent from the notes, say that ownership needs confirming instead of assigning someone based on a guess.
For clients, report the promise—not the ticket list
Organize the update around agreed milestones: what was delivered, what evidence supports it, what still needs acceptance, and what the client needs to do. Fictional example: 'Checkout built; tests passed; sponsor review pending; launch date unconfirmed' becomes 'Checkout is ready for sponsor review. Technical tests passed, but client acceptance and launch timing remain unconfirmed.' Do not turn a finished build into an accepted milestone or claim customer impact without measured outcomes. Leave internal margins and private comments out of the shared page, while keeping material scope, cost, and schedule risks visible.
Build a short briefing with supporting detail
Lead with overall position, changes, and decisions. Put the work log beneath those sections for readers who want it. Ask for a static HTML page in your saved style, if available, then check the source facts and recipient access before publishing. Label the reporting period prominently.

Keep creating and revising in the agent you already use. Start with a saved artifact style and learn how to update HTML without changing its link.

Use the full promptReady for your agent and your notes

Use the conversation where you already did the work. Only attach material you are allowed to share.

Get the ready-to-copy creation request →

Using only the project materials I provide, create a weekly status briefing for [audience] covering [date range]. Compare with the previous update. Lead with the overall position, meaningful changes, and decisions needed. For each material risk, include its consequence, known owner, next action, and confirmed deadline; mark missing information explicitly. Separate completed work, planned work, estimates, and interpretation. For a client audience, organize by agreed milestones and distinguish delivery, client acceptance, and measured outcomes. Omit internal margins and private comments from the output, not material scope, cost, or schedule risks. Ask for missing acceptance evidence rather than treating silence as approval. Name the approval contact and deadline only when supplied; direct replies to the established email or project workflow, not a form in the artifact. Do not infer progress percentages or invent dates. Keep an optional work log below the main summary. Build readable static HTML without scripts, forms, or live-data claims. Use my saved artifact style if available, prioritizing clear headings and restrained color. Include only audience-safe source notes and links. Show me the draft and flag contradictions for review. Do not publish or change anyone's access without separate explicit approval. If this is a sprint review recap, preserve the Sprint Goal, supplied Definition of Done, done/not-done work, stakeholder feedback and proposed adaptations. Do not mark incomplete work Done or treat feedback as an agreed backlog commitment. The static recap does not replace the collaborative Sprint Review. If I ask for a one-page project summary, produce a concise responsive overview of purpose, current position, next decision and approved evidence links. Do not shrink text to force one printed page. For unapproved work, clarify whether I need a proposal instead; do not recast a proposal as approved progress.

Check before you shareAccuracy, clarity, and permission

Does every completed claim mean completed in the source, rather than started or nearly done?
Are milestones, reporting period, owners, and deadlines accurate and unambiguous?
Can the intended reader identify the decision or next action without reading the work log?
Have private ticket comments, customer details, and unsuitable internal links been removed?
For client reports, is delivery separate from acceptance and measured impact, with material risks still visible?

When HTML fits

Use an HTML briefing when readers need a portable summary with readable sections and links to evidence. A dated snapshot can be shared without making everyone navigate the project tracker.

When another format fits better

Keep the tracker as the source of truth for task assignment and changing status. If its existing report already answers your client's questions, share that rather than maintain a second copy. Use the established email or project workflow for approval records. This HTML report is not a live dashboard, and publishing it does not automatically refresh its contents.

What we started withThe same facts, as an email

Fictional project email

Northstar onboarding refresh — September 1–5 update

Hi product lead and delivery team,

The September 18, 2026 launch target is at risk, but has not moved. We have completed 9 of the 12 planned sprint tasks (75%), compared with 6 of 12 (50%) last week. These are sprint task counts, not a prediction of overall project completion. This week the welcome email copy was approved, the onboarding checklist was implemented, and the analytics event names were agreed.

Two dependencies remain. Mobile QA has 3 open defects; Eli owns fixes and retesting by September 10. Severity and user impact still need assessment. Legal approval of the consent wording is outstanding; Noor expects a response September 9, and launch depends on that approval.

Decision needed: could the product lead approve two additional QA days by September 8? This is proposed staffing, not an approved change. Noor will follow up on September 9, Eli will retest by September 10, and I will share a launch readiness check September 11.

We do not yet have customer outcome measurements, budget figures, or an updated launch commitment.

Maya, project lead

Inspect the HTMLOne self-contained file

The example is sanitized and isolated from this site. No scripts, forms, or live data.

<!doctype html>
<html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><title>Northstar weekly update · September 5, 2026</title><style>
*{box-sizing:border-box}html{color-scheme:light}body{margin:0;background:#f2efe6;color:#192c30;font:16px/1.55 system-ui,sans-serif}main{max-width:1120px;margin:auto;padding:clamp(20px,5vw,60px)}h1,h2,h3,p,figure{margin:0}h1{max-width:850px;font-size:clamp(36px,6.5vw,76px);line-height:1.04;letter-spacing:-.045em;font-weight:750;margin:30px 0 24px}h2{font-size:clamp(25px,3.4vw,38px);line-height:1.15;letter-spacing:-.025em}h3{font-size:20px;line-height:1.3}p+p{margin-top:12px}.eyebrow{font:700 11px/1.6 ui-monospace,monospace;letter-spacing:.12em;text-transform:uppercase}.masthead{display:flex;justify-content:space-between;gap:12px;flex-wrap:wrap;border-top:5px solid #192c30;border-bottom:1px solid #192c30;padding:14px 0}.brand{font-size:16px;letter-spacing:.14em}.status{display:inline-block;background:#fae0ad;border:1px solid #86521c;padding:4px 10px;color:#65400e;font-weight:700;font-size:12px}.intro{font-size:20px;max-width:670px}.byline{font-size:13px;margin-top:20px;color:#4c5d60} .decision{margin-top:32px;display:grid;grid-template-columns:1fr auto;gap:28px;align-items:center;background:#192c30;color:#fffaf0;padding:clamp(22px,4vw,40px);border-left:7px solid #ee9b71}.decision h2{margin:12px 0 18px;max-width:530px}.decision p{max-width:580px}.decision .eyebrow{color:#ffd0ad}.request-number{font-size:clamp(56px,9vw,100px);font-weight:750;line-height:1;letter-spacing:-.065em;color:#ffd0ad}.request-caption{display:block;font-size:12px;line-height:1.4;letter-spacing:0;max-width:95px;margin-top:10px}.section-head{display:flex;justify-content:space-between;align-items:baseline;flex-wrap:wrap;gap:12px;margin-bottom:26px}.section-head .eyebrow{color:#526266}.section{margin-top:48px;padding-top:20px;border-top:1px solid #aab5ad}.sprint-layout{display:grid;grid-template-columns:1.2fr 1fr;gap:40px}.comparison{padding:24px;background:#fffdf7;border:1px solid #b7c1b9}.bar-label{display:flex;justify-content:space-between;gap:10px;font-size:14px;margin-bottom:10px}.bar-label strong{font-variant-numeric:tabular-nums}.task-strip{display:grid;grid-template-columns:repeat(12,minmax(0,1fr));gap:4px;height:34px;margin-bottom:22px}.task-strip span{border:1px solid #a6b2ae;background:#eeeee7}.task-strip .done{background:#235c51;border-color:#235c51}.previous .done{background:#718a81;border-color:#718a81}.legend{font-size:12px;color:#405454}.changed{list-style:none;padding:0;margin:18px 0 0}.changed li{display:grid;grid-template-columns:28px 1fr;gap:10px;padding:12px 0;border-bottom:1px solid #c3cdc4}.check{color:#235c51;font-size:20px;font-weight:800}.fine{font-size:13px;color:#4c5d60}.source-limit{margin-top:16px;max-width:750px}.gates{border-top:1px solid #aab5ad}.gate{display:grid;grid-template-columns:48px 1.2fr 1fr;gap:20px;padding:24px 0;border-bottom:1px solid #aab5ad}.gate-number{font:400 38px/1 Georgia,serif;color:#a54627}.gate h3{margin:8px 0 12px}.gate .owner{border-left:3px solid #c0cbc1;padding-left:20px}.owner strong{display:block;margin:8px 0}.owner p{font-size:14px}.timeline{display:grid;grid-template-columns:repeat(5,minmax(0,1fr));list-style:none;padding:0;margin:0;gap:0}.timeline li{border-top:3px solid #c3cdc4;padding:18px 16px 0 0;position:relative}.timeline li:before{content:"";display:block;width:11px;height:11px;background:#192c30;border:2px solid #f2efe6;position:absolute;top:-7px;left:0}.timeline .target{border-top:3px dashed #9a6c26}.timeline .target:before{background:#9a6c26}.timeline .date{font-size:24px;font-weight:700;letter-spacing:-.035em}.timeline p{font-size:13px;margin-top:8px}.timeline strong{display:block}.timeline .eyebrow{font-size:10px;letter-spacing:.04em}.caveat{display:grid;grid-template-columns:1fr 2fr;gap:24px;background:#e5e9df;padding:24px;margin-top:38px}.caveat p{font-size:14px}footer{border-top:1px solid #aab5ad;margin-top:40px;padding-top:20px;font-size:12px;color:#4c5d60}footer p+p{margin-top:8px}
@media(max-width:700px){.sprint-layout{grid-template-columns:1fr;gap:24px}.gate{grid-template-columns:34px 1fr;gap:12px}.gate .owner{grid-column:2}.timeline{grid-template-columns:1fr}.timeline li,.timeline .target{border-top:0;border-left:3px solid #c3cdc4;padding:0 0 26px 24px}.timeline .target{border-left-style:dashed;border-left-color:#9a6c26}.timeline li:before{top:9px;left:-7px}.timeline p{margin-top:4px}.timeline .date{font-size:22px}.caveat{grid-template-columns:1fr;gap:14px}.decision{grid-template-columns:1fr}.request-number{display:none}.section{margin-top:36px}.comparison{padding:18px}.task-strip{gap:3px}.masthead{align-items:center}}
@media print{body{background:#fff;font-size:11px}main{max-width:none;padding:12px}h1{font-size:38px;margin:18px 0}h2{font-size:23px}.intro{font-size:15px}.decision{background:white;color:#192c30;border:2px solid #192c30;padding:18px}.decision .eyebrow,.request-number{color:#192c30}.request-number{font-size:60px}.section{margin-top:24px}.decision,.comparison,.gate,.timeline li,.caveat{break-inside:avoid}.task-strip .done{background:#235c51;print-color-adjust:exact}.previous .done{background:#718a81}.sprint-layout{gap:24px}.gate{padding:16px 0}.timeline{display:block}.timeline li,.timeline .target{border-top:0;border-left:2px solid #aab5ad;padding:0 0 12px 18px}.timeline li:before{top:7px;left:-6px}.timeline .date{font-size:17px}.caveat{background:white;border:1px solid #aab5ad}footer{font-size:10px}}
</style></head><body><main>
<header><div class="masthead"><p class="eyebrow brand">Northstar / Fieldnotes</p><p class="eyebrow">Weekly update · September 1–5, 2026</p></div><h1>Three more tasks done.<br>Two launch gates open.</h1><p class="intro">The onboarding refresh is moving forward. Mobile QA and consent approval still put the September 18 launch target <span class="status">At risk</span></p><p class="byline">Prepared by Maya, project lead · For the product lead and delivery team</p></header>
<aside class="decision" id="decision"><div><p class="eyebrow">Product lead · Decision needed by September 8</p><h2>Approve two additional QA days.</h2><p>This staffing change is proposed, not yet approved. Mobile testing is one of the two open launch dependencies.</p></div><div class="request-number" aria-hidden="true">+2<span class="request-caption">QA days requested</span></div></aside>
<section class="section" id="sprint"><div class="section-head"><h2>Momentum, measured.</h2><p class="eyebrow">01 / Current sprint</p></div><div class="sprint-layout"><div class="comparison" role="group" aria-label="Sprint task comparison"><div class="bar-label"><span>Last week</span><strong>6 / 12 · 50%</strong></div><div class="task-strip previous" aria-hidden="true"><span class="done"></span><span class="done"></span><span class="done"></span><span class="done"></span><span class="done"></span><span class="done"></span><span></span><span></span><span></span><span></span><span></span><span></span></div><div class="bar-label"><span>This week</span><strong>9 / 12 · 75%</strong></div><div class="task-strip" aria-hidden="true"><span class="done"></span><span class="done"></span><span class="done"></span><span class="done"></span><span class="done"></span><span class="done"></span><span class="done"></span><span class="done"></span><span class="done"></span><span></span><span></span><span></span></div><p class="legend">Each segment = one planned task.<br>Filled = complete; outlined = remaining.</p></div><div><h3>What changed this week</h3><ul class="changed"><li><span class="check" aria-hidden="true">✓</span><span>Welcome email copy <strong>approved</strong></span></li><li><span class="check" aria-hidden="true">✓</span><span>Onboarding checklist <strong>implemented</strong></span></li><li><span class="check" aria-hidden="true">✓</span><span>Analytics event names <strong>agreed</strong></span></li></ul></div></div><p class="fine source-limit">This measures task completion in the current sprint, not overall launch readiness. The twelve-task denominator is the same in both snapshots.</p></section>
<section class="section" id="gates"><div class="section-head"><h2>Two gates. Neither cleared.</h2><p class="eyebrow">02 / Launch dependencies</p></div><div class="gates"><article class="gate"><span class="gate-number" aria-hidden="true">01</span><div><p class="eyebrow">Mobile QA · Open</p><h3>3 defects need fixing and retesting.</h3><p class="fine">Severity and user impact are not yet assessed.</p></div><div class="owner"><p class="eyebrow">Owner → Next action</p><strong>Eli · September 10</strong><p>Fix and retest mobile defects by the target date.</p></div></article><article class="gate"><span class="gate-number" aria-hidden="true">02</span><div><p class="eyebrow">Consent wording · Awaiting Legal</p><h3>Approval is still outstanding.</h3><p class="fine">Launch depends on this approval. An expected response is not a confirmed approval.</p></div><div class="owner"><p class="eyebrow">Owner → Next action</p><strong>Noor · September 9</strong><p>Follow up on consent wording. Legal’s response is expected, not guaranteed.</p></div></article></div></section>
<section class="section" id="next"><div class="section-head"><h2>The next checkpoints.</h2><p class="eyebrow">03 / September 2026</p></div><ol class="timeline"><li><span class="date">Sep 08</span><p class="eyebrow">Decision due</p><p><strong>Product lead</strong>Consider the two additional QA days.</p></li><li><span class="date">Sep 09</span><p class="eyebrow">Response expected</p><p><strong>Noor</strong>Follow up with Legal.</p></li><li><span class="date">Sep 10</span><p class="eyebrow">Retest target</p><p><strong>Eli</strong>Fix and retest mobile.</p></li><li><span class="date">Sep 11</span><p class="eyebrow">Readiness check</p><p><strong>Maya</strong>Share the launch readiness check on September 11.</p></li><li class="target"><span class="date">Sep 18</span><p class="eyebrow">Target · at risk</p><p><strong>Launch</strong>Date unchanged; QA and consent approval remain dependencies.</p></li></ol><p class="fine source-limit">Sequence shown, not a time-scale chart. These are decisions, expectations and targets—not a new launch commitment. The launch is at risk, not delayed yet.</p></section>
<aside class="caveat"><h3>What we cannot say yet</h3><p>No customer outcome measurements, budget figures, or revised launch commitments are available. More tasks completed is progress—not proof of launch readiness.</p></aside>
<footer><p>Source: the fictional project notes accompanying this example. All dates are in 2026.</p><p>Fictional worked example by share/artifacts. Names, dates, and figures are invented for demonstration. Static snapshot; no live data or automatic updates.</p></footer>
</main></body></html>

Another example: a portal launch updateA separate fictional case, from notes to next action

A launch update with one clear decision

An illustrative team is preparing a customer portal launch. Its notes include finished interface work, an outstanding permission review, and two possible launch scopes.

The original notes

Updated navigation. Fixed eight issues. Continued permission testing. Met with operations. Launch discussion ongoing.

Position

Core interface work is complete. Launch timing remains unconfirmed because permission testing is incomplete.

Changed this week

The navigation milestone is complete; the permission review remains open. These are separate outcomes, not one overall completion claim.

Decision needed

Choose whether to launch the core portal first or wait for the additional account roles.

Next action

The project lead will confirm the launch option after the security reviewer supplies the remaining test results.

Watch next week

Report the permission review result and the confirmed scope. Do not carry forward an unverified launch date.

The useful unit is not an activity. It is a change, its consequence, and what someone should do next.

Questions, adaptations & sourcesGo deeper when you need to

How do I adapt this into a client progress report?

Set the audience to your client and provide the agreed milestones, delivery evidence, and acceptance state. Lead with what changed for them and the response you need, not internal ticket activity. A delivered feature can still be awaiting client acceptance; neither proves a customer outcome. Verify sensitive details and evidence links before sharing. Keep approval replies in your existing email or project workflow—the page does not collect sign-off.

Should I include everything the team did?

Keep a detailed work log only if it helps the audience. The opening should explain material changes and needed actions. Effort can be important context, but a long activity list does not establish whether the project is on course.

Can I update the same report link each week?

You can update a published share/artifacts page at the same URL. Change its reporting period and review the replacement. If readers need a historical record, keep dated snapshots separately rather than overwriting the only copy of an earlier update.

What if the notes disagree about project status?

Ask the agent to list the disagreement and its sources. Confirm the correct status with an accountable person. Until then, label it unresolved; choosing the most optimistic note would hide precisely what a status report should make visible.

A sprint review recap

Help stakeholders inspect the Sprint Goal, completed work and feedback after a working session. A reading page supports the review; it does not replace the conversation or turn suggestions into agreed backlog work.

Fictional inputs: Fictional Sprint 8 aimed to improve search. Search changes meet the team's supplied Definition of Done. Export work is incomplete. Stakeholders suggested checking keyboard access next; the team has not agreed that follow-up. No delivery date was agreed.

A clearer result: Lead with the search outcome against the Sprint Goal. Keep export explicitly incomplete. Label keyboard-access work as stakeholder feedback awaiting a team decision, not committed work. Keep the absent delivery date unresolved.

A one-page project summary

Treat one page as a request for a concise reading experience, not tiny typography or forced print pagination. Summarize current work here; use a project proposal when the reader must authorize work that has not been approved.

Fictional inputs: Fictional portal project: core navigation complete; permission testing incomplete; launch date unconfirmed. The sponsor must choose core-only scope or wait for extra account roles after receiving the remaining test results. The project tracker retains detailed tasks.

A clearer result: Use four short sections: purpose, present position, decision needed and evidence to check. Keep the incomplete permission review beside the launch question. Link to the authorized tracker rather than copying every task; no invented launch date or completion score.