The operating context
Four constraints that shape a public sector workplace
General characteristics of how public sector estates are typically structured — not claims about any specific organisation.
Capital is slow, revenue is scarce
Replacement budget arrives on a cycle you do not control, so extending the life of healthy hardware is worth more than a faster refresh.
Residency is not negotiable
Where data is processed and how long it is retained are frequently statutory rather than preferences.
Genuinely mixed estates
Devices spanning five or more years, several build generations and multiple support models are the normal condition, not technical debt to apologise for.
Accessibility is an obligation
Assistive technology has to keep working through every change, and the evidence that it does needs to be produced on request.
Where to look first
Four populations, four different first problems
Public sector organisations rarely have one workforce. Baselining them together produces a number nobody recognises.
Corporate and policy staff
Office-based, document-heavy, broad application estate.
- Long-tail application reliability
- Collaboration and meeting quality
- Ageing hardware ranked by strain
Practical note: This is usually where extension evidence pays back fastest, because the workload is light enough that older hardware genuinely still copes.
Public-facing service points
Shared devices, queue pressure, fixed opening hours.
- Session handover time between staff
- Boot and readiness at opening
- Link quality per site, separated from devices
Practical note: Seconds at a counter are visible to citizens. This population justifies its own baseline and its own target.
Field and inspection teams
Mobile, intermittently connected, frequently offline.
- Connectivity quality by area, not fleet-wide
- Application behaviour when offline
- Battery health against shift length
Practical note: Field staff are the least likely to report a problem and the most likely to be working around one.
Assistive technology users
Specialist software, low tolerance for change.
- Compatibility verified through every change wave
- Performance measured with assistive software loaded
- Regression detected before wave two
Practical note: Treat this as a named cohort with its own baseline. An aggregate score will never surface a regression here.
Deployment
Sovereign and on-premises options
Residency requirements should be settled before a pilot, not discovered during a security review. Deployment model is a first conversation, not a late one.
- Managed regional processing in EU, US and APAC
- Private tenancy where shared infrastructure is not permitted
- On-premises deployment by agreement for restricted estates
- Data inventory and retention published in full, and configurable
Procurement
What a public sector evaluation usually needs
Published so the information gathering can happen before the procurement clock starts.
| Requirement | Where it is answered | Available before contract |
|---|---|---|
| Data inventory and retention | Trust Center | Yes, published |
| Processing location options | Trust Center | Yes, published |
| Sub-processor list | Trust Center | Yes, on request |
| Accessibility conformance statement | Security pack | Yes, on request |
| Penetration test summary | Security pack | Yes, under NDA |
| Exit and data portability | API documentation | Yes, published |
Commonly paired with
Start with the estate you already own
For most public sector organisations the first useful output is a defensible extension list, not a business case for new hardware.
Request a demo