How to Write a Budget Request: Template and Example

How do you write a budget request?

Write a budget request as a one-to-two page decision document. Open with the exact amount and what you want approved. Then explain the problem, the options you considered, what each costs, what happens if nothing is funded, and how you will measure the result. Approvers rarely reject a request because the number is large. They reject it because the problem is vague, the alternatives are missing, or they cannot tell what they are signing up for. The template below fixes all three.

What does a budget request template look like?

Copy this. It works for headcount, software, training, equipment and facilities projects. Delete sections that do not apply, but keep the order. The order is what makes it easy to approve.

BUDGET REQUEST: [Short, specific title]

Submitted by: [Name, role, department]
Date: [Date]
Decision needed by: [Date, and why that date matters]

1. THE ASK
We request [$ total] from [budget line / cost center] to [one-sentence
description of what the money buys], starting [date].
  - One-time cost: [$]
  - Recurring cost (per year): [$]
  - Funding type: [capital / operating / headcount]

2. THE PROBLEM
[2-4 sentences. What is happening now, who is affected, and how you know.
Include one or two hard facts: a count, a cost, an incident, a deadline.]

3. WHAT HAPPENS IF WE DO NOTHING
[Cost, risk or lost opportunity of waiting 6-12 months. Quantify what you
can. Label estimates as estimates.]

4. OPTIONS CONSIDERED
| Option | Upfront cost | Ongoing cost | Main benefit | Main risk |
| A. Do nothing / minimum | | | | |
| B. Recommended | | | | |
| C. Alternative / phased | | | | |

5. RECOMMENDATION AND WHY
[Which option, and the two or three reasons that decided it.]

6. COST BREAKDOWN
[Line items that add up to the ask. Include contingency and say how much.
Name the source of each figure: vendor quote, internal estimate, contract.]

7. BENEFITS AND HOW WE WILL MEASURE THEM
[2-3 measurable outcomes, a baseline, a target, and a date to check.]

8. RISKS AND DEPENDENCIES
[What could go wrong, who else must act, what you will do about it.]

9. TIMELINE
[Key milestones with dates, including when money is actually spent.]

10. APPROVALS AND OWNER
Budget owner: [Name]. Approvers needed: [Names/roles]. Success owner: [Name].

Two rules for filling it in. First, every number needs a source in plain words ("Vendor quote dated March 4," "Finance system, last 12 months"). Second, if a figure is your estimate, say so. Approvers forgive uncertainty. They do not forgive discovering it later.

How do you fill it in? A worked facilities capital example

Here is the template filled in for a common facilities request: replacing aging rooftop heating and cooling units. All figures below are illustrative. Replace them with your own quotes and records.

BUDGET REQUEST: Replace four end-of-life rooftop HVAC units at the Eastside office

Submitted by: Dana Ortiz, Facilities Manager. Decision needed by: April 30, because installation must be scheduled before the summer cooling season and lead times for equipment are several weeks.

1. The ask. We request $189,200 from the FY capital budget to replace four rooftop HVAC units that have reached the end of their service life, starting in May.

• One-time cost: $189,200
• Recurring cost: none new (maintenance contract is unchanged)
• Funding type: capital

2. The problem. The four units are 19 years old, past the typical 15 to 20 year service life for this equipment. Repair spending on them was $18,000, $29,000 and $41,000 over the last three years ($88,000 total, from the maintenance work order system). Our service vendor has told us in writing that some parts are becoming hard to source and that further major repairs are likely.

3. What happens if we do nothing. We expect repair costs to keep rising; the vendor's informal estimate for next year is $50,000 or more (estimate, not a quote). A failure during peak summer would leave the north and west zones without cooling, affecting about 120 employees, with temporary cooling rental as the fallback.

4. Options considered.

5. Recommendation. Option B. Phasing costs about $4,400 more in total and leaves two failing units in service through a cooling season. Replacing all four removes the largest operational risk with one installation window.

6. Cost breakdown.

• Equipment and installation (four units, vendor quote): $152,000
• Crane and roof curb work: $14,000
• Permits and commissioning: $6,000
• Contingency (10% of $172,000): $17,200
• Total: $189,200

7. Benefits and measurement. Target: zero unplanned cooling outages in the first summer; HVAC repair spend at the Eastside building down from the $41,000 baseline to under $10,000 in year one; energy use compared against last year's utility bills after one full season. The vendor projects energy savings, but we are not counting them in the justification until verified.

8. Risks and dependencies. Equipment lead time (mitigation: place order on approval); roof access and crane scheduling (mitigation: weekend installation); permit timing (mitigation: vendor files in week one).

9. Timeline. Approval by April 30. Order placed by May 3. Installation across two weekends in June. Commissioning and sign-off by end of June.

10. Approvals. Budget owner: Director of Real Estate. Approvers: Finance business partner, VP Operations. Success owner: Dana Ortiz.

Notice what makes this work. The ask is exact. The history of repairs is sourced. The "do nothing" option has a cost. The savings that nobody has verified are left out of the justification on purpose, which makes everything else more believable.

What is different about a facilities capital budget request?

Facilities requests get extra scrutiny because the amounts are large and the work affects everyone in the building. If you are searching for how to write a facilities capital budget request, add these elements to the template.

Asset age and condition. State the age, the expected service life, and the condition evidence: inspection reports, repair history, manufacturer end-of-support notices. Condition data beats opinion.

