IT Budgeting

IT budgeting translates strategic technology priorities into financial plans that secure resources for operations, maintenance, and investment. This procedure covers the complete budget cycle from initial development through in-year management, producing a budget that aligns with organisational financial processes while accounting for the particular challenges of grant-funded and multi-year technology investments.

Prerequisites

Before beginning budget development, confirm these requirements are in place:

Verify you have read access to the prior year’s budget workbook and actual expenditure reports. If the organisation uses a financial planning system, confirm your user account has the IT cost centre assigned.

Procedure

Gather baseline cost data

1. Export the prior fiscal year’s actual IT expenditure from the financial system, grouped by account code. Request this from Finance if you lack direct access. The export should include all 12 months to reveal seasonal patterns.

2. Reconcile the financial system totals against your own records. IT often tracks costs that Finance categorises differently. A discrepancy of more than 5% indicates classification issues that will affect budget accuracy.

3. Identify each cost as either committed or discretionary. Committed costs recur automatically without new decisions: staff salaries, software subscriptions with auto-renewal, maintenance contracts, network circuits. Discretionary costs require active decisions each year: new hardware purchases, project costs, training, consultancy.

4. Calculate your committed baseline by summing all committed costs and applying known changes:

Prior year committed costs                    £485,000
+ Staff cost increases (2.5% inflation)       + £8,125
+ Known subscription increases                + £12,400
+ New subscriptions (approved in-year)        + £24,000
- Cancelled subscriptions                     - £6,200
- Staff departures not being replaced         - £45,000
= Committed baseline                          £478,325

This baseline represents the minimum budget required to maintain current service levels with no new investment.

Categorise costs correctly

IT budgets divide into capital expenditure and operational expenditure, a distinction that affects financial reporting, tax treatment, and funding source eligibility.

Capital expenditure covers assets with useful lives exceeding one year: servers, network equipment, major software implementations, infrastructure projects. Most organisations set a capitalisation threshold below which items are treated as operational regardless of lifespan. Common thresholds range from £1,000 to £5,000. Hardware costing £800 is operational expenditure even though the laptop lasts four years.

Operational expenditure covers consumable or short-term costs: staff salaries, subscriptions, maintenance, consumables, training, utilities. Cloud services present classification challenges because they replace capital assets with operational payments. A server purchase is capital; the equivalent cloud compute is operational.

Within these categories, further classify costs as direct or indirect. Direct costs are attributable to specific services or projects: the database licence supporting the case management system, the developer working on the grants platform. Indirect costs support IT broadly without clean attribution: the IT manager’s salary, the service desk software, the office network.

+------------------------------------------------------------------+
|                        IT COST STRUCTURE                         |
+------------------------------------------------------------------+
|                                                                  |
|  +---------------------------+  +---------------------------+    |
|  |    CAPITAL EXPENDITURE    |  |  OPERATIONAL EXPENDITURE  |    |
|  +---------------------------+  +---------------------------+    |
|  |                           |  |                           |    |
|  | Direct:                   |  | Direct:                   |    |
|  | - Project hardware        |  | - Application licences    |    |
|  | - Software implementation |  | - Cloud service fees      |    |
|  | - Infrastructure builds   |  | - Project staff costs     |    |
|  |                           |  | - Vendor support          |    |
|  | Indirect:                 |  |                           |    |
|  | - Shared infrastructure   |  | Indirect:                 |    |
|  | - Network equipment       |  | - IT staff salaries       |    |
|  | - Data centre investment  |  | - Service desk tools      |    |
|  |                           |  | - Training budget         |    |
|  |                           |  | - Utilities allocation    |    |
|  +---------------------------+  +---------------------------+    |
|                                                                  |
+------------------------------------------------------------------+

Figure 1: IT cost structure showing capital/operational and direct/indirect dimensions

Build the budget structure

5. Create the budget workbook with separate worksheets for staff costs, software and subscriptions, hardware, services and contracts, and projects. Each worksheet follows the same column structure:

6. Populate staff costs first as they represent 40-60% of most IT budgets. For each position, calculate the full cost including salary, employer pension contributions, national insurance, and any benefits. Apply the organisation’s standard uplift percentage for pay increases. Where positions are vacant, budget at the midpoint of the salary band unless recruitment is imminent at a known salary.

Senior Systems Administrator
Base salary                               £52,000
Employer pension (8%)                     + £4,160
Employer NI (13.8% above threshold)       + £5,765
Benefits (healthcare, training allowance) + £1,200
= Total staff cost                        £63,125

With 2.5% pay increase from April:
Q1 (3 months at current)                  £15,781
Q2-Q4 (9 months at new rate)             + £48,534
= Annual budget                           £64,315

7. Enter software and subscription costs using renewal dates from your asset inventory. Subscriptions renewing mid-year require split calculations. A £12,000 annual subscription renewing in September with a 10% price increase:

