A weekly operations report should help a founder decide what needs attention next. Your assistant can prepare the facts, reconcile open items and highlight exceptions. You retain the decisions that change priorities, spending or commitments. The report becomes useful when those responsibilities are clear.
A long list of completed tasks can still leave you uncertain about the business. Did a request actually reach the next owner? Is a deadline in danger? Which approval is holding up work? A compact report with evidence can answer those questions without turning every Friday into another meeting.
What belongs in a weekly operations report?
Start with the reporting period and the time the information was checked. Then cover material changes, work at risk, decisions required and next actions. Link to the underlying records for detail. A small business does not need an impressive dashboard if a clear written brief supports the decisions.
| Section | Assistant prepares | Founder reviews |
|---|---|---|
| Changes since the last report | Verified completions and changed commitments | Whether the change affects priorities |
| Exceptions | Blocker, impact, owner and next check | Whether escalation or a tradeoff is needed |
| Decision requests | Question, options, deadline and supporting evidence | Approval, rejection or a request for more information |
| Next period | Planned actions and known dependencies | Capacity and priority conflicts |
This is a proposed working format, not a claim about a particular client’s results. It can form part of a defined complete operations support arrangement, where reporting connects work across tasks, CRM and website activity.
Define the sources before asking for a summary
Agree which tools and records the assistant will check. A task board may show that an item is complete, while the linked document is still awaiting review. A CRM activity may indicate that an email was drafted, without proving it was sent. The reporting process should resolve those differences or mark the uncertainty.
Specify what counts as evidence for each recurring workstream. For content, it may be an approved draft or a verified live URL. For a supplier request, it may be the latest written reply. For a data task, it may be the reviewed file and a record of exceptions. Do not let the same word, “done,” hide different states.
Asana’s official guidance on project status updates describes updates as snapshots: reported task details remain frozen even when the underlying task changes later. Apply that principle to a weekly brief by retaining its reporting date and linking readers to current records.
Turn a blocker into an answerable decision
Compare two hypothetical reporting lines. “Website work is delayed” tells the founder little. “The service page draft is ready; pricing approval is outstanding; please confirm the approved version before the planned review” identifies the dependency and the next decision. The assistant should avoid inventing a completion date when approval timing is unknown.
A useful decision request includes the question, the facts available, any realistic options, the person authorized to decide and the consequence of waiting. The assistant can recommend an option when it falls within the agreed role, but should distinguish that recommendation from an approved instruction.
- Write one clear question for each decision.
- Link to the evidence rather than copying sensitive records into every report.
- Distinguish a confirmed deadline from a proposed target.
- State what can proceed while the item waits.
- Record the decision in the underlying task after the founder responds.
Keep AI summaries attached to checked facts
AI can help organize notes, group similar items or make a report easier to read when its use is approved for the information involved. It should not infer that a message was sent, a payment was approved or a page was published. Those are states that need evidence.
Have the assistant check names, dates, totals and commitments against the source records. Keep “not checked” and “awaiting confirmation” visible when appropriate. A smooth paragraph is less useful than a precise statement of what is still unknown. Avoid placing confidential material into a tool unless the business has authorized that use.
Agree a reporting rhythm that supports action
Choose a cutoff, delivery time and review window that fit the founder’s actual week. State how urgent exceptions reach the owner between reports. A weekly brief should not become a reason to hold a time-sensitive issue until Friday.
Review the format after several cycles. Remove sections nobody uses and add missing decision context. Track whether questions receive decisions and whether those decisions reach the people doing the work. Do not judge reporting only by document length, task counts or a promise of hours saved.
If your needs extend to a coordinated team arrangement, compare Web Morphix’s operations and admin support with the responsibilities you need covered. For direct support, discuss a reporting scope with Maaz: bring an anonymized sample of your current update, the tools involved and the decisions you still have to chase.
Frequently asked questions
Should a weekly update list every task?
Keep the full detail in the work system. Use the report for meaningful changes, exceptions and decisions, with links for readers who need the task-level detail.
Can an assistant choose priorities?
They can apply priorities you have agreed and flag conflicts. Changes that affect external commitments, cost or strategic direction need the authority you specify.
Does reporting require a new tool?
No. A consistent document and reliable source records may be enough. Add reporting software only when it solves an identified need and someone owns its upkeep.
How do I know the report is accurate?
Ask for source links, clear reporting dates and explicit uncertainty. Sample-check important items and reconcile disagreements with the underlying records before relying on the summary.