Cloud, SaaS, colocation, or on-premises: choosing where agency workloads run
How public cloud, vendor-hosted SaaS, colocation, and on-premises infrastructure differ, and the criteria an agency uses to choose.
Articles
Every reference article on hqt.org in Guides & Checklists, written for agency procurement, technology, and program staff.
How public cloud, vendor-hosted SaaS, colocation, and on-premises infrastructure differ, and the criteria an agency uses to choose.
How custom development, commercial products, low-code configuration, and open source compare for an agency system, and how to decide.
A comparison of single-vendor suites and best-of-breed systems, with the questions an agency should answer before choosing.
Hiring staff, contracting a managed service, or buying project by project: what each model costs an agency in money, risk, and retained knowledge.
Full replacement, incremental modernization, re-platforming, or an API layer: how to compare four options for an aging system.
Four models for continuous security monitoring, what each asks of staff and contracts, and how response decisions stay with the agency.
How agencies choose among a commercial AI service, a provider model in their own cloud tenancy, and a self-hosted open model.
A checklist for agency project managers and department leads deciding whether a new system is ready to go live on its scheduled date.
A readiness checklist for IT and program staff to work through before drafting a solicitation for technology products or services.
A checklist for IT and contracting staff closing out a technology contract: notice, data return, access shutdown, and handover to the next supplier.
Work through this checklist before completing a cyber insurance application or renewal so every answer you give is backed by evidence.
A checklist for a newly appointed agency IT leader covering people, systems, contracts, security, work already in flight, and setting direction.
A pre-launch checklist for agency project teams verifying that a resident-facing website or application conforms to WCAG 2.1 Level AA.
A working checklist for program, legal, and IT staff negotiating or reviewing an interagency data sharing agreement.
A checklist for records officers and IT staff testing whether an agency system can retain, find, produce, and redact public records.
A month by month approach to a SaaS renewal: notice windows, price escalation caps, usage inventory, and exit readiness.
What belongs in an incident response plan a small agency team can follow, from severity levels to who approves a public statement.
What a privacy impact assessment answers, and how to make it a gate in procurement rather than paperwork filed after go-live
How agencies define engagement types, authorization, testing windows, deliverables, and a required retest in a penetration test solicitation
How to run security awareness training and phishing simulations that change staff behavior and still satisfy auditors and insurers
The sequence of a data conversion during a system replacement, who owns each decision, and what belongs in the statement of work
How agency staff plan and run user acceptance testing: scenario-based test scripts, tester recruitment, defect severity, and formal sign-off.
How to run a forms modernization effort, from inventory and process redesign to platform choice, accessibility, and ongoing ownership.
How to weigh native apps, responsive websites, and progressive web apps for resident services, and defend the choice
The parts of a working data governance program in a public agency, and the order to put them in place without new headcount.
A practical guide to picking inputs, outputs, outcomes, and efficiency measures a small staff can define, sustain, and review
How to choose peer jurisdictions, normalize the numbers, and document definitions so a comparison holds up in public.
How to assemble an evaluation set from real agency cases, set the answer key, and hold vendors to a measured accuracy number.
A practical structure for a technology strategic plan agency staff will read, plus an annual refresh routine that keeps it current.
How to charter an IT steering committee that decides: membership, decision rights, cadence, intake, and scoring.
A practical guide to fixing IT classifications, shortening hiring timelines, and keeping technical staff at a public agency.
How agencies prepare staff for a new system: naming super users, mapping role changes, timing training, and staffing go-live.
A practical method for running legacy and new payroll side by side: how many cycles, which cases to force in, and how to clear every variance.
A sequenced year-end close calendar, subledger tie-outs, and the reports and IT control evidence auditors ask for.
A working separation checklist for public agencies covering final pay, benefits, account access, physical assets, and records holds.
A structured checklist for planning, running, and closing out parallel payroll testing before a new HR system goes live.
A working method for estimating camera storage, bitrate, and network load before purchase, with a 200 camera worked example.
How to specify construction closeout as a structured data handover so asset records, as-builts, and controls files reach your systems.
A specification and siting checklist for public self-service kiosks in agency lobbies, from ADA placement and PCI scope to staffing the helper role.
A checklist for configuring, monitoring, and proving access controls in health and human services case systems.
A requirements checklist for tree inventory and urban forestry software: data fields, work order links, refresh cycles, and RFP terms.
A practical quarterly restore drill programme for agency IT: what to sample, how to time it against RTO, and what evidence to keep.
How to escalate from tabletop to live failover, scope a test to one maintenance window, and close the findings.
How to turn a long scanner export into a tracked remediation queue with owners, deadlines, and signed risk acceptances.
How public agencies run a blameless outage postmortem, brief officials and the press, and hold hosted vendors to their own review.
How to write operational runbooks agency staff can follow during a late-night outage, and how to keep them current.
How agencies keep network diagrams, system profiles, and as-built records current, and who owns each update.
A ready-to-run two-hour tabletop exercise for a SCADA compromise at a water utility, with injects, roles, and decision points.
A runnable ninety-minute tabletop exercise for districts facing a vendor-disclosed breach of student records.
A one-page set of cybersecurity measures a city council or board can act on, with cadence, open-meeting, and definition guidance.
How to run a tabletop exercise for a 911 center CAD outage, from declaring continuity to rebuilding the call record.
How sample frame, mode, response rate, weighting, and margin of error determine whether a resident survey's numbers hold up.
A field-by-field guide to designing intake, permit, and inspection forms so the submissions can actually be counted and reported.
How to choose the right denominator for agency per-capita rates, which population estimates to cite, and how to handle small jurisdictions.
Why average response times mislead on skewed data, how to compute percentiles consistently, and what to publish.
How to tell whether a month-over-month or year-over-year move in a low-count agency measure is real signal or ordinary variation.
Why a before-and-after chart rarely proves a program worked, and the low-cost comparison designs agencies can use instead.
How to scope, teach, tier, and evaluate an internal data literacy program so agency staff can interpret the reports they already receive.
Compares central, embedded, and contracted analytics staffing on responsiveness, definitions, retention, and cost for public agencies.
A practical method for choosing your first automation target using system event data, queue and rework measures, and short staff time studies.
How agency teams find, question, and document software vendor references so the answers are useful and the award file holds up.
How to seat, brief, and run a proposal evaluation panel: conflict disclosures, confidentiality, independent scoring, and the written record.
A section-by-section guide to drafting the surveillance impact report and use policy your governing body will review.
What an acceptable use policy needs to cover, from personal use and monitoring notice to remote wipe, plus who must review it.
How a small public agency can layer its security policies, adopt them in a sensible order, and keep the suite current.
How a local government builds the program around its retention schedule: roles, written policy, training, destruction approvals, and audits.
A practical guide to issuing, scoping, applying, tracking, and releasing legal holds across agency email, chat, file shares, and vendor systems.
Get in touch
Talk with an HQT engineer. We respond to agency, corporate, and partner inquiries promptly.