Finance for Non-Finance Managers SOP / Operating Playbook

Model Operating P&L Manager SOP and Operating Playbook

Purpose and scope

Purpose

The manager's purpose is to translate operating activity into financially responsible action. In practical terms, you need to answer five connected questions:

• What changed in revenue, cost, margin and operating result?
• Which operating drivers explain the change?
• When will the related cash be received or paid?
• What should change in the budget or forecast?
• Which action or internal investment should be taken, recommended or escalated?

The role is not limited to reading a monthly report. You own the quality of the operating assumptions, the actions under your control and the clarity of the recommendation you give to finance and leadership.

Included work

This model covers a business unit, region, site, service line, product, programme or other operating area with an assigned P&L, budget or resource responsibility. It includes:

• interpreting management P&L results;
• explaining actual-versus-plan and actual-versus-forecast differences;
• maintaining operating assumptions for budgets and rolling forecasts;
• connecting price, volume, mix, labour, material, capacity and service drivers to financial outcomes;
• examining contribution, break-even and other unit-level economics suited to the business model;
• identifying cash-timing and working-capital effects that arise from operating choices;
• preparing options and business cases for internal spending or investment;
• deciding within delegated limits and obtaining approval outside them; and
• recording actions, assumptions, decisions and follow-up.

Operating boundaries

You may interpret, challenge, estimate, recommend and act within delegated operating limits. You do not create accounting policy, change official financial records, move funds, approve borrowing, set tax treatment, make specialist assurance conclusions or authorize expenditure beyond your approved limit.

Do not force every business into the same metric. A useful “unit” may be an order, customer, subscription, delivery, appointment, production batch, occupied room, case or billable hour. Finance and the operating owner should agree definitions before the analysis is used.

Roles and working relationships

A handoff is complete only when the receiving person knows what is being transferred, which decision or action is expected, when it is needed and where the supporting information can be checked.

Required inputs and source-of-truth rules

Before you explain a result or make a recommendation, collect the smallest sufficient set of approved inputs:

• management P&L for the period and a comparable budget, forecast or prior-period view;
• definitions for revenue, gross profit, contribution, operating expenses and the operating result used locally;
• operational volumes, capacity, labour, material, service, quality and delivery measures;
• realized prices, discounts, product or customer mix, and commercial commitments where relevant;
• budget and forecast assumptions, rates, timing and owners;
• approved cash-timing information such as receivable, billing, inventory, supplier-payment and capital-spend dates;
• the business's unit definition and agreed variable-cost logic;
• active actions, prior decisions, known risks and unresolved exceptions; and
• delegated decision limits and approval routes.

For each material number, identify:

• its definition;
• reporting period and currency;
• source system or owner;
• whether it is actual, committed, forecast, estimate or assumption;
• when it was refreshed;
• whether finance has reconciled it; and
• any known limitation.

Local-system field: official management P&L and period-close report.
Local-system field: approved operational data source.
Local-system field: budget and forecast platform.
Local-system field: authorized cash or working-capital view.
Local-policy field: financial calendar, reporting cutoff and late-adjustment process.
Local-policy field: metric definitions, materiality thresholds and delegated decision rights.

When two sources disagree, do not choose the more convenient number. Record the difference, identify the owners of both sources and obtain a reconciled figure or label the analysis provisional.

Trigger-to-close workflow

Use this workflow for a scheduled performance review, a material variance, a forecast update, a margin problem, a cash-timing concern, a budget request or an internal investment choice.

1. Qualify the trigger and the decision

State what initiated the work and what must happen next. A trigger might be the monthly close, a weekly forecast cycle, a margin threshold, a missed volume plan, an unexpected cost, a delayed customer payment, an inventory build or a request for new spending.

Write one decision question. For example: “Should the region change staffing and scheduling for the next forecast period?” is clearer than “Review costs.” Identify the decision owner and needed-by date at the start.

Check whether the issue is within your role. Route suspected financial-record errors, unauthorized transactions, legal or contractual questions, safety concerns, sensitive data or activity beyond your access immediately to the appropriate owner.

Output: review brief with trigger, period, scope, decision question, owner and deadline.

2. Confirm the baseline and data readiness

Choose the comparison that fits the question: budget, latest forecast, prior period, prior year, approved business case or agreed unit target. Keep the approved baseline separate from the latest expectation.

Confirm that the P&L and operational measures cover the same period, organisational boundary and currency. Check whether late invoices, accruals, allocations, corrections or timing differences could change the interpretation. Ask finance to resolve official-reporting questions; do not silently alter a number.

Decision: Is the information good enough to support action?

