Who decided?

The room has several answers

The board paper says the rollout will require a second weekend of field work. The customer has already been promised that the business will absorb the cost. The owner asks who approved that promise. The sales director looks toward operations. Operations points to an account thread. Finance says it only received the revised estimate yesterday.

There is no shortage of people who know something about the decision. The account manager asked whether another weekend was possible. A field manager said a crew could be available. Someone in finance confirmed that the cost had been estimated. The customer's contact received an email saying the business would take care of it.

Each person can explain their contribution. Nobody can point to the moment when a person with the right authority accepted the extra cost. The conversation moved gradually from possibility to expectation to promise. By the time the owner asks who decided, the business is already committed.

Participation can look like permission

The field manager's reply was about availability. A crew could work that weekend. That did not mean the extra work was included in the customer's price, or that the field manager had authority to give it away. A statement about what is possible became part of the apparent approval for what should happen.

Finance's estimate was equally easy to misread. Putting a number on the work helped the business understand the proposal. It did not authorize the expenditure. Yet a person reading quickly could reasonably assume that finance had seen the cost and was comfortable with it.

The account manager had a different pressure. The customer needed reassurance, and several colleagues had replied helpfully. Waiting for another discussion felt like creating a delay after the practical questions had already been answered. The final email was written as a service gesture, not as a request to change the company's margin.

The better question is what the business intended to delegate. An account manager might be allowed to rearrange a meeting but not promise free field work. A service manager might approve a small recovery cost within a budget but need finance for a larger commitment. The boundaries can be practical without requiring the owner to attend every exchange.

The decision should have an address

The useful record is narrower and stronger. It says what was proposed, what cost and customer obligation were understood, who approved that proposal and what authority they used. If a condition was attached, the condition travels with the approval. A later reader should not have to infer it from the tone of the conversation.

That does not require a written essay for every decision. It requires a clear approval for the decisions that create a material commitment, and a way to carry that approval into the action. The person sending the promise should not have to guess whether a colleague's earlier reply was enough.

The owner can then keep responsibility without becoming the approval queue. People know what they may decide, exceptions reach the right person, and the business can explain a commitment without reconstructing office politics. A board can ask who signed off and receive an answer about the decision rather than a list of everyone who was nearby.

At the next board meeting, the owner does not need another list of everyone copied into the conversation. The useful answer is a particular decision: this proposal, this person, this authority. If the business cannot point to that moment, what exactly did it mean when it said the work was approved?