TOR starter kit for government software
Ten things to put in the terms of reference for a software system procured under RA 9184 — the checklist we would want in front of us if we were writing one. Free to copy and adapt. No form, no sign-up.

Ten clauses, and why each one matters
Each item lists what to write into the TOR and the reason. Use the ones that fit your project; leave the rest.
-
Write acceptance criteria, not a feature list
A feature list is nearly impossible to fail. An acceptance criterion names a real office, real records and a real test.
- Each module accepted against a written test: who performs it, with which records, and what result counts as a pass.
- Sample records supplied by the office (for example, twenty businesses from the treasurer’s list) for the test.
- A demonstration does not count as acceptance.
Why: It is the one change that makes every other clause enforceable.
-
Put the existing records in scope
Every office already holds records, and they are never as clean as the reports suggest.
- Migration of a named record set is part of the contract price.
- A reconciliation report showing what moved, what did not, and why.
- Acceptance of the migration is separate from acceptance of the software.
Why: Without it, the cheapest compliant bid excludes migration, and the old data becomes the next administration’s problem.
-
Name ownership and the way out
Source code, data export and environment access are three separate things. All three belong in the TOR.
- Source code ownership by the agency, or escrow with stated release conditions.
- Export of all records in a documented, non-proprietary format, on request and at contract end.
- Administrator access to the production environment, or a documented handover of it.
Why: An agency that cannot export its own records has bought a subscription to its own data.
-
Stage the acceptance, and the payments
One acceptance event at the end puts all the risk at the point of least time and least leverage.
- Design acceptance: the documented design, signed off.
- Functional acceptance on a pilot office, with live records.
- Full acceptance after a defined period of live running.
- A payment attached to each stage.
Why: Problems surface while there is still time and money to fix them.
-
Budget for the year after go-live
Support, hosting and change requests decide whether a system becomes part of how the office works.
- Support for at least twelve months after full acceptance, with response times by severity.
- Hosting, backups and a tested restore, priced separately from the build.
- A change-request rate or allowance for the first year.
Why: A procurement that funds only the build has funded the least durable part of the programme.
-
Require training and a handover pack
The people who run the system after the vendor leaves need more than a manual.
- Training for counter staff, supervisors and system administrators, with attendance records.
- Runbooks: deployment, backup and restore, user administration.
- An as-built document of the architecture and integrations.
Why: Handover artefacts produced during the build are cheaper and more accurate than ones reconstructed at the end.
-
Put the data-protection position in writing
Under RA 10173 the agency is the personal information controller; the vendor is a processor.
- Controller and processor roles stated in the contract.
- Retention periods, breach notification duties and timelines.
- Rules for sub-processing, and where the data is hosted.
Why: An assurance is not a contract term. The National Privacy Commission will ask for the terms.
-
Set the security baseline
State the controls the delivered system must have, so they are priced rather than optional.
- Role-based access, with counter, supervisor and administrator roles separated.
- An audit trail of changes to records, against named accounts.
- Encryption in transit; encryption at rest for personal data.
- Scheduled backups with a restore test before go-live.
Why: Controls added after award are change requests; controls in the TOR are part of the price.
-
Simplify the process before automating it
RA 11032 asks for streamlining as well as automation.
- The redesigned process, signed off by the office, attached to the TOR or required as the first deliverable.
- Forms, steps and approvals the system must remove, not only the ones it must support.
Why: Automating a process that has not been simplified encodes the queue into software.
-
Evaluate for delivery, not demonstrations
A committee reading documents alone cannot tell a maintainable system from a demo.
- A migration plan and a training plan inside the technical proposal.
- A technical evaluator from the office that will use the system.
- References for a comparable system running in a comparable office.
Why: It is the cheapest way to tell a bidder who has delivered into a live office from one who has not.
A practical checklist, not legal advice. Check every clause with your BAC secretariat and your legal office against RA 9184, its implementing rules and current GPPB issuances before you publish a TOR.
Want a second pair of eyes on a draft TOR?
Send it over. We will tell you which clauses a bidder could satisfy without delivering a working system. We cannot advise once a procurement is open, so ask before it is.