• If yes, continue and record minor limitations.
• If partly, continue only with clearly labelled estimates and a plan to confirm them.
• If no, stop the recommendation and request the missing or corrected information.

Output: confirmed baseline and data-readiness note.

3. Reconcile the operating story with the P&L

Read the P&L from outcome to drivers. Start with revenue, then gross profit or contribution, controllable operating expenses and the defined operating result. For each material variance, ask which operating event created it.

Use a driver bridge where practical:

• Price: change in realized price after discounts or concessions.
• Volume: change in units, jobs, customers, hours or another agreed activity measure.
• Mix: shift toward offerings, channels or customers with different economics.
• Variable cost: change in input cost per unit, including labour or material where suitable.
• Fixed or step cost: change in costs that do not move directly with each unit over the relevant range.
• Timing or classification: difference caused by recognition timing, cutoffs, allocation or correction rather than operating performance.

Do not assign a cause because it sounds plausible. A cause should connect a financial variance to an observed operating driver and a named owner who can confirm it.

Output: P&L commentary and driver bridge separating facts, assumptions and unresolved questions.

4. Test unit economics and operating capacity

Unit economics describes the revenue, variable cost and contribution associated with a meaningful unit of activity. Define the unit first. Then calculate only with approved components.

A common starting point is:

• contribution per unit = realized revenue per unit minus agreed variable cost per unit;
• contribution rate = contribution divided by revenue; and
• break-even units = relevant fixed costs divided by contribution per unit, when contribution is positive and the assumptions suit the business.

Check capacity as well as arithmetic. More volume may require overtime, extra delivery miles, additional support or quality rework. A product can show positive contribution per unit but still be a poor choice if capacity is constrained, acquisition cost is omitted or demand is uncertain.

Local-policy field: approved unit definition, cost classification and treatment of shared costs.
Local-system field: realized price, volume, cost and capacity sources.

Output: unit-economics diagnosis with sensitivities and operational constraints.

5. Connect profit to cash timing

Profit records revenue and cost under the organisation's accounting approach. Cash reflects when money is received or paid. The two can move differently.

Identify operating events that may absorb or release cash:

• invoicing readiness and billing delay;
• customer payment timing and disputed receivables;
• inventory purchases, usage and excess stock;
• supplier deposits and payment terms;
• payroll and other dated operating commitments; and
• approved capital expenditure.

Use the authorized cash or working-capital view. Your task is to identify the operating cause, owner and timing risk, not to invent a cash balance or funding decision. A profitable order may consume cash before customer payment; lower inventory may release cash but create service risk if cut without demand and lead-time analysis.

Escalate borrowing, credit, covenant, banking and liquidity-policy decisions to the responsible specialists.

Output: profit-to-cash timing note with dated operating actions and escalations.

6. Refresh the budget or forecast

A budget is an approved plan and resource boundary. A forecast is the current best estimate based on what is known now. Do not change the budget to hide a variance. Update the forecast when a driver has changed and the effect is supportable.

Build the update from drivers rather than applying one unexplained percentage. State expected volume, realized price, mix, variable rates, staffing, capacity, fixed commitments and timing. Show a base case and at least one relevant downside or sensitivity when uncertainty could change the decision.

For every changed assumption, record:

• old value and new value;
• reason and supporting source;
• financial and operating effect;
• owner;
• confidence or range;
• action tied to the assumption; and
• next review point.

Output: rolling forecast or scenario update and budget-versus-actual explanation.

7. Develop actions and decision options

Turn diagnosis into choices. Options may involve scheduling, capacity, waste, service design, product mix, approved price changes, discount control, inventory, billing readiness, vendor timing or staged spending.

For each option, show:

• expected operating change;
• P&L effect and timing;
• cash effect and timing;
• customer, workforce, quality and delivery consequences;
• assumptions and sensitivities;
• reversibility and stop conditions;
• action owner; and
• approval needed.

Include a realistic “do nothing differently” baseline. Avoid presenting a single precise return when important inputs are estimates.

Output: decision options with trade-offs and a recommended action or escalation.

8. Frame an internal investment or resource request

When an option requires material spending, prepare a business case before seeking approval. State the problem, baseline, options and incremental cash flows. Use the organisation's approved decision method, which may include payback, net present value, internal rate of return or another rule supplied by finance.

Keep operating assumptions separate from accounting allocations. Show the timing of outflows and benefits, implementation dependencies, downside case, critical sensitivity, staged release and post-decision review. Use only the hurdle rate and financial treatment provided through approved local sources.

The manager prepares and recommends. The named approver decides. A calculation does not create approval and does not repair unsupported assumptions.

