Sector notes
What the grant assessor is actually reading for
Two of our named projects were grant-funded: the Raymang Eggs robotics line under an Enterprise Development Grant, and the PestBusters programme as the first project under the Lead Enterprise Development Scheme. Neither was won on the technology. Both were won on a defined problem, a scoped project, and an outcome that could be measured.
Executive summary
3
things an assessor reads for: a business problem, a scoped project, a measurable outcome
2
named projects on this site that were grant-funded, both on those three
Core conclusions
- A grant application is read by someone looking for a business problem, a scoped project and a measurable outcome — the same three things a good scoping document already contains.
- The technology is the means, and an application that leads with it has usually not yet said what the problem is.
- If the scoping stage has been done properly, the application is a reformatting exercise. If it has not, no amount of writing fixes it.
An SME owner who has decided to automate something usually arrives at the grant application in the wrong order: the equipment has been chosen, a quote is in hand, and the application is the paperwork between them and the co-funding. Written in that order, the application leads with the machine, and the assessor is left to work out for themselves what problem it solves.
It helps to think about who is reading it. An assessor is not evaluating the robot. They are evaluating whether public money spent on this project will produce a business that is measurably stronger than it was, and whether the applicant has thought about it clearly enough to be trusted with the money. Three things answer that.
What applicants write, and what the assessor needs
| What the application usually leads with | What the assessor is reading for |
|---|---|
| The equipment: model, vendor, capability | The business problem: what is going wrong now, measured how, costing what |
| The technology's benefits, in general | The scope: what exactly will be built, what it replaces, and what it will not do |
| An improvement, as a percentage | The outcome: the quantity that will change, its baseline now, and when it will be measured again |
| A quote | A plan: who does what, in what order, and what happens if a stage fails |
The Raymang Eggs application, in those three parts
The problem was not 'we need robots'. It was that weekly import shipments arrived as pallets of boxed eggs, unboxing them by hand was repetitive work that wore down local retention under tight limits on hiring foreign workers, and the resulting bottleneck drove up chilled storage needs and led to write-offs against short expiry windows. That is a business problem with a cost attached, and it is what the application opened with.
The scope was a line that replaced the manual process end to end: a six-axis arm transferring cartons from pallet to conveyor, a mechanical cutter making precision cuts on all four sides, the robotic system lifting the top and staging trays for inspection, and a third arm clearing the cut cartons. Named stages, each with a boundary.
The outcome was a quantity: unboxing that took 24 hours by hand, done in one hour for the same stock. Not an efficiency percentage — a measurement the business could be revisited on.
It is the same document the scoping stage produces
None of this is special grant-writing skill. A site assessment that maps what is actually running, a preliminary design that fixes the scope, and a baseline recorded before anything is built — that is the consulting stage of an ordinary engagement, and its output is the same three things the assessor is looking for. On the PestBusters programme, the first project under the Lead Enterprise Development Scheme, the structure was the same: a defined transformation, delivered in two scoped phases, against outcomes stated in advance.
Which is the practical point. If the scoping has been done, the application is a reformatting exercise. If it has not, the application is where the gaps show — and an assessor who finds them is right to.
Before applying
- Write the problem in one paragraph with a number in it, before naming any equipment.
- Fix the scope: what is built, what it replaces, what it explicitly does not cover.
- Record the baseline now, in the unit the outcome will be measured in, signed by the people running the current process.
- Name who owns the outcome twelve months after commissioning, because the assessor will ask and the answer should not be the integrator.
The grant does not fund the machine. It funds the change the machine is supposed to make, and an application that can say what that change is, in a number, is most of the way there before the equipment is mentioned.