April-August (5 months at £1,000/month)   £5,000
September-March (7 months at £1,100/month) £7,700
= Annual budget                           £12,700

8. Hardware costs depend on your refresh cycle and any planned projects. Organisations without systematic refresh budgeting face unpredictable spikes when equipment fails. A sustainable approach budgets annual hardware at 20-25% of total hardware asset value, reflecting a 4-5 year replacement cycle. With £200,000 in hardware assets, budget £40,000-50,000 annually for replacements.

9. Services and contracts include maintenance agreements, managed services, consultancy, and telecommunications. Review each contract’s renewal terms. Multi-year contracts with fixed pricing provide budget certainty; annual contracts expose you to price increases.

Incorporate strategic investments

10. Review the IT strategy or roadmap for planned initiatives requiring budget. Each initiative needs a cost estimate broken into:

The implementation cost covers one-time expenses to deliver the initiative: project staff time, consultancy, software implementation fees, hardware purchases, data migration, training. This is often capital expenditure.

The ongoing cost covers recurring expenses once the initiative is operational: subscription fees, support contracts, additional staff time, infrastructure running costs. This is operational expenditure that adds to your baseline permanently.

11. For each initiative, document assumptions and estimation basis. A cloud migration project estimate might read:

Cloud Migration - Phase 1 (File Services)

Implementation (Year 1):
  Consultancy (architecture and migration)     £35,000
  Staff backfill during project               £20,000
  Data migration tooling                       £5,000
  Training                                     £8,000
  Contingency (15%)                           £10,200
  Implementation total                        £78,200

Ongoing (from Year 2):
  Cloud storage (estimated 5TB at £0.02/GB)   £1,200
  Backup service                               £2,400
  Support contract                             £6,000
  Ongoing annual total                         £9,600

Assumptions:
- Current on-premises storage costs £18,000/year
- Net annual saving from Year 2: £8,400
- Payback period: 9.3 years (excluding avoided hardware refresh)

12. Prioritise initiatives against available budget. The gap between requested investment and available funding forces difficult choices. Present options rather than a single take-it-or-leave-it budget:

Option A - Maintain current services only
  Committed baseline                         £478,325
  Essential refresh (end-of-support systems)  £45,000
  Total                                      £523,325

Option B - Essential modernisation
  Option A total                             £523,325
  Cloud migration Phase 1                     £78,200
  Security improvements                       £32,000
  Total                                      £633,525

Option C - Strategic advancement
  Option B total                             £633,525
  New case management system                 £145,000
  Data platform implementation                £89,000
  Total                                      £867,525

Handle grant-funded IT costs

Grant funding introduces complexity because costs must align with grant periods, comply with donor requirements, and demonstrate direct benefit to funded activities.

13. Identify which IT costs are allowable under each grant. Grants vary in what they permit:

Direct charging allows IT costs attributed to specific grant activities. A database supporting only the funded programme can be charged directly. Staff time spent on grant-specific IT work can be charged if timesheets support the allocation.

Indirect cost recovery allows a percentage of IT costs as overhead. Organisations negotiate indirect cost rates with major donors. A 15% indirect rate on a £500,000 grant yields £75,000 toward overhead including IT.

Unallowable costs cannot be charged regardless of benefit. Some donors prohibit capital purchases, require pre-approval above thresholds, or exclude certain cost categories entirely.

14. Map IT budget lines to funding sources. A cost can be funded from unrestricted funds, charged directly to grants, or recovered through indirect rates. The same £50,000 system might appear as:

Grants management system - £50,000 total

Funding allocation:
  Direct charge to Grant A (40% usage)        £20,000
  Direct charge to Grant B (25% usage)        £12,500
  Indirect recovery from all grants           £10,000
  Unrestricted funds (remainder)               £7,500

15. Align budget timing with grant periods. A grant running July to June requires budget recognition different from your April to March fiscal year. The financial system should track grant expenditure separately, but your IT budget must anticipate cash flow timing.

+------------------------------------------------------------------+
|                    GRANT-FUNDED IT TIMELINE                      |
+------------------------------------------------------------------+
|                                                                  |
|  Fiscal Year:  Apr----Jun----Sep----Dec----Mar                   |
|                 |      |      |      |      |                    |
|  Grant A:      [===============================]                 |
|  (Apr-Mar)      ^                              ^                 |
|                Start                          End                |
|                                                                  |
|  Grant B:             [========================]                 |
|  (Jul-Jun)             ^                       ^                 |
|                       Start                   End                |
|                        |                       |                 |
|                        +--- Straddles two -----+                 |
|                             fiscal years                         |
|                                                                  |
+------------------------------------------------------------------+

Figure 2: Grant periods overlapping fiscal year boundaries

Plan multi-year investments

Major IT investments span multiple years for implementation and generate ongoing costs indefinitely. Single-year budgeting obscures these commitments.

