The UK government is preparing to revise the commercial guidance used to plan and buy major technology programmes, bringing artificial intelligence, cloud concentration, cyber risk, and legacy systems into a framework first published in 2022.

The existing Digital, Data and Technology Playbook sets expectations for central government projects from initial assessment through contracting, delivery, and service management. Procurement officials expect a second version to be released in September.

The revision is due to address AI deployment and risk, cloud purchasing, cybersecurity, agile contracts, intellectual property, legacy technology, and more reliable cost estimates. Departments are expected to retain the “comply or explain” model, under which project teams follow the guidance or justify a different approach.

The final document has not yet been published, so its specific requirements remain unconfirmed. Its development nevertheless follows repeated criticism of programmes that begin with unrealistic budgets, unclear ownership, fragmented data, and contracts that make later change expensive.

Procurement inherits earlier decisions

Technology failures are often attributed to tender design, although many originate before procurement begins. A department may approach suppliers after choosing an architecture, setting an implausible deadline, underestimating legacy integration, or assuming that poor data can be repaired during delivery.

Competition is already constrained by that stage. Only a small number of vendors may be able to accept the scope and risk, while bidders either price uncertainty into the contract or expect later changes to recover costs.

A stronger playbook can require earlier market engagement and more credible “should cost” modelling, although departments need enough technical expertise to challenge their own assumptions. Guidance has limited value when teams lack the skills or authority to stop an unrealistic programme.

AI introduces further uncertainty because products, models, and pricing arrangements are changing more quickly than conventional public-sector contracting cycles. Buyers must establish what data a system uses, how outputs are checked, where models are hosted, who carries liability, and whether the service can be replaced without losing operational knowledge.

Purchasing access to a model without funding workflow redesign, assurance, integration, training, and continuing evaluation may produce an impressive pilot without a dependable service. Delegating too much design authority to one supplier can create an equally serious dependency on its platform and consultancy work.

Cloud architecture has become a commercial decision

Government cloud use has expanded from commodity hosting into critical platforms, data services, and AI infrastructure. That has improved access to modern technology, but it has also concentrated spending among a small number of providers and introduced persistent questions over egress charges, interoperability, resilience, and sovereign control.

The separate Cloud Challenge Book 2026 encourages public bodies to examine those trade-offs rather than defaulting to established buying patterns. Incorporating similar expectations into the DDaT Playbook could make them part of routine commercial assurance.

Legacy technology will require equal attention. Departments often buy a new front end or analytical layer while retaining the underlying systems, data structures, and manual processes that constrain performance. Without a funded retirement plan, modernisation can simply add another component to an already complicated estate.

The scale of public technology expenditure gives the guidance economic weight beyond Whitehall. Government estimates have placed annual public-sector digital spending as high as £46 billion, supporting consultancies, software vendors, cloud companies, integrators, and specialist suppliers.

Smaller businesses may benefit from modular procurement, clearer intellectual property rules, and contracts that avoid transferring disproportionate risk. Additional assurance requirements can also favour large companies with established legal and compliance teams, so the revised playbook will need to distinguish useful control from documentation that merely increases bidding costs.

Commercial guidance cannot replace experienced technical, operational, and procurement staff. Its value will become visible when departments use it to challenge a weak project before publication rather than explaining afterwards why familiar compromises should continue.