Chapter 12
Earning Authority Again
At 8.42 on Monday morning, Maya found an expired date beside the service-credit use in the register.
The small group still had access. Advisers were still using the retrieval feature to find procedures. Daniel had tested the latest source update. Leila’s team had reviewed the recent cases. Nothing on the screen announced a problem.
The date was the end of the authority Maya had granted after the source-change incident.
She called Daniel.
“Is it still on?”
“Yes. The review is this afternoon.”
“The permission ended this morning.”
Daniel looked at the decision record. Maya was right. They had agreed to review the narrowed use by that date. They had not written an automatic extension into the decision.
“I can disable it now,” he said.
Maya considered the service team’s working day. The approved ordinary search route remained available. A sudden switch without telling Leila would create confusion, but leaving the feature running because the meeting was later would turn an expiry date into decoration.
“Tell Leila. Pause new access until we decide. Keep the source documents available.”
Daniel called Leila before changing the setting. She told the team leads which search route to use and asked them to pass the instruction to the small group. At 9.03, Daniel confirmed the retrieval feature was unavailable for service-credit questions. The procedure collection remained accessible through the ordinary knowledge base.
At the afternoon meeting, Nadia put the decision record on the table.
“We remembered the incident trigger,” she said. “We nearly forgot the date.”
What the date meant
Maya had not set the date because she expected the feature to become unsafe on a particular morning. She had set it because the evidence supporting a limited use would age.
The team had narrowed the feature after an unreviewed procedure edit reached live advisers. For approval and eligibility questions, it now showed source material and status rather than drafting a case outcome. Leila had taken control of relevant source changes. Daniel could test them and disable access. Priya and the team leads could see how advisers worked with the feature. Nadia could challenge the review. Maya could decide whether those conditions still justified use.
Those were arrangements to be checked, not promises that would remain true indefinitely.
Daniel asked whether they should have scheduled the review a day earlier.
“Yes,” Maya said. “And the expiry should have appeared in your access schedule as well as my decision record.”
The lapse was brief. The team had an approved fallback. No adviser had been told to rely on an expired decision once Maya found it. Still, they recorded the missed handoff. If renewal depended on someone noticing a date in a register, the arrangement needed work.
How would your team notice that permission was about to expire?
Guidance
Trace the date from the decision record to the person who controls access. Check whether a review can happen before expiry and whether someone is responsible for acting on the result. Identify the working route staff would use if renewal were delayed.
Your answers are saved only in this browser on this device. Nothing is sent anywhere.
Leila wanted to know whether the morning pause itself counted as a failure of the tool.
“No,” Nadia said. “It is a failure in how we managed its authority.”
That distinction mattered. A retrieval answer could be correct while the organisation lacked current permission for that use. The reverse was also possible: a current authorisation could remain on paper after the sources or working conditions had changed.
Authority expires because its reasons can expire.
Maya asked the group to treat the meeting as a fresh decision. The fact that advisers had used the feature yesterday would not settle whether they should use it tomorrow.
What the review could show
Leila brought the case and source review. Daniel brought the configuration and access history. Priya brought examples from advisers, including cases where they chose ordinary search. The CFO brought the cost view Finance had built with the team, updated with the work actually spent during the further limited period.
The feature had helped some advisers find a relevant procedure when the customer’s language did not match the document title. In those cases, the source link made the instruction easier to inspect. The narrower display for approval and eligibility questions had avoided the earlier problem of a generated sentence appearing to give an adviser decision authority.
It had not become the preferred route for every case. Some advisers reached a known procedure faster through ordinary search. One had stopped using the feature for straightforward questions after finding that reading an answer and then its source added work. Leila regarded that as a sensible choice.
The source-change route had been exercised during an ordinary procedure update. Leila received the proposed change before publication, checked its status, and Daniel tested questions against a restricted copy. The live feature did not see the new wording until that work was complete. This was evidence that the repaired route could function during normal work, though it was still one update.
The incident log showed no further customer decision made from an unchecked output. It did show doubtful answers caught by advisers. The team reviewed them, corrected one source label and left another answer as a known limitation: when two procedures both appeared relevant, the feature displayed both rather than pretending to settle which governed the case.
Priya thought that limitation was acceptable if an adviser understood it. Nadia asked how they knew.
Priya had asked advisers to talk through several recent cases. Most could explain when to use the source and when to refer. One adviser had described the two-source display as “the system being unable to choose”. She had then checked the case facts and asked a team lead. Her action was sound, though her description suggested the training could be clearer.
The CFO’s update showed that the work of source control and monitoring had continued. It had become more regular and less dominated by incident recovery. There was still no sound basis for claiming a cash saving. The benefit was more modest: useful procedure discovery in some cases, with a source that an adviser could check, at a continuing cost the organisation could now describe.
Maya asked Leila for her recommendation.
“Renew the narrow use for this group,” Leila said. “Do not widen it yet. Keep ordinary search available. We should make the expiry visible in the access process this time.”
Daniel agreed, but wanted to discuss the system provider before they decided.
A feature inside a contract
The retrieval feature came with the existing knowledge base. That had made the initial route smaller than introducing a separate product. It did not mean the organisation should accept every term and operating limit without review.
Daniel had asked the provider how source updates reached the feature, whether earlier versions could remain available and what controls existed to hold a change for approval. The response clarified parts of the update process. It did not give Leila the publication control she needed by itself. Their own source route remained essential.
The CFO opened the Vendor Evaluation Sheet. She did not want the team to compare a long list of features. They had a specific use and a specific failure behind them. The questions were whether the service could support the narrowed workflow, whether the organisation could inspect and manage source status, what support was available when behaviour changed, and what it would take to leave.
Daniel could answer some from experience. The feature was available through a familiar screen. It could be disabled for the small group. The team had been able to preserve outputs and test changes. Other matters depended on the contract and the provider’s support arrangements.
The AI Contract Review Checklist brought a different set of questions into the room. Which use and data were covered by the current terms? What records could the organisation obtain if it needed to investigate an output? How were changes to the service communicated? What happened to configuration and retained material if they stopped using the feature or changed the knowledge-base arrangement?
Maya did not ask Daniel to give a legal interpretation of the contract. She asked him and the CFO to mark what was known, what was written in the agreement and what needed specialist review. They could then decide whether an unresolved term was material to this limited use.
The CFO also wanted a commercial answer. If the provider later charged separately for the retrieval feature or changed a usage allowance, the current cost case would change. She asked Daniel to obtain the applicable pricing and notice terms in writing before anyone proposed a larger group.
Leila looked at the evaluation.
“Would any of this make us move to the demonstrated product?” she asked.
“Not on its own,” Maya said. “We are deciding whether this use still earns permission. A different product would need its own case.”
The demonstrated product had been set aside for service-credit retrieval after the bounded comparison. The small internal build remained deferred. Neither became the automatic answer to a weakness in the current arrangement.
A renewal is a decision about the work as it now exists, not a reward for the original choice.
The retrospective without a victory line
Nadia brought the Retrospective Template to a separate session with the working team. Maya stayed for it but asked others to speak first.
Daniel said the ability to disable the feature quickly had worked. They had preserved the source versions and outputs after the unreviewed edit. The investigation could establish what advisers might have seen. The repaired source route had then survived one ordinary update.
He also said the initial design had assumed he would be told when a procedure changed. That assumption had not been built into the publication process. The team learned it when the live source moved without him.
Leila said the team had treated source ownership as a task before release, but had not fully accounted for who else could edit a procedure in the knowledge base. She now had a review route for approval, eligibility and escalation changes. She wanted the same question asked of other source collections before anybody reused the feature elsewhere.
Priya said advisers had learned to report doubtful answers when they did not have to prove the technical cause. She wanted that expectation kept. She also wanted less training language about “using AI well” and more examples of the actual service-credit steps: find the current source, check the case facts, follow approval, record the decision.
Nadia asked what had not worked.
“The first announcement said what was in scope,” Priya said. “It did not tell people enough about what an odd answer looked like. We learned that from the reports.”
The CFO added that Finance had looked at the invoice first because that was the easiest cost to find. It took the source-change recovery to make the continuing people’s time visible. She wanted future cases to budget for that work before release.
Maya asked what the team would do differently if it began this same use again.
Leila would settle procedure status before comparing tools, and make the source change route part of the release conditions. Daniel would test access and source updates using an ordinary adviser account. Priya would bring adviser wording into the test earlier. Nadia would insist on an expiry date paired with an advance review booking. Maya would ask what a clean exit required at the first authorisation, not at the renewal meeting.
They recorded those decisions. They did not write that the pilot had been a success because it remained in use. Continuation was one possible result of learning.
A good retrospective has to be useful even if the next decision is to stop.
The option to retire
Maya asked Daniel to show the Exit and Retirement Checklist.
“If we decide not to renew,” she said, “what happens tomorrow?”
Daniel had already paused access that morning. The ordinary procedure route was working. A permanent retirement would still require more than leaving the switch off.
He would remove the service-credit group’s access to the retrieval feature, document the final configuration and identify any trial or live copies held outside the approved source collection. Leila would confirm that current procedures were available through ordinary search and that no instruction sent to staff still pointed them to the retired feature. Team leads would check open cases where an adviser had relied on a generated answer and ensure the case record cited the governing procedure and approval, rather than the assistant’s wording.
Priya would tell advisers what was retiring and what remained. The source documents were not being withdrawn. The approved service-credit process would continue. Staff should stop relying on saved answers or screen captures because those could outlive the source version that produced them.
The incident and decision records would be kept according to the organisation’s normal record arrangements. Removing access did not mean erasing the evidence of why the use had been authorised, paused, narrowed and stopped.
The CFO asked about cost. The exit would take staff time but was manageable while the group was small and the fallback remained familiar. If they widened use and let procedures become harder to reach without the feature, the exit cost would grow.
They did not retire it that day. Walking through retirement still sharpened the renewal decision. If Maya could not explain how the organisation would leave, she would have less control over the terms on which it stayed.
Nadia asked whether a tool should be retired as soon as it failed to produce a cash return.
“No,” the CFO said. “But the benefit has to be worth its continuing work. We should be able to say what we are buying with that effort.”
For the service-credit use, the evidence supported a narrow benefit. The organisation could continue to test whether that benefit held. It did not support expanding access simply to recover the effort already spent.
Policy and permission
Leila had updated the AI Policy One-Pager after the source-change incident. Its plain rules covered permitted use, prohibited inputs, source checking, human approval, reporting and who could authorise a change in scope.
Maya asked whether a policy statement renewed the service-credit use.
“No,” Leila said. “It tells people the standing rules. This decision says this particular use can continue under them.”
That distinction was important. A general policy could say that staff must check outputs. It could not establish that the source collection for service credits was current or that the team had capacity to review it. A decision for this use needed its own scope, owner, evidence and expiry.
What does a particular use still need to establish under your general policy?
Guidance
Choose one use covered by your policy and look for its current decision. Check what that decision says about the source collection and the people available to review it. Name any condition that the policy alone cannot establish.
Nadia noticed a line in the policy that said staff should “always validate AI outputs”. She asked Priya what it meant on a call.
“Open the cited procedure, check that it is current, read the relevant passage, then check the case facts,” Priya said. “And refer if the procedure says to refer.”
They changed the broad sentence to a more usable instruction for the service-credit setting. The one-pager remained short. It did not attempt to reproduce every procedure. It gave staff the boundary and the route to the source of authority.
Maya also asked whether the policy covered a new team asking to use the knowledge-base feature for a different task. It said such a use needed screening and a named decision owner. It did not allow one team’s approval to spread to another merely because the same technology was already available.
The sales director’s tender trial remained closed. The marketing assistant remained a separate entry in the register. The service-credit renewal would not settle either.
The decision before the switch
At 3.26, Maya returned to the register entry. She had evidence of a narrower working use, a functioning source-change route in one ordinary update, a known fallback, continuing costs and an exit path. She also had limits: uneven usefulness across advisers, doubtful outputs still possible, and no demonstrated cash return.
She wrote the renewal decision in plain terms.
The small group could continue using the retrieval feature to locate and check service-credit procedures. For approval and eligibility questions, it would display source material and status without drafting a case outcome. Advisers would establish case facts and follow the existing team lead approval route. Leila would own the sources and service outcome. Daniel would control configuration, test approved source changes and disable the feature if a trigger was met. Reports would continue through the service route. Nadia would challenge the next review. Maya would decide whether to renew, narrow, expand or retire it at the new expiry.
FIG-12.1
What a renewal decision names
| Element | What Maya’s renewal said |
|---|---|
| Scope | The small group; service-credit procedure retrieval only |
| Authority mode | Assist; approval and eligibility questions get source material and status, not a drafted outcome |
| People’s duties | Establish case facts; follow team lead approval; report doubtful outputs |
| Owners | Leila: sources and service outcome. Daniel: configuration, source-change tests, disable. Nadia: challenge. Maya: the decision |
| Evidence for next time | Reports, case review, source-change route performance, cost of continuing work |
| Expiry | A new date, visible in the access schedule as well as the decision record |
The review meeting went into their calendars before Daniel restored access. The access setting carried the same end date as the decision. Daniel would receive a reminder before it, and Leila would bring evidence in time for a decision before permission lapsed.
Maya declined to widen the group. A request for expansion would require evidence that the benefit survived ordinary use and that the source and review work could support more advisers. The current renewal did not imply approval for that step.
She signed.
Daniel restored access to the authorised group and checked it with an ordinary adviser account. Leila sent the team a short note: the limited use had been renewed under the same narrowed boundary, the ordinary search route remained available, and the reporting path had not changed.
Priya watched an adviser ask a service-credit question later that afternoon. The feature showed the relevant procedure and its status. The adviser opened it, checked the case record and referred the approval question to the team lead. Priya did not record the interaction as proof of a strategy. It was one case handled within the renewed authority.
The next question on Tom’s desk
At 5.04, Maya sent Tom a short account of the renewal. It said what the organisation had allowed, why it had kept the group small, what it cost to maintain, and when the authority would be reviewed again.
Tom replied with a question for the next board discussion.
Do we know what rules already apply when we use this sort of system?
Maya did not forward it to Daniel as a request for a list of AI laws. The service-credit decision involved customer information, communications, approvals and records before the retrieval feature arrived. The technology had changed how information was found and presented. It had not made the organisation’s older obligations disappear.
She asked Nadia to help map the question to the actual uses in the register. The renewed service-credit use would be one entry. The tender and marketing uses would need their own questions if they moved forward. The small-claims proposal, still at an early stage, would require particular care if anyone suggested giving a system authority to decline a claim.
Maya closed the register. The service-credit feature had earned permission to continue for another bounded period. That did not answer every question Tom could ask about it.
Use the Retrospective Template to record what changed your judgement, including failures and repairs. Use the Exit and Retirement Checklist before renewal so stopping remains practical. Keep the AI Policy One-Pager usable for staff, and use the Vendor Evaluation Sheet and AI Contract Review Checklist to examine the service and its terms against the work you actually authorise.
Chapter 13, The Rules That Already Apply, asks which obligations already bind the organisation’s decisions and records, however those decisions are produced, and how the team finds questions that need specialist advice.
