Sokros Copilot
Ask the record, not the room.
Everything the platform has recorded (grades, fields, live events, chain firings) surfaces as answers in plain language: retrieved, quoted, never invented.
Live today over marking records in CIPD centres · one product, one name
Inside Studio, the Copilot sits in the corner of every screen.The desk →
01 · The mechanic
It answers from the record, or says so.
A chatbot fills silence with fluency. The Copilot is retrieval over stored decisions, and it treats an empty result as an answer.
Every line carries the record it came from: the grade, the field, the firing, the frame. Ask something the record does not hold and you get "not on record", with what the record does hold nearby. That sentence is the product.
Not on record.
No stored decision covers writing style for this script. On record: the grade per criterion, the gate results, and the feedback sheet as dispatched. Would you like those?
An honest miss beats a fluent guess. Every time.
02 · The reach
One question away.
Whatever the layer recorded, the Copilot can reach: one interface across marking, extraction, the live layer and the chains.
Why was this script referred?
Marking records
The referral reason, the gate that failed and the quote behind it, while the learner is still on the phone.
Which suppliers touch a site with an open finding?
Resolved entities
The entity graph walked for you: supplier, site, finding, each edge quoting its record.
What fired the certificate chain last week?
Chain firings
Every firing with its rule version, what ran, and what waited for approval.
Which agreements cap liability below one million?
Extraction fields
The clause list with each cap quoted from the page that says so.
What happened in the yard on Tuesday morning?
The live layer
Events with their frames and timestamps, and the chains they triggered.
03 · Shapes
Ask for the shape, not just the number.
Some questions want a chart. The Copilot draws it from the query result, and each point stays attached to the records that built it.
Referral causes by unit, findings by site, chain activity by week: the chart is an answer, so it inherits the answer's rules. Click a bar and you are reading the records underneath it.
Drawn from the RTD log, not from memory. The odd one out is quoted: wrong brief year spiked in the September intake.
04 · Reports
The Friday report writes itself.
A recurring answer becomes a rendered document: your template, your house wording, the record's content.
The EQA pack, the weekly site summary, the escalation note: rendered row for row the way the CIPD feedback sheet is today, every line traceable, and held as a draft until a person releases it. Nothing sends itself.
Your template · section 1
Open findings: 1 (Site A, fire door F-112)
Your template · section 2
Permits issued: 14 · all authorised on live values
Your template · section 3
Certificates due in 30 days: 1 (forklift, renewal booked)
05 · Clearance
Answers with clearance.
Scoped to your role
A course coordinator and a DPO ask the same record and see different answers. Scope is configuration, written and versioned like everything else.
Inside your boundary
The Copilot runs where the record runs: in-region or on your own floor. Questions and answers never leave to be understood elsewhere.
Asking is on record too
Every question, every answer, every rendered report is itself recorded. The audit trail covers the asking, not just the deciding.
Ask it something the room can't answer.
Bring the question your team answers by folder-diving. One briefing, your own records loaded, the answer quoted in front of you.
A 30-minute briefing: one record scoped, a gated pilot plan.