A waiver changes the gate, not history
Synthetic onboarding N-265 requires configuration G and training T; optional orientation O may be waived by the named onboarding owner. G and T are complete, while O is waived with reason “customer has reviewed the approved guide”. N-265 is ready under this policy, but only two tasks were performed. If a prerequisite specifically requires performance evidence, a waiver does not satisfy it unless that dependency rule is also explicitly revised.
| Task | Requirement | Recorded outcome | Evidence |
|---|---|---|---|
| G: configuration | Mandatory | Completed | Test record G-8 |
| T: training | Mandatory | Completed | Attendance/task record T-8 |
| O: orientation | Waivable in fixture | Waived; not completed | Owner decision W-8 and reason |
Evaluate readiness with explicit allowed outcomes
- Read mandatory and waivable tasks
- Record completion evidence
- Record allowed waiver separately
- Check readiness and performed totals
A blank result cannot become a waiver. A waiver needs its owner decision and the relevant allowed rule.
How many tasks were performed, and is N-265 ready?
Show the worked answer
Two performed tasks and one waived task. N-265 is ready because the two mandatory tasks are done and the optional task has an allowed waiver.
The waiver is a local operational decision, not a compliance exemption or proof of staff training.