Questions Heads of People ask
before relying on it.

Short answer: Yes — because it protects them, not because they're told to use it.

Managers don't use ANCHOR out of compliance. They use it because it reduces their exposure.

When a decision is challenged, they need to explain how they got there. ANCHOR gives them a clear, timestamped record of their reasoning — in around 60 seconds.

That's why it gets used.

Short answer: No — if it's positioned correctly, it feels like protection, not oversight.

Adoption depends on framing. When introduced as "this helps you justify your decisions" or "this protects you if something is challenged," managers engage. When framed as monitoring, they resist.

This is a positioning decision, not a product issue.

Short answer: Around 60 seconds per decision.

Managers are not writing reports. They are mapping what happened, applying a standard, and selecting a proportionate response.

It fits into how decisions are already being made — just with structure.

Short answer: Minimal — you engage where it matters, not constantly.

ANCHOR runs asynchronously. Managers submit decisions. You see patterns and flags. You respond when needed.

There's no requirement for constant oversight.

Short answer: No — it demonstrates structured decision-making, which reduces risk.

The real risk is inconsistency without evidence.

ANCHOR shows decisions were considered, reasoning was structured, and patterns can be reviewed.

That strengthens your position.

Short answer: Nothing escalates automatically — flags are advisory, not urgent.

ANCHOR does not create alerts that require immediate action. It surfaces potential risk. You decide if and when to respond.

The presence of a system matters more than response speed.

Short answer: It shows decisions were made consistently and with intent.

ANCHOR creates a record of what was considered, how the decision was made, and how similar situations were handled.

That demonstrates governance — which is what's assessed.

Short answer: Typically 50–500 employees — where inconsistency exists but isn't visible.

At this stage, multiple managers are making decisions, patterns are forming, and HR doesn't have full visibility.

ANCHOR makes those patterns visible early.

Short answer: No — this is exactly when it becomes valuable.

At 80 people, inconsistency already exists. You just can't see it yet.

You also don't have the infrastructure to catch issues later. That's where risk compounds.

Short answer: Position it as manager protection, not HR oversight.

Rollout should focus on "this helps you make defensible decisions" and "this gives you something to stand on if challenged."

When managers see the benefit, adoption follows.

Short answer: One session. One real scenario.

You don't need a rollout to test it.

A single session will show whether decisions differ, where inconsistency exists, and whether this is worth solving.

Short answer: No — it captures real decisions, not theoretical behaviour.

Training focuses on what managers should do.

ANCHOR shows what they actually do, where it differs, and what needs adjusting.

It works in real time, not retrospectively.

Short answer: Those track issues after they happen — this shows what caused them.

Case systems are downstream.

ANCHOR sits upstream: capturing decisions before escalation, and showing patterns across managers.

They solve different problems.

Short answer: Yes — but it becomes targeted and relevant.

ANCHOR shows where gaps actually are.

Training can then focus on real scenarios and real inconsistencies — rather than generic guidance.

Short answer: Yes — your records remain yours.

All Decision Receipts can be exported and retained internally.

You're not locked into the system to access your own data.

Short answer: It can sit alongside existing tools — it doesn't replace them.

ANCHOR focuses on decision-making.

It complements HR systems, case management tools, and training programmes — rather than replacing them.