Human decisions remain human
ANCHOR can frame questions, identify gaps and signal review needs. The authorised person or group remains responsible for deciding what action is appropriate.
ANCHOR uses AI to help surface missing context, assumptions and unresolved risk in consequential people decisions — including decisions made by managers and by People teams themselves. It does not make employment decisions, replace professional judgement or remove organisational accountability.
ANCHOR sits between a person’s first interpretation and the action that follows. That person may be a manager, HR professional, Employee Relations lead, People partner, senior leader or another authorised decision-maker. ANCHOR introduces structure, challenge and visibility while responsibility remains with the organisation.
ANCHOR can frame questions, identify gaps and signal review needs. The authorised person or group remains responsible for deciding what action is appropriate.
A signal cannot automatically begin a formal process, change employment status or issue an organisational judgement.
The workflow separates observed information from interpretation so assumptions are easier to identify and challenge.
Health, disability, access, support, process and working conditions can be surfaced before a route hardens into action.
ANCHOR does not present incomplete or failed analysis as a confident answer. Missing information remains explicit.
Not every decision requires escalation. Signals help the organisation direct review to the decisions where additional challenge, independence or specialist input is most useful.
The model is not the decision-maker. It contributes structured challenge inside a process that can be used by managers, People teams, Employee Relations, senior leaders and other authorised decision-makers, with review routed to the person or function best placed to provide appropriate independence and expertise.
ANCHOR does not assume that risk sits only with managers. It examines the quality of the decision itself, whoever is making it, and routes review according to the organisation’s governance model.
Before a pilot or licence begins, the organisation agrees what data is needed, who can access it, how long it is retained and how deletion or export will be handled.
Only fields needed to structure, review and resolve the decision are agreed for the implementation.
Scenario information is used to generate advisory prompts and decision signals for authorised human review.
Decision-maker, reviewer, governance and administrator access is defined according to the organisation’s operating and assurance model.
Retention, export and deletion expectations are documented before live use and reviewed during the pilot.
ANCHOR is designed so that access to decision information can reflect the organisation’s operating model rather than exposing every record to every user.
A failed AI response is not converted into a false clean result, fabricated risk score or pretend Decision Receipt.
If the AI service cannot return a valid analysis, ANCHOR should stop that part of the workflow and make the failure visible.
It should not silently assign a lower-risk result, create a completed receipt or allow a technical error to appear as organisational approval.
The next action is operational: retry, seek human review or use the organisation’s fallback route.
The implementation should establish the operating conditions around ANCHOR before real organisational decisions are processed.
Which decision types are in scope, which are excluded and what the pilot is intended to learn.
What information is genuinely needed and what should not be entered into the system.
Who can submit, review, administer, export and see pattern-level information.
How advisory and escalation signals connect to the organisation’s existing routes.
How long pilot records are needed and what happens at the end of the engagement.
What users do if analysis fails, information is wrong or urgent human review is required.
How all users — including managers, People professionals and leaders — are told what ANCHOR does, what it does not do and how their inputs will be used.
How the organisation will assess usefulness, proportionality, user behaviour and governance friction.
No. It provides structured prompts and advisory signals. The organisation remains responsible for review, advice and action.
No. It means no specific signal was identified from the information provided. It is not legal approval, policy approval or a guarantee that the decision is appropriate.
No. ANCHOR can support managers, People teams and other decision-makers, but it does not replace professional judgement, specialist advice or an appropriately independent review route.
Yes. ANCHOR is designed for consequential people decisions regardless of whether they originate with a line manager, HR Business Partner, Employee Relations lead, People Director, senior leader or another authorised role. Review should be routed to someone with appropriate authority, independence or specialist expertise.
The minimum useful fields should be agreed for the deployment. Users should not enter information that is unnecessary for the decision workflow.
Access should be configured according to role and organisational responsibility. The intended model is not universal visibility.
The output is advisory and remains subject to human review. Users should be able to challenge, correct or disregard it, and technical failures should remain visible rather than being converted into a false result.
No. Detailed assurance should be completed against the actual deployment, contracts, processors, retention rules and access model agreed with the organisation.
Bring your People, leadership, data, security, legal or procurement questions. We will separate fixed product principles from the controls that need to be agreed for your organisation.