A Revised Forecast Is Not an Approved Forecast

SF Scott Farrell • November 21, 2026 • scott@leverageai.com.au • LinkedIn

A revised forecast in your board pack is not proof Finance approved it.

Here's the scene. Last Tuesday, the board update changed one phrase. Wave 2 went from "on track" to "recoverable delay." The author field shows a service account. Version history says "updated." A month later, someone preparing the next pack finds the phrase and has to decide whether to repeat it.

Most organisations end up in a hallway at this point. Someone thinks Finance wrote it. Someone thinks it was always there. Someone searches the chat export for "recoverable" and hopes.

Now suppose the AI session that did the work was recorded with its verbs intact. The session read the vendor email and the steering inputs. It modified the forecast workbook. It modified the board pack. All in one episode.

Those verbs answer two questions, and both answers are blunt.

First, this was not a wording tweak. The new sentence is tied to a specific revision of the forecast, made in the same piece of work. You can't treat "recoverable delay" as someone's softer phrasing and move on.

Second, you can't call it signed off. Finance review of the contractor-rate assumption was still open when the work ended. That gap covers one assumption, not the whole forecast. Nobody misled the board. But the next writer has no right to carry that assumption forward as approved.

The difference between "read" and "modified" sounds pedantic. It decides who gets credit, who gets blamed, and what the board is told next month. Collapse both into "related to" and every session that ever opened the file becomes a suspect author.

Keeping more chats doesn't fix this. Buying a better search box doesn't fix it either. You need a record of which session changed which version, and whether it read or wrote, kept at the moment the work happened. You can't rebuild that afterwards.

If an AI changed a sentence in your last board pack, could anyone on your team tell you what it was allowed to say?


Discover more from Leverage AI for your business

Subscribe to get the latest posts sent to your email.

[rpnnrecommend total="5" thumbnails="false" class="recommendedlist" ]

Leave a Reply

Your email address will not be published. Required fields are marked *

© 2026 Leverage AI, Scott Farrell. All rights reserved. This content is made available on a limited, revocable, read-only basis only. No licence or right is granted to copy, reproduce, republish, scrape, store, adapt, summarise, index, embed, or use this content to create derivative works, work product, deliverables, methodologies, training materials, prompts, templates, software, services, research, or commercial outputs, whether by humans or machines, without prior written permission. This restriction includes internal business use, client work, consulting, advisory, implementation, and any use in or for artificial intelligence, machine learning, data extraction, retrieval, evaluation, fine-tuning, or knowledge-base construction.