Give each finance review meeting a decision and a cost

A finance calendar can fill with meetings that cover the same numbers at different levels of detail. The weekly operating review revisits the monthly pack, the leadership meeting repeats the operating review, and analysts spend the remaining time preparing another presentation. The remedy starts by identifying the decision each meeting exists to make.

Some meetings authorize spending. Others resolve a forecast assumption, assess a risk or decide what to investigate. A session may also provide necessary oversight without producing an immediate action. State that purpose precisely. Reviewing performance is too broad to determine whether a particular attendee, chart or hour is necessary.

For each recurring meeting, record the decision owner, required evidence, preparation deadline and expected output. If a decision belongs elsewhere, move it to the appropriate forum rather than keeping the meeting as a compulsory rehearsal. People should know when an issue becomes a decision and where that decision will be recorded.

Estimate the resources the current process uses over a normal cycle. Include extracting data, reconciling versions, writing commentary, rehearsing, attending and documenting follow-up. Ask the people doing the work for a recent example. Calendar duration alone often understates the commitment, particularly where a presentation is rebuilt for several audiences.

Suppose eight people attend a weekly one-hour meeting. At an illustrative average resource cost of $75 per hour, attendance represents $600. If preparation uses another ten hours at $60 per hour, the weekly resource estimate is $1,200. Over 48 occurrences, it totals $57,600. These assumed rates make the calculation visible; they are not salary benchmarks or an estimate of any particular company's cost.

Most of that amount may be existing payroll. Canceling the meeting does not automatically save $57,600 in cash. It releases capacity that might support better analysis, faster decisions or less overtime. Describe the benefit according to what the organization can actually do with the time.

A weekly review is useful when decisions can still change the following week's outcome. It is less useful when the relevant data arrives monthly and nothing material has changed since the previous meeting. Conversely, a monthly committee can be too slow for a cash issue that requires action before the next payroll date.

Map each material decision to its last responsible date. A supplier commitment, hiring start or price change may have a deadline imposed by operations. Work backward to the evidence cutoff and meeting date. The calendar should give the decision owner time to act rather than explain afterward why an approved plan could no longer be implemented.

Use exception triggers for events that do not fit a fixed schedule. A significant change in expected receipts can justify a focused discussion. Define who can call it, what evidence is required and who must attend. An exception process works best when routine issues still have a predictable place to go.

Choose a shared source for the figures and preserve its date and definitions. The SEC's guidance on performance metrics, written for public-company disclosure, emphasizes understanding what a metric measures and how it is calculated. The same clarity is useful in an internal meeting, even where those disclosure rules do not apply. A changed definition should not travel through several presentations unnoticed.

Let participants read straightforward updates in advance when that fits the team. Reserve discussion for decisions, disagreements, uncertainty and exceptions that require judgment. This requires a concise packet with clear questions; distributing a large spreadsheet immediately before the meeting does not create meaningful preparation time.

Avoid measuring improvement only by a shorter meeting. A ten-minute session that postpones every difficult issue can create more work later. The objective is to reach a sound decision at the right point, with enough challenge to expose an unsupported assumption and enough clarity to prevent the same debate next week.

For each agenda item, distinguish the person deciding, the people supplying necessary evidence and those who need the eventual outcome. Some participants may attend only the relevant part. Others may receive the decision record. The arrangement should preserve access to the people who understand operational constraints, not merely reduce headcount around the table.

Be explicit about delegation. If a substitute can provide information but cannot authorize a commitment, the meeting may still fail to resolve the issue. Define what authority is needed and how decisions will be escalated when the authorized person is unavailable. A recurring meeting should not become a queue for absent approvals.

Review the experience of junior staff as well. Preparing analysis can be valuable development, while rebuilding cosmetic slides every week may add little learning. Keep opportunities to explain reasoning and receive feedback even when reducing repetitive presentation work.

Change a limited part of the cadence for several cycles. Record decisions reached, unresolved items, preparation hours and actions completed on time. Ask whether important issues surfaced later than before and whether the freed capacity was used as intended. Compare the process with its own previous performance instead of declaring every canceled meeting a success.

Keep the resulting calendar simple enough to maintain. Each meeting should have a current owner, purpose and next review date. Retire sessions whose original purpose has ended, and restore a focused review if a concrete control or decision gap appears. Finance time is a resource to allocate; the calendar deserves the same deliberate attention as other recurring commitments.