Job report-pack-commentary-every-number-traced · revised 12 October 2026
Add the paragraph of commentary to my monthly report, and prove every number in it
Your existing report gains a short commentary where every figure is copied from a computed table and a script proves it. No cause is stated unless you supplied it.
You might be seeing
- The commentary takes an afternoon each month
- A figure in the text no longer matches the table next to it
No passwords, keys, card details or admin invites needed to start.
What usually happened
A model writing about numbers is fluent and can be wrong: it can round differently, swap two columns or state a cause nobody gave it. A wrong total is easy to spot; a wrong sentence is not. The remedy is to take every figure from a computed table and prove it.
Who it’s for: Operations lead or finance manager who writes the 'what changed' paragraph of a monthly report by hand.
Usually starts when: The report goes out with a hand-written paragraph that takes an afternoon and sometimes quotes last month's figure.
The result: Each period's existing report gains a short commentary in which every figure is copied from a computed table and a script proves it. No cause is stated unless you supplied it in a reasons file. A deliberately corrupted table makes the check fail or the text refuse to be written.
Check whether this job fits
Answer these without sending files or logins. Nothing is submitted unless you choose to contact us.
What you get
- The commentary for each of three months
- The trace table
- The checker script and its output
- The top-movers list
- The reasons file template
- Wording rules and thresholds, listed
Included
- One repeatable export with up to six tables
- A short commentary and a computed top-movers list, in a fixed style
- A trace table: each number in the text, and the table cell it came from
- A reasons file that you keep, and the only source of any 'because'
- A checker script, and three months of drafts for you to read
Not included
- Forecasts, advice or board narrative
- Stating a cause you did not supply
- An export that changes shape from month to month
- Personal data
- Sending the report to anyone
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
In all three months of drafts, every numeral in the text matches the cell the trace table names for it (right metric and period) under the stated rounding. One unmatched numeral fails the whole test.
Evidence: The trace table and the checker output.
On 3 tables that you corrupt and we do not see beforehand (swapped columns, a blank month, a sign flip), the checker fails or the text refuses to be written.
Evidence: The three corrupted tables and the results.
Causal words appear only where the reasons file supplies the reason.
Evidence: A script search of the text against the reasons file.
Words such as 'strong' and 'sharp' follow the thresholds listed in code.
Evidence: The thresholds and a check of every such word.
You read the three drafts and accept the style; any rule change is made in writing.
Evidence: Your written acceptance.
Sign-off. You read the three drafts and the trace table, and sign off in writing. Payment follows sign-off. A person on your side still reads each month's text before it goes out.
If it fails. If a check above is not met, you do not pay for this fixed scope. You keep the results and the failures, and we agree whether to stop or re-quote. No surprise work.
When it fits, and when we stop
It fits when
- An existing report built from a repeatable export
- The tables hold no personal data
- A named person reads the commentary each month for the first three months
- You keep a reasons file, even if short
We stop and tell you if
- The export changes shape from month to month
- You want causes worked out rather than supplied
- The report holds personal data that cannot be removed
- You want forecasts or advice in the text
What could go wrong
The job reads copies you send and writes files. It changes nothing in your systems, so there is nothing to revert. Our copies of your files are deleted when the job ends.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| A fluent sentence over-claims, for example 'strong growth' on a small move. | Words such as 'strong' are set by thresholds in code and listed. A word outside the list fails the check. |
| A cause is stated that nobody gave. | 'Because' and 'due to' are allowed only where your reasons file supplies the reason. |
| Your files go to a model provider outside your control. | Before any file is shared we name the provider, its country and its retention terms in writing. Entry jobs run on redacted, synthetic or public copies, or on your own provider account with a key you hold. |
A separate automated reviewer checks the trace table and the corrupted-table cases before hand-over. A named person on your side reads the three drafts and signs off. No person on our side is included unless your agreement names one, and at launch the work is largely automated.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Agree the tables, style, word thresholds and severe errors in writing
- Receive three months of the export and your reasons file
- Build the computed tables and the commentary template
- Run the trace check, your corrupted tables and the three drafts
- Independent review of the trace table and the wording rules
- Hand over the commentary, checker and script; delete our copies
This is a one-off job, not emergency cover or a subscription. We confirm eligibility, the price, a start window and a delivery date before you accept, and work starts only after inputs, a secure handoff route and permissions are in place. Model usage up to a cap agreed in writing is included, and an enquiry creates no charge or booking.
Need to keep it working?
Want this commentary written and checked every month? A monthly service does that.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Explore an ongoing managed lane, or mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- Write the commentary yourself from the table, using the same top-movers list. It is quick if the list is computed for you.
- Microsoft retired the COPILOT cell function in Excel from 14 September 2026. Copilot in Excel is still available through its side pane. support.microsoft.com
- For month-end commentary on variance against budget or the prior period, built from a profit and loss or trial balance, see our month-end commentary job. This job is for any report pack you already produce, for any team.
Questions
Does the AI work out the numbers?
No. Numbers come from code. The model only helps with wording, and a script proves every figure.
Can it tell me why sales moved?
Only if you gave a reason in the reasons file. It will say what moved, not guess why.
Does it send the report?
No. A person on your side reads and sends it.
Send an enquiry
Send us
- Which report, how often, and how many tables
- A past commentary you wrote, with personal data removed
- No real records, personal data or credentials in the first enquiry
Later, once you agree
- Three months of the export, redacted if needed, by an agreed secure route
- Your reasons file for those months
- A named person who reads each draft
- A written cap on model usage
You keep your report and every decision. We work on exports you send by an agreed secure route, return commentary, a checker and a script, and delete our copies when the job ends. We never send the report anywhere.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “report-pack-commentary-every-number-traced” as the subject.