Service standards for a grant team, covering accuracy, response times and complaints

Internal service standards make grant work observable. They should say what the team will do, how quickly, what evidence proves completion and who handles exceptions. Avoid public promises that the business cannot measure or control.

These are proposed editorial standards for recipients and advisers, not government requirements. Adjust them to the live scheme, customer relationship and team capacity.

What to take away

• Internal service standards should state what the team will do, how quickly, and what evidence proves completion.
• Set a second-person check for applications, agreement acceptance and claims, based on value and risk.
• Distinguish acknowledgement from resolution, and start the clock from a defined event with stated pause reasons.
• Log a proposed change before commitment and obtain written funder consent where required.
• Give each standard an owner, target, data source and review date, and retire measures that no longer support decisions.

Accuracy standard

Every eligibility, cost and outcome claim should have a named source and review date. Figures must reconcile across the application, budget, cash flow and report. Correct material errors in every affected record.

Set a second-person check for applications, agreement acceptance and claims. Define the sample size or full-review requirement based on value and risk.

Response standard

Set target times for acknowledging internal questions, funder requests, supplier issues and suspected errors. Distinguish acknowledgement from resolution. A quick automated reply is not a completed answer.

Start the clock from a defined event and pause it only for stated reasons. Monitor the proportion met and the age of open exceptions.

Evidence standard

Create evidence at the time of activity. Use consistent project and cost IDs. Store the approved quotation, decision, contract, invoice, payment and delivery record together.

The Cabinet Office Model Grant Funding Agreement illustrates evidence, monitoring, reporting and audit provisions that may appear in central government awards. Use the recipient's signed requirements as the acceptance criteria.

Change standard

Log a proposed change before commitment. Assess scope, cost, eligibility, timing, outcomes and approvals. Obtain written funder consent where required and retain the decision with the revised forecast.

Set an escalation period shorter than the time left before the decision is needed. Do not let an unanswered request become informal permission.

Claim standard

Prepare claims to an internal deadline that allows review. Reconcile every line to the ledger, source evidence and bank record. Check duplicates, credit notes and VAT. Keep the submitted version and acknowledgement.

Government grant-agreement guidance says central government agreements should include financial and delivery reporting and validation. A recipient's standard should make those duties routine.

Communication standard

Use plain language and distinguish a condition, recommendation and unresolved question. Date fast-changing information and link to the controlling source. Never promise an award or describe a commercial adviser as government approved without evidence.

Where the business advises applicants, record conflicts and commercial payments. Give users a correction and complaint route with a named owner.

Security and privacy standard

Limit access to bank details, payroll, participant data and commercial records. Use approved sharing methods, multi-factor authentication and a defined retention process. The NCSC small organisations guide gives UK security actions, while the ICO covers personal-data duties.

Set a route for reporting a lost device, misdirected email or suspicious bank-change request. Test it before an incident.

Review and improvement standard

Report a small set of measures: errors found after submission, evidence exceptions, missed milestones, overdue changes, claim queries and complaints. Investigate causes, not just totals.

The Government Service Standard is designed for public services and is not binding on an ordinary grant recipient. Its point on defining success and publishing performance data can still prompt a useful question: can the team prove that its standard improves delivery?

Give each standard an owner, target, data source and review date. This draft contains no live internal links and remains on hold until the proposed targets are tested against real team capacity.

Retire a measure when it no longer supports a useful decision.

Before you act

• Name a source and review date for every claim.
• Set target times for acknowledging questions and requests.
• Create evidence at the time of activity.
• Log changes before commitment and get written consent.
• Prepare claims to an internal deadline that allows review.
• Set a route for reporting lost devices or suspicious bank-change requests.

Common questions

How should a grant team handle accuracy across records?

Every eligibility, cost and outcome claim should have a named source and review date. Figures must reconcile across the application, budget, cash flow and report. Correct material errors in every affected record, and set a second-person check for applications, agreement acceptance and claims.

What does the response standard require for internal questions and funder requests?

Set target times for acknowledging internal questions, funder requests, supplier issues and suspected errors. Distinguish acknowledgement from resolution, because a quick automated reply is not a completed answer. Start the clock from a defined event and pause it only for stated reasons.

How should a team handle a proposed change to a grant?

Log a proposed change before commitment. Assess scope, cost, eligibility, timing, outcomes and approvals. Obtain written funder consent where required and retain the decision with the revised forecast. Set an escalation period shorter than the time left before the decision is needed, so an unanswered request does not become informal permission.