6 Questions About Making Technical Research Grant-Friendly for Non-Expert Panels, Answered

Why does a non-expert panel decide on my highly technical grant?

You send in a brilliant, meticulously detailed proposal - months of research, cutting-edge methods, everything carefully cited. Then you find out it's going to be judged by a panel where only one person might have a PhD in your field, and the rest come from policy, industry, community arts, or programme management. It feels unfair.

But it's intentional. And understanding why changes how you write.

Most grant panels - whether from UKRI, Innovate UK, the NSF, or foundations - are deliberately composed of 3 to 8 members with mixed expertise. UKRI makes this explicit: “Your application is likely to be seen by many people, including some who will not be familiar with your particular specialism… the ideas you wish to convey… should be apparent to a wide audience.” Innovate UK assessors typically come from industry backgrounds - they care about market potential and route to commercialisation, not the elegance of your equation. The NSF judges every proposal against two universal criteria: intellectual merit and broader impacts - meaning you must explain why your work matters beyond the lab.

This isn't a bug in the system. It's the feature. Funders are preparing your project for the real world. In the real world, your work will have to convince non-specialists - investors who don't know your field, policymakers who write the regulations, end-users who decide whether to adopt your solution. The panel mirrors that audience. Their job is to decide whether your project is worth public money - not to validate your technical thesis.

So the specialist on the panel will check your science is sound. The other seven are there to ask the question you need to answer: "So what?"

What does 'So what?' actually mean in a technical context?

"So what?" sounds dismissive - like a bored panel member checking their watch. But in a technical grant context, it's a real, structured question. And you need to answer it at three distinct levels.

The human level: Who actually benefits?

Your panel doesn't care about your method. They care about what your method does for someone. Take the Arts Tech grant that initially read: "Interrogates the tension between legacy and interface." The funded version? "20 youth will co-design and launch a bilingual public storytelling app - with $32/hr developer rates, UX testing stipends, and 3 school partnerships confirmed."

Same technical work. Radically different answer to "So what?"

The systemic level: What changes beyond the project?

This is about shifting practice or infrastructure. Not "We'll publish a paper" but "Our open-source sensor array, validated in 3 NHS clinics, enables clinical validation of early dementia detection at TRL-7 - creating a procurement pathway for 40+ NHS trusts."

Panels score on durability, not just activity.

The societal level: Why does this matter now?

Funders publish missions for a reason - Net Zero, Healthy Ageing, Equity in STEM. Your proposal must connect your technical work to one of these. A quantum sensor isn't cool because it measures gravity. It matters because it helps farmers detect soil subsidence without digging, saving £12k/hectare and reducing carbon emissions.

The key insight: panels score on impact, not technical merit alone. Over 73% of rejected proposals fail because they skip this translation step. Your rigorous methodology is table stakes. Your "So what?" is what gets funded.

How do I translate my technical terms without dumbing them down?

The trick isn't to simplify your science - it's to change how you frame it.

Try the record-and-transcribe method. Explain your project out loud to a friend who knows nothing about your field. Record it. Then transcribe the conversation and edit it for clarity. What you'll end up with is naturally accessible language - words you already use when you're not hiding behind jargon.

Then, swap abstract verbs for concrete, human-centred actions.

Don't write: "We will leverage AI-driven analytics to optimise nanoparticle delivery systems."

Write: "We'll train 12 community health workers to use a tablet-based symptom triage tool in three rural clinics, so children receiving chemotherapy can be treated closer to home - reducing hospital stays by three days."

The technical work is identical. But the second version names a human actor (community health workers), a concrete action (training, using a tool), a location (three clinics), and a real-world result (shorter hospital stays). The panel can see it happening.

Before and after - side by side

Before (jargon-loaded) After (clear, human-centred)
"Nanoparticle delivery system enabling targeted chemotherapeutic intervention" "Reduces chemotherapy side effects for children in regional oncology units, enabling outpatient treatment and cutting hospital stays by three days"

Notice: the after version doesn't cut the complexity - it translates the purpose of the complexity. You're not dumbing down the science. You're showing why it matters to a real person.

