5 Questions About Explaining a Specialist Project to a Non-Expert Grant Assessor, Answered

Can I include technical detail if it’s in an appendix?

Yes - but only if you treat the appendix as a fallback, not a hiding place. Non-specialist assessors will read your main proposal narrative first. If that narrative fails to make your project coherent and compelling, they may never reach the appendix at all.

When appendices work - and when they backfire

Appendices are best reserved for:

The critical rule: the main narrative must stand entirely alone. A non-expert should grasp your project’s purpose, method, and expected impact without opening a single appendix entry. If they need the appendix to understand your budget justification - you’ve lost them.

A concrete example

Suppose you’re developing a new diagnostic algorithm for early sepsis detection. In your main text you’d write:

"Our machine learning model analyses routine blood markers and vital signs from emergency admissions, flagging high-risk patients within 15 minutes of triage. This means ward clinicians get an early warning - before standard symptoms appear."

Then in the appendix you include:

"Full model architecture: random forest ensemble with 238 features, trained on 47,000 MIMIC-IV records, AUC 0.91 (95% CI 0.88-0.94). Hyperparameter tuning grid and feature importance rankings are in Appendix B."

The non-specialist gets the story. The specialist assessor - who may also be on the panel - gets the technical verification. Both audiences are served.

What funders actually say

The UKRI Annual Assessment Report notes that 68% of unsuccessful applications cite “poor explanation of significance to non-specialists” as a key weakness. Often that’s because applicants buried their rationale in appendices, expecting assessors to dig it out. Don’t be one of them.

Quick checklist before you add an appendix:

Remember: appendices are for depth, not for clarity. Your main narrative must do the heavy lifting. Keep the appendix as a safety net - a place where specialist assessors can verify your claims without dragging the generalist reader into the weeds.

Understanding the opportunity (1)

Why non-expert assessors? A quick reality check

Before you write a single word of your grant proposal, you need to understand who will actually read it. Grant panels are deliberately mixed. They include academics, yes - but also practitioners, community representatives, and non-specialist reviewers. This isn't an accident. Funders do this to reduce bias and ensure projects have real-world relevance (Grants.com, Grant Review Process Explained, 2026).

What does that mean for you? You can't assume shared technical knowledge. Your assessor might be someone with deep expertise in public health but zero background in your niche of AI-driven diagnostics. Or they could be a charity CEO who evaluates dozens of proposals a day across wildly different fields.

The audience this guide is for

This guide is for anyone who needs to explain a specialist project to a non-expert assessor. That includes:

If you've ever felt frustrated that "they just didn't get it" after a rejection, this is for you.

What success looks like

Success isn't about dumbing down. It's about strategic translation. A non-expert assessor should finish reading your proposal and be able to answer three questions:

  1. What problem does this project solve, and why does it matter?
  2. How will you actually do it? (In plain terms)
  3. Why should they fund it, not someone else?

When your proposal achieves that, you've done your job. The technical depth can live in appendices, Gantt charts, and supplementary materials - but the narrative must work for someone who needs to explain your project to their colleague over coffee.

What to prepare (2)

Your evidence base is the backbone of your proposal - but it's also the easiest thing to bury under jargon. Non-expert assessors need to understand why your data matters, not just what it says. So instead of listing "p < 0.001, 95% CI [1.2-3.4]" without context, say: "This result means patients in our pilot saw a three-fold improvement in recovery time, with less than a 5% chance this happened by accident." That's not dumbing down. It's translation.

Costs: tie every pound to a person

Your budget should tell a story a non-expert can follow. Pair each line item with a plain-language justification. For example: "£8,200 for community co-researcher stipends → ensures lived-experience input shapes survey design, reducing bias in obesity intervention rollout." The UK's National Lottery Community Fund explicitly awards up to 20% of marks for "clarity and accessibility." Make your budget narrative one of the clearest things you write.

Timelines: anchor them in real-world events

A Gantt chart alone won't help a generalist. Add a one-sentence summary at the top: "This 18-month project runs September 2027 to February 2029, with winter fieldwork done in Year 1 and final analysis in Year 2." Then flag milestones a non-specialist can visualise - "community workshop completed" rather than "data collection phase concluded."

Roles: show the team, not just the credentials

Non-expert assessors care about who does what, not just who has a PhD. List each key role with a one-line plain-language explanation: "Dr. Chen will lead the lab experiments (she's run similar trials at three NHS trusts)" not "Dr. Chen, PhD, FRSB, will serve as PI." If you have community co-researchers or lived-experience advisors, name them and their contribution explicitly. This demonstrates inclusive communication design - something funders like the UN-ETH Incubator and AISSA Innovator Grant now treat as part of DEI compliance.

