Most innovate uk grants applications lose marks for fixable issues. This guide lists the common mistakes when applying for UK grants and the exact remedies that help reviewers score your bid with confidence.
Winning is not only about great ideas. It is about making it easy for assessors to award points. Below is a myth-busting, fix-focused playbook covering scope fit, evidence, letters, portal compliance and budgets. Use it as a pre-submission checklist.
1) Scope drift
The mistake: Writing what you want to say rather than what the call asks. Applicants describe broad ambitions that only partly match the published aims.
How to fix it
- Build a line-by-line scope map. Two columns: left = exact call text, right = where your answer addresses it.
- Write a 50-word fit statement for each question that restates the aim and your outcome.
- Remove anything that does not support a published aim or expected outcome.
Proof that scores
- A short table quoting the call text with your alignment notes.
- Beneficiary statements with baseline metrics and target improvements.
2) Thin evidence
The mistake: Claims without proofs. Impact and technical novelty are asserted but not demonstrated.
How to fix it
- Create an evidence index per work package. Include design versions, test logs, pilot data and references.
- Use a simple logic model. Inputs, activities, outputs, outcomes and impacts with KPIs and data sources.
- Add one worked example that shows method, result and implication.
Proof that scores
- Redacted charts or tables from trials or simulations.
- Third-party letters that reference data access, sites or cohorts.
3) Weak end-user letters
The mistake: Generic support letters that praise the idea but promise nothing specific.
How to fix it
- Script letters to include five items: who they are, the problem, access commitments (site, data, users), success metrics they will measure, and adoption intent if targets are met.
- Get signatures from decision-makers, not only technical contacts.
- Date letters within the last eight weeks.
Proof that scores
- Letters stating test locations, sample sizes, KPIs and decision gates.
4) Portal compliance errors
The mistake: Missed page limits, broken links, wrong file types, missing declarations or mis-named uploads.
How to fix it
- Build a portal checklist. Limits, attachments, naming rules, declarations and hyperlink testing.
- Upload a day early. Do a final PDF print check for broken anchors, figure labels and cross-references.
- Keep a submission log with version numbers and timestamps.
Proof that scores
- A signed internal checklist and a frozen upload pack.
5) Mismatched budgets
The mistake: Finance forms do not mirror the work plan. Costs are departmental, not milestone based. Assumptions are implicit.
How to fix it
- Budget by milestone, not department. Each line links to a deliverable and acceptance criteria.
- Publish an assumptions log. The five drivers of cost and timing, each with a source and sensitivity.
- Get benchmark quotes for subcontracted items and note why options were accepted or rejected.
- Plan for claims-in-arrears to protect cash.
Proof that scores
- A milestone-based budget table and a one-page sensitivity showing a 10 percent slip.
6) Vague risk management
The mistake: Boilerplate risks with no early-warning signals or owners.
How to fix it
- Name real risks with triggers you will monitor.
- Assign an owner and date to each mitigation.
- Add two go or kill gates that protect public money if tests fail.
Proof that scores
- A risk register with probability, impact, early warnings and mitigations.
7) Unclear TRL positioning
The mistake: Confusion between feasibility, industrial research and experimental development.
How to fix it
- State your Technology Readiness Level (TRL) at start and finish.
- Tie tasks to TRL movement and acceptance tests.
- Place validation activities in the right phase.
Proof that scores
- A TRL ladder diagram with tests and exit criteria.
8) No exploitation plan
The mistake: Impact is described, but the route to adoption and revenue is unclear.
How to fix it
- Draft a partner-level exploitation plan. Who sells or deploys, to whom, at what price, and when.
- Name the procurement route, standards and certifications required.
- Include a simple unit-economics snapshot and resourcing after the grant.
Proof that scores
- A one-page table per partner with time-to-revenue and dependencies.
9) Ignoring grants–tax interactions
The mistake: Double funding risks when mixing grants and R&D tax relief.
How to fix it
- Write a cost treatment memo. For each category, state if a cost is grant-funded, claimable for tax, or excluded.
- Keep subcontractor scopes and timesheets that show task-level links to eligible R&D.
Proof that scores
- Reconciliations from the work plan to finance forms and to the memo.
10) Late Red Team reviews
The mistake: Reviews happen when there is no time to fix issues.
How to fix it
- Schedule a mid-draft review at T-10 days and a final Red Team at T-5.
- Use a scoring rubric aligned to the call’s headings.
- Freeze a final version for portal upload.
Proof that scores
- A review log with action owners and dates closed.
Quick reference table
| Problem | Fast fix | Evidence to attach |
| Scope drift | Line-by-line scope map | Fit statements, annotated call text |
| Thin evidence | Evidence index, logic model | Redacted data tables, trial summaries |
| Weak letters | Script with access, KPIs, intent | Signed letters from decision-makers |
| Portal errors | Upload checklist, early dry run | Signed checklist, frozen PDFs |
| Budget mismatch | Milestone-based costing, assumptions log | Sensitivity analysis, benchmark quotes |
Mini case example
A materials SME applied to a feasibility competition with a broad narrative and generic letters. The team rebuilt the bid in one week: a scope map tied each paragraph to call lines, end-user letters named a pilot site and success KPIs, the budget was rebuilt by milestone with a short sensitivity, and a Red Team review removed vague claims. The resubmission scored higher on relevance, implementation and value for money because assessors could award marks with confidence.
Actionable 12-item checklist before you submit
- Scope map completed and embedded in answers.
- Fit statements lead each question.
- Logic model attached with KPIs and data sources.
- Evidence index for each work package.
- TRL start and finish stated with exit tests.
- Exploitation plan per partner with route to adoption.
- Milestone-based budget reconciled to finance forms.
- Assumptions log and a 10 percent sensitivity.
- Risk register with early warnings and owners.
- Two end-user letters with access, KPIs and intent.
- Portal checklist signed, uploads tested, links verified.
- Mid-draft and final Red Team reviews completed.