Local-policy field: spending, operating-expense and capital approval thresholds.
Local-policy field: approved decision method, hurdle rate source and review forum.
Local-system field: business-case template and approval record.

Output: internal decision memo or business case with recommendation, scenarios and approval request.

9. Communicate, hand off and obtain decisions

Prepare a concise review pack that answers:

• What changed?
• Why did it change?
• What happens if no action is taken?
• Which options were tested?
• What do you recommend, and on which assumptions?
• What may you decide locally?
• What needs approval, from whom and by when?
• What will be measured after the decision?

Reconcile the pack with finance before presenting material financial claims. Send each action to a named owner with due date and completion evidence. Send each approval request to the person who can decide it.

Output: performance review, decision request, action handoffs and recorded decision.

10. Execute, monitor and close the loop

After a decision, update the forecast and relevant records without rewriting the original baseline. Track whether actions occurred and whether the expected operating drivers moved. Separate implementation progress from realized financial benefit.

At closure, record:

• decision and conditions;
• actions completed and open;
• actual or latest expected financial effect;
• material differences from the approved case;
• continuing risks and owners;
• next review date; and
• any further decision needed.

If the result differs from the case, investigate rather than forcing the narrative to match. A useful close identifies what the organisation learned and which assumption should change next time.

Output: updated forecast, action record and decision closeout note.

Operating cadence

Daily or active-operating cadence

• Review demand, volume, staffing, capacity, service, quality and material operating exceptions.
• Check urgent billing blocks, inventory shortages, supplier changes or customer issues that may affect cash timing.
• Confirm that immediate actions stay within approved budget, pricing and spending limits.
• Record material new facts in the approved system and notify the relevant owner.
• Escalate suspected record errors, unauthorized spend, sensitive-data exposure or a decision outside your role.

Local-policy field: daily exception thresholds and emergency route.
Local-system field: daily operating dashboard and exception record.

Weekly cadence

• Review volume, price, mix, labour, material, capacity, margin and forecast signals.
• Compare current drivers with the latest forecast and identify changes that could affect the next reporting period.
• Review aged billing, receivable, inventory or supplier-timing exceptions with the responsible owner where these affect your operation.
• Update assumptions, actions, risks and decisions using a consistent cutoff.
• Meet finance or another named partner when a material variance or decision needs reconciliation.
• Confirm owners and due dates for the next operating actions.

Local-policy field: weekly cutoff, materiality criteria and meeting participants.

Monthly or period-close cadence

• Confirm the reporting period, organisational scope and source readiness.
• Review the management P&L from operating result to its drivers.
• Prepare the actual-versus-budget and actual-versus-forecast explanation.
• Update the driver-based forecast and relevant scenarios.
• Review unit economics, margin, capacity and cash-timing signals.
• Decide routine corrective actions and prepare exceptions for approval.
• Present the review, record decisions and update owners.
• Close prior actions and schedule the next review.

Local-policy field: close calendar, review forum, distribution list and approval sequence.

Quarterly, annual or planning cadence

• Revisit demand, capacity, price, mix, cost rates and fixed commitments.
• Test whether the unit definition and driver model still reflect the operation.
• Build or challenge budget assumptions from operating activity.
• Review resource allocation and internal investment priorities.
• Compare realized results with earlier business cases.
• Identify assumptions that repeatedly fail and improve the next planning cycle.

Event-driven cadence

Run the trigger-to-close workflow when there is a material price or supplier change, demand shock, margin decline, forecast miss, cash-timing concern, unexpected commitment, investment request, major customer or product-mix shift, capacity constraint, data conflict, policy breach or decision deadline at risk.

Decision and approval model

Local-policy field: replace typical owners with the actual decision-rights map and approved delegates.

Handoffs

Every financial-operating handoff should include:

• subject, period and organisational scope;
• current version and source date;
• facts, assumptions and estimates clearly separated;
• relevant P&L, cash, budget or unit-economics effect;
• action or decision requested;
• named receiving owner;
• needed-by date;
• attachments or source-system location;
• known limitations and open questions; and
• confirmation of receipt or decision.

Common handoffs include:

• finance to manager: reconciled P&L, definitions and reporting adjustments;
• manager to finance: operating causes, forecast assumptions and corrective actions;
• sales to manager: pipeline, realized price, discounts and customer mix;
• operations to manager: volume, labour, material, quality and capacity facts;
• manager to treasury, credit or collections owner: billing, receivable, inventory or supplier-timing risk;
• manager to approver: business case, scenarios and recommendation;
• approver to manager: decision, conditions and release limits; and
• manager to action owner: expected operating result, boundaries, due date and completion check.