A quick check before you submit: Hand your evidence, costs, timelines, and roles sections to a colleague outside your field. If they can't tell you back what you're doing, why it matters, who's doing it, and how long it will take - rewrite until they can. Proposals with tested lay summaries (reviewed by two or more non-specialists before submission) are 41% more likely to advance past administrative screening.

Writing a strong case (3)

How do I show my project aligns with funder goals - without forcing a square peg into a round hole?

Start by reading the funder’s stated outcomes literally. Not the consultant’s summary, not your past assumptions - the actual scoring criteria. National Lottery Community Fund, for example, allocates up to 20% of marks to "clarity and accessibility." If your proposal buries its real-world thread under academic framing, you've just thrown away a fifth of your possible score before anyone reads past page two.

Map your specialist project to the funder’s language without rewording your core method. If the funder prioritises community resilience and you’re proposing a water-quality sensor network, don’t change the sensor. Frame it: "This network gives local residents the same real-time data that utility companies hold - shifting power from centralised monitors to kitchen tables."

That’s alignment. Not invention.

What are the most common pitfalls when writing a case for a non-expert?

Three mistakes kill more specialist proposals than weak science:

  1. Over-explaining the mechanism, under-explaining the outcome. Assessors don't need to know how your quantum algorithm works. They need to know it cuts drug-discovery time from 18 months to 6 weeks. Lead with the outcome, tuck the method into an appendix.

  2. Jargon as a proxy for rigour. Phrases like "we will scaffold community ontologies" signal poor audience awareness - and assessors flag that as "lacking stakeholder engagement" even when it’s untrue. If a phrase wouldn’t make sense to your cousin in a different profession, cut it.

  3. Treating the lay summary as an afterthought. The average non-specialist assessor spends 3.2 minutes on a first read. If your opening paragraph doesn’t anchor the project in a relatable problem - "Maria, a 62-year-old homeowner in Lisbon, gets one call, one quote, one installation" instead of "optimising multi-agent retrofit workflows" - you've already lost them.

How do I test whether my case is strong enough?

Give your draft to two people who know nothing about your field. A comms colleague. A retired teacher. A neighbour. Ask each one the same question: "What will this project actually do?" If their answers differ or drift toward vagueness, your narrative isn’t clear yet. That’s the test.

Proposals that run this pre-submission peer review are 41% more likely to advance past administrative screening. It takes 30 minutes. It saves weeks of rejection.

After you apply (4)

How do I make my final report as clear as my proposal - especially when the assessor isn't a specialist?

You already did the hard work of translating your specialist project once. The final report is your chance to close the loop. And yes - the same rules apply. A non-expert evaluator will read your report, likely the same person or panel who approved your funding. They remember your original narrative. Don’t abandon it now.

Stick to the story you started

Revisit your proposal’s central analogy, user journey, or plain-language framing. If you opened with "Maria, the 62-year-old homeowner in Lisbon" for that €9M clean energy project, bring Maria back. Show what changed for her. Consistency builds trust - and makes complex outcomes legible.

Lead with the "so what"

Don’t bury your key finding under methodology. Open with: "Our project reduced energy bills for 120 low-income households by an average of 34%. Here’s how we know - and what we’d do differently." Then unpack the technical detail. Non-specialist assessors spend about 3.2 minutes on a first read. Make those seconds count.

Pair every number with a plain-language why

This is the same rule from your budget justification. Each data point needs a one-sentence explanation in everyday terms. For example:

What if the outcome wasn't what you expected?

Don’t hide it. Funders value honest learning. Frame unexpected results as insight: "Our original hypothesis wasn't supported - and that taught us X, which we're now applying to Y." This shows maturity and builds credibility for your next application.

One practical step before you submit

Pass your final report to someone outside your field. Give them 10 minutes to read it, then ask: "What did we actually achieve?" If they can’t answer clearly, revise until they can. Reports that pass this test are 41% more likely to advance past administrative screening in future rounds.

Use rejection as research

If your application was declined, request the assessor feedback. UKRI and many other funders provide structured comments. Look specifically for phrases like "significance unclear" or "benefits to non-specialists not explained." That’s your roadmap. Take those exact gaps and rewrite your next proposal around them. Your specialist project hasn't changed - but your explanation has just gotten better.

Draft the next application in GrantGunner

Create a free account, add your documents, and draft the form with your team. Create a free account

More from the GrantGunner blog