Small business grants operations: running a funded project with one accountable owner

A grant project needs its own operating system. The minimum useful version connects the signed award, approved scope, budget, procurement, evidence, reporting and change decisions. It tells each person what they own and prevents a rushed claim from becoming the first proper review of the records.

This guide was researched on 4 September 2026 for small businesses delivering funded work in England. It does not replace a scheme's rules or agreement. Translate the exact award into the controls below and obtain legal, finance or tax advice where interpretation matters.

What to take away

• Turn the signed award into a versioned baseline and do not run delivery from an earlier draft.
• Name one accountable owner for delivery, with deputies and financial approval limits.
• Capture evidence at the point of work and review it weekly, not at the claim deadline.
• Control procurement and change before commitments, as silence from a contact is not approval.
• Reconcile the project ledger to accounting and bank records, separating net amount and VAT.

Turn the award into a controlled baseline

Gather the final application, offer letter, funding agreement, schedules, written clarifications and approved budget. Identify which document takes priority if two provisions conflict. Do not run delivery from an earlier draft of the application.

Create a baseline containing:

• funded purpose and activities
• start, end and claim dates
• outcomes, outputs and milestones
• cost headings and grant contribution
• applicant and match contributions
• procurement requirements
• evidence and retention duties
• reporting and audit access
• publicity and branding conditions
• change, suspension, recovery and termination provisions

The Cabinet Office Model Grant Funding Agreement illustrates how these subjects may be structured for central government grants. A recipient's actual agreement may differ. Use the model to spot questions, never to overwrite signed terms.

Give the baseline a version number and approval date. Store it in a location the project team can access without allowing silent edits.

Appoint one accountable owner

The project needs one person accountable for delivery, even when finance, technical and commercial staff own separate tasks. Name deputies for absence and set financial approval limits.

Use a responsibility table for every obligation. It should distinguish the person who performs a task, the person accountable for the result, those consulted and those informed. Avoid assigning a duty to a department name without a named owner.

The accountable owner should run a short mobilisation meeting before the first commitment. Review the purpose, scope, budget, milestones, risks, claims and change route. Invite delivery partners and the finance person who will reconcile payments.

Build the work plan around evidence

Break each approved activity into tasks with an owner, start date, finish date, dependency and acceptance test. Add the evidence produced by the task. A milestone is stronger when completion creates an observable record.

For example, "install equipment" might require an approved quotation, purchase order, delivery note, serial number, acceptance test, invoice, proof of payment and asset register entry. The evidence list must follow the award conditions and the nature of the purchase.

Do not leave documentation until the claim deadline. Capture it at the point of work and review it weekly. Missing proof can turn a genuine project cost into an unsupported claim.

Control procurement and suppliers

Read the award's procurement, competition, conflict and connected-party clauses before approaching suppliers. Document thresholds and the process that applies at each value. Do not split one requirement into smaller purchases to avoid a control.

Write the need and evaluation criteria before viewing bids. Keep invitations, quotations, questions, scores, approvals and declarations. Confirm the supplier's legal identity, bank details, insurance and ability to deliver. Use proportionate checks, but record what was checked and when.

The government's grant-agreement guidance expects eligible expenditure, audit, assurance and counter-fraud provisions in central government agreements. Its purpose is public grant management, but recipients can use those headings to prepare a defensible supplier file.

Put scope, price, delivery, acceptance, intellectual property, confidentiality, personal data, subcontracting and change terms in writing. Align supplier dates with the funding period. A supplier's promise does not extend the grant end date.

Keep a project ledger

Assign each cost an internal ID and grant heading before commitment. Record budget, committed value, invoice value, payment, proposed eligible value and forecast to completion. Reconcile the ledger to the accounting system and bank evidence.

Separate net amount and VAT. Record the basis for any VAT treatment and whether the scheme permits the amount claimed. Do not treat every gross invoice as eligible merely because the business paid it.

Monitor committed costs as well as paid costs. A project can appear under budget while unsigned or unrecorded commitments build outside the ledger.

Manage people and time evidence

Where staff time is claimed, define the permitted calculation and evidence before work begins. Timesheets should identify the person, date, project activity, hours and approval. They should agree with employment and payroll records where the scheme requires that link.

Do not reconstruct several months of time from memory. Set a weekly completion deadline and have managers review unusual hours, leave conflicts and duplicated allocations.

Partners and contractors need equally clear records. A partner cost is not automatically eligible because it appeared in the application. Confirm its agreement, activity, rate, evidence and payment treatment.

Operate change control

Delivery rarely follows the first plan exactly. The control is not to prevent change; it is to identify, assess and authorise it before the business creates an unsupported liability.

Use a change record containing the reason, affected scope, cost heading, grant share, milestone, risk and recommended decision. State whether funder approval is required and attach the written response.

