The mistake embarrassed him at first. Then he recorded what he had done, restored the approved training configuration, and wrote down why the error had occurred. Leila reviewed the note and told him that careful documentation of a mistake was part of becoming a dependable technician. "Nobody learns anything from a report that says everything went perfectly," she said. Marcus thought about Emma's circuit and smiled. "Unless it really did," he answered.
Adrian Bell did attend the budget meeting, and he had a different view of the staffing problem. The company was preparing for a major contract renewal and looking for ways to reduce operating costs without affecting executive service levels. Adrian proposed postponing the vacant technician position, reducing preventive maintenance inspections, and replacing several older control modules under a single vendor contract that promised fewer emergency calls. He presented the plan with clean charts and a savings figure large enough to attract the attention of the finance committee.
Natalie looked at the projected savings and asked how the estimate accounted for the failures that had occurred on the twenty-seventh floor. Adrian replied that the recent sensor incident was an isolated anomaly and that the new vendor arrangement would simplify maintenance. He spoke with confidence, moving quickly past the question as though speed itself could establish an answer. Natalie asked whether the review of previous controller replacements had been completed, and Adrian's expression tightened.
"Facilities is handling it," he said. "But we shouldn't let one cleaning employee's lucky diagnosis become the basis for corporate policy." The room went quiet in the manner of executives who recognized that an important person had just chosen an unfortunate phrase. Natalie set down her pen and looked at him.
"The issue isn't the employee's former title," she said. "The issue is whether the proposed system will actually improve reliability. Bring me evidence of that, including the maintenance team's findings, before you ask for approval."
Adrian nodded, but as he left the meeting he was already composing a message to Peter asking for the review to be closed by Friday. The request did not tell Peter to falsify anything. It simply placed a date on work that could not responsibly be completed within that date, which was a common corporate way of discouraging an inconvenient answer. Peter read the message and forwarded it to Leila, then called Natalie through the normal reporting channel to explain what remained unverified.
The following Monday, a technical review meeting was held with finance, procurement, and operations represented. Marcus was invited to attend as the employee who had helped establish the original sensor discrepancy, but he was told in advance that he would not be expected to defend the whole maintenance budget. He arrived carrying the same plain notebook he used at work and sat near the back of the table, beside Leila. Natalie was there, as was Adrian, whose expression suggested he considered the meeting a needless complication.