Build a weekly status report from updates you already have

Weekly reporting often means rewriting the same updates in different formats. AI can help organize those inputs, but the useful part is preserving what the team actually said. The first version of this workflow uses a short collection template and a draft-only report. It needs no automatic access to internal chat, project management or email.

Before you start

• Updates collected for the same reporting period.
• A simple report template and a named report owner.
• Permission to process the selected business information.

Tools: ChatGPT, Claude, Copilot. Use an assistant approved by your organization. This text-based first version does not require new integrations; account features and data policies still apply.

The workflow, step by step

1. Standardize the inputs

   Ask each contributor for completed work, next work, blockers and decisions needed. Add the project name, reporting period and a source reference. Use ordinary text or an exported table. Keep sensitive personnel and customer details out unless your approved environment permits them.

2. Define the report's audience

   A team lead needs different detail from an executive. Choose an output length, the decisions the reader needs to make, and the threshold for calling something blocked. Avoid a numeric project-health score unless the business has a real definition for it.

3. Draft from the provided updates

   Ask the assistant to group related work while retaining source references. Require completed, planned and blocked states to stay separate. Ask it to expose conflicting updates rather than choosing a version. A statement that an item is ‘nearly done’ should not become ‘complete’.

4. Check the exceptions first

   Review the blocker and decision sections before polishing the introduction. Confirm owners and dates with the source author. If two updates disagree, send a concrete question to resolve the conflict. Keep unresolved issues in the report when they matter to the audience.

5. Publish and maintain the template

   Have the report owner approve the final text. Record recurring missing fields and simplify the input form where needed. Once the manual version is useful, consider a scheduled collection and draft, keeping the same approval and source-reference requirements.

Try it with a sample

Use this synthetic input to see the distinctions your output should preserve.

What a good result should preserve

The draft is complete, but approval is not. The pilot date is conditional. The missing checklist handoff is a blocker to investigate. A good report makes those dependencies visible instead of announcing that onboarding and the pilot are both ready.

A prompt you can adapt

Create a weekly status report using only the updates below. Audience: business owner. Sections: completed this week; next steps; blockers; decisions needed; conflicting or missing information. Keep plans separate from completed work. Preserve the source reference for each substantive point. Do not invent percentages, deadlines or health scores. If two inputs conflict, flag the conflict. End with three questions that would most improve the report.

REPORTING PERIOD: [dates]
UPDATES: [paste approved inputs]

Check the result

• Plans and conditional dates remain conditional.
• Each substantive statement has a source reference.
• Conflicting updates are visible.
• No invented completion percentage or health score.

What to keep in mind

This is an original researched procedure with synthetic inputs, not a measured case study. It does not establish a connection to your internal tools. The report owner is responsible for approving facts and distribution.

Sources & review notes

These sources support the tool context and review principles. The workflow, prompt, and synthetic example are original editorial material.

• Anthropic: Claude Academy

  Primary educational reference for deliberate AI collaboration and review.

• AWS: AI for business operations

  Business-oriented guidance for choosing practical bounded AI workflows.