Youth behavioural simulation

Practice the difficult interaction before it’s with a real child.

Your staff can recite the de-escalation technique. Nobody can tell you whether they can use it at 9pm with a fifteen-year-old shouting at them in a hallway — and the first time anyone finds out is with a real child. SIMCareReady is the practice layer that sits in that gap.

What we are held to

Anyone can name a standard. These are the numbers.

Every commitment below is enforced in code and tested on every build. If one stops being true the build fails and the claim comes off this page — which is the only version of a standards claim worth reading.

0

Sessions in which frightening a young person produces compliance.

Compliance cannot rise while perceived threat is at or above 70. It is structurally impossible for this platform to teach a staff member that fear works — not discouraged in a prompt, impossible in the code.

Proven by standards-check: compliance cannot rise while perceived threat is 70 or above

0

Behavioural state changes written by the language model.

The model proposes; a separate rules layer decides. Every proposal it makes is capped, floored or refused before it touches the simulation, and every refusal is recorded where a facilitator can read it. Nothing about how a young person behaves is left to a model's mood.

Proven by standards-check: an absurd proposal is constrained rather than obeyed

100%

Competency scores that cite a timestamp and quote the learner's own words.

A supervisor coaching from this can point at the exact second. A judgement nobody can point at cannot be returned at all — the schema refuses it.

Proven by standards-check: a score cannot be returned without a timestamp or without the quote

0

Exercises that escalate past the level the scenario authorised.

Every scenario carries a hard ceiling on agitation and perceived threat. A de-escalation exercise cannot become a restraint scenario because a model decided to push.

100%

Scenario objectives that map to a competency the scorecard actually reports.

No objective exists that nothing measures. If a scenario says it teaches something, the debrief scores it — or the scenario does not release.

3

Named human approvals required before any scenario reaches a learner.

A clinical subject-matter expert, a simulation expert and a safety reviewer — each by name and date, not by job title. Software does not approve its own clinical content here. Until all three sign, the scenario is refused.

100%

Sessions that end in a structured debrief with one specific change to practise.

The turning point named, the deciding moment quoted, one change specific enough to rehearse, and the same scenario offered one difficulty higher. A session cannot end without it.

0

Behavioural gauges visible to a learner during practice.

A learner who can see the numbers plays against the numbers. The observer panel is for a facilitator, it is off by default, and the interface says so whenever it is on.

0

Real children represented, referenced or inferred about — ever.

Every persona is a composite written to exercise a behavioural model. No record, no likeness, no diagnosis about any real person, and no reference to anything outside the scenario. Stated in the prompt, in the briefing and on screen throughout.

0

Certification or accreditation claims we have not earned.

A guard scans our own public copy and fails the build on any phrasing that implies one of these bodies has certified, accredited, approved or endorsed this software, or that its effectiveness has been proven in a study. Those bodies accredit organisations and programmes, never software, and the audience for this product knows exactly what those words cost to earn.

100%

Sessions written out in full as a dated, auditable record.

Every exchange, the proposed state change, the applied state change, every constraint that fired, and the scorecard. That is what an organisation puts in front of a surveyor — and it is what turns thousands of sessions into workforce readiness data nobody currently has.

Why this is not AI role-play

Three differences, and the first one is the whole thing.

01

Built for youth, not adapted to them

Competitors sell horizontal healthcare role-play — the same conversational model wearing a younger face. A fifteen-year-old in escalation does not argue like an adult, does not calm on adult cues, and does not respond to authority the way an adult does. The behavioural model here is built on developmental stage: escalation outruns de-escalation, working memory narrows under arousal, autonomy outranks comfort, shame turns outward.

02

Graded against your standards, not a model’s opinion

You load your approved training materials, SOPs, de-escalation framework and terminology. The platform then answers did this employee respond the way we expect — not did an AI think that sounded reasonable. For an organisation already running an established evidence-based model, that difference is the entire product.

03

Competency intelligence, not attendance records

Across thousands of sessions it learns which interventions work against which behavioural patterns, and surfaces things nobody can currently see — new staff consistently missing early escalation cues, competency collapsing once peer conflict enters the scenario. That is workforce readiness data, and it does not exist today at any price.

Traditional training teaches what to do. It cannot tell you whether someone can do it when a distressed fifteen-year-old is yelling at them.

The standards stack

16 standards met and enforced. 3 supported. Nothing claimed that isn’t.

The platform is built against the INACSL Healthcare Simulation Standards of Best Practice and SAMHSA’s trauma-informed principles. Where a standard governs organisations rather than software — COA, CARF, the Joint Commission — we say so and produce the evidence instead of pretending to hold the accreditation. See the full matrix, line by line →

What we will not tell you

Built against the INACSL Healthcare Simulation Standards of Best Practice and SAMHSA's trauma-informed principles — enforced in code and checked on every build, not asserted in marketing. Where a standard governs organisations rather than software, we say so and produce the evidence instead. SIMCareReady holds no certification or accreditation from any body named here and does not claim one.

There is no efficacy evidence for this product yet and we will not imply otherwise. Simulation-based competency training is well established in child welfare — Illinois runs an entire Child Protection Training Academy on it. What is unproven is whether this delivers it at a fraction of the cost. That is what a design partnership is for.

A guard in the build scans our own copy and fails it on any phrasing that would imply a certification, accreditation or proven result we have not earned. It has already caught us once, on this page.

Who is building this

Small and senior, on purpose.

KnightByrd Tech LLC. The person taking your feedback is the person changing the system, with no account layer in between. Your scenarios and rubrics are your content, exportable, and any pilot is structured so you can walk away having spent time rather than money.