Formatting a report should make its information easier to use while preserving its meaning. Numbers, units, dates, approval status, and action owners need as much attention as headings and spacing.
This guide uses a messy fictional management note and a complete formatted text example. The examples show the intended transformation; they are editorial examples rather than a recorded product benchmark.
Decide what may change
Separate the formatting task from the writing task. A formatting brief might allow headings, tables, consistent date presentation, and shorter paragraphs while keeping the original facts and commitments fixed.
If the source says a budget has been requested, the formatted version should not say it has been approved. If a metric is missing, a well-designed table should identify the gap rather than make up a value to complete the row.
For this example, preserve:
- The company, October 2026 reporting period, and AUD currency.
- October revenue of A$126,000 and September revenue of A$120,000.
- October operating costs of A$94,500 and September costs of A$84,000.
- Seventeen on-time projects out of 20 due in October, and the 95% target.
- The proposed A$3,000 support request and its unapproved status.
- The three action owners, their responsibilities, and their due dates.
The source also says the cause of the cost increase is unknown. Keep that uncertainty in the formatted report.
Give the formatting task a clear boundary
Use a prompt like this with your own source text:
Format the supplied management note as a concise report.
Improve headings, spacing, paragraphs, and tables.
Do not change facts, commitments, owners, dates, or approval status.
Use these sections:
1. Performance
2. Delivery notes
3. Decision requested
4. Actions
5. Information not supplied
Use AUD consistently. Expand the supplied dates for readability.
Label missing values as not supplied.
You may calculate the on-time rate as 17 divided by 20,
but do not add other derived metrics or explanations.
Do not invent a quotation, forecast, source, or approval.
You can develop the report in the NextDocs document workspace. Keep the original note available so that you can compare the result with it. The prompt sets a constraint; you still need to check that the result follows it.
Build a table that retains units and gaps
The source note combines several values in a sentence. A table can make their relationship clearer:
| Metric | September | October |
|---|---|---|
| Revenue | A$120,000 | A$126,000 |
| Operating costs | A$84,000 | A$94,500 |
| On-time projects | Not supplied | 17 of 20 due, or 85% |
| On-time delivery target | Not supplied | 95% |
The October on-time rate is 17 divided by 20. The source does not supply the September project figures or its target, so those cells remain marked as not supplied. Do not borrow a plausible value from another document without identifying that source and approving the change.
If a table becomes too wide, reduce its number of columns or divide it by topic. Essential units and comparison periods should remain readable.
Preserve the status of decisions
The messy source says:
REQUEST, NOT APPROVED: up to3000 temporary specialist support
in first two weeks of november.
A formatted version could read:
Consider up to A$3,000 of temporary specialist support for the first two weeks of November. This request has not been approved.
The currency is made explicit and the spacing is improved. The amount remains a maximum proposed cost. The formatted version should not turn it into actual spending, a fixed commitment, or a completed action.
Status words such as proposed, approved, completed, and estimated carry meaning. Include them in the review even when the numbers themselves match.
Put each action next to its owner and date
A short action table reduces the effort required to find a responsibility:
| Owner | Action | Due |
|---|---|---|
| Delivery Lead | Confirm client review dates and escalation contacts. | November 10, 2026 |
| Operations Lead | Prepare a two-week capacity plan. | November 10, 2026 |
| Finance Lead | Review operating costs and the support request. | November 12, 2026 |
Do not combine two owners into a generic “team” if the source assigns separate responsibilities. If an owner or due date is absent, flag it for a decision rather than silently adding one.
Review meaning before appearance
Compare the formatted version with the original in two passes. First check facts and status: values, units, dates, names, owners, missing information, and claims about cause and effect. Then check presentation: headings, table labels, paragraph length, spacing, and page breaks.
The formatted example keeps the delivery observations separate from the cost question. The source describes late approvals and a scheduling conflict, but it does not establish why operating costs increased. Formatting should not create that explanation.
If you want analysis as well as formatting, make it a second task with its own source requirements. The monthly management report guide shows a broader example that includes additional calculations and a management decision.
Ask for precise revisions
Once the facts are checked, make a revision request that names the change:
Shorten the delivery-notes section to two sentences.
Keep the two late approvals, the separate scheduling conflict,
and the unknown cause of the cost increase explicit.
Leave the performance table, decision status, actions and dates unchanged.
Review the changed section and the fixed fields afterward. A request to “make it more professional” gives the model less guidance about what must remain stable.
Check the exported document
Open the exported file in the application the reader will use. Inspect the widest table, the longest heading, text selection, page breaks, and a small revision. A correct preview inside one application does not establish identical behavior in another.
Current NextDocs Tasks fixed-page Word and Google Docs exports preserve measured text and artwork, with text arranged as positioned lines. Significant rewrites or font changes in the destination can require layout repair. If your reviewer needs a freely reflowing document for extensive editing, test that requirement with a short sample first.
For an approved visual version, inspect the PDF before sharing it. The export overview explains available formats; check the behavior of the actual artifact you are using.
Keep a repeatable formatting brief
Save the original input, the formatting instructions, and the approved result. For the next report, keep the structural rules and replace the source facts. This gives the reviewer a clear basis for checking whether the transformation preserved what mattered.
Try the source note, compare it with the formatted example, and format your own document in NextDocs. Approve the facts and commitments before treating the layout as finished.
