CASE STUDIES
Every business is different. But the problems that make a business harder to run are often surprisingly familiar.
Case study 01
A property and serviced accommodation business was dealing with information coming from several different places. Booking information, financial information, property information and bank transactions all needed to tie together.
The problem wasn’t simply doing a reconciliation.
It was being able to confidently answer three questions:
The problem
Multiple sources of booking and financial information made it difficult to see the complete picture.
Bookings came through different channels, while financial information needed to be reconciled against the underlying booking activity.
There were also property and unit-level differences to account for, alongside client money and specific treatment of items such as cleaning fees.
Without clear rules for how these different pieces of information should connect, reconciliation could become a manual exercise in finding and explaining differences.
What we found
The issue wasn’t a lack of information.
There was plenty of information.
The problem was that there wasn’t one clear, repeatable process for bringing it together and dealing with exceptions.
The business needed defined rules around what should be recorded, how activity should be tracked and what should happen when the numbers didn’t agree.
What we did
We designed a clearer reconciliation process built around the way the business actually operated.
This included defined financial rules, property and unit tracking, a booking-to-financial process, treatment of cleaning fee income and cleaning costs, bank reconciliation and controls around client money.
We also established a way of dealing with exceptions rather than allowing every difference to become a manual investigation from scratch.
The aim wasn’t to create more administration.
It was to create a reliable way of knowing what should have happened, checking what actually happened and identifying what needed attention.
What changed
The business now has a repeatable way to reconcile its activity and identify what needs attention.
Instead of relying on individual knowledge and manual checking, there is a clearer process with defined rules, tracking and exception handling.
Why it matters
Good financial control isn’t just about making the numbers balance.
It’s about being able to trust the process that gets you there.
Case study 02
Important guest messages, enquiries, maintenance issues and operational updates were coming through different channels.
Someone needed to keep checking everything to make sure nothing important was missed.
The problem
The business was receiving a mixture of routine activity and genuinely important messages.
The difficulty was that someone had to monitor the incoming information continuously to work out which messages actually needed action.
That creates a familiar problem.
The more things there are to watch, the more time someone spends watching them.
And when the business owner or a key member of the team is the person doing the watching, the problem becomes another dependency on them.
What we found
Not everything needed the same level of attention.
Some messages were routine.
Others represented an exception that needed somebody to act.
The problem was that the existing approach treated everything as though it needed to be monitored manually.
The business didn’t necessarily need someone watching everything.
It needed a way of identifying what mattered.
What we did
We designed an exception-based monitoring approach.
Instead of requiring someone to manually monitor every incoming message and update, the process is designed to identify information that needs attention and alert the appropriate person.
The focus shifts from:
“Has someone checked everything?”
to:
“Has anything happened that needs someone to act?”
That distinction is important.
The objective isn’t to automate everything for the sake of automation.
It’s to remove unnecessary monitoring while keeping the things that genuinely matter visible.
What changed
Routine activity can continue without constant manual checking, while important exceptions are brought to the attention of the right person.
The business has a clearer way of distinguishing between information that can continue through the normal process and information that requires intervention.
Why it matters
You shouldn’t need someone constantly watching the business to know when something needs attention.
Monitor for exceptions. Not everything.
Case study 03
Keeping track of requirements, training, inspections, certificates, policies and evidence was becoming increasingly difficult to manage alongside everything else.
The problem
Compliance creates a particular kind of workload.
There are things that need to happen.
There are things that need to happen regularly.
There are things that need to be recorded.
And there needs to be evidence that they happened.
As the number of requirements grows, keeping everything in your head becomes increasingly difficult.
The risk isn’t necessarily that nobody cares about compliance.
It’s that important things can become dependent on memory, individual knowledge or someone remembering to check.
What we found
The problem was not simply the number of compliance requirements.
It was the way they were being managed.
A requirement on its own doesn’t tell you:
Without those connections, compliance can become another collection of documents, reminders and things someone has to remember.
What we did
We structured compliance around six clear elements:
Requirement
What needs to happen?
Owner
Who is responsible?
Frequency
When or how often does it need to happen?
Evidence
What demonstrates that it has happened?
Status
Where are we now?
Exception
What needs attention?
This creates a more practical way of managing compliance.
Rather than simply storing policies, certificates and records, the process makes ownership, activity and exceptions visible.
What changed
Compliance becomes something that can be owned, monitored and reviewed rather than something that has to be remembered.
The business has a clearer framework for knowing what needs to happen, who is responsible and where attention is required.
Why it matters
Compliance shouldn’t live in a filing cabinet.
It should be owned, monitored, evidenced and reviewed.