Application craft
Grant application rejected? How to prepare a stronger resubmission
Turn grant rejection feedback into a practical resubmission plan. Learn what to change, how to strengthen evidence and when a different competition makes sense.
First, establish whether resubmission is the right move
If your grant application was rejected, start by diagnosing the decision rather than rewriting the opening paragraph. A stronger resubmission needs to address why the original bid failed, demonstrate what has changed and satisfy the rules of the competition you are entering. Grants are competitive awards, so a credible project can still miss out. Your first task is to distinguish a correctable weakness in the application from a mismatch between the project and the funding opportunity.
Read the decision letter, assessor feedback and original competition guidance together. Identify whether the problem concerned eligibility, scope, evidence, delivery confidence or competitive ranking. Then check the intended competition's rules on previously submitted projects, including any restrictions on resubmission. Do not assume a revised title makes the project a new application. If the original opportunity is no longer suitable, use the UK business grant directory of live competitions to investigate alternatives, checking each funder's guidance before committing writing time.
Turn assessor feedback into an evidence checklist
Create a feedback table with six columns: application question, assessor comment, underlying concern, evidence needed, responsible person and completion date. Keep the assessor's wording separate from your interpretation. For example, a comment that customer demand is unclear might mean your target buyer was poorly defined, your research was too general or the proposed product lacked a credible route to adoption. Those are different problems. Identify the specific gap before asking the team to collect more material.
Read comments alongside the published assessment criteria and your submitted answers. Assessors can only evaluate what the application communicates within the permitted format. If your team had strong evidence but left it out, the remedy is clearer presentation. If the evidence did not exist, editing alone will not fix the weakness. Where comments conflict, look for the shared concern underneath them. Prioritise issues that affect the project's central case, rather than treating every sentence of feedback as equally important.
Collect evidence that changes the funding decision
Choose evidence that directly resolves the identified concern. If technical feasibility was weak, design a focused test of the assumption most likely to undermine the project. Record the method, result, limitations and implications for the proposed work. If market demand was weak, speak to the people who would buy, approve or use the output. Ask about their existing approach, purchasing constraints and acceptance requirements. A general expression of interest is less informative than a specific explanation of what adoption would require.
Suppose you proposed an inspection system and assessors questioned whether it could operate reliably in its intended environment. A useful response would be representative test results, clearly stated performance requirements and an explanation of the technical work still needed. Another paragraph describing the market's size would not answer that concern. Avoid claiming that early tests prove the entire solution. Assessors need to understand both the evidence supporting your approach and the unresolved challenges that justify the proposed research and development.
Rebuild the application around the revised project
Once the evidence is stronger, update the whole application rather than patching individual answers. A narrower technical objective may change the work packages, staffing, subcontracting needs, costs and commercial timetable. Check that those changes appear consistently throughout the bid. Use a simple traceability check: each objective should connect to planned work, an observable result and a justified resource requirement. Remove activities that no longer contribute to the revised objectives, rather than retaining them because they appeared in the original submission.
Write for an assessor who has never seen your earlier application. Explain the problem, proposed advance, remaining uncertainty, delivery approach and intended benefit without relying on the previous feedback for context. Where the competition asks what has changed, answer directly with the relevant evidence and revisions. Otherwise, make the application stand on its own. Our guide to writing a grant application can help structure the narrative, but the competition's questions, scoring criteria and word limits must govern the final response.
Run a challenge review before deciding to submit
Ask someone outside the writing team to review the revised bid against the actual assessment criteria. Give them the competition guidance and application first, without a verbal explanation from the founder. Ask them to identify unsupported claims, unclear dependencies and contradictions between the technical plan and budget. Afterwards, compare their findings with the original feedback table. If they raise the same underlying concerns, the revision has probably not gone far enough, even if the wording is substantially different.
Set a go or no go decision before the submission deadline. Proceed when the project fits the competition, the material evidence gaps are closed and the delivery resources are credible. Pause if success still depends on unconfirmed access to essential facilities, an unwilling project partner or technical claims the team cannot substantiate. An external review through grant consultancy and grant writing services can help challenge those assumptions. It cannot guarantee an award or compensate for a project that does not meet the competition requirements.
Where to go next
Prepare a short resubmission pack containing the original application, decision letter, assessor feedback, revised project summary and intended competition guidance. Add your feedback table and identify which actions are complete, underway or unresolved. This gives your team a shared basis for deciding whether to submit again, gather further evidence or pursue a different opportunity. Do not let the time already spent on the original bid become the reason to invest in another application that still has the same weaknesses.
To discuss that decision, book a 15-minute grant scope and eligibility assessment with GrantUp. Bring the feedback and a clear description of what has changed so the conversation can focus on competition fit and the next practical steps. GrantUp's grant funding support has a minimum upfront setup engagement fee starting from £1,750 plus a success fee on award. The purpose of the initial assessment is to examine whether pursuing grant support makes sense, not to promise a successful resubmission.
Ready to turn this into a funded proposal?
Book a free 30-minute consultation with a senior grant consultant. We will check your eligibility, match you to the right program, and map out your submission timeline.
Learn more about our approach