The short version
- A useful pilot answers one operational question: can tenants complete a shared-room or parking booking with less help while the building team keeps control of permissions and exceptions
- Keep the scope to one building and a limited set of resources, name the owners, and record a baseline over comparable days before anything changes
- Define four measures and keep them apart: booked utilisation, admin effort, unmet demand and self-service completion. A booking is not occupancy
- Report to the owner as a decision, not a dashboard tour: the problem, the test coverage, the result, the outstanding risks and the proposed next step
A shared-space pilot works when it tests one building, one clear question and a small set of rooms and parking bays over about 30 days, with a recorded baseline, agreed metric definitions, tenant permission checks and an owner update that says what the results do and do not support. The sections below give you each of those parts.
A short pilot can show whether a new booking process works for a building and its users. It should answer a defined operational question, with an agreed baseline and a decision at the end.
For commercial property managers, a useful starting question is: can tenants complete a shared-room or parking booking with less help, while the building team retains clear control of permissions and exceptions? If you have not yet mapped where tenants get stuck today, start with the audit in making shared amenities easier to use.
Choose a manageable scope
Start with one building and a limited set of resources. Include representative users rather than only enthusiastic volunteers. Someone who visits once a week may find problems that a daily user no longer notices.
Name the pilot owner, reception lead, tenant contact and technical reviewer. Explain how participants get help and what happens if the new process fails. A documented fallback makes it easier to test honestly without hiding problems to keep the pilot moving.
A 30-day plan is a useful organising window, not a guaranteed implementation time. Identity, contractual or data requirements may need to be resolved before the trial begins.
Establish the baseline before you change anything
Record the current process over comparable days. Count requests, completed bookings, requests needing assistance and the time the team spends handling them. Keep a short log of the reason for each exception.
Be precise about what your systems can measure. A reservation shows intent to use a resource. A check-in or observation offers different evidence. Neither should automatically become a claim about building occupancy, tenant satisfaction or lease renewal.
| Measure | Definition | What it tells you | What it does not tell you |
|---|
| Booked utilisation | Booked resource-hours divided by available resource-hours | How much of the bookable time was reserved | Whether anyone arrived |
| Admin effort | Handling minutes divided by completed requests | How much team time each booking costs | Whether staffing costs will fall |
| Unmet demand | Valid requests that could not be fulfilled divided by valid requests | Whether capacity or rules are blocking tenants | Why each request failed, unless you log it |
| Self-service completion | Tasks completed without assistance divided by observed tasks | Whether tenants can book unaided | Whether they liked doing it |
Document exclusions, opening hours and the coverage of any physical observations. Do not combine room-hours and parking-bay days into a single unexplained utilisation percentage. The space utilisation definition explains why the two need separate denominators.
Include the difficult scenarios
A pilot that only tests successful bookings leaves the building team to discover the exceptions after rollout. Try overlapping requests, a cancellation, a no-show, a late arrival and a user whose access changes.
Agree how to handle resource priorities before testing them. An allocation policy may be constrained by existing tenant entitlements. The pilot should not silently change those arrangements. For parking, the guide to fair office parking allocation sets out the policy choices, and the difference between parking management and parking enforcement matters when a barrier is involved.
Use synthetic identities to check the separation between tenant organisations. Test booking details, notifications, reporting and exports. Stop expansion if a mandatory privacy or access requirement fails, even when users like the interface. The multi-tenant definition describes what that separation should look like.
Ask users about completed tasks
Use the same short questions before and after the pilot: were you able to complete the task, did you need help, and what would you change?
Report how many people responded. A handful of positive comments can identify a promising improvement, but it should not be presented as a building-wide satisfaction result.
The Building Engines and BOMA 2026 research announcement describes ongoing tenant communication demands and gaps between management perceptions and occupants’ experience. It is a vendor-sponsored survey of more than 350 CRE professionals. Use it as a reason to examine your own process, not as a baseline for your building.
Give the owner a decision, not a dashboard tour
Keep the pilot update to five parts: the original problem, the test period and coverage, the operational result, the outstanding risks, and the proposed next step.
For example, if handling time falls, state the measured change and the number of requests observed. Describe the time released as available team capacity unless staffing costs actually fall. Include subscription and setup costs separately.
Also record alternative explanations. A quieter week, a different tenant mix or extra support from the pilot team can improve the numbers without proving that the new process will perform the same way across the portfolio.
A short room-booking trial does not establish higher rents or stronger renewals. Those outcomes need different evidence and a longer view. The immediate decision is whether the process works well enough to continue, revise or stop.
Expand when the operating model is ready
Before adding another building, confirm who maintains resources and permissions, who handles exceptions and what support has been agreed. Re-test the conditions that change between sites, including identity setup, tenant boundaries and local operating rules.
HybridHero can be evaluated through its meeting room and parking workflows. Bring the pilot scenarios to the demonstration and ask the team to show how the proposed configuration meets them. If you are still choosing between tools, the guide to reviewing property operations software properly covers the requirements and cost questions.
Download the Shared Rooms and Parking Pilot worksheet from the free property manager operations pack for the 30-day working plan, metric definitions and owner-update template.
Common questions
How long should a shared-room and parking pilot run?
About 30 days of live use is a practical window, long enough to cover several ordinary weeks and at least one exception of each type. Add preparation time for identity, contractual and data questions before the trial starts, and do not count that as pilot time.
What metrics should a room booking pilot track?
Four, kept separate: booked utilisation, admin effort per request, unmet demand and self-service completion. Record the denominators and exclusions for each so the owner can see what the numbers cover.
Can a pilot prove that better amenities improve tenant retention?
No. A 30-day booking trial can show whether a process works and how much team time it takes. Renewal and rent outcomes need different evidence over a much longer period, and the owner update should say so plainly.
Who needs to be involved in a building pilot?
A pilot owner, a reception lead, a tenant contact and a technical reviewer, plus representative users from more than one tenant organisation. The technical reviewer is the person who tests tenant separation with synthetic identities.