Budget Plan

Budget Plan

Create structured, defensible budgets for departments, projects, or the entire organization. This skill walks through revenue projections, cost categorization, allocation strategy, variance thresholds, and approval workflows.

Step 1 — Define Budget Scope and Parameters

Gather the foundational inputs before building any numbers.

Checklist

• Confirm fiscal calendar alignment (calendar year vs. fiscal year)
• Identify all cost centers and GL codes in scope
• Obtain prior-period actuals (minimum 2 periods for trend)
• Clarify headcount plan and hiring timeline
• Document any board-mandated constraints (e.g., "hold OpEx flat")

Step 2 — Revenue Projections

Model the revenue side before allocating costs.

1. Historical Trend: Pull 3–5 periods of revenue data; compute CAGR and sequential growth.
2. Pipeline-Weighted Forecast: Apply probability weights to sales pipeline stages.
3. Segment Breakdown: Split by product line, geography, or customer tier.
4. Sensitivity Band: Model optimistic (+15%), base, and conservative (-15%) scenarios.

Revenue Projection Template

Step 3 — Cost Categorization

Classify every line item into a standard taxonomy.

Checklist

• Every line item maps to a GL code
• Fixed vs. variable classification is validated with Finance
• Discretionary flags are agreed with budget owner
• No "miscellaneous" bucket exceeds 5% of total budget

Step 4 — Allocation Strategy

Distribute the budget envelope across categories.

1. Priority Ranking: Rank categories by strategic alignment (must-have, should-have, nice-to-have).
2. Baseline Lock: Lock non-discretionary fixed costs first (salaries, rent, committed contracts).
3. Growth Investment: Allocate a defined percentage (e.g., 15–25%) to growth initiatives.
4. Reserve Buffer: Hold 3–5% as contingency for unplanned needs.
5. Quarterly Phasing: Spread allocations by quarter, accounting for seasonality and hiring ramps.

Allocation Summary Template

Step 5 — Variance Tracking Framework

Define how actuals will be monitored against the plan.

Variance Response Actions

• Yellow: Document root cause; adjust forecast; no reallocation needed.
• Red: Mandatory reforecast within 5 business days; reallocation proposal required; leadership review.

Step 6 — Approval Workflow

Route the budget through the appropriate sign-off chain.

1. Draft Submission: Budget owner submits to FP&A for structural review.
2. FP&A Review: Validate assumptions, cross-check with headcount plan, flag anomalies (2 business days).
3. Department Head Approval: Sign-off on priorities and trade-offs.
4. Finance Leadership Review: CFO or Finance Director reviews aggregate picture.
5. Executive / Board Approval: For budgets above materiality threshold or with strategic implications.
6. Lock and Publish: Freeze approved numbers in the financial system; distribute to cost center owners.

Approval Checklist

• All assumptions documented and sourced
• Headcount plan reconciled with HR
• Capital vs. operating expenditure correctly classified
• Inter-department transfers and chargebacks reflected
• Prior-period variance commentary included
• Contingency reserve justified

Output Format

Deliver the budget plan as a structured document containing:

## Budget Plan — [Department / Project] — [Time Period]

### 1. Executive Summary
- Total budget: $X
- Key assumptions (3-5 bullets)
- Major changes vs. prior period

### 2. Revenue Projections (if applicable)
[Revenue table with scenarios]

### 3. Cost Breakdown
[Categorized cost table with quarterly phasing]

### 4. Allocation Rationale
[Priority ranking and strategic justification]

### 5. Variance Thresholds & Governance
[Threshold table and escalation paths]

### 6. Approval Status
[Sign-off tracker with dates]

### 7. Appendix
- Detailed line-item schedule
- Assumption log
- Comparison to prior period

Quality Checklist

• Revenue and cost figures reconcile to the total envelope
• All line items have an owner and a GL code
• Quarterly phasing sums to annual totals
• Assumptions are explicit, not buried in formulas
• Variance thresholds are realistic and agreed upon
• Approval workflow has clear SLAs
• Document is version-controlled with change log

Edge Cases