Board Case Study · Public SaaS (Enterprise)

The Eight-K Clock

An AI feature has been mis-stating contract terms for six weeks. Finance thinks it's material. The earnings call is in nine days, and the 8-K clock may already be running.

The situation

Meridian Cloud is a public enterprise-SaaS company, $1.4B revenue, that shipped an AI "contract assistant" summarizing customer agreements inside its product. A support escalation reveals the model has been misrepresenting renewal and liability terms for roughly six weeks, and an unknown number of customers may have relied on it.

Finance estimates the revenue and remediation exposure could cross the materiality line. The audit committee chair is asking whether this is a current-report (8-K) event and, if so, when the four-business-day clock started, at detection, at confirmation, or at the board's own knowledge. The disclosure committee has never run an AI incident through its process.

The earnings call is in nine days. The prior 10-K described AI as a tailwind and named no specific model risk. Plaintiff firms monitor for exactly this gap between AI marketing claims and AI reality, and the company's D&O tower renews next quarter.

“Is this an 8-K event, and if it is, when did the clock start? We're nine days from the earnings call and the last 10-K called AI a tailwind.”

Audit Committee Chair

The decision on the table

  • Decide whether the AI incident is material and triggers a current-report (8-K) obligation, and fix when the clock started.
  • Reconcile prior 10-K AI disclosure with the reality now on the table, ahead of the earnings call.
  • Stand up a disclosure-committee process that can actually evaluate an AI incident, before the next one.

Run this case with your board.

The full case, scenario architecture, board materials, and facilitation notes, is shared with boards and partners on request.

Request the full case All case studies