From one observation to a decision you can defend.
Competency-based assessment fails in the same place every time: between the instructor's sheet and the board's decision, where results are averaged, remembered or argued. TRDSS replaces that gap with rules you can read.
Four levels. No averaging between them.
A K/S/A triple is observed on a Particular Control Situation. The engine derives the result of that situation, then the status of the performance objective it serves, then of the observable behaviour, then of the competency. At each step the rule is the handbook's, and the result keeps its link to the evidence.
What happens between the session and the board.
- 01
Capture
The instructor records Knowledge, Skills and Attitude for each control situation met in the session, on the standard form. The sheet is signed and locked. From here on nothing is edited, only appended.
- 02
Qualify
Each POK is weighed by its pedagogical justification, its NGP value, the criticality of the situation and the instructor’s safety and orderly-flow judgement. A late read-back on a quiet frequency and a lost separation are not the same negative evidence.
- 03
Trajectory
The sequence of results on the same situation across exercises is read as a trajectory. Recovery counts only under the handbook conditions: a later OK clears an earlier POK or NOK when its value of demonstration, built from equivalence class, workload and discovery or replay, is at least as high.
- 04
Cascade
The PCS result (acceptable, with reservation, not acceptable) feeds the performance-objective status, which feeds the observable-behaviour status (demonstrated, with reservation, not demonstrated), which feeds the competency. No arithmetic compensation at any level; the ALWAYS and ALMOST ALWAYS standards and the Competency Acceptance Matrix decide.
- 05
Recommend
The engine issues one of two statements, READY FOR FINAL ASSESSMENT or FURTHER TRAINING REQUIRED, with three levels of drill-down to the evidence, recurrence alerts and an override path that requires a written justification.
- 06
Decide
The final PASS or FAIL stays a human act, at the board, under governance checks. TRDSS prepares the decision; it does not take it.
Built to be audited, not only to be used.
The decision matrices of the EDS TRDSS Handbook are configuration, versioned and dated. A change of handbook edition is a new rule set, and old assessments keep the one they were computed with.
Every status keeps its link to the evidence it was derived from, and the audit pack is hashed. An auditor can replay any result from the audit pack and get the same answer.
When a sequence is not covered by the handbook, the engine raises a rule gap instead of guessing. The gap is logged for the organisation to arbitrate.
Pre-OJT exercises on the simulator and daily OJT session logs feed the same consolidation at behaviour level. One picture of the trainee, not two.
Pre-board reports compile the sessions and pre-fill the competency grid. The board drills into the rule logic, approves or overrides. Instructor, assessor and board chair sign in sequence.
Minimum observations and distinct contexts per competency (three and two in the ADC Rating module), stable-run length and critical competencies are parameters of the ACM, shown on every report that depends on them.
TRDSS implements the decision matrices of the EDS TRDSS Handbook, written by ATCE in cooperation with EDWARE, in line with ICAO Doc 10056 on competency-based assessment and Regulation (EU) 2025/2143. The assessment plan, milestones and evidence guide remain documents of your approved Unit Training Plan; EDS carries their digital representation and guarantees their application. It does not write or approve them.
Bring an assessment sheet. We'll show you what the engine does with it.
Forty-five minutes, your competency framework, a real trainee trajectory anonymised. You'll see every rule that fires.