Escalate changes early. Supplier substitution, delayed start, revised specification, moved expenditure or reduced output may need consent even if the total award stays the same. Silence from a contact is not an approved variation.

Maintain the original baseline and an approved current forecast. Do not erase history by editing the submitted budget in place.

Prepare payment claims as a routine

Build a claim calendar from the agreement. Work backwards from each deadline to allow finance reconciliation, evidence review, authorised signature and correction. Confirm whether the claim is based on expenditure incurred, paid, forecast or another definition.

Create a claim pack with the required form, cost ledger, invoices, proof of payment, procurement evidence, staff records, milestone evidence, variance explanation and declarations. Include only material requested or needed to support the claim, while retaining the complete project file.

The model agreement contains options under which payment can depend on eligible expenditure already paid or on sufficient assurance about future use. That difference changes working-capital needs. Follow the live award's payment mechanism.

Have a second person trace a sample from claim to bank and from bank to claim. Resolve duplicates, credit notes, foreign exchange differences and allocations before submission.

Report delivery honestly

Use the definitions agreed with the funder. Separate activities, outputs and outcomes. Report the measurement period, source and limitations. Do not convert a target into a result or count the same beneficiary twice.

Explain slippage with its effect and recovery action. An early, specific warning gives the funder a chance to decide whether a change is acceptable. A vague positive narrative can hide a problem until recovery is impossible.

The model agreement's monitoring section includes progress against outcomes, milestones and indicative performance measures. It also illustrates duties to notify actual or potential failure. The recipient must check the language and timetable in its own agreement.

Protect project information

Limit access to applications, bank evidence, payroll data, participant records and commercial quotations. Use approved storage, multi-factor authentication, secure sharing and a retention schedule. Remove access when staff or suppliers leave the project.

The National Cyber Security Centre small organisations guide provides practical UK guidance on accounts, devices, backups and incident preparation. The ICO data-protection guidance hub is the starting point where personal data is involved.

Do not email an unrestricted workbook containing personal or sensitive financial information merely because a deadline is close. Confirm the funder's approved transfer method.

Run monthly control reviews

At least monthly, review delivery against scope, milestones, budget, cash flow, risks, procurement, evidence, changes and next claim. Frequency should increase when the award, pace or risk requires it.

Use exceptions rather than a ceremonial status meeting. Which costs lack evidence? Which milestone is threatened? Which forecast changed? Which decision needs funder approval? Assign a named action and date for each answer.

Keep minutes short but sufficient to show the issue, evidence, decision and owner. Correct an inaccurate record promptly.

Prepare for audit from the first day

An audit-ready file allows an independent reviewer to understand why the award was made, what the recipient did, what it spent and what resulted. Use consistent IDs across the baseline, procurement, ledger, claims and evidence register.

Retain records for the period specified by the agreement and applicable law. Do not invent one universal retention period. Place a hold on disposal if an investigation, dispute or audit remains open.

Test the file before the final claim. Select one staff line, one supplier line and one reported outcome. Trace each through approval, activity, invoice or time record, payment and report. Fix the system where the trail breaks.

Close the project properly

Reconcile the final cost, grant received, match contribution, assets, commitments and unspent money. Complete the final report and any evaluation. Record continuing conditions affecting assets, intellectual property, publicity, records or data.

Close supplier contracts and access accounts. Archive the authorised record and assign an owner for post-project duties. Review what worked, what failed and which assumption should change next time.

Do not announce unsupported outcomes just because the funding period has ended. Publish only results backed by the agreed evidence and label any later projection clearly.

This draft contains no live internal links. It remains on editorial hold pending an identifiable author, fact-checker, qualified review and a publication-day check of every legal, financial and programme reference.

Before you act

• Gather final application, offer letter, agreement and approved budget.
• Appoint one accountable owner and name deputies for absence.
• Build a work plan with evidence for each task.
• Read procurement and conflict clauses before approaching suppliers.
• Set a claim calendar working backwards from each deadline.
• Limit access to project information and remove it when people leave.

Common questions

What should a controlled baseline contain?

A baseline should include funded purpose, activities, dates, outcomes and milestones. It should also cover cost headings, grant and match contributions, procurement requirements, and evidence duties. Add reporting, audit access, publicity conditions, and change, suspension, recovery and termination provisions.

How should staff time evidence be managed?

Define the permitted calculation and evidence before work begins. Timesheets should identify the person, date, project activity, hours and approval. They should agree with employment and payroll records where required. Set a weekly completion deadline and have managers review unusual hours, leave conflicts and duplicated allocations.

What is the purpose of change control?

Change control identifies, assesses and authorises change before the business creates an unsupported liability. Use a change record with the reason, affected scope, cost heading, grant share, milestone, risk and recommended decision. State whether funder approval is required and attach the written response. Silence from a contact is not an approved variation.