A volunteer shortwave club turns on a log helper but never shows operators what may be pasted, how to report a bad answer, or who to call. Which governance control is still missing?
Select an answer to reveal the explanation.
Short Explanation
Think of a log helper with no word on what may be pasted, how to report a bad answer, or who to call. The missing control is team training. Do not swap the model instead.
Full Explanation
Turning on a volunteer shortwave club log helper without showing operators what may be pasted, how to report a bad answer, or who to call leaves team training missing from the governance stack. Governance closes only when people know the protocol. Training covers allowed data classes, escalation paths, incident contacts, and what never to paste into the helper; swapping models does not teach operators those behaviors or create a report path.
Another model swap fails by concept: changing weights or providers does not communicate paste rules, reporting steps, or on-call contacts. Amazon Inspector fails because CVE scanning of hosts does not teach operators what they may paste into the log helper. A dashboard title fails because charts are not a report-a-bad-answer path or a human contact tree when something goes wrong.
Exam caveat: training must be refreshed when policy or tools change; a one-time kickoff drifts quickly as volunteers rotate through the club. Operational check: publish a one-page protocol for paste rules, bad-answer reporting, and on-call contacts; brief operators before enablement; run a tabletop where someone reports a bad answer; and verify the test report reaches the named contact without requiring a model change.