Everything we're considering, planning, building and have shipped — in the open. Votes here genuinely change the order we work in, because a request from someone running a real building beats our best guess every time.
Loading the roadmap…
Target windows are shown where we're confident enough to commit. Where there's no date, it means we haven't scheduled it — not that we've forgotten it. Nothing here is a contractual commitment; plans change when we learn something.
A roadmap is a promise; release notes are the receipt. We publish the fixes as well as the features — a changelog that only ever announces good news isn't a changelog, it's an advert.
The most useful suggestions describe the problem, not the feature. “I can't tell which tenants are over their meeting room allowance” tells us more than “add a usage report” — because there might be a better answer than a report.
We read every one. Good ideas go onto the board as Considering so other operators can vote. If we're not going to build something, we'd rather say so than let it sit in a queue forever.
Something broken rather than missing? That's support, and it'll get looked at faster.
Sign in to suggest an idea or vote. We ask so that one person is one vote — otherwise the board is decided by whoever refreshes hardest. No password to invent: we email you a link.
JavaScript is required to sign in. If you'd rather just tell us, email support@work-hub.co.uk.
Votes tell us what matters and to how many operators. They don't automatically win — a small number of votes on something that unblocks a whole workflow can beat a popular nice-to-have.
A few items are foundations — the public API, for instance, makes a dozen other integrations cheaper. Those sometimes jump the queue even without the most votes.
If we've decided against something, we'd rather tell you and explain why than leave it sitting in Considering for two years. A clear no is more useful than a vague maybe.