Picture an office where a system was built, it worked, and the people who built it moved on. Now a report needs a new column, or the server needs to be moved, and nobody in the building knows how. The system the office paid for has become something it rents from whoever still understands it.
What lock-in means
Lock-in is the situation where an organization cannot change supplier, or even make small changes itself, without unreasonable cost. It comes in several forms. The data may be stored in a format only one company's product can read. The system may have no written documentation, so the knowledge exists only in a few people's heads. The contract may leave ownership of the program code with the developer.
For a private business this is an inconvenience. For a public office it is more serious, because the service has to continue through changes of leadership, budget cycles and the end of any single contract. A permit system or a payroll system cannot stop because a supplier closed, raised its price or lost interest.
We are a supplier ourselves, so this is partly a statement against our own short-term interest. We think a developer earns repeat work by being useful, not by being impossible to replace.
What other governments require
Governments that have built many digital services have written this lesson into their rules. The United Kingdom's Service Standard has 14 points. Three of them deal with this subject: choose the right tools and technology, make new source code open, and use and contribute to open standards, common components and patterns.1
The guidance under those points is plain. Teams should understand the total cost of ownership of a technology and preserve the ability to make different choices in future, and should reduce the chance of getting locked into contracts for specific tools and suppliers by using open standards.2 Because public services are built with public money, the team should keep ownership of the intellectual property of new code, which also makes it less likely to be locked in to a single supplier.3 Open standards help an office avoid getting locked into a particular supplier or technology.4
The United States government's Digital Services Playbook says the same in contract terms. Its checklist asks that the contract specify that software and data generated by third parties remains under the government's control, and that it include a transition of services period and a transition-out plan. It advises that technology choices should seek to avoid vendor lock-in.5
What Philippine law says about cost over time
The New Government Procurement Act, Republic Act No. 12009, approved on July 20, 2024, moves Philippine procurement in the same direction. One of its governing principles is sustainability in a procurement process that covers the whole lifecycle of a property and ensures value for money. It defines lifecycle cost as the total cost of ownership over the entire life span of an asset, from acquisition through operation and maintenance to disposal.6
The Act requires procuring entities to adopt a procurement strategy that considers the whole lifecycle of a project. It also says specifications should be based on characteristics, performance requirements or recognized standards, and that reference to a brand name is not allowed except for stated reasons such as technical compatibility, interoperability, servicing or maintenance.6
The Act does not mention software lock-in by name, and we do not want to overstate it. But the idea carries over directly. The price of a system is not the amount on the contract. It is that amount plus every year of hosting, support, changes and training that follows, and a system only one supplier can maintain makes each of those years more expensive.
What a real handover includes
Our approach is to treat the handover as part of the product, planned from the first week and not assembled in the last. An office should finish a project holding everything it needs to run the system, hire someone else to improve it, or move it to another server.
Auditors look for some of this already. The Commission on Audit's guidelines on electronic documents require an agency that uses electronic signatures to develop, maintain and update the system documentation, to keep standard operating procedures for its electronic records, and to train its employees in their proper use.7 Documentation and training are not extras. In that setting they are part of what the auditor expects to see.
We keep our own website to the same rule. Its design decisions, supported screen sizes and step-by-step instructions for running and checking the site are written down beside the code, and automated checks run before any change is published. A developer who has never met us should be able to pick it up.
- The program code, with the office's right to use and change it stated in the contract.
- The office's data, exportable in common formats such as spreadsheet and text files.
- A user manual for staff, written in plain language with pictures of the real screens.
- An administrator's guide: how to add users, back up, restore and move the system.
- Technical documentation that lets another developer continue the work.
- Training for the people who will use and look after the system, and a named period of support after launch.
Open standards in everyday terms
An open standard is a published, shared way of doing something that no single company controls. The format of ordinary web pages, the SQL language used by many database systems, and plain export files such as CSV are examples. When a system is built on them, many developers already know how to work on it and many tools can read its data.
This matters for talent as well as cost. A system built on widely taught technology is easier to find people for. We believe local offices should be able to hire local people to look after their systems, and that choice of technology either opens that door or closes it.
Questions to ask before you sign
Any office or business in the Bangsamoro can protect itself with a few questions. Who owns the code when the contract ends? Can we export all our data at any time, in a format another system can read? What manuals and training are included in the price? If your company closed tomorrow, what would we need to keep running, and do we already have it?
A supplier confident in its work should answer these without discomfort. We would rather be asked back because the system served the office well than be kept on because nobody else can open it.
Sources
- Service Standard - Service Manual. GOV.UK, Government Digital Service.
- 11. Choose the right tools and technology - Service Manual. GOV.UK, Government Digital Service.
- 12. Make new source code open - Service Manual. GOV.UK, Government Digital Service.
- 13. Use and contribute to open standards, common components and patterns - Service Manual. GOV.UK, Government Digital Service.
- The Digital Services Playbook. U.S. DOGE Service, United States Government.
- Republic Act No. 12009, New Government Procurement Act. The Lawphil Project, Arellano Law Foundation, 2024-07-20.
- COA Circular No. 2021-006, Guidelines on the use of Electronic Documents, Electronic Signatures, and Digital Signatures in Government Transactions (attached to DPWH Department Memorandum Circular No. 57, series of 2021). Commission on Audit, copy published by the Department of Public Works and Highways, 2021-09-06.