Capital versus operating. Companies draw the line differently. Many treat a purchase above a set dollar threshold with a multi-year useful life as capital, and routine repairs as operating expense. Ask your finance partner for your company's threshold and capitalization policy before you submit, because it decides which budget the request lands in.

Risk framing. Describe what failure looks like in operational terms: a building zone unusable, a safety or code compliance issue, a lease or insurance obligation. Approvers weigh risk to people and operations heavily.

Total cost of ownership. Show the purchase price plus maintenance, energy and expected lifespan, not just the sticker price. A cheaper unit that costs more to run is a worse option, and approvers know it.

Disruption and scheduling. Say when work happens, who is affected, and how you will limit the impact. Weekend or after-hours work often costs more; include that.

Multiple quotes. Many companies require two or three competitive bids above a certain amount. Attach them or summarize them, and explain why you picked the one you did.

Contingency. Construction and installation work surprises people. Include a contingency line and say how you chose its size. Ten percent is common as a starting point, but use whatever your company expects and the complexity of the work justifies.

What do approvers actually look for?

Whoever signs your request is usually asking five quiet questions:

1. How much, exactly? Round, unsourced numbers look like guesses.
2. Why now? There should be a trigger: a deadline, a failure risk, a contract end, a growth event.
3. What else did you consider? One option reads as a purchase order, not a decision.
4. What does it cost to say no? If the answer is "nothing," the request will wait.
5. How will we know it worked? A named measure and a date to check it.

Also remember that the person who approves your request often has to defend it to someone else. Write it so they can forward it without rewriting. A clear first paragraph, a table of options and a total that adds up are what travel upward well.

Can AI help you write a budget request?

Yes, for structure, wording and stress-testing. No, for the facts and figures. AI is good at turning your messy notes into the template, tightening a rambling problem statement, and playing a skeptical finance reviewer. It is unreliable at anything that requires real data: it will happily produce a plausible savings percentage, a "typical" payback period or an industry benchmark that does not exist.

Paste this prompt into your AI assistant, then fill in the bracketed parts with your real information. Remove anything confidential your company does not allow you to put into a public AI tool, or use the tool your company has approved.

You are helping me write an internal budget request for my leadership.
Use the structure below. Only use the facts and numbers I give you. If a
number or fact is missing, write "[NEEDED: ...]" instead of making one up.
Do not add statistics, benchmarks, savings percentages or industry claims.

Structure: 1. The Ask, 2. The Problem, 3. What happens if we do nothing,
4. Options considered (table: upfront cost, ongoing cost, benefit, risk),
5. Recommendation and why, 6. Cost breakdown, 7. Benefits and how we will
measure them, 8. Risks and dependencies, 9. Timeline, 10. Approvals.

Keep it under two pages. Plain language. Lead with the exact amount.

My facts:
- What I want to buy or fund: [...]
- Total amount and breakdown, with sources: [...]
- One-time vs recurring costs: [...]
- The problem and the evidence I have: [...]
- Options I considered and their costs: [...]
- What happens if we wait: [...]
- Deadline or trigger: [...]
- Who approves, and who owns the result: [...]

After the draft, list: (a) every [NEEDED] item, (b) the three toughest
questions a finance reviewer would ask, and (c) any sentence in the draft
that is an estimate rather than a sourced fact.

What to check in the answer:

• Every number matches what you gave it. Add up the cost breakdown yourself. AI often makes arithmetic slip.
• No invented claims. Look for phrases like "industry standard," "typically saves," or "studies show." Delete them unless you can cite the source.
• Estimates are labeled. If the draft states an estimate as fact, fix it.
• The tone fits your company. Some cultures want a formal memo, others a short note. Adjust.

A second prompt worth running after you finish the draft:

Act as a skeptical finance business partner reading this request. Tell me
the five reasons you might reject or delay it, what additional evidence
you would want, and which section is weakest. Be specific.

Then answer those objections in the document itself, before the real reviewer asks.

What mistakes get budget requests rejected?

• Burying the ask. If the amount is on page two, the reader forms an opinion without it.
• Only one option. It looks like you decided before you analyzed.
• Benefits without numbers. "Improved efficiency" means nothing. "Cut weekly report prep from six hours to one" can be checked.
• Counting unverified savings as justification. If the case only works with optimistic savings, it will not survive a question.
• Forgetting recurring costs. Licenses, maintenance and support contracts are the number finance asks about first.
• No contingency, or an unexplained one. A request with no cushion signals inexperience; a large unexplained one signals padding.
• Skipping the pre-conversation. Talk to your finance partner and your boss before you submit. A request that surprises someone in the review meeting is much more likely to stall. Ask what budget line it fits, what the threshold for extra approval is, and when the cycle closes.
• Missing the calendar. Many companies set budget cycles months in advance. A good request submitted after the window may wait a year. Find the dates early.

Is there a better way to track budget requests than a spreadsheet?

If you submit requests regularly, or you collect them from a team, the pattern gets painful fast: versions in email, no single view of what is pending, and no record of what was approved and why. With Remy, you can describe a budget request tracker in plain English (a submission form using the fields from the template above, an approval flow with roles for submitters and approvers, and a dashboard of requests by status, amount and department) and Remy builds it as a full-stack app with sign-in, a database and a live URL. A typical initial build takes about an hour. Pricing is on the Remy site, and AI usage is billed at cost.