Our approach
Rank the fixes
Make the findings and recommended next steps clear before committing to a build.
Nexus Advisory
Nov 13, 2026
Turn observations into a decision
A list of problems is only useful if you can decide what to do with it. The existing audit returns a ranked list of findings with a recommended fix for each. That gives the next conversation a concrete starting point.
Keep the evidence visible
An approved fact and an assumption are different inputs. The FIELD GUIDE outline makes that distinction explicit: gather the records behind the path, then separate facts from assumptions. Questions that cannot be answered from the records should remain questions.
Decide what is worth building
A recommendation is not an automatic implementation commitment. You can keep the report or talk through a separately scoped next step. Implementation is priced in a written proposal after the audit, with the audit fee credited toward it.
A useful first read
Read the FIELD GUIDE outline for the questions behind the path, or how it works for the existing choices after the readout. Book the free call to discuss where your own work gets stuck.
What we look at
Start with the findings and the records behind them. Ask why a recommendation should come first, what effort it involves and what still needs checking. Keep a missing fact visible so that a confident-sounding suggestion does not outrun the evidence.
A useful ranking helps the owner choose an action. It does not give every problem the same weight or assume every fix should be built. Some findings need investigation before a recommendation is ready for implementation.
Your artifact: the ranked list
The ranked list connects each finding to a recommended fix and a reason for its place. Include the effort involved, assumptions and missing information. It supports a decision to investigate, act, pause or discuss a separate build. The specific outputs and the records needed are agreed in scope.
Example: ranked-list outline
This is an example outline for discussing the recommendation, not a scored business or a customer result.
- Finding: what the review actually established.
- Evidence: the supporting record and the limit of what it can show.
- Recommended fix: the proposed change or further investigation.
- Reason for priority: why this action should be considered before another.
- Effort and dependencies: the people, information or access the decision still needs.
- Uncertainty: assumptions and unanswered questions that could change the order.
- Next decision and owner: who decides whether to proceed and what check would make that decision useful.
Read across the items before commissioning a fix. If the evidence changes, revisit the order rather than treating the first list as permanent.
Who owns follow-through
The review makes the recommendation and its limits clear. The business owner chooses the next move. Agree a responsible person for the action and a check before it starts. Building is separate work; a ranked list is not a purchase order or permission to change a live system.
Questions about choosing the fixes
Is the top recommendation an automatic build?
No. Keep the report, investigate further or discuss a separately scoped next step. A recommendation supports your decision; it does not make that decision for you.
What if the records do not support a confident recommendation?
Keep the question open and identify the information needed. The existing method separates a missing record from a proven problem.
Do we have to replace our tools?
The recommendation does not commit you to replacing tools or commissioning every fix. Understand the work before deciding what change is useful.
What comes after the ranked list?
The owner can stop, ask their own team to act or discuss building a worthwhile fix. Implementation has separately agreed terms, with your audit fee credited toward it.