When Decisions Are Made but Not Tracked

Owners rarely lose value because they did not ask the right questions. They lose value because they asked, decided, and then allowed the asset to drift back to default behaviour. In an operated hotel, default behaviour sits with the operator. If an owner cannot evidence intent and follow-through, the operator position becomes the default.

This is not administration. It is a control problem. A decision that is not recorded behaves like an opinion. An approval that is not tracked behaves like consent. An action without a single accountable owner behaves like nobody's job. These gaps show up later as cash conversion variability, delayed CapEx, and performance that cannot be explained.

Where the problem shows up

You will recognise the pattern quickly.

• The same topics return every month with slightly different wording. The meeting feels busy, but nothing closes.

• "We agreed" becomes "we discussed", then becomes "we will revisit".

• Commercial initiatives stall because nobody owns the next step, and deadlines are not explicit.

• CapEx commitments creep. Scope expands quietly, timelines slide, and funding assumptions blur.

• Approvals become disputed. The operator believes the owner approved. The owner believes it was only a proposal. Time passes and the hotel proceeds anyway because the approval window closed, or the item is treated as deemed approved under the agreement.

The minimum system that works

Owners do not need complex workflow software. They need three registers that stay light and are reviewed every month. If you implement one change, implement the discipline of updating these registers before the meeting and closing them during the meeting.

Decision Log
A Decision Log is a record of intent. Minimum fields:

• Decision statement (one sentence, no ambiguity).

• Rationale (why this is the decision, not a recap of the discussion).

• Effective date.

• Financial envelope (the cap, not the wish list).

• Expected outcome (what should improve, and how you will recognise it).

• Dependencies (what must happen for this to work).

• Revisit trigger (what would justify reopening the decision).

Approval Register
An Approval Register is a dated record of approvals requested, deadlines, and outcomes. It protects the owner against drift and protects the operator against ambiguity. Minimum fields:

• Item requiring approval (capital expenditure (CapEx), material contract, policy change, brand consent, lender consent).

• Date submitted for owner approval.

• Response deadline (the approval window defined by governance or agreement).

• Outcome (approved, rejected, approved with conditions, deemed approved, withdrawn).

• Financial envelope and funding source.

• Conditions and information relied on (what the approval is based on).

• Link to the next step in the Action Register.

Action Register
An Action Register is accountability. Minimum fields:

• Action (verb first).

• Single accountable owner (one name).

• Due date.

• Status (not started, in progress, blocked, done).

• Dependencies.

• Closure evidence (what proves it is done, not only that it was attempted).

• Escalation trigger (what forces an owner decision between meetings).

Boundary statement: this is owner steering, owner approvals, and follow-through. It is not an operations task list. If an item can be solved by the hotel team within existing authority and budget, it does not belong here.

Cadence that creates closure

The registers only work if the meeting is designed for closure, not conversation. A practical sequence is:

• Close prior actions. Anything overdue is either re-dated with a reason, escalated, or cancelled. No silent carry-over.

• Confirm decisions still stand. If a decision is being reopened, state the trigger and the new options.

• Review approvals pending and upcoming deadlines. If the owner needs more information to decide, set a firm date for the missing inputs and a firm date for the decision.

• Then move into performance and forward priorities.

Owners often start meetings with the profit and loss (P&L) and end with "other items". This sequence often reduces closure. The P&L discussion only creates value if it produces decisions, approvals, and owned actions.

Controls that keep the system owner-side

A register system fails when it becomes vague. Apply three controls.

• Decided versus noted. If it is not decided, record it as "no decision" with the condition required to decide.

• Envelope discipline. Every decision and approval must state a financial envelope and funding source. If the envelope changes, that is a new decision.

• One owner, one date. Committees do not deliver actions. If an action has multiple stakeholders, keep one accountable owner and list others as contributors.

Escalation triggers should stay simple: cash downside, CapEx commitment, deadline approaching, lender or brand consent required, or any dependency that threatens the critical path. When a trigger is hit, do not wait for the next monthly meeting.

Failure modes and fixes

Common failure modes are predictable.

• Too detailed. The register becomes an operations tracker and collapses under its own weight. Fix: keep only owner steering items, approvals, and commitments.

• No dates or owners. Everything becomes "in progress". Fix: enforce a due date and one accountable owner for every action.

• Decisions without a revisit trigger. People reopen topics casually. Fix: define what would justify reopening, otherwise the decision stands.

• Approvals without a clock. Owners lose control by silence. Fix: always record submitted date, response deadline, and outcome, including deemed approved where applicable.

Closing thought

Owner-side asset management is not about attending meetings. It is about ensuring that monthly information becomes controlled outcomes. Decisions that stay decided reduce drift. Approvals that do not drift protect owner intent. Actions that close convert analysis into Owner Free Cash Flow (OFCF) and predictable cash yield. Over time, this is what turns operational activity into durable owner value.