Selecting grant software by testing the workflow before trusting the brochure

Choose grant software after mapping the work it must support. A tool may help with opportunity research, collaborative drafting, budgets, delivery evidence or reporting. Few products perform every task well, and the funder's submission service remains mandatory where specified.

What to take away

• Map the work the tool must support before comparing products or reading brochures.
• Test a representative workflow from opportunity capture to approved submission before committing.
• Require named accounts, version history, approvals and recoverable deletion for evidence control.
• Calculate total cost including licences, migration, training, support, renewal increases and exit.
• Set weighted criteria and minimum scores for security and data export before demonstrations.

Define the use case

List current applications, users, partners, data types, deadlines and reporting duties. Record the failure to fix: lost versions, weak approval, duplicated budgets or missing claim evidence. Do not buy a broad platform for an unnamed problem.

Mark must-have, useful and unnecessary requirements. Include the required file formats and the longest expected application or evidence record.

Test the workflow

Use a representative scenario from opportunity capture to approved submission. Assign an answer, revise it, resolve a comment, change a budget line, restrict a confidential attachment and export the final pack. Compare the export with the funder's fields.

UKRI's current Innovate UK application guidance says relevant applications must use the Innovation Funding Service and describes lead applicant and partner responsibilities. An internal tool must support that route, not create a competing final version.

Check evidence control

Require named accounts, access levels, version history, approvals, timestamps and recoverable deletion. For funded delivery, link each cost to procurement, invoice, payment and acceptance evidence.

The Cabinet Office Model Grant Funding Agreement illustrates record, reporting and audit provisions that may appear in an award. Turn the signed agreement into test cases.

Assess security and privacy

Identify personal, financial and commercially sensitive information. Review authentication, encryption, backup, incident notification, administrators, hosting, subprocessors, retention and export. Test access using ordinary roles.

The NCSC small organisations guide covers practical protection of accounts, devices and backups. The ICO guidance hub supplies current UK data-protection guidance.

Do not rely on a generic security statement. Record which plan, configuration and contract were assessed.

Calculate total cost

Include licences, setup, migration, integration, training, support, storage, specialist configuration, renewal increases and exit. Model the number and type of users across the contract term. Check whether quoted prices include VAT.

Value the staff time saved cautiously. Measure the existing task and pilot result rather than assuming a vendor's percentage applies to the business.

Check supplier and contract

Confirm legal identity, financial stability proportionate to dependency, support hours, service levels, data ownership, subcontracting, liability, renewal, termination and export. Ask how the service handles outages near a grant deadline.

Run references for comparable use. Keep marketing claims separate from contract commitments.

Plan integration and ownership

List each system that will exchange applicant, budget, accounting or reporting data. Define which system owns the authoritative value and who resolves differences. An integration that copies an old budget more quickly still creates the wrong claim.

Ask the supplier to document interfaces, authentication, update timing, failures and change notice. Test a rejected record, corrected invoice and deleted user as well as a clean transaction. Keep a manual reconciliation until the connection proves reliable over a full reporting cycle.

Set an internal owner for configuration and renewals. Supplier support can fix a product issue, but it cannot decide whether a grant cost is eligible or approve the business's submission.

Prepare for exit

Export application text, attachments, user records, audit history and evidence links in usable formats. Check whether relationships between records survive. Record the time and skill needed to move them.

The exit plan should cover contract notice, access removal, archive, deletion evidence and any required retention. Test it before dependency grows.

Score and decide

Set weighted criteria before demonstrations. Require minimum scores for security, data export and any binding workflow. Record evidence beside each score and have a second person challenge the recommendation.

Pilot the preferred option before a long commitment when practical. This draft contains no live internal links and requires current product, contract, privacy and security checks before publication.

Before you act

• List current applications, users, partners, data types and deadlines.
• Mark must-have, useful and unnecessary requirements.
• Test a representative scenario from capture to submission.
• Check named accounts, access levels and version history.
• Model users and costs across the contract term.
• Pilot the preferred option before a long commitment.

Common questions

Why should a funder's submission service shape the choice of grant software?

UKRI guidance says relevant Innovate UK applications must use the Innovation Funding Service, covering lead applicant and partner responsibilities. An internal tool must support that route rather than create a competing final version, so the funder's service remains mandatory where specified.

What should be tested in a supplier demonstration?

Use a representative scenario from opportunity capture to approved submission. Assign an answer, revise it, resolve a comment, change a budget line, restrict a confidential attachment and export the final pack. Then compare that export against the funder's fields before scoring the product.

How should integration risks be managed?

List each system exchanging applicant, budget, accounting or reporting data. Define which system owns the authoritative value and who resolves differences. Ask the supplier to document interfaces, authentication, update timing, failures and change notice, and keep manual reconciliation until the connection proves reliable over a full reporting cycle.