The findings report
A report written to be used, not filed
Its job is to change what happens next. Everything in it is structured to make that easy.

Structure of the report
Summary for decision-makers
Two pages without jargon: the overall condition, the three to five findings that matter most, and what we recommend doing first.
Ranked findings
Each finding records observation, evidence, consequence, recommended response, rough effort and our confidence. They are ordered by consequence, so the top of the list is where attention should go.
System map
An annotated diagram of components, data flows and external dependencies as they actually exist, marking where risk concentrates.
Sequenced response
A suggested order of work that keeps the system running while it improves, with quick wins separated from structural change.
What we did not examine
A short, explicit list of limits, so that nobody mistakes silence for approval.
How we rate consequence
We avoid traffic-light theatre. Each finding is described by what would realistically happen if nothing changed: lost data, slower delivery, harder hiring, supplier dependency or cost growth. You can then weigh it against your own priorities, which we do not presume to know better than you.
Confidence levels used
- Verified
- We observed it directly in code, configuration or records.
- Inferred
- Strongly suggested by evidence but not directly observed.
- Reported
- Described to us in interviews and not independently checked.
Reports are delivered as a PDF and an editable document, so your team can lift findings into its own planning tools. Diagrams are supplied in an editable format too.
The report belongs to you. You may share it with suppliers, investors or boards as you see fit; we simply ask that it is shared whole rather than in fragments that change its meaning.