How to Run an Employee Suggestion Scheme in the UK

Start with why schemes stall

The evidence on participation is consistent. In a survey of organisations with more than 1,000 employees, run by the employee ideas vendor Sideways 6, 4 in 5 employees said they have ideas, a third felt their ideas were ignored, more than half said their company fails to act on good ideas, and 18% said they were too afraid to submit. Those are vendor survey findings rather than neutral research, but they match what anyone who has run a scheme will tell you.

The practical conclusion is simple: the bottleneck is almost never capture. It is what happens in the two weeks after somebody submits something.

The HMRC rules for suggestion scheme rewards

This is the part most UK guides get vague, so here it is straight from gov.uk. There are two kinds of award:

• Encouragement awards for good suggestions or special effort: exempt from tax and National Insurance up to £25.
• Financial benefit awards for suggestions that will save or make your business money: exempt up to £5,000. The exempt amount is the greater of 50% of what you expect the suggestion to make or save in the year after you act on it, or 10% of what you expect it to make or save in the first five years.

For an award to be exempt, four conditions apply:

1. The scheme must be open to all your employees, or to an entire group of employees such as everyone in one office or site.
2. The suggestion must be about your business.
3. It must be likely that the employee would not have made the suggestion as part of their normal work.
4. The suggestion cannot be made at a meeting for proposing new ideas.

Pay more than the limits and the excess is earnings: you report it to HMRC and run PAYE tax and National Insurance on it through payroll. One practical consequence: write down the savings estimate you used for any financial benefit award, because that number is the basis of the exemption and you may need to show your working.

Decide these eight things before you launch

• Who can submit. Everyone is simplest, and it is what the HMRC condition expects. If you limit it, limit it to a whole group, not to selected people.
• Anonymity. Allow anonymous submissions for sensitive ideas, and say in the policy how those are handled and how the submitter hears back.
• Categories. Five to eight is plenty: safety, quality, cost, maintenance, customer, process, environment, people.
• Response cadence. Acknowledge within 48 hours, decide within 10 working days, and give a reason either way.
• A parked status. Good ideas that need budget or another team get a date to come back, not silence.
• Who decides. A supervisor for local ideas, a small panel for cross-cutting ones. Two levels is enough.
• Rewards. Set bands in advance, keep them inside the HMRC limits, and include non-cash recognition as well.
• The owner. One named person runs the scheme. Schemes without an owner drift.

A 90-day rollout plan

Days 1 to 14: design

Pick the owner, write the one-page policy, agree the categories, set the response times and decide the reward bands. Tell your payroll or finance contact what the reward policy is so nobody is surprised at month end.

Days 15 to 45: pilot with one team or site

Run a single challenge with a real question and a deadline. Track response time from day one, not just submission counts. If supervisors cannot hit 48 hours in the pilot, fix that before you scale, because scaling a slow process just creates more silence.

Days 46 to 75: company-wide launch

Brief managers before employees, then open it up. Run the first reward cycle, and make the recognition public. Publish the first numbers: ideas received, ideas answered, ideas implemented.

Days 76 to 90: review and fix

Look at the two slowest steps in the process and fix them. Add a second challenge if the first one worked. Decide what to do with the parked ideas before they age out.

Measure these four things

• Participation rate: the share of invited people who have submitted at least once.
• Response time: the median days from submission to first response. This is the number that predicts whether the scheme survives.
• Implementation rate: ideas acted on as a share of ideas received.
• Value: named savings or improvements, with the estimate method written down.

The five documents worth writing

1. A one-page policy: who can submit, anonymity, categories, response times, reward bands.
2. Submission form fields: description, area, expected benefit, and a way to flag safety.
3. Four response templates: acknowledgement, accepted, parked with a review date, declined with a reason.
4. A monthly digest template: ideas in, answered, implemented, plus the best idea of the month.
5. A reward nomination form, with a savings estimate field for financial benefit awards.

Keep all five short. A policy nobody reads is worse than a policy that fits on one page.

When software starts to help

A form and a spreadsheet can run a scheme for a while, and there is nothing wrong with that. It breaks when volume grows and the response cadence slips: submissions scattered across inboxes, no visible status for the submitter, rewards decided from memory. That is the point where employee idea software earns its keep — a digital employee suggestion box with a named owner, a visible status for every idea, and a response cadence you can actually hit. Harmoni handles submission, AI-assisted triage, a manager review queue, challenges, rewards and reporting, and you can see the detail on the features page. Prices are on the pricing page, and if you would rather run it yourself in a spreadsheet, this guide is still the plan to follow.