# Workflow: draft a project weekly report

Organize confirmed progress, open decisions and next actions into a reviewable report.

Updated: 2026-10-05
Desktop 0.5.0-rc.35 · Web 0.5.0-rc.36
Canonical: https://ai.z-group.cn/docs/en/weekly-report/

## Define the scope
Specify the project, reporting dates and time zone, and provide authorized conversation records or source files. Do not treat all unconfirmed workspace discussions as project facts.
## Steps
1. Create a reporting conversation with source scope and cutoff time.
2. Separate completed work, work in progress, open questions, risks and next actions.
3. Require a source for each update. Flag missing dates, owners or completion evidence.
4. Review delays, dependencies and external-sharing scope against the project plan.
5. Save a new document and have the project lead review it before sending.
6. Once the process works, consider a [scheduled task](../automations/) with the same review requirements.
## Copy this request
```text
Draft this project's material-work report for Monday through Friday.
Use sections for confirmed progress, unresolved questions, risks and next actions.
Include sources and dates. Write “Unassigned” for unknown owners; do not assign people yourself.
Separate suggestions from approved decisions.
Return the draft for review and do not send it externally.
```
## Expected result
Readers can distinguish facts, recommendations and open decisions. Actions identify specific work without invented commitments. If no new information exists, say so rather than filling the report with fabricated progress.
## Acceptance
Check project scope, dates, numbers, owners and content intended for external sharing. A successful scheduled run confirms execution, not the report's accuracy.