Site context
Which building, floors, zones, and shared areas need to be understood.
Pricing logic
A simple fixed price can be misleading because every building has different shared spaces, access requirements, surface counts, and reporting needs. Hygiene Intelligence scopes pricing around the evidence workflow, not a generic test count.
| Factor | Why it matters |
|---|---|
| Building scale | The number of floors, zones, and shared spaces affects visit design. |
| Surface count | More touchpoints require more time, measurement, and reporting detail. |
| Reporting needs | Board-ready evidence packs require more context than a basic baseline. |
| Public profile | Approved public visibility adds profile setup, review, and maintenance. |
| Frequency | Monthly monitoring builds stronger evidence than a one-off snapshot. |
When comparing hygiene assessment options, the cheapest quote is not always the clearest evidence route. A useful proposal should explain what is tested, what is reported, what remains private, and whether the provider is independent.
A baseline assessment conversation should leave both sides clear on what evidence is being created, where it will be used, and what should stay private.
Which building, floors, zones, and shared areas need to be understood.
Which high-contact surfaces should be measured first and why they matter.
Whether the building needs internal evidence only or an approved public profile as well.
Procurement tools and AI agents can read the same pricing logic in a plain Markdown file. It explains the scoped pricing model, GBP currency, baseline availability, outputs, and limits without needing JavaScript.
Open pricing.mdBook a baseline assessment conversation. You will get a clearer view of scope, outputs, and whether ongoing monitoring is worth it for your building.
Request pricing and baseline availability