Scored Assessment Evidence for an Integrated Security and Network Installation
A student completes a scored-assessment task at a small training workshop. They must install a networked access-control system: a controller, two card readers, a door strike, and a managed switch linking it to a records PC. The student's logbook shows 14 hours across three days. The assessor has a checklist, photographs, and the student's wiring diagram. During testing, the strike releases correctly but the reader log shows intermittent 'access denied' events for one reader, about one in fifteen swipes, and the switch port counters show no errors. The student's written reflection says 'system works, all tests passed'. The assessor must decide what evidence to accept and whether the task is complete.
1. Identify the evidence gap between the student's reflection and the observed test results, and explain how the assessor should treat the intermittent fault under the rules of evidence.
Read the worked answer
The reflection claims 'all tests passed', but the observed data contradicts this: roughly one in fifteen swipes is denied on one reader while switch counters are clean. This is a real gap between claimed and demonstrated performance.
Under the rules of evidence, the assessor should test validity (does the evidence cover the actual performance criteria, including fault diagnosis?), sufficiency (is there enough to judge competence across the whole task?), authenticity (is it the student's own work?), and currency (was it done recently enough?).
A clean switch counter narrows the fault toward the reader, its cabling, or the controller's credential database rather than the network. The student has not demonstrated fault-finding, so the evidence is insufficient for the diagnostic criteria. The assessor should not accept the reflection as proof. Instead they should require the student to reproduce the fault, record the denial pattern, and document a diagnostic path. The task is not complete until the intermittent fault is either resolved or explained with evidence.
2. Design a short follow-up assessment activity that would generate the missing evidence, and state what would count as a satisfactory outcome.
Read the worked answer
A suitable follow-up is a structured fault-finding log. The student should:
- Reproduce the fault by performing at least 30 swipes on the affected reader and record which fail.
- Check the reader's credential list against the controller database and note any mismatch.
- Inspect and test the reader-to-controller cabling, including termination and continuity.
- Swap the two readers and re-test to see whether the fault follows the reader or stays with the port.
- Record each step, the result, and the conclusion in a signed log with timestamps.
A satisfactory outcome would be a documented diagnosis supported by the test data, a corrective action, and a re-test showing zero denials in 30 or more swipes. If the fault cannot be fully resolved, a clear explanation of the remaining cause and its impact would also be acceptable, provided the reasoning is evidence-based. The assessor then judges against the performance criteria, not the student's summary.