16. Create a multi-year projection showing the full cost profile of planned investments. A five-year view reveals how current decisions affect future budgets:

The baseline grows at 2.5% annually for inflation. Implementation costs spike in their delivery year then drop to ongoing costs. Hardware refresh varies based on equipment age profiles.

17. Document the assumptions underlying multi-year projections. Future years carry increasing uncertainty. Note which figures are contractually fixed, which are estimates, and which are placeholders for planning purposes.

Submit and gain approval

18. Compile the budget submission package:

The summary page shows totals by major category, comparison to prior year, and key variances requiring explanation.

The detailed workbook contains line-by-line budgets with all supporting calculations.

The narrative document explains major changes, risks, and the relationship between budget and strategy. This is where you justify investments and explain trade-offs.

The options paper presents alternative budget levels if applicable, showing what each option enables and what it sacrifices.

19. Submit by the deadline specified in the financial calendar. Late submissions delay the entire organisational budget process and damage IT’s credibility.

20. Prepare for budget review meetings. Finance and leadership will question significant variances and new investments. Anticipate questions and prepare concise answers:

21. Negotiate and revise as required. Budget approval rarely happens without iteration. Track each version of the budget with change notes. Maintain a log of what was requested versus what was approved to inform future planning.

Track budget in-year

22. Establish a monthly budget review rhythm. On the fifth working day of each month, compare actual expenditure to budget:

Monthly Budget Review - September

                          Budget    Actual    Variance   YTD Budget  YTD Actual  YTD Var
Staff costs               £39,500   £38,200   +£1,300    £237,000    £231,400   +£5,600
Software/subscriptions    £18,200   £22,400   -£4,200    £109,200    £108,800   +£400
Hardware                   £3,750    £1,200   +£2,550     £22,500     £18,400   +£4,100
Services/contracts        £12,000   £11,800     +£200     £72,000     £71,200   +£800
Projects                  £15,000   £24,000   -£9,000     £90,000     £86,000   +£4,000
------                   --------  --------  --------   ---------   ---------  --------
Total                     £88,450   £97,600   -£9,150    £530,700    £515,800  +£14,900

23. Investigate variances exceeding 10% of the budget line or £5,000, whichever is lower. Variances fall into three categories:

Timing variances resolve over time. A subscription invoiced in September instead of August creates a September overspend that offsets August’s underspend. No action required beyond noting the timing shift.

Permanent variances affect the full-year position. A 15% price increase on a subscription not anticipated in the budget creates ongoing overspend. Action required: identify offsetting savings or request additional budget.

Coding errors reflect incorrect account assignment. A hardware purchase coded to software distorts both lines without affecting the total. Action required: request journal transfer to correct category.

24. Document variance explanations. Finance will ask why lines are over or under budget. Maintain a running log of significant variances with explanations and any corrective actions taken.

Reforecast when conditions change

25. Trigger a formal reforecast when cumulative variance exceeds 5% of total budget, when significant new requirements emerge, when a planned initiative is cancelled or deferred, or when Finance requests a reforecast as part of organisational planning.

26. Build the reforecast from actual year-to-date spending plus revised estimates for remaining months:

Full-year reforecast (at end of Q2)

                    Original   YTD      Remaining   Revised    Variance
                    Budget     Actual   Forecast    Full Year  to Budget
Staff costs         £474,000  £231,400  £239,000    £470,400   +£3,600
Software            £218,400  £108,800  £118,000    £226,800   -£8,400
Hardware             £45,000   £18,400   £32,000     £50,400   -£5,400
Services            £144,000   £71,200   £74,000    £145,200   -£1,200
Projects            £180,000   £86,000  £110,000    £196,000  -£16,000
---------          ---------  --------  ---------  ---------  ---------
Total             £1,061,400  £515,800  £573,000  £1,088,800  -£27,400

27. Explain material reforecast variances and propose management actions. If the reforecast shows an overspend, identify options: defer discretionary spending, reduce scope of planned work, request additional budget with justification.

Verification

After completing budget development, verify the submission:

Run this verification command against your budget workbook to check for common formula errors:

# Excel formula audit
1. Formulas > Show Formulas (Ctrl+`)
2. Review each formula references correct cells
3. Check SUM ranges include all data rows
4. Verify no hardcoded values in formula cells
5. Formulas > Error Checking > Trace Precedents

Confirm Finance has received and can open all submitted files. Request acknowledgement of receipt.

Troubleshooting

IT Budget Template

Use this template structure for the detailed budget workbook. Create one worksheet per major category.

Budget Header

Staff Costs Worksheet

Software and Subscriptions Worksheet

Hardware Worksheet

Services and Contracts Worksheet

Projects Worksheet

Summary Worksheet

Assumptions and Risks

See also

• Cost Allocation
• IT Planning and Prioritisation
• Funding IT Operations
• Capacity Planning
• Asset Management
• Vendor and Licensing Management