Skip to content

Government

Government technology with scope and procurement separated

State the public need, owners, proof, procurement route, and work limits before work starts.

Presenter discussing a government program with colleagues around a table

Public-sector brief

Describe the service need before discussing a delivery route

Start with the public goal, users, choice, and data. Then list the agency owners, review needs, procurement proof, and staff limits.

Jurisdiction detail

Open the government ICT page that matches the buyer

These pages keep the buying route apart from the service talk. Use the page for your buyer. Check its current route and proof.

Treat procurement, delivery, and personnel evidence as separate records.

Decision record

Give each boundary an owner and a source

The brief should show who confirms the need, data, buying route, and staff for the work.

Keep compliance claims scoped

Name the control, rule, policy, or approval that applies to the work. A broad tech claim does not prove that the work meets it.

Read public-sector case studies.

Discuss a government technology requirement

Describe the agency need at a high level. Confirm the procurement status, staff needs, work scope and evidence before delivery. Use an agreed channel for any agency or project material.

Want to learn more?

Explore the rest of the site or get in touch with the team.