Responsible AI

AI Fairness in Practice: 10 Steps to Educate Your Company

A practical programme for teaching a whole company what AI fairness means — updated for the era of LLM agents, from data provenance to incident drills.

Engatica editors · 2026-10-14 · 9 min read
AI fairnessResponsible AIGovernance

2026 was the year the fairness calendar everyone had memorised fell apart. The EU pushed its high-risk AI obligations back to December 2027; Colorado repealed its first-in-the-nation AI Act and replaced it with a narrower law that starts in January 2027. But one set of duties did not move at all: since 2 August 2026, telling people they are dealing with an AI has been enforceable law in Europe. Fairness education in 2027 is no longer about preparing for a deadline. It is about teaching the calendar as it actually is — and the habits that survive every version of it.

The 10 steps

  1. Name an owner. Fairness without an accountable role is everyone's job and no one's.
  2. Teach the failure gallery. Real cases — hiring screens, credit models, image systems — teach faster than principles.
  3. Map where models touch people. You cannot govern an inventory you do not have; include vendor AI and shadow LLM use — and, now, agents: which agent can touch which system, acting under what identity and on whose authority. NIST's NCCoE opened a dedicated project on software and AI agent identity and authorization in February 2026 precisely because agents are commonly run as generic service accounts with no dedicated identity, authorization or accountability controls (Cloud Security Alliance, 2026). An inventory that cannot answer that question will miss the fairness failures most likely to make news — an agent's biased actions, not just its answers.
  4. Make provenance a habit. Every dataset and retrieval corpus gets a source, a date and a known-limitations note.
  5. Test outputs by group, routinely. Slice quality metrics by the cohorts your decisions affect, before users do it for you on social media.
  6. Write the escalation path. Who can pause a model or agent, on what evidence, within what hour? Decide before the incident.
  7. Include affected voices. Review panels that include the people your system serves catch harms that metrics miss.
  8. Train the buyers, not just the builders. Procurement checklists for vendor AI prevent most third-party fairness debt.
  9. Drill an incident. One tabletop exercise a year — a biased agent decision, a press query, a regulator letter — is worth a shelf of policies. Rehearse against the real reporting clocks that attach to the EU AI Act's high-risk regime: 15 days for a serious incident generally, 2 days for widespread infringements or critical-infrastructure disruption, and 10 days where a death is involved (ilert, 2026). A drill that does not rehearse an actual statutory clock is theatre.
  10. Publish what you can. A short public model/system card builds the discipline internally and trust externally.

The bottom line

Fairness education works when it is operational: tied to the prompts, data and agents people actually ship. That is also why our LLM hub treats evals as a fairness tool, not just a quality tool — the same sliced test sets serve both.

Step zero: teach the real calendar

Before the ten steps, one lesson now has to come first, because your staff will repeat the wrong dates in meetings if you do not replace them. The regulatory calendar for AI fairness, as it stands in late 2026:

The teaching point is not the dates themselves; dates will move again. It is that disclosure duties survived every negotiation while assessment duties slipped — regulators, in the end, protected the citizen-facing obligations and deferred the paperwork. Build your programme in that order: what people are owed today, then the evidence machinery for 2027.

Frequently asked questions

Is the Colorado AI Act still in effect?

Not in its original form. Colorado repealed its broad 2024 AI Act (SB 24-205) and replaced it with SB 26-189, a narrower law applying from 1 January 2027. For automated decision-making in consequential domains — employment, credit, housing, healthcare, education — the duties are notice before use, a plain-language explanation after an adverse decision, human review on request, and records kept for three years.

What does the EU AI Act require right now?

The transparency duties — and they are already enforceable. Since 2 August 2026, Article 50 requires disclosing to people that they are interacting with an AI, and machine-readable marking of AI-generated content; the Digital Omnibus did not delay them. Only the marking of systems already on the market before August 2026 has a grace period, ending 2 December 2026. The high-risk regime follows on 2 December 2027.

How do you teach a whole company about AI fairness?

Make it operational, not theoretical. Name an accountable owner, teach a gallery of real failures, inventory every place models and agents touch people, and make data provenance a habit. Test outputs sliced by the groups your decisions affect, write the escalation path before an incident, train the buyers of vendor AI — not just the builders — and run one incident drill a year against the real statutory reporting clocks.

Why do AI agents create new fairness risks?

Because an agent does not just answer — it acts: screening, scoring, refusing, under an identity somebody has to inventory. Agents are commonly run as generic service accounts with no dedicated identity, authorization or accountability controls, which is why NIST's NCCoE opened a dedicated project on agent identity and authorization in February 2026. The fairness failures most likely to make news are biased actions, not biased answers.

Sources

  1. Goodwin. (2026). "Not Delayed, Not Deferred: EU AI Act Transparency Obligations Are Now in Force". Goodwin Procter LLP.
  2. Proskauer Rose LLP. (2026). "What Colorado AI Law's Major Rewrite Means For Employers". Proskauer.
  3. Ropes & Gray LLP. (2026). "Colorado Scales Back AI Law, with Targeted Implications for Health Care". JD Supra.
  4. ilert. (2026). "EU AI Act 2026: Delay, New Deadlines & Article 73 Reporting". ilert.
  5. Cloud Security Alliance. (2026). "NIST AI Agent Standards: What It Means for Enterprise Security" (CSA Research Note).
  6. Teampl Consulting. (2026). "The EU AI Act's High-Risk Deadline Just Moved to 2027" (summarising Holland & Knight and DLA Piper analyses).
  7. Singla, A., Sukharevsky, A., Yee, L. & Chui, M. (QuantumBlack, AI by McKinsey). (2025). "The State of AI in 2025: Agents, Innovation, and Transformation". McKinsey & Company.