Platform · Directives
Judgement, by the book.
A directive is a category of decision, written down: what it reads, what it may decide, and whether it suggests the call or executes it. Your estate runs on a shelf of them, each one versioned.
The same decision mechanics grade regulated qualifications across 34 centres in 20 markets
WHEN a submission lands in the queue
CHECK signature page present · unit and brief match
CHECK word count inside tolerance
SUGGEST Revert to Draft, reasons attached
EXECUTE where the centre's written rule allows
Back with its reasons in under two minutes on instant plans.
01 · The anatomy
Suggest, or execute. Never improvise.
A directive has exactly two postures, and both sit on the same reading of the evidence. There is no third.
It reads before it decides
Values extracted and quoted, hard requirements checked present or not, quality banded only after they stand. The order a professional works in, held on every case the directive touches.
Suggest
The directive drafts the call with its grounds attached and holds it for the person it names. Every directive starts here, and some never leave: for plenty of decisions, a good draft is the whole product.
Execute
Where your written rule allows, the decision runs and files its record. A directive acts only through the actions written in it, and an action outside the written set has nowhere to come from.
There is no improvisation step. A decision the directive was never given cannot be made, which is the point: the shelf of directives is the complete list of what the system may decide on your behalf.
02 · The catalogue
Categories for the decisions you already make.
Most estates run the same handful of calls a hundred times a week. Directives name them, write them down, and version them.
Eligibility & intake
Is this complete, matched and markable? Signature page present, unit and brief match, word count inside tolerance. The suggestion is Revert to Draft with the reasons attached, and the queue holds nothing but workable cases.
Compliance & certification
Is the certificate current, the permit signable, the register clean? A forklift certificate expiring 2026-03-01 holds every permit that depends on it, automatically, until a person or a renewal clears it.
Financial thresholds
Is the value inside the written limit? A £2,000,000 liability cap checked against the floor your playbook sets, an early-settlement window open or shut on the recorded terms.
Quality banding
Which band does the evidence earn? Criteria judged against your own descriptors, from Refer through Pass to High Pass, with the reasoning written down beside the quotes that support it.
Release & dispatch
Does this leave the boundary now, in a batch, or not yet? A 5CO01 cohort released to the LMS in one click, a work order opened, an email held where the rule says hold.
Integrity & anomaly
Does this case look like the others, or not? Similarity and misuse signals with the flagged passages quoted, values that match no pattern set aside. Always a signal for a person, never an automatic penalty.
Each category arrives configured to your estate and stays amendable; every amendment is a new approved version.
03 · Suggestion first
It suggests before it executes.
Execution rights are granted per directive, per role, and versioned like everything else. Until you grant them, every decision arrives as a suggestion.
A person can always be the last step, and for decisions about people that is the default: a flag is a signal for your team, never an automatic penalty. People are decided by people; the directive drafts the call and files whatever the person does with it.
Approve, amend, or send it back. Whichever it is, the decision and the suggestion it started from are filed together.
04 · Across systems and industries
One decision language, wherever the values come from.
A submission queue, a certificate register, an invoice ledger, a camera on a yard: the directive reads the value on record, not the system it came from.
The six categories cover estates as different as an awarding-body centre and a port. What changes between them is the values and the written rules. The mechanics of suggest, execute and record do not, so a team that has read one directive can read them all.
Centre queues · certificate registers · invoice windows · dispatch queues · live sites · model output
Where directives run by sector: the solutions library →·For live sites: Sokros Sentinel →
05 · Determinism
Same case, same call.
Every decision is stored
Outcome, grounds, quoted values, directive version, who or what executed: one record per decision, kept like every other record on the platform.
Any decision replays
Re-run last Tuesday's call against the same values and the same directive version and it lands identically. That is what makes an appeal answerable.
No call without a category
A directive decides only what it was written to decide. A new kind of decision is a new authored version, approved before it fires, never a quiet extension.
Bring a decision you make a hundred times.
One briefing: your call written as a directive, suggestions landing in front of you, execution rights exactly where you want them.
A 30-minute briefing: one decision category scoped, a gated pilot plan.