A quick test: If you can swap your sentence into the format "[Who] will [do what] in [where] so that [outcome]", you're on the right track. If you can't - if your sentence has no human subject and no concrete outcome - it's still too abstract. Go back and edit.

Should I lead with the science or the outcome?

Lead with the outcome. Every time.

A technical proposal that opens with your methodology is a proposal that's already fighting an uphill battle. The panel doesn't know - yet - why your nanoparticle synthesis or quantum error-correction scheme matters. They need a reason to care before they'll wade into the details.

The narrative-then-data structure works because it mirrors how people actually learn. You start with something concrete and human. Then you layer in the technical specifics.

Take the NSF engineering proposal that scored exceptionally well in 2025. It didn't open with acoustic sensor arrays or signal-processing algorithms. It opened with a quote from a rural water utility manager: "We lose 40% of treated water to undetected leaks - and have no budget for fibre-optic monitoring."

That's your "So what?" answered in one sentence. A real person. A measurable problem. A clear gap.

Your first paragraph must do three things

  1. Name the human problem - who suffers, what's broken, why now?
  2. State the concrete outcome - what changes, for whom, by how much?
  3. Hint at how you'll get there - just enough to make the solution believable

Only then do you move into your technical approach. The panel now has a frame to hang your methods on. They're reading to understand how you'll deliver that outcome, not to decode your field.

What this looks like in practice:

Not this: "We propose a graphene-based electrochemical sensor array capable of detecting salivary biomarkers at femtomolar concentrations using differential pulse voltammetry."

But this: "Every week, 12 children in rural Kenyan clinics are misdiagnosed with malaria because there's no rapid, low-cost test for febrile illness. We'll develop a graphene sensor chip - manufactured at under $2 per unit - that detects three viral biomarkers from a single drop of saliva within 10 minutes."

Same science. Radically different entry point. The panel gets the outcome first, trusts the technical detail second.

One more thing: lead with this in every key section. Your executive summary, your impact statement, your budget justification - each should re-anchor the reader in the real-world outcome before diving into specifics. Repetition here is not redundancy. It's reinforcement.

What does a funded proposal look like when it's technical but clear?

Take two proposals with the same technical depth. One gets funded. The other doesn't. The difference is almost never the science - it's whether the panel can see who benefits and why it matters.

GreenPulse Ltd: real farm, real mission, real numbers

GreenPulse Ltd wanted to develop precision soil sensors to help UK farms reduce fertiliser runoff. Their technical work was solid. But what actually secured their Innovate UK Smart Grant was a deliberate, step-by-step strategy.

First, they ran a Defra-aligned feasibility study (£98k). This was small, targeted, and explicitly mapped to the UK government's Future of Food & Farming mission. They didn't claim to solve world hunger - they demonstrated TRL progression on a real UK farm. Measurable. Verifiable. No hype.

That feasibility study gave them the evidence they needed to secure £750k follow-on funding. The panel didn't need to understand the sensor's electrical engineering. They saw the outcome: measurable reduction in runoff, a clear commercialisation pathway, and direct alignment with a national priority.

What this teaches you: Anchor your technical claims in a real setting. Name the farm. State the cost. Show the progression. Don't make the panel guess whether your work translates outside the lab.

AHRC Proof of Concept: R4RI as a team narrative

For an Arts and Humanities Research Council application, the team used the R4RI (Résumé for Research and Innovation) format to tell a joint story - not just list CVs.

Instead of a heading like "Awards and Publications," they wrote: "Contributions to new ideas" - and under it described how Dr A (a computational linguist) and Ms B (a community archivist) co-developed a participatory transcription framework. Together, they enabled 120+ marginalised speakers to co-author oral histories.

No jargon. No abstract claims. Just two people, a clear collaboration, and a specific outcome with a number attached.

The funded pattern: specifics, humans, outcomes, no jargon

Both examples follow the same formula:

Your technical work deserves funding. But the panel can't fund what they can't picture. Give them a concrete scene - not an abstract system.

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