Portfolio analytics, and our service levels in public

Pipeline analytics for multi-site facility teams, plus our support policy and service level targets published in full.

Published By &

Handee stops work reaching a vendor whose credentials have lapsed. That has been the point of the product since day one, and it is the part most facility teams come to us for.

It is worth being precise about what that means, because it is what separates Handee from the alternatives. Contractor compliance networks hold documents. Facility management platforms treat compliance as a field on a vendor record. Spreadsheets do what spreadsheets do. All of them record. None of them stop anything. A contractor whose insurance expired last Tuesday still appears in the list, and the job still goes out.

Handee treats credential state as a gate rather than a note. Work does not reach a vendor who is not currently verified for that site's jurisdiction and trade. When a credential lapses, that vendor stops being eligible without anyone raising a ticket, and becomes eligible again when they renew. Compliance stops depending on somebody remembering to check.

That is the half of the job we started with. It is not the whole job.

Compliance gating tells you that the work went to someone qualified. It tells you nothing about where the work then went. Which sites are slow to get quotes back. Whether a job has been sitting unassigned for nine days. Whether the pipeline leaks at dispatch or at award. Most operators running more than a handful of sites answer those questions by exporting to a spreadsheet on a Friday afternoon, if they answer them at all.

Version 1.3 addresses that gap, and a second one: the fact that you had no way to check how we ourselves behave before you commit.

Advanced Analytics: where the work actually is

Growth and Business operators now have an Advanced Analytics view alongside the standard dashboard. It answers three questions.

Where does the pipeline leak? A cohort funnel follows work orders raised in a given month through open, dispatched, quoted and awarded. Because it is cohort-based rather than a snapshot, you see the actual conversion of a month's work rather than a mixture of this week's new jobs and last quarter's stragglers.

How long does each stage really take? Stage durations are reported as median and 90th percentile, not just an average. The average hides the jobs that hurt; the p90 is where the complaint calls come from. Durations are computed over a trailing window you choose, 30, 60 or 90 days, so a bad quarter last year stops dragging your current numbers around.

What is ageing right now? Work in progress is bucketed by age, under a day, one to three days, three to seven, seven to fourteen, and beyond, split by priority. Each priority carries its own breach threshold, so a high-priority job sitting for four days surfaces while a routine one at the same age does not shout at you.

None of this asks you to log anything new. It reads the status history the system already records as work moves through its lifecycle.

Advanced Analytics is part of the Growth plan and above. Starter operators keep the standard dashboard.

Our service levels, published in full

The second half of 1.3 is not a feature. It is two documents.

Handee now publishes a Support Policy and a Service Levels document, both readable without an account. They set out the priority levels, the support hours, the escalation path, and the response times we aim for.

We have been deliberate about what those documents claim. Everything in the service levels page is a target, not a contractual guarantee, and the page says so in its first section. No service credits attach to any figure in it. That is a choice, and here is the reasoning: we are an early-stage company, and we would rather publish numbers we consistently beat than numbers we owe you money for missing. If your procurement process needs contractual service levels with remedies, tell us before you buy and we will negotiate them into the agreement rather than pointing you at a web page.

What is on the page:

  • First response targets by priority and tier. A P1 critical issue on Business targets four business hours; Growth targets one business day.
  • A 99.5% monthly availability target for the web application, with the exclusions stated rather than implied.
  • Data residency: Handee runs on Microsoft Azure in Ireland (North Europe region). Customer data is stored in the EU. Backups retained seven days with point-in-time recovery.
  • Security and data protection response times, including breach notification in time for you to meet your own GDPR Article 33 obligation.
  • Versioning. Faster targets take effect immediately. Slower targets are announced thirty days in advance.

We also declined to publish figures we cannot yet stand behind. There is no recovery time objective on that page, because we do not have one we would defend under scrutiny. If your process requires one, ask and we will tell you honestly what we can support.

The pages render directly from the documents themselves, so the published page and the document can never drift apart. Both are linked from the footer, along with a status page link on a stable path.

Where this is going

Handee's goal is to be where commercial property teams across Europe check compliance and reach their contractors, covering ten thousand properties by 2027. Getting there means the system has to do more than block the wrong vendor. It has to show you the portfolio you are running and be honest about its own behaviour while doing it.

The measure we hold ourselves to is not features shipped. It is the human time recovered on the work you hand over.

Operators start free. Two seats, ten work orders, ten facilities, no card. Bring one site or your whole portfolio and see what the pipeline actually looks like.

Get started for free today