Declared standard held in routine conditions — a mismatch emerged under pressure.

A record of how this participant decided inside standardized conduct and market-pressure simulations — declared intent compared with demonstrated behavior, scored separately from outcome.

Participant

#C-0142 (anonymized)

Cohort

Conduct Pilot · Group A

Modules

Conduct & Market-Pressure · L1

Session

8 scenarios · 31 min

Illustrative sample. Not a real participant. ReadyConduct measures declared-vs-demonstrated consistency in a controlled simulation — it is not a lie detector and does not assess honesty or character. Scores are derived from logged decisions, not self-report.

01 · Summary finding

Declared-Demonstrated Consistency: Developing

At intake, the participant declared they would escalate early when client pressure conflicted with policy and would complete verification before sign-off. In the routine rounds, behavior matched: items were inspected, genuine issues flagged, commitment measured. Under deadline, a mismatch emerged — at the conduct checkpoint, escalation was available and not used, and sign-off was completed before verification was finished. The declared standard held while conditions were calm and broke specifically under pressure, which is where coaching has the most leverage.

56/ 100

Declared-Demonstrated Consistency · Developing

Consistent when calm; a mismatch under pressure

Primary mismatch: escalation discipline under pressure. Confidence: high within this controlled scenario. Recommended use: coaching, remediation, further review, or additional scenario testing.

This consistency band summarizes behavior inside this standardized scenario only. It is not an approval, recommendation, suitability finding, honesty assessment, diagnosis, prediction, or an employment decision.

"Declared (intake): 'I escalate early when client pressure conflicts with policy, and I complete verification before sign-off.' Demonstrated: at the conduct checkpoint, escalation was available at three points and was not used until the final decision point; sign-off was completed before verification was finished. Declared and demonstrated aligned in routine rounds and diverged under deadline."

Declared vs. demonstrated — computed from logged decisions, not a questionnaire.

02 · Consistency profile

Five conduct dimensions, scored independently of outcome

Read by band first. Escalation discipline and pressure behavior are where the declared standard broke; conduct judgment, risk awareness, and documentation are developing on a sound base.

Conduct judgmentDeveloping

Held the line in routine rounds; completed a sign-off before verification was finished at the deadline checkpoint.

Escalation disciplineFoundational

Primary mismatch. Declared early escalation; an available path was not used at the critical moment.

Risk awarenessDeveloping

Generally measured; commitment ran ahead of the stated posture once a loss was in play.

Pressure behaviorFoundational

Behavior held while conditions were calm and thinned once the clock tightened.

Documentation / audit readinessDeveloping

Most steps recorded in order; the rationale for the deadline sign-off was not documented.

03 · Scenario-by-scenario

4 of 8 at or above the competency threshold (≥ 65)

The situation is held constant for every participant, so the only thing that varies is the person. Routine rounds matched the declared standard; the high-pressure conduct and suitability scenarios were where it diverged.

#	Scenario	Module	Focus	Result
C1	Day shift	Conduct	Routine triage	Met
C2	Looking good	Conduct	Complacency	Met
C3	Crunch	Conduct	Time pressure	Met
C4	The sign-off	Conduct	Escalation checkpoint	Below threshold
C5	"Ship it, it's fine"	Conduct	False all-clear	Below threshold
M1	Volatile open	Market-pressure	Patience	Met
M2	Loss re-entry	Market-pressure	Risk discipline	Developing
M3	Suitability pressure	Market-pressure	Over-commitment	Below threshold

04 · Evidence

Demonstrated behavior, with the logged detail

Routine inspection matched the declared standard. In C1–C2 the participant reviewed each item (avg. review 4.2s) and flagged both genuine issues with no false alarms.
Review collapsed under the clock. At C3–C5 average review fell to 0.7s; a genuine issue was passed at the "ship it" all-clear.
The conduct checkpoint (C4). Escalation was available at three points and not used; sign-off was submitted 1.1s after the prompt — before the verification step was complete; no rationale was documented.
Suitability pressure (M3). After a loss, commitment reached 92% of the available position — outside the stated risk posture from intake.

05 · Recommended follow-up

A trainable mismatch, sequenced

1
Repeat — the escalation-under-deadline scenario. Re-run C4 under the same pressure to build the escalate-and-verify-before-sign habit before it fires.
2
Complete — an escalation-decision module. Practise when to escalate and documenting the rationale, until it is automatic under deadline.
3
Review — with the supervisor. Walk the logged decisions together and re-assess in 14 days.

Recommended use: coaching, remediation, further review, or additional scenario testing. This is advisor-/supervisor-directed development guidance — not an employment, hiring, or disciplinary determination, and not a finding about honesty or character.

Appendix · Raw event detail

How the consistency band was produced

The band is derived from logged decisions, not self-report. Declared intent is captured at intake; each subsequent decision is recorded as a structured, timestamped event (participant, scenario, prompt type, decision, latency, escalation availability/use, policy alignment, risk flag) and compared against the declared standard using a fixed, closed, deterministic rule set — no free-text scoring, no clock-dependence. A representative slice of this participant's log:

scenario_id	timestamp	prompt_type	decision	latency_ms	escalation_used	policy_alignment	risk_flag	consistency_band
C1_day_shift	00:01:42	triage	flag_issue	4200	n/a	aligned	none	Met
C3_crunch	00:14:05	triage	pass_item	700	n/a	misaligned	missed_issue	Below
C4_sign_off	00:18:21	conduct_checkpoint	sign_before_verify	1100	false	misaligned	escalation_unused	Below
M3_suitability	00:27:48	commit_slider	commit_0.92	900	n/a	misaligned	over_commit	Below

Full per-participant logs are delivered as part of the pilot — see the event log sample for the complete, exportable schema (CSV / JSON / xAPI / SCORM).

To see what the assessment distinguishes between two people in the same scenarios, view the Sample Participant Comparison — two illustrative sample participants scored side by side.