I inspected a lot of services over thirteen years, and I met a lot of registered managers. Some ran services I left feeling reassured about. Some ran services I worried about long after I'd driven away. Over time I stopped being surprised by which was which, because the difference between a good registered manager and a struggling one showed up in a handful of patterns that became easy to recognise.
This isn't a how-to guide. It's what I actually saw, the things that separated the registered managers who ran genuinely good services from the ones who didn't, regardless of sector, size, or how the service looked on paper.
They knew their service specifically
The single clearest signal. A good registered manager could talk about their service in specifics, how many people they cared for, what the current risks were, what had gone wrong recently and what they'd learned, where the service was strong and where it needed work. They didn't talk in generalities about "delivering high-quality, person-centred care." They talked about their actual service, as it actually was, that week.
The registered managers I worried about talked in abstractions. Ask them about their service and you got the mission statement. Ask them about their current risks and you got a pause. The abstraction wasn't a communication style; it was a symptom. They talked in generalities because they didn't have the specifics, they weren't close enough to the service to know them.
Knowing your service specifically isn't a presentational skill. It's the evidence that you're actually running it, rather than presiding over it.
They surfaced problems rather than hiding them
This one surprised people. New registered managers often assumed that the way to do well with an inspector was to present a flawless service, to make sure nothing looked wrong. The best registered managers did the opposite. They told me where the problems were.
"We had two safeguarding referrals last quarter, and honestly, the second one took us too long to act on, here's what we changed." "Our night-shift staffing is the thing I'm most worried about right now, and here's the plan." A registered manager who could say that reassured me enormously, because it told me they could see their own service clearly and weren't hiding from its problems.
The registered managers who presented a flawless service made me look harder, because no service is flawless, and a registered manager who couldn't see any problems was a registered manager who would miss the problems when they mattered. The ability to see your own service's weaknesses honestly is the same ability that catches the serious problem early. Hide the small ones and you lose the muscle that catches the big ones.
Their records ran at the same tempo as their work
I've written about this elsewhere, but it's the pattern that most reliably predicted how a service was actually doing. In a good service, the records reflected reality. What had happened that week was written down. The incident from Tuesday was logged by Wednesday. The risk that emerged this month was on the register. When I asked to see something, it was there, current, and matched what the team told me.
In a struggling service, the records lagged the reality. The incident log was thin not because few incidents happened but because they weren't all being recorded. The risk register was last updated months ago. The action plan listed actions that everyone had stopped tracking. The records had become a separate artefact, maintained for the regulator, decoupled from the actual running of the service.
The good registered managers didn't keep records to satisfy me. They kept them because running the service properly produced them. That's the distinction. When the records are a byproduct of running the service well, they're current and they're true. When they're a task done for the inspector, they're neither.
They understood the role was accountability, not authority
The registered managers who struggled often treated the role as the top of the hierarchy, the most senior person, the decision-maker, the one in charge. The ones who thrived understood it differently. They understood the role was about being answerable: that their job was to be able to account for how the service had run and why.
That framing changed everything about how they worked. They kept evidence because they understood they might need to account for a decision. They acted on concerns because they understood that an unaddressed concern was something they'd have to explain later. They built systems that ran without them because they understood that a service dependent on one person was a service that would fail the moment that person was unavailable.
Authority is about being in charge. Accountability is about being answerable. The good registered managers understood they'd signed up for the second, and they ran their services accordingly.
They treated the regulator as a professional counterpart
The relationship a registered manager had with CQC told me a lot. The good ones treated us as serious professional counterparts, not as friends, and not as enemies, but as people doing a job that, at its core, shared their own goal: making sure the service was safe and well run.
That meant they were honest with us. They notified us when they should. They didn't try to manage us or hide things from us, and they didn't crumble defensively the moment we asked a hard question. When they thought we'd got something wrong, they said so, with reasons. When we'd identified a real problem, they engaged with it rather than denying it.
The registered managers who treated us as adversaries, to be managed, deflected, or feared, tended to run services where that defensiveness ran all the way through. A service that's defensive with the regulator is often a service that's defensive internally too: where staff are afraid to raise concerns, where problems get minimised, where the culture discourages the honesty that safety depends on.
They cared about the people, and it showed in the systems
The last pattern is the one that's hardest to put into a checklist but easiest to feel in a service. The best registered managers genuinely cared about the people using their service, and crucially, that care showed up in the systems, not just in the warmth of the staff.
Plenty of services had kind, caring staff. That's necessary but not sufficient. The best services had kind, caring staff and systems that made the care safe and reliable, so that the quality of a person's care didn't depend on which staff member happened to be on shift, or whether anyone remembered the thing that mattered. The registered manager's job was to build the systems that made good care the default rather than the lucky outcome.
A service running on the goodwill of good people, without the systems, is a service one bad day away from a serious problem. The good registered managers knew that, and they built the systems precisely because they cared about the people enough to not leave their safety to chance.
The thread that runs through all of it
If there's one thread connecting these patterns, it's this: the good registered managers ran their services in a way that was honest, evidenced, and systematic, not because the regulator demanded it, but because that's what running a genuinely good service requires. The regulatory compliance was a byproduct of running the service well, not the goal.
That's the reframe I'd offer anyone stepping into the role. Don't run the service to satisfy CQC. Run it well, know it specifically, surface its problems, keep the records current, understand your accountability, engage honestly with the regulator, and build the systems that make good care reliable, and the regulatory side takes care of itself. The registered managers who chased compliance directly tended to achieve neither good care nor good ratings. The ones who ran genuinely good services achieved both.
How Verivius helps
Verivius exists to make the "honest, evidenced, systematic" way of running a service the default rather than the project. The platform runs the incident, complaint, safeguarding, notification, risk, action, and supervision lifecycles in one place, with a complete audit trail, so the records run at the same tempo as the work, the problems are surfaced rather than buried, and the evidence of how you ran the service is there when you need it.
It was built by an ex-CQC inspector for exactly the registered managers I've described, the ones who want to run a genuinely good service and have the systems make that reliable, rather than depending on holding the whole picture in their head.
Frequently asked questions
What's the single most important quality in a registered manager?
Knowing your service specifically. A registered manager who can talk about their actual service, its real risks, its recent history, where it's strong and weak, is demonstrating that they're genuinely running it. Vagueness about your own service is the clearest warning sign.
Is it better to present a flawless service to an inspector, or be honest about problems?
Be honest about problems. An inspector is far more reassured by a registered manager who can see and address their service's weaknesses than by one who claims everything is perfect. The ability to see your own problems honestly is the same ability that catches serious issues early.
How do inspectors tell if a service is genuinely well run?
A combination of signals: whether the registered manager knows the service specifically, whether the records reflect reality, whether problems are surfaced and acted on, and whether the systems make good care reliable rather than dependent on individual staff. The records running at the same tempo as the work is one of the most reliable signals.
What's the difference between a registered manager who runs a good service and one who doesn't?
Mostly it's whether they run the service honestly, systematically, and with the records reflecting reality, rather than treating compliance as a task done for the regulator. The good ones run a genuinely good service and the compliance follows; the struggling ones chase compliance and achieve neither good care nor good ratings.
This article was last reviewed on 31 May 2026. It reflects the founder's experience as a CQC inspector across thirteen years.
Related reading: What a registered manager actually does · The first 90 days as a new registered manager · Unannounced CQC inspection: the first thirty minutes