Guidance
Practical notes for managers
Questions worth answering before you commission administrative software, whoever builds it.

Scope
Scope
How do we choose the first workflow?
Pick one that is frequent, administrative, painful and owned by a manager who can make decisions. Avoid anything that needs clinical content to function.
Should we buy a product instead?
If an established product fits most of your process, often yes. Bespoke makes sense when local rules are distinctive or tools must fit around existing systems.
How do we avoid scope creep?
Write down what is out of scope at the start, and agree that new ideas go to a list for a later release.
Data
Data and governance
When should our DPO be involved?
From the outline stage, before anything is built. It is far easier to design minimisation in than to remove data later.
Do we need a DPIA?
Your data protection lead will decide. We provide clear technical descriptions to support one.
Can a supplier test with real data?
It should rarely be necessary. Ask for fictional test data and challenge any supplier who insists otherwise.
Change
Change
How do we introduce a new tool without disruption?
Run it alongside the existing process for a few weeks, with a named person collecting feedback.
What training is needed?
Short, role-specific sessions and one-page guides usually work better than long manuals.
Who owns the tool afterwards?
A named manager for the workflow, plus whoever is responsible for technical support.