Systems Audit · Standalone advisory
Understand how the work actually moves before deciding what to change.
A standalone systems audit that maps your current operation, identifies where time and information are being lost, and gives you a practical roadmap for improvement.
The problem
The visible problem is rarely the whole problem.
Most teams can tell you which process feels slow. Very few can point to the place where the time is actually going, because the losses sit between people and between systems, where nobody owns the view.
What stays invisible without a map: where work is waiting, why the same information gets entered more than once, which handoffs quietly produce errors, where knowledge depends on one person being available, and whether automating a step would fix the problem or simply move it somewhere less visible.
Request arrives
Owner clear
Logged by hand
Re-entry, second copy
Waiting on approval
No visibility, no clock
Work completed
Owner clear
Recorded again
Third copy, drift starts
Closed
Reported from copy three
What it is
A clear picture of the operation as it works today.
A structured assessment of how work moves through your business, carried out with the people who do it. It is not a software pitch, and it does not start from an assumption about what the answer will be. The output is evidence you can act on, in your own numbers, whoever ends up doing the work.
How it runs
Six steps, in sequence.
Understand
Review the operation, systems, roles and existing documentation.
Map
Document workflows, handoffs, waiting points and repeated work.
Measure
Use your figures to estimate time, cost, capacity and risk.
Prioritise
Separate urgent problems from lower-value improvements.
Recommend
Produce a practical future-state direction and roadmap.
Present
Walk the team through the findings, assumptions and decisions.
Deliverables
What you leave with
- Executive summary
- Current-state process maps
- Bottleneck and risk register
- Time and cost model with visible assumptions
- Prioritised opportunity list
- Future-state workflow recommendations
- Phased implementation roadmap
- Findings presentation and handover
01 · Current-state process map
02 · Bottleneck and risk register
03 · Time and cost model, with assumptions
Figures shown are illustrative only. Real models use your numbers, with every assumption stated.
Example diagnostic
What the audit records, step by step.
An illustrative enquiry-to-follow-up process. Select any step to see what the audit would document about it. This is what the mapping stage produces, before any decision about tooling has been made.
Select a step. Illustrative example, not a client process.
Enquiry received
Observation
The starting point. The audit records how the enquiry arrives, who sees it first, and what they are expected to do with it. Nothing is flagged here yet.
Recorded as: Entry point, single channel
Evidence: Observation and interview with the person who handles intake
Question raised: Does every enquiry arrive this way, or are there side channels?
Fit
When an audit is the right next step.
- Several people or systems touch the same process
- Work regularly waits between teams
- Information is copied between inboxes, spreadsheets and CRMs
- The business is considering automation but does not know where to start
- A previous technology project treated symptoms rather than causes
- Leadership needs evidence before approving investment
Useful whether or not a build follows.
The audit is designed to stand on its own. You can implement the recommendations internally, take them to another provider, or use them as the basis for a future project. The value is the clarity, not a commitment to a particular tool or supplier.
Questions
Before you enquire.
Is this the same as a discovery call?
No. A discovery call is a short conversation to work out whether we should work together. The audit is a paid piece of advisory work with its own deliverables, carried out over a set of sessions with your team, and it produces documents you keep.
Do we need to be considering AI or automation?
No. The audit is about how work moves, not about a category of software. Plenty of findings are resolved by changing an approval rule, removing a duplicate record, or clarifying who owns a step. If automation is the right answer for something, that comes out of the evidence rather than going in as an assumption.
What information will you need from us?
Access to the people who do the work, a look at the systems involved, any existing process documentation, and whatever figures you already track. If you do not have clean numbers, we work with reasonable estimates and label them as estimates.
Who should participate?
The people who run the process day to day, plus whoever can make decisions about changing it. Operational staff know where the work actually sticks. Leadership sets what counts as an acceptable answer. Both perspectives are needed.
Can our internal team implement the recommendations?
Yes, and many should be implementable without external help. The roadmap is written so that your own team, or any provider you choose, can pick it up and act on it.
Will you recommend specific software?
Only where the work justifies it, and only after the current state is mapped. Where a tool is genuinely the right answer, you get the requirement and the reasoning rather than a single vendor name, so you can run your own selection.
How are estimates and assumptions handled?
Every number in the model is traceable. Figures come from your data where it exists, and from stated assumptions where it does not. Assumptions are written on the page next to the number they support, so you can challenge any of them and see what changes.
What happens after the audit?
You have the findings, the roadmap and the presentation, and the engagement is complete. What you do next is your decision: run it internally, hand it to another provider, or talk to me about building part of it. None of those is assumed.
If the operation feels inefficient but the cause is unclear, start by making the work visible.
A short initial conversation will confirm whether an audit is appropriate. No implementation commitment is required.