The South African Bureau of Standards (SABS) has put 81 AI use cases out for public comment. One of its draft AI standards collects them, and the drafts were published on 21 October 2026, with comments open until 10 November. Each draft is an identical adoption of an ISO/IEC AI document. They cover transparency, data quality, human oversight, and the benefits and environmental impact of AI. They are voluntary and carry no legal force unless a law references them. That makes them a test a board can set for itself, and four points show how to use it.
1. Read them as a buying checklist, not as regulation
Be clear about what these documents are. The reporting from Polity, MyBroadband and the law firm Werksmans describes voluntary standards. No regulator will enforce them, and no one will fine a company for ignoring them.
That is exactly why they are useful. The Draft National AI Policy of 10 April 2026 was withdrawn, so South African boards have no settled rulebook to point at. A voluntary standard fills part of that gap. It gives a CFO a published, internationally derived list of what good looks like.
Boards that wait for binding law will wait a long time. The better move is to borrow the standard's language now. Put its headings into supplier questionnaires and contract schedules. A supplier that cannot answer in those terms has told you something.
2. Ask every supplier the same five questions
The drafts name four areas: transparency, data quality, human oversight, and benefits and environmental impact together. I have split the last one in two, which gives five written questions.
Can the supplier explain, in plain terms, how the system reaches its outputs? Where does its data come from, and how is quality checked? Who can override the system, and when? What measurable benefit does the supplier commit to? What does it cost the environment to run?
The oversight area appears under the reference SATS 8200, which gives the board a handle for the conversation. Identical questions matter more than clever ones. When five suppliers answer five different questions, no one can compare the answers. When they answer the same five, the weak answer stands out in minutes.
3. Use the 81 use cases to test your own portfolio
One draft collects 81 use cases. Every board should know where AI already runs in its own business, and the collection is a prompt to check. That gap is the quiet risk.
Ask management to map each live AI deployment against the nearest use case. The draft provides a template and summaries for use cases, which gives a common way to describe a deployment. Where there is no match, the board has found a deployment that nobody has yet described in standard terms.
This is a CFO's exercise as much as a technology one. Spend without a described purpose cannot have a measured return. The return should be written down before the contract is signed, not argued about after it.
4. Count how many ways your suppliers document AI, then act this quarter
Run the five questions across your current suppliers and count the formats that come back. The more formats you hold, the more of your own staff time goes into translating between them.
Be careful with the evidence here. These drafts do not say that fewer suppliers is better. They say what should be documented. The consolidation question is the board's own, and the count answers it with your data, not with a slogan.
There is a deadline to use too. Comments close on 10 November. Anyone running AI at scale can read the drafts and tell SABS what works and what does not.
What the board should do before 31 December
Do three things this quarter. Add the five areas to every AI supplier contract and renewal. Ask management for the map of live AI use against the 81 use cases. Send SABS comments before 10 November if any draft clause would be hard to meet in practice. Adopting a voluntary standard early carries internal and supplier costs, but it gives the board a written answer from every supplier before the first renewal falls due.
A note on sourcing. The Polity text appears to be the Werksmans advisory, so those two sources may not be independent. MyBroadband appears to have published around 22 October 2026, though I have no exact date.