A forwarded spreadsheet without a question, owner or deadline is not a complete handoff.

Escalation

Escalate early enough for the receiving owner to act. A useful escalation is concise and decision-ready.

Escalation note

Escalation triggers

• a material variance exceeds the locally approved threshold;
• the official P&L conflicts with operational source data;
• a forecast depends on an unconfirmed assumption that could change the decision;
• margin deterioration cannot be explained or corrected within delegated limits;
• cash-timing pressure may affect commitments or service continuity;
• an action would exceed budget, pricing, staffing, vendor or spending authority;
• an investment case uses an unapproved rate, method or financial treatment;
• a commitment appears unauthorized, duplicated or incorrectly recorded;
• confidential information appears in an unapproved system or AI tool;
• a contract, tax, legal, safety, regulatory, credit or treasury question arises; or
• a decision is late and the delay creates material cost or operating risk.

Local-policy field: materiality thresholds, named recipients, delegates, response expectations and after-hours route.

Records and approved tool categories

Approved tool categories may include enterprise finance systems, planning platforms, spreadsheets, business-intelligence tools, operational systems, customer or service platforms, procurement systems, document repositories and collaboration tools. The playbook does not assume one named product.

Local-system field: approved systems, access roles, data classifications, naming conventions, version rules, retention and reconciliation owner.
Local-policy field: permitted spreadsheet models, distribution limits, sign-off requirements and record retention.

Quality measures and KPIs

Use a small set of financial and process measures. Define each measure before applying a target.

Local-policy field: definitions, targets, tolerances, reporting period, exclusions and accountable reviewer. Never invent a target because a dashboard needs a colour.

Exception handling

AI-assisted work with human control

AI may help organize approved inputs, draft a variance explanation, identify inconsistent assumptions, propose questions or test whether a decision memo addresses the required fields. It does not become a financial source, set company policy, approve an action or decide which risk is acceptable.

Before using AI:

• confirm that the tool and task are approved;
• use fictional, genuinely sanitized or specifically authorized information;
• provide only the minimum permitted context;
• identify facts that must remain unchanged;
• request a structured draft tied to named source fields;
• reproduce important calculations independently;
• compare each claim with an approved source;
• remove unsupported explanations;
• assign a named human reviewer; and
• store only the approved final record in the authorized system.

Local-policy field: approved AI uses, prohibited data, required review and disclosure.
Local-system field: approved AI service, permitted integrations and retention setting.

This playbook does not present any passage as an AI-generated result. A manager remains responsible for every final number, explanation, recommendation and handoff.

Reusable SOP model

Copy and adapt this model before operational use. Complete every local field from an approved source.

Operating identity

Trigger and completion

Ordered operating steps

1. Qualify the trigger, scope, decision owner and deadline.
2. Confirm the baseline, definitions, reporting period and data readiness.
3. Reconcile the operating story with the management P&L.
4. Test unit economics, capacity and relevant sensitivities.
5. Identify profit-to-cash timing effects and specialist escalations.
6. Refresh the driver-based forecast or scenarios.
7. Develop actions and compare decision options.
8. Prepare any internal investment or resource request using approved methods.
9. Communicate the recommendation, complete handoffs and obtain decisions.
10. Execute, monitor the drivers and close the decision loop.

Local configuration

Output checklist

• review brief;
• reconciled P&L commentary and driver bridge;
• unit-economics or margin diagnosis where relevant;
• profit-to-cash timing note where relevant;
• updated forecast or scenario view;
• decision options and recommendation;
• internal business case when spending approval is needed;
• action handoffs and decision record; and
• closeout note with measured or latest expected effect.

Final quality check

Before using this playbook, confirm:

• the operating area, period and decision question are clear;
• P&L and operating data cover the same scope and period;
• material numbers have approved definitions, sources and owners;
• facts, estimates and assumptions are visibly different;
• the driver explanation reconciles to the management P&L;
• unit economics uses a meaningful unit and agreed cost logic;
• profit-to-cash timing is considered without taking treasury or credit authority;
• budget and forecast remain distinct;
• options include operating, financial, customer, workforce, quality and timing effects;
• any investment case uses approved methods and rates;
• decisions inside and outside the manager's role are explicit;
• every handoff names an owner, action or decision, deadline and source;
• actions are checked against later operating and financial results;
• local-policy and local-system fields are completed before operational use;
• confidential information stays in approved systems; and
• any AI-assisted draft is checked against source facts and owned by a named human.

This playbook reflects the frozen U.S. vacancy research on financial responsibilities beyond the finance function and the independent late-2026 finance decision review. Adapt every local field before operational use.