First look at Hugo
ESB audits are
getting an upgrade.
Hugo helps you manage findings, corrective actions and evidence across your sites — with the same ESB audit expertise behind the process.
ESB audits are
No change to your audit standards
Built with ESB auditors
Previews shared first to the list
A note from Ben Gardner
Why we're introducing Hugo
Ben explains why ESB built Hugo, what improves for clients and what stays the same. A practical update — not a sales pitch.
Why we're introducing Hugo
Audit findings only matter if the actions get done.
For site teams
Clearer actions. Fewer missed deadlines. Less digging through reports.
.svg){kind=icon}
For compliance teams
Findings, evidence and corrective actions in one place.
For operations leaders
See which sites need attention before small issues become bigger ones.
For senior leaders
Better visibility of recurring issues and progress across the estate.
The important part
What changes. What stays the same.
What changes
Your support from the ESB team
Evidence is easier to manage
Site progress is easier to see
Reporting becomes clearer
Follow-up becomes less manual
Recurring issues are easier to spot
What stays the same
Your ESB audit expertise
Your audit standards
Your ESB relationship
Your audit methodology
Your support from the ESB team
The practical judgement behind every audit
Migration
Moving from the legacy platform to Hugo
Selected ESB clients will be moved across to Hugo first.
ESB will manage the transition from the legacy platform and share clear guidance before anything changes.
This includes what stays the same, what historical audit records move across, who needs access and what your team needs to do next.
The aim is simple:
keep the same ESB audit expertise, with a better platform behind the work.
Sneak peek
The screens your team will use first
A preview of the Hugo interface — designed for clarity, not complexity.
Site dashboard
See what needs attention at site level.
Coming soon
Corrective actions
Track owners, deadlines and status.
Evidence upload
Keep proof linked to the right finding.
Estate view
Spot overdue actions and recurring issues.
What Hugo helps you do
Less admin. Clearer follow-up.
Rollout
Know what is coming before it lands.
01
Stage One
Join the priority list
Get previews, rollout updates and walkthrough opportunities first.
02
Stage two
Watch the previews
See how findings, actions, evidence and reporting will work.
03
Stage Three
Review what changes
Understand what your team will do differently and what stays the same.
04
Stage Four
Confirm migration details
For selected clients, ESB will explain how historical audit records will be moved from the legacy platform into Hugo before rollout begins.
05
Launch
Prepare for rollout
Training and guidance will be shared before clients move across.
Client questions
Practical details we'll confirm before rollout.
Will our ESB audit service change?
The service stays familiar. Hugo improves the platform used to deliver, evidence, report, and follow up audits.
Why is ESB introducing Hugo?
ESB has built Hugo to give us greater control over the platform that supports our audit service, so we can improve reporting, evidence handling, corrective action follow-up, and the client experience.
What happens to our previous audit history?
ESB will confirm what audit history is moving into Hugo and what clients will be able to access.
Will my team need training?
ESB will provide guidance before clients need to use Hugo. The aim is to keep the upgrade straightforward.
What will reports look like?
Preview examples will be shared as part of the rollout updates.
Who will need to use Hugo?
ESB will clarify which client users need access and what they will use it for.
What do we need to do now?
Nothing until ESB confirms next steps. You can register interest or request a walkthrough if you would like to see Hugo sooner.
Priority updates
Get Hugo updates and sneak peeks.
Join the priority list to receive product previews, rollout details and early walkthrough opportunities before Hugo is introduced more widely.
Oops! Something went wrong while submitting the form.