A summary that helps someone decide
At the end of the week, a business owner may have plenty of updates and few clear answers. Messages, tasks and documents are available, yet it is still difficult to tell what moved forward, what needs help and which decision should come next. Delegating a weekly summary becomes easier when you define the deliverable before asking someone to gather information.
On October 28, 2026, Asana published a status reporting guide that distinguishes a project's current condition from work accomplished over a period. That distinction is useful: listing activities does not necessarily explain where operations stand today.
This proposal adapts that idea to administrative work in small businesses and real estate teams. It is organizational guidance, with no promises of savings or client results.
Define who will read it
Identify the main reader and the decision they should be able to make afterward. A business owner may need to prioritize outstanding work; a coordinator, identify dependencies; a department lead, request missing information. Trying to answer everyone at the same level of detail can weaken the summary's focus.
Agree on which processes belong in the report and which fall outside it. For example, start with a defined set of administrative tasks rather than collecting every conversation across the company. Both the person preparing the report and the reader should understand its scope.
Define the reporting period and information cutoff as well. A summary of last week and an update prepared today may contain different information. Include both references when necessary to interpret the status.
Choose where each fact is confirmed
Ask for important items to be traceable to an authorized task, file or document. Decide with the team which record takes precedence when two messages conflict and who should resolve the discrepancy.
The person preparing the summary can gather information and flag questions. They should not turn a pending response into confirmation simply to complete a section. When evidence is missing, make that visible and assign the appropriate inquiry.
In a real estate operation, avoid allowing an administrative action to be interpreted as professional approval or a contractual change. The summary communicates information confirmed by responsible parties; it does not replace their decisions or documents.
Agree on what each status means
Microsoft's task progress documentation distinguishes work that has not started, is in progress or is completed. It provides a conceptual reminder that a label needs a shared meaning, even if your team uses another tool.
Define your own reporting criteria. Is a task finished when a document is prepared, delivered or acknowledged by the appropriate person? The answer depends on the work. Make it clear so different stages do not get combined under the same word.
If an activity awaits approval, describe that condition without presenting the task as finished. Also identify who can change the status and what information they need before doing so.
Design a short, repeatable structure
As a working proposal, organize the summary into these sections:
- Position at the cutoff: what the reader needs to know first.
- Confirmed progress: deliverables or milestones with available supporting information.
- Blockers and questions: what prevents progress and who needs to respond.
- Decisions requested: what needs deciding, by whom and by when.
- Next reporting period: planned actions and confirmed owners.
Keep lengthy details in the original records and link what readers need to explore further. Avoid copying an entire conversation when describing its operational consequence is enough.
Atlassian recommends written updates that also record decisions and their rationale, risks and lessons learned. To apply that guidance, preserve the reason for a priority change. The next reader can then understand why the plan changed, rather than simply seeing that a change occurred.
Separate a request from a decision already made
In the decisions section, explain the outstanding question and which work depends on the answer. Avoid vague wording that requires the reader to reconstruct the context. If a date has not been confirmed, mark it as still to be agreed.
When an answer arrives, record the decision in the agreed location and check which actions need updating. Someone reading the summary is not enough: reading, responding and carrying out the work are different events.
Urgent matters need the channel and attention defined by the team. Do not wait for the weekly report to communicate a blocker that requires action before the next cutoff.
Delegate preparation with clear responsibilities
Agree on who gathers information, who confirms it and who authorizes sharing. Define the recipients and what information they need for their work. Linking a file does not mean every recipient needs access to its full contents.
Before starting, provide a reference for the expected format and explain which questions should be escalated. Review the first report with its preparer and give specific feedback: a status without evidence, a decision without an owner or a link to the wrong record.
The goal is to build a shared understanding of the deliverable. The summary does not need to become an assessment of each person's value or a performance measure based solely on the number of closed tasks.
Check whether the summary serves its purpose
After several cycles, ask whether the reader can locate pending decisions, understand blockers and find support for reported progress. Remove unused sections and add context when the same question keeps returning.
If you include metrics, define their source, period and meaning. Do not mix tasks created with tasks completed or compare periods with different scopes without explaining the difference. When data is insufficient, a verifiable description is preferable to an unsupported number.
My Virtual Assistant presents administrative support, transaction coordination and assistance with recurring tasks. Contact its team with the processes you want summarized and your expected format to agree on the scope of support. Business priorities and decisions remain with the people responsible for them.
Sources and information date
Research and editorial cutoff: November 3, 2026. This practical guide draws on a recent publication and official documentation. It does not present market statistics.
- Asana: How project status reports work, date indicated: October 28, 2026.
- Atlassian: Weekly Project Updates, standing guide consulted; no editorial date indicated.
- Microsoft Support: Set and update task progress, official documentation consulted as background on statuses; no editorial date indicated.
- My Virtual Assistant: services and contact, information and links verified November 3, 2026; no editorial date indicated.
