A steering committee can approve an AI pilot in twenty minutes. The budget has a figure and the vendor has a name, and the sponsor leaves with a yes. The day the work stops, if nobody takes a second vote, is still unwritten. Someone usually notes that a working group can define success criteria the following week, the room agrees, and the meeting ends without a calendar day. Settling that day later means a worse meeting, after the money is spent and several people have organized their quarter around the pilot continuing.
Approve the end with the start
A stop date is a day someone can put on a calendar. Phrases such as "when the model is good enough," "once legal is comfortable," and "after we see traction" move whenever the people using them want more time. Approval of the spend waits until the room can point at a Friday, however small the first invoice looks.
For a pilot attached to work the company performs today, the weeks the tool is in use have to outlast two weeks of good manners. Handlers will try a new drafting tool in the first week because a vice president asked them to. The numbers worth having show up in a later, ordinary month, when volume is normal. Six to ten weeks of live use, counted from the day the workflow is in people's hands, is usually long enough to see that month. Integration time sits outside those weeks. If the integration slips, one written note may move the stop date by the same number of days.
When the underlying workflow is not running yet, the approval splits the calendar. The build gets its own checkpoint, and a missed checkpoint stops the work. The weeks of live use start only after the checkpoint is met. One motion that covers both construction and operation will reach its date with a demonstration and a request for more calendar. The request will sound practical. Read against the original minutes, it is a second project, and it needs its own approval.
The stop date belongs on a meeting the committee holds in the ordinary course. A Friday during an offsite, or a week when the person keeping the date is away, invites a postponement until everyone is back, and the later meeting has more spent money behind the pilot. Set the start so live use falls in the six to ten weeks before that meeting.
The minutes can carry the decision in a single sentence. Approve a pilot of claims-correspondence drafting for a regional insurer's Midwest claims book, live use beginning when that book's queue integration is in production, stopping on Friday, 12 June, unless this committee votes to continue on the evidence named below. A CFO can repeat that sentence without a translator.
The shutdown is the default
A date by itself produces a readout. People arrive and discover that nobody is authorized to turn anything off, and the hour becomes a negotiation. That negotiation belonged in the approval, while continuation was a choice.
The default goes into the same minutes as an instruction. On the stop date the integration is switched off, the token budget is closed, and contractor time charged to this pilot stops, unless a continuation vote has been recorded. The minutes should name the objects an engineer can act on without calling another meeting: the environment, the service account, and the user group that loses access. If two supervisors keep receiving drafted letters from a side inbox after the official channel is closed, the drafting has continued outside the pilot. Cost and claimant data both become harder to account for.
Data gets a sentence beside the date. The sentence should say what is deleted, what is retained, for how long, and who may instruct the vendor. Pilots outlast their announcements in the stores nobody mentioned. Prompt logs that include claimant details, and a search store of the claim files that nobody put in next quarter's budget, remain after a status note reports that the team learned a great deal. The approval is early enough to ask the security partner what the contract requires. In the month of the stop date, the same question arrives as an incident.
Continuation is a separate decision. The evidence page is filed a week before the stop date, so the committee reads it before anyone walks into the room. For the claims pilot, the page shows the share of drafts a handler sent without a material rewrite, the median minutes spent on a drafted letter against the prior quarter for the same letter types, and the cost of an accepted letter once review time is included. A page missing from the status memo leaves nothing to vote on, and the default stands.
Those figures come from the queue. A strong score on a vendor-chosen sample of last year's letters can sit beside longer handle times on live work. The approval names which result the committee will read, and the vendor agrees to that choice before kickoff.
People will try to park pieces of this with a working group. The data sentence, the name of the person who will keep the date, and the figures on the evidence page are the pieces most often deferred. If they leave the room unfinished, the Friday in the minutes is ceremonial. The working group will define success a few weeks later, under the sponsor, with the vendor present.
A second person keeps the date
Running the pilot is the sponsor's work. The stop date needs a holder who is scored on keeping the date. After kickoff, keeping the option open is an ordinary managerial impulse. A contractor has started, and a business unit has been promised a result. Another month might soften the numbers. The holder exists so that a further month comes back as a written request.
A workable holder is the finance partner assigned to the initiative, or the person who already prepares the monthly AI note for this committee. The stop date is on their calendar. The shutdown steps are drafted the week after approval, when the pilot is only a proposal, and filed with the status memo. On the stop date the committee marks up that note, which names the service account and the purchase order. A request to move the date returns to the committee that approved the pilot, in writing, ahead of the date, with the evidence page or with a plain account of why the page is not ready.
The license term belongs with that person too. A yearly license signed in April for a pilot that stops in June leaves finance paying for months the committee expects to switch off. Any term past the stop date, including an automatic renewal in the vendor's order form, needs its own signature from that committee.
Vendors will ask for more time. When a success manager can move the date with a note to the champion, the date was a personal intention. The request returns to the committee as a change to a decision recorded in the minutes. It states the original date, the proposed date, which measures are in hand, what spend continues through the extra weeks, and what those weeks are supposed to change. The committee acts on those facts.
While the room is doing paperwork, the charter should say how a stop on the planned date will be read. It is the ordinary completion of a pilot that reached its date without a continuation vote. In the operators' reviews, that stop counts as finishing the assignment. The sponsor's judgment in bringing the pilot forward stays intact. If the charter is silent, rumor supplies the meaning, and capable people round the share of unedited drafts upward, because they expect the close to be read as theirs. The extension that follows is paid for with a softer page than the minutes required.
The people doing the work should hear the stop date at kickoff, as part of the assignment, from the sponsor and the holder together. Hearing it first as a rumor in the eighth week teaches them that the date is negotiable and that a candid number carries a penalty. A short note at kickoff, with the Friday and the default written out, is enough.