MoneyMakers
WhySupportSign in

funding · Guide

How to Write a Business Grant Application: Work Plan, Budget and Evidence

Turn a project idea into scoped work, costed milestones and evidence that a grant reviewer can check.

MoneyMakers Editorial17 November, 2026
Paper work plans and colored blocks aligned against a metal ruler.
AI-generated editorial illustration.

A grant reviewer is usually trying to determine whether a proposed project will serve the call's objective at a defensible cost. A strong company story helps, but it cannot substitute for a work plan, evidence and a budget that agree with each other.

Draft the application as a chain: a demonstrated problem, work to resolve it, observable results, and costs necessary for that work. If a sentence does not help a reviewer follow a link in that chain, it probably belongs elsewhere. Check eligibility separately before building the proposal.

Key Takeaways

  • Draft from the live call and scoring criteria, with one testable claim and a source for each important answer.
  • Break the project into work packages with owners, delivery dates and acceptance criteria.
  • Calculate budget amounts from units of work and match them to the permitted cost categories.
  • Reconcile activities, outcomes, scope and numbers in every application attachment before submitting.

Turn the scoring criteria into a writing map

Use the form and assessment guidance for the exact funding opportunity. Copy the criterion names into a working sheet, then give each a claim, evidence and owner. An innovation criterion might require evidence of what existing approaches cannot do. A delivery criterion might require an agreed test site. Check whether any question is scored differently, whether minimum scores apply, and which documents reviewers can see. Avoid making an important answer depend on an attachment the form does not permit.

Innovation Norway's Startup Grant 1 guidance exemplifies a specific evidence request: its description emphasizes establishing what customers do today, testing hypotheses and reducing market uncertainty. This does not make customer interviews the right evidence for every grant. It shows how a call's purpose dictates what should appear in the proposal. For a technology validation call, measurements and an accepted testing method could be more central.

Write the short project objective after mapping the criteria. State who has the problem, where the gap sits, what will be tested and what decision the work will support. A weak objective says “build an innovative platform.” A stronger hypothetical version says “determine whether a retrofit sensor can identify a specified equipment failure early enough for operators to stop a process, under test conditions from two pilot sites.” It names a result and limits the claim to the planned work.

Specify work packages people can verify

A work package is a unit of delivery with a clear output and owner. Start from the objective and work backward. Which outputs need to exist in order to answer the project question? What data, equipment or participants are required? Give each package a date range, dependencies and a person or organization that is responsible. “Project management” can be a necessary activity, but on its own it does not show how uncertainty will be reduced.

Distinguish activity, deliverable and outcome. Running interviews is an activity. A record of the interview set and a defensible analysis is a deliverable. Deciding whether to run a paid pilot is an outcome the work can support. Similarly, building a prototype does not establish that it works to specification. Include what will be measured and how it will be judged, including what a failure would mean for the next package.

Break dependencies out explicitly. For the sensor project, instrument calibration comes before field testing. A pilot site needs installation consent before field data can be collected. If the pilot site is unavailable, a lab run may still answer one question, but it does not replace observation in the field. Write down the fallback, what it can test and what it cannot. That level of specificity helps assess feasibility without pretending every partner will perform as expected.

Cost the work rather than allocating a round number

Give each line an activity, cost category, quantity, unit price, basis and expected date. A test quote may specify twenty instrument hours and a report; a staff estimate may use approved rates and hours by package, if the call allows staff costs. Keep receipts and underlying quotes in a project folder so the proposed cost can be verified. Distinguish a quote from an assumption and explain where pricing is still uncertain.

Innovate UK's funding rules illustrate why allowable categories and rates need to come from the actual program. Collaboration and research category can affect funding. A business cannot take an allowable example from one competition and assume another will treat its staff costs, subcontracting, travel or equipment in the same way. Record the relevant rule beside each material cost.

Reconcile eligible costs, match and funding request. In an illustrative call that covers 60% of $50,000 in eligible costs, the grant request is $30,000 and the eligible company contribution is $20,000. If there is $8,000 of non-eligible spend, total project cost is $58,000 and the business funds $28,000 overall. Where reimbursement applies, the company may also have to finance the gap between paying suppliers and receiving its claim. Align the budget period and cash forecast.

Build an evidence pack that answers objections

Use evidence directly connected to the claim being made. A partner email confirming a test site supports access but not commercial demand. A purchase order supports willingness to buy on specific terms, not repeat buying across an industry. A bench test supports performance under test conditions, not reliability in field use. Describe the source, date, method and limit in a sentence the reviewer can interpret without guessing.

For market evidence, describe what buyers do now, what they spend or lose if measurable, and how you obtained that information. Report the number and type of conversations only if known. For technical evidence, show the baseline, target and method used to compare them. For team capability, explain who has done relevant work and how any gap is covered. Scrub confidential information, follow the provider's submission rules and obtain permission when necessary.

Anticipate a skeptical question for every high-scoring answer. What if the proposed benefit already exists in a less expensive tool? What if the person writing the letter cannot authorize a site visit? What if the test result is produced under easier conditions than the baseline? Give the answer wherever it affects scope or credibility. Do not invent precision. A named limit and plan to test it may be the most useful finding in the application.

Worked example: reconcile a sensor proposal

A hypothetical team wants to test shop-floor equipment monitoring. It scopes three packages: establish a calibration baseline, run supervised trials at two sites, and analyze detection and false alarms against agreed measures. A laboratory quote supports the first package. Each site letter confirms access, not a commitment to buy. The final report will record results from both sites and any limit arising from sample size or setup.

Finance initially budgets $12,000 for travel and deployment, but the narrative says one testing visit per site and the budget assumes four. The team decides whether extra visits are necessary for safety and measurement, then updates both documents. A separate commercialization activity is valuable but is outside the test work; the team removes it from its grant request rather than describing it as testing. The proposed scope now matches the costs.

Before submission, a colleague checks the plan against the call. They mark each material claim as demonstrated, proposed or dependent. The company can already bring technicians to one site, can propose a calibration target, and depends on the second site confirming dates. Those are different states. The application handles uncertainty by setting a decision date and fallback instead of misstating current readiness.

Separate funding outputs from company ambitions

An ambitious three-year growth plan can help explain why a six-month test matters, but the grant reviewer needs to see what belongs inside the funded project. Mark work that depends on the test result as future work. For example, a commercial roll-out may follow successful calibration; its costs and outcomes should not be described as part of the calibration project unless the call covers them. Give the reviewer a clear boundary: expected deliverables at close, decisions informed by those deliverables and separate investments the business might make afterward. That way a weaker or inconclusive result still leaves an auditable project, instead of contradicting a promise to launch.

Submit the version you can deliver

  • Compare each scored answer with its evidence; make the link explicit in the answer.
  • Check dates, outputs and owners across the narrative, schedule, budget and letters.
  • Verify eligible and non-eligible costs, match, allowed starting dates and cash timing.
  • Use the actual form requirements, confirm submission, and save the submitted version as the project baseline.

After submitting, preserve the budget and evidence as of that date. If circumstances change while the proposal is reviewed, track the change and follow the program's communication rules. Avoid starting work based on an expected approval unless the terms permit it and the company has decided to bear the cost. The value of a sound application is that you can run the project it describes if it is awarded, and make an informed decision about the work if it is not.

Sources and reference documents (2)
  • Innovation Norway's Startup Grant 1 guidance
  • Innovate UK's funding rules

AI assisted with research and drafting. Send an editorial correction.

Grants directory
Previous articleHow to Find Business Grants You're Eligible ForNext article What Happens After You Win a Business Grant? Payments, Reporting and Eligible Costs
OriginalArticlesT&CPrivacyRefundsContact