A team that knows the place — and can run it.
Familiarize people with the real site and systems, train them to the current procedures, and prove competency by role — so opening day meets a team that’s ready, not just trained on paper.
| Competency by role | Operators | Controllers | Maint. |
|---|---|---|---|
| Emergency response | |||
| Degraded‑mode ops | |||
| Site familiarization | |||
| Drills & exercises |
People can pass the course and still be lost on day one.
A training binder and a kickoff briefing don’t make a team ready. Readiness is people who know the actual building and systems, can run the current procedures, and have proven it — by role, before the doors open.
Trained on paper
- A one‑time briefing on slides, months before go‑live.
- No one has walked the real site or touched the real systems.
- Attendance is tracked; competency is assumed.
- Who’s ready — and who isn’t — is anyone’s guess.
- Contractor‑run technical training happens off to the side, unmeasured.
Familiar & competent
- People familiarize on the actual facility and systems.
- Training is tied to the current, approved procedures.
- Competency is assessed and recorded — by role.
- Readiness by role is visible, and gaps surface early.
- The owner governs quality — even when a contractor delivers the training.
Plan → Familiarize → Train → Assess → Evidence.
A loop that turns a workforce into a competent, familiar operating team — and turns that readiness into evidence a gate can rely on.
Familiarize people with the real thing — not a slide of it.
The gap a classroom can’t close is knowing the actual place. Familiarization puts people in the real environment before it goes live.
Site & system familiarization
Walk the building, find the equipment, and learn the systems people will actually operate.
Orientation & walk‑throughs
Structured orientation and guided walk‑throughs, scheduled as go‑live approaches and access opens.
Familiarization runs & drills
Repeated familiarization runs and drills build the muscle memory a briefing never will — often inside a trial.
Deliver training — tied to the procedures people actually run.
- T‑01Plan, schedule, and registerStreamline planning, scheduling, and registration — with self‑registration for stakeholders and their personnel.
- T‑02Role‑based curriculaGive each role the training it needs — operators, controllers, maintenance, emergency services, and partners.
- T‑03Trained on the current procedureTraining draws on the current, approved procedures from Operating Knowledge — never last year’s version.
Content from Operating Knowledge
Operating Knowledge writes and approves the procedure; Familiarization & Training gets it into people — so the two stay in lockstep.
Contractors deliver much of the technical training. You still own the quality.
O&M‑style technical training is often delivered by contractors under their contract. Readiness doesn’t transfer with it — the owner’s team oversees it, measures it, and proves it worked, the same way it does for familiarization and induction.
- O‑01Import the contractor training scheduleBring the delivery party’s training plan into CitiriOS so it’s visible and governed alongside your own — not in a separate tracker.
- O‑02Opti extracts the spec from the contractOpti reads the contractual training obligations and drafts the setup — courses, audiences, and frequencies — for your team to review and confirm.
- O‑03Manage registration in one placeRun registration and attendance for contractor‑delivered and owner‑run sessions from a single system.
- O‑04Survey, collect feedback, analyzeCapture participant feedback on every session — technical, familiarization, and induction — and analyze quality so gaps get fixed before go‑live.
Delivered by the contractor, owned by you
The contractor performs the training under its obligations; the readiness team stays accountable for whether it happened, met the spec, and produced ready people — with feedback and competency as the proof.
Prove competency by role — not attendance.
- A‑01Assess, don’t assumeConfirm competency through assessment, sign‑off, and drills — not a signature on a sign‑in sheet.
- A‑02A competency matrix by roleSee who is competent for what, by role and cohort — and where the gaps are before go‑live.
- A‑03Competency & feedback become evidenceCompetency records and participant feedback feed the evidence chain and trial and gate criteria — so “the team is ready” is provable.
Readiness you can see by role
A live competency matrix turns “are the people ready?” from a nervous guess into a status you can point to and defend.
Attendance is not competency. A course is not familiarity.
Completing training is an evidence candidate — competency is assessed, and becomes accepted readiness evidence through the evidence workflow. And knowing a procedure isn’t the same as knowing the building it happens in.
Three capabilities, one hand‑off.
Keeping these distinct is what makes readiness real — each proves a different thing, in order.
Powered by CitiriOS. The people side of readiness.
Familiarization & Training draws on operating knowledge, rehearses through trials, and proves competency into the evidence chain.
Open with a team that’s truly ready.
Book a demo built around your familiarization, training, and competency needs — from role‑based curricula to a live competency matrix.
Figures shown are illustrative, not a customer result. Training completion is an evidence candidate; competency is assessed and accepted through CitiriOS evidence workflows. Training delivered by contractors remains their responsibility; CitiriOS governs the owner’s oversight, registration, feedback, and evidence. CitiriOS integrates with — and does not replace — an LMS or HR system. Opti suggests and cites; people assess and sign off competency.