Reporting
Automate Report Writing
The slow part of a report is often explaining what the figures mean. A workflow can prepare that first draft, but it needs clear rules about the period, calculations and claims it can make. Start with checked facts and give the reviewer a way to trace each important sentence back to its source.
Key takeaways
Calculate the facts before drafting the explanation.
Keep each important claim linked to its source and period.
Review meaning and uncertainty before sending the report.
To automate report writing, collect approved source data, calculate the measures consistently, and draft each section from those checked results. Keep source references with the text, flag missing information, and require review before sharing. Use fixed wording for repeatable facts and human judgment for explanations, recommendations and uncertain conclusions.
- Check source data
- Calculate measures
- Draft factual sections
- Review claims and context
- Approve and deliver
Define the question the report must answer
Write down the audience, reporting period and decision the report supports. A weekly service update may need to explain open requests and unresolved blockers. A sales report may need to compare completed orders with a previous period. Give each section a specific purpose so the workflow does not fill the page with descriptions of every available number.
Create a short report specification: section title, source, calculation, comparison period, allowed wording and reviewer. Decide which sections can use fixed sentences and which need interpretation. A missing explanation should remain a question for the owner, rather than becoming a confident guess in the final document.
Prepare a small table of checked facts
Extract only the fields needed for the report. Keep stable record IDs, dates, units and source links. Check duplicate rows, missing values and incomplete periods before calculating totals. Record when the data was collected as well as the period it describes. These dates answer different questions when an export arrives late.
Microsoft documents Power Automate operations for filtering rows, selecting fields and creating tables. These can help prepare a consistent input for a report. Their availability does not establish that the underlying figures are correct; the workflow still needs checks appropriate to your source and business definitions.
Keep calculations outside the writing step. Store the numerator, denominator and result for percentages, and label whether a change is in percentage points or a relative percentage. Let the draft use those approved results instead of asking a writing tool to recreate arithmetic from a long list of records.
Keep the denominator visible in a worked example
Consider an illustrative service report for one complete week. The team received 40 new requests. It resolved 30 of those requests and also resolved five requests carried over from an earlier week. There were 35 resolutions during the week, but only 30 belong to the 40 requests received in that week.
A useful draft says: 40 new requests arrived; 30 of them were resolved by the cutoff, giving a current-week resolution share of 75%. Five older requests were also resolved. Dividing all 35 resolutions by the 40 arrivals produces 87.5%, which answers a different question. Neither figure alone proves that the team became faster.
Store the source IDs behind the two groups and keep the cutoff in the report. If a request closes after the cutoff, it belongs in the next snapshot or a clearly labelled correction. This example illustrates report logic; it is not a customer result or an expected performance target.
Give the draft a controlled structure
For a stable fact, a template may be enough: name the measure, current value, comparison value and period. Add optional sentences only when their conditions are met. If the comparison is missing, leave out the change claim and show what is unavailable. A blank value must not turn into zero by accident.
For more varied prose, provide an approved fact table and explicit instructions about scope. Ask for short factual paragraphs with source IDs attached. Keep customer text and imported notes separate from the workflow instructions. Material inside a source record should be treated as evidence to review, not an instruction to change the report or contact somebody.
Distinguish observation from explanation. A rise in overdue requests is an observation if the counts support it. Saying a new policy caused the rise requires separate evidence. Put unverified explanations into the reviewer notes and leave them out of the approved narrative until the owner can support them.
Review sentences against evidence
Use a claim checklist before approval. For each material sentence, confirm the source, period, units and arithmetic. Check names and dates against the original record. Look for wording that implies a guarantee, a cause or an overall conclusion from a small sample. The reviewer should be able to open the relevant source without searching through an entire export.
Check what the draft leaves out as well as what it says. Missing departments, unclassified rows and late submissions may change the interpretation. Put material gaps near the affected result. A general note at the bottom of a long report is easy to miss.
Let the reviewer accept, edit or reject the draft. Record the approved version and the reason for any changed calculation. If only the wording changes, keep the same fact-table reference. If the facts change, regenerate the affected section and repeat its checks.
Keep approval and delivery as separate steps
Save the approved document with a report ID, period and revision. Confirm the intended recipients and their access before sending a file or shared link. Store the returned delivery reference so a retry can distinguish a failed export from an already-sent report.
If a delivery result is uncertain, check the destination before repeating it. If new information arrives later, create a dated correction that explains the changed measure and preserve the previous version under your normal retention policy. A live dashboard can continue changing while the sent report remains a record of what was known at its cutoff.
Test one report before expanding
Run a small trial with a normal period, a missing source, repeated records, a corrected figure and an interrupted delivery. Compare the draft with the report your team would have written manually. Record review effort, factual corrections and missing context rather than counting generated words as success.
The downloadable worksheet helps define claims and review checks. Share a redacted sample report and the tools behind it if you want a custom workflow planned around your existing process.
Your ready-to-use checklist
0 of 6 checked
Make the next step clear.
Report-writing workflow worksheet
Free templateConnect this with the rest of your workflow
Sources and notes
Sources checked on November 2, 2026.
- Microsoft: work with data operations
Filtering, selecting and formatting structured input before report preparation.
