A procurement brief that says “implement the DPG” leaves most of the purchase undefined. Which services will change? Who cleans the records? Who approves the interfaces? What proves the system is ready to run without the implementation team in the room?

A useful DPG procurement brief connects each required service outcome to a deliverable, an acceptance test and a named owner. It covers the work around the software: migration, integration, training, operations and eventual handover. This is a delivery specification, not a legal contract or a scorecard for choosing the product.

Start with the service you need. If the product decision is still open, use the open-source software evaluation guide separately. Mixing product selection and an implementation brief makes it hard to see what bidders have actually priced.

Define the purchase before listing features

Write a short service boundary: the users, transactions, locations and channels in the first release. Describe the current problem in observable terms. “Improve registration” is an ambition. “Allow authorised district staff to submit and correct a registration, including when the central connection fails” gives a delivery team something to investigate.

Then separate confirmed requirements from questions discovery must resolve. A fixed price against unknown migration quality or an unapproved operating model will contain assumptions. Get those assumptions into the open.

The UK Digital, Data and Technology Playbook emphasises outcomes, whole-life value and knowledge transfer. Those are useful commissioning principles. It is UK guidance, not UAE law or a substitute for a country's procurement rules, donor conditions or institutional approvals. A UK- or UAE-based commissioner buying delivery abroad still needs the applicable local requirements checked.

Label the phase explicitly: discovery, proof of concept, pilot or production rollout. OpenCRVS's implementation guidance, for example, says its proof of concept is not live registration or a full requirements-gathering exercise. Don't buy a demonstration and leave everyone to assume it includes an operational service.

Turn requirements into evidence

Use a row for each obligation. The requirement explains what must be true; the deliverable is what the supplier produces; acceptance evidence shows whether it works. “Documentation delivered” isn't a useful test of whether another team can operate the service.

AreaSpecify the deliveryAsk for acceptance evidence
Service designApproved workflows, roles and exception pathsService owner walks through ordinary and failed transactions
ConfigurationVersioned settings, languages, forms and access rulesRepresentative users complete agreed scenarios on the release candidate
Data migrationMapping, cleansing decisions, reconciliation and rejected-record handlingTrial migration accounts for source records and explains exceptions
InterfacesNamed systems, exchanged fields, permissions and failure behaviourTest reports include rejected, delayed and duplicate messages
OperationsMonitoring, backup, restore and incident proceduresReceiving team restores a test environment and handles a simulated incident
HandoverRepositories, deployment instructions, documentation and trainingAuthorised receiving team deploys from the supplied material

These are example acceptance methods, not universal thresholds. The buyer must set volumes, recovery objectives, accessibility needs, response times and tolerances appropriate to the service. Put a reviewer and a decision date beside each row.

An acceptance test needs someone authorised to accept it. A consultant can demonstrate that a workflow runs. Only the responsible institution can confirm it is the workflow it is allowed to use.

people sitting on chair in front of table while holding pens during daytime
Illustrative photograph, not a record of an engagement. Photo: Dylan Gillis / Unsplash.

Price the awkward boundaries

For each interface, identify both owners. Record who supplies the test environment, approves the data exchange, changes the receiving system and resolves a mismatch. “Integration with the national platform” is not a complete scope when that platform's team has committed neither access nor time.

The same applies to physical delivery. Devices, connectivity, travel, office readiness, local-language support and staff release for training need owners and budget lines. Where the buyer supplies something, say when it will be available and what happens to the plan if it isn't.

Ask bidders to distinguish included work, optional work and exclusions using the same headings. Separate one-off implementation costs from recurring operations, hosting, upgrades and support. Specify the comparison period and currency, and ask for assumptions on volumes, taxes and exchange rates rather than quietly comparing unlike totals.

For civil registration programmes, the existing digitisation guide covers the wider institutional work. Bring the relevant responsibilities into this purchase instead of assuming the software supplier owns all of them.

A worked requirement: the connection fails

Imagine a pilot in which a district office cannot reliably reach the central system. This is an illustrative commissioning example, not a claim about any particular DPG's offline capabilities.

A weak requirement says “must work offline”. A better brief defines the permitted user action during an outage, the information that may be stored locally, the expected outage duration, how staff can see pending work, and what should happen after reconnection. Ask the supplier to confirm whether the proposed product and version support that behaviour.

The evidence might be a controlled interruption during an agreed test: authorised staff continue the permitted task; queued work is visible; reconnection does not create duplicate records; rejected transactions reach a human queue. Security and service owners approve the test design before it runs.

If the required behaviour isn't supported, record a decision: change the operating process, add a separately scoped component, or reconsider the product. “To be configured later” is not a resolution.

Buy the ability to keep running

Specify who will control the hosting account, deployment repository, configuration history and operational documentation. Credentials need a secure transfer process, not an attachment to the final report. Agree access roles without assuming every supplier needs permanent administrator access.

Ask the legal and procurement teams to translate intended ownership and reuse into appropriate terms. Open-source licensing does not, by itself, settle ownership of every new document, integration or supplier-created component. Record the relevant licences and dependencies rather than writing “all IP belongs to us” over the top of them.

Include an exit deliverable from the start: a maintained inventory, data export instructions, an agreed assistance period and a rehearsal of the receiving team's work. The handover should be a demonstration, not a folder. Paying for training attendance is different from seeing the operational team complete the tasks it will inherit.

Use the procurement brief worksheet

Download the editable DPG procurement brief worksheet (CSV). It contains example requirement rows with deliverables, acceptance methods, buyer dependencies, owners and pricing prompts. No macros or formulas.

Replace the examples with your programme's requirements. Mark each row confirmed, discovery needed or out of scope. Have service, technical, operational and commercial owners review it before issuing the brief. An unresolved dependency should stay visible; don't turn it into a mandatory requirement just to complete the document.

If the brief needs a delivery review before it goes to market, my open-source and DPI work covers programme design and commissioning. Let's talk about the service you need to buy.

Frequently asked questions

Can one brief cover discovery and implementation?

Yes, if it separates the phases and their decision points. State what discovery must resolve, what evidence releases the next phase and how bidders should price uncertainty. Don't describe an unknown implementation scope as fully specified.

Should every requirement be mandatory?

No. Separate essential service obligations from preferences and unresolved questions. Ask the responsible owner to confirm why each mandatory item is necessary. Procurement specialists should check how those categories fit the applicable competition rules.

How do you specify support before knowing the supplier?

Describe the service's operating hours, incident consequences, required coverage and receiving team's responsibilities. Ask bidders to explain their proposed support model against those needs, including exclusions. Agree measurable targets rather than accepting “ongoing support”.

Is this worksheet a tender document?

It is an editable requirements aid. Your procurement and legal teams still need to place it within the right sourcing process, terms, evaluation method and approvals. It does not establish compliance with a particular jurisdiction.