This is the move that actually breaks the rescue cycle. Most of what leaders escalate to HR is routine: “what does our policy say, what am I allowed to do here?” Answer that instantly and reliably — with an unmissable stop-line for the matters that genuinely need HR — and the leader self-serves the simple, while HR keeps the serious.
2·A gave the leader the records. 2·B gives them the rules — and, just as importantly, the boundary that keeps everyone safe.
Picture the queue of questions that lands on HR's desk. A large share are not sensitive judgement calls at all — they are “where do I find it / what does the policy say / am I allowed to do this” questions a confident leader could answer in a minute, if only they had a fast, trustworthy way to check.
Today, with no such way, the safest move a leader can see is “ask HR.” And so the simplest query becomes an escalation, the escalation becomes a dependency, and the dependency keeps the cycle turning. Give the leader the rules on tap, and that whole bottom tier of the queue simply dissolves.
Enablement without a boundary is just risk. The stop-line makes the boundary visible and consistent, built into every answer. The principle is simple: the clearer the rule, the greener the light; the more it turns on judgement, sensitivity or law, the redder it gets.
The red light is the most important feature, not a limitation. A tool that knows what it must not answer is exactly what makes it safe to let leaders self-serve everything else.
Watch how one tool handles a green, an amber and a red — grounding the easy ones and refusing the hard one. This is the boundary working in real time.
“One of my team wants to take annual leave next month — how much notice are they meant to give, and can I say no if it clashes with a deadline?”
“Someone's quality has slipped for a few weeks. I want to raise it informally — what's fair, and what should I be careful of?”
“A team member has accused another of bullying. How do I investigate it and what disciplinary action can I take?”
An exec's first instinct is rightly cautious: won't letting leaders self-serve policy create risk? Done this way, it does the opposite — it makes a currently invisible, inconsistent process visible, consistent and governed.
Every leader gets the same grounded answer from the same source — replacing the lottery of who they happen to ask and what they half-remember.
The red line is explicit and built in. You can see exactly what is self-served and what is escalated — and tune it. Governance you can point to.
HR's time shifts from answering routine queries to handling the genuinely sensitive — and maintaining the policy base the tool draws on.
This only works if the answers are right and the boundary holds. Two disciplines make that true.
The tool answers from the organisation's own current policies and instruments — loaded into a secure, maintained knowledge base — and cites where each answer comes from, so the leader can verify. It is only ever as good as the content behind it, which makes HR's role as curator essential, not optional.
It is support, not authority. For anything green it informs; for amber it informs and prompts a check; for red it refuses to advise and routes to HR. The leader still owns the decision, and HR still owns the serious matters and the policy itself. Enablement and governance move together — that is what makes it safe to scale.
When the routine answers itself and the serious is clearly flagged, the leader stops asking permission — and HR stops being a permission desk.
This is the hinge of the whole model: dependence dissolves on the simple, judgement is protected on the serious, and HR finally becomes the architect and guardian it was always meant to be.
The rules handle “what am I allowed to do.” But the hardest part is often the human moment itself. Next: a private space for the leader to rehearse the difficult conversation, test the tone, and walk in prepared — coaching, not scripting.