Every model we deploy for an agency ships with a model card
A short, plain-language document that explains what a model does, how it was tested, and where it should not be used.
Blog
HQT blog posts on data for public agency technology teams.
A short, plain-language document that explains what a model does, how it was tested, and where it should not be used.
Publishing what people repeatedly ask for is cheaper than answering each request by hand.
Addresses disagree across permitting, assessment, billing, and dispatch, and reconciling them takes an address layer with a named owner.
Legacy data resists conversion in ways a schema mapping never shows, so we plan and validate migration as its own project.
Real-time data from meters and sensors looks simple until the sensors misbehave. Design notes for utilities and public works.
Most dashboards die within months. The fix is less about visualization and more about definitions and ownership.
The most valuable part of a utility digital twin is the part nobody wants to fund: accurate asset data.
Get in touch
Talk with an HQT engineer. We respond to agency, corporate, and partner inquiries promptly.