Supervised autonomy works when three things line up, in order. First, design the process before anything is configured: who owns it, what could go wrong, and where a person must decide (Define). Then run it in Traffic Lights, which records every step, approval and rule change as the work happens (Monitor and Govern). Finally, answer your board from that record, and ratify each change it shows you should make (Improve). The kit walks through all three, with a worksheet for the first and an illustrative sample board report for the last.
or email demo@traffic-lights.io
PDF · 17 pages · free, no sign-up.
The five questions your board will ask
When a board member, auditor or regulator asks about your AI agents, reassurance is not enough. These are the questions they ask; the kit lists the evidence for each and where it lives in Traffic Lights.
- 1What are your AI agents doing?A complete picture of agent activity: not a list of tools, but a record of what agents actually did.
- 2Who approved what, and when?Every consequential outcome has a named person behind it: who decided, when, and on what basis.
- 3What policies govern your agents?Agent behavior is governed by defined, versioned rules that can be shown to a regulator.
- 4What happens when something goes wrong?The process escalates to the right person and stops a bad outcome from spreading.
- 5How are you improving over time?Thresholds change on evidence, and human review becomes more targeted, not more burdensome.
Today the board report is assembled from the platform's screens and exports. A generated board report is coming.
Seven design steps
The worksheet asks these questions in the same order as Traffic Lights' process wizard, so a completed worksheet carries straight across.
| Step | What you decide |
|---|---|
| 1 · Identify | Name the process, what it is for, who owns it, and whether AI takes part. |
| 2 · Control environment | Who holds authority over the process, and how changes to it are governed. |
| 3 · Risk assessment | What could go wrong, how much it matters, and whether it can be undone. |
| 4 · Control activities | The steps of the process, who or what performs each, and where a person must decide. |
| 5 · Information and communication | Who is told what, through which channel, and how fast they must act. |
| 6 · Monitoring | How you will know the process is healthy, and how it reaches your oversight body. |
| 7 · Improvement and ratification | How the process changes over time, and who approves each change. |
What's inside
| Part | Question it answers |
|---|---|
| 1 · Design | How do I design a process that will stand up to scrutiny? |
| 2 · Operate | What does Traffic Lights record while the process runs? |
| 3 · Report | What will the board, auditor or regulator ask, and can I answer it? |
| Appendix A | What does a finished board report look like? (Illustrative sample, fictional data.) |
For the questions alone, see the board checklist.
Structured around COSO's Internal Control–Integrated Framework; compliance is determined by your auditors. COSO is a trademark of the Committee of Sponsoring Organizations of the Treadway Commission; Traffic Lights is not affiliated with or endorsed by COSO.