Managing Labs, Equipment and Meeting Rooms
Booking, approvals, damage and the one piece of equipment everyone needs at once. The facilities half of an incubation centre, done properly.
The bit that is genuinely operational
Programme design gets the attention. Facilities are what actually generate the complaints, and they are managed on a whiteboard in more incubation centres than anyone admits.
The failure modes are consistent and all of them are avoidable: two teams booked into the same lab, one company monopolising the good instrument, a broken piece of equipment with no record of who used it last, and a meeting room permanently held by a recurring booking nobody attends.
Separate the three things
They behave differently and treating them alike is where trouble starts:
| Type | Nature | Needs |
|---|---|---|
| Allocation | Ongoing - a desk, a cabin | Rate, deposit, term, notice |
| Booking | A window - room, lab, instrument | Availability, quota, sometimes approval |
| Consumable | Depleting - materials, print credit | Balance, top-up, charging |
Most centres model the first and improvise the other two. Bookings in particular need real machinery, because two people wanting the same window at the same time is a conflict a spreadsheet cannot prevent - it can only record after the fact.
Decide what needs approval, and be sparing
Approval is a bottleneck. Use it where it earns its place:
No approval - a meeting room during working hours, a hot desk, a shared workspace. Publish availability, let people book, enforce a quota.
Approval - anything scarce, expensive, or with a safety dimension. A lab with one instrument. Equipment requiring induction. Out-of-hours building access. The auditorium.
Approval plus supervision - anything where an untrained user can hurt themselves or destroy something costly.
The mistake is requiring approval for everything because it feels safer. It is not safer; it produces a queue, and a queue produces workarounds - people asking a friendly staff member directly, which is exactly the informal allocation you were trying to avoid.
Publish quotas before you need them
Every shared resource needs a stated limit per startup per period, written down at the start.
The reason to do it early is social rather than technical. Introducing a limit after one team has been monopolising the instrument is a conversation about that team. Having had the limit all along makes it a rule about the resource.
Sensible shapes:
- Meeting rooms: a number of hours per week per startup
- Shared instruments: a number of sessions per week, and a maximum consecutive slots
- Out-of-hours access: named individuals only, after induction
- Auditorium: by request, with notice
Record who used it, and when
Every booking should leave a record of who booked, for when, for what, and whether they turned up.
The last field is the one people leave out and the one that pays for itself. No-shows are the largest hidden cause of resource scarcity in incubation centres: a room booked and unused is a room unavailable to someone who needed it. If you can see no-show rates, you can introduce a simple rule - two no-shows and bookings need approval for a month - and reclaim a surprising amount of capacity.
It is also what you need when something breaks. "Who used the instrument last" is an answerable question if bookings are recorded and an unanswerable one otherwise.
Write down liability before anything breaks
The agreement a startup signs should cover, for facilities specifically:
- Which facilities they may use, and any induction required first
- Who may operate what - named individuals for anything specialised
- Liability for damage, and whether it is capped
- What happens to their deposit if something is damaged
- Whether supervision is required, and who provides it
Centres routinely discover none of this was written down at the moment an expensive instrument is damaged. The conversation that follows is bad for the relationship and usually ends with the centre absorbing the cost, because there is nothing to point at.
Charge for the expensive things
Bundling all facilities into a desk rate is simple and it has two costs.
Light users subsidise heavy ones, which is unfair in a way founders notice. And there is no price signal, so the team that would book the good instrument every afternoon has no reason not to.
A small charge for scarce, expensive resources - even a heavily subsidised one - changes behaviour more than the amount suggests. It also gives you a defensible answer when someone asks why they cannot have it all day.
Maintenance is a scheduling problem
Shared equipment needs servicing, calibration and occasional repair, and those need to be bookings too - blocked out in the same system, visible to everyone.
Maintenance that lives in a separate calendar produces the worst possible outcome: a startup books the instrument, arrives, and finds an engineer working on it. That single experience does more damage to confidence in the booking system than a month of minor conflicts.
A short setup checklist
- Allocations, bookings and consumables handled as different things
- Approval required only where scarcity or safety justifies it
- Quotas published per resource, before anyone hits them
- Every booking records who, when, what, and whether they attended
- No-show rule written down
- Induction requirements stated per facility
- Liability and damage terms in the signed agreement
- Expensive resources charged separately, even nominally
- Maintenance blocked in the same calendar everyone books from
Frequently asked questions
- Should facility bookings need approval?
- It depends on scarcity and risk. A meeting room usually does not - first come, first served with a quota works. A lab with one shared instrument, or anything where damage or safety is a factor, should. Approving everything creates a bottleneck nobody thanks you for.
- How do you stop one startup monopolising shared equipment?
- A published quota per period, and a rule about consecutive slots. Both need to exist before the problem appears, because introducing a limit in response to one company's behaviour is a conversation nobody wants and it looks personal.
- Who is liable if equipment is damaged?
- Whoever you wrote it down as, at allocation. Most incubators discover they never wrote it down, at the moment something expensive breaks. Put liability, induction requirements and supervision rules in the agreement before anyone books anything.
- Should facilities be charged for separately from desks?
- Usually yes, at least for the expensive ones. Bundling everything into a desk rate means light users subsidise heavy ones, and it removes the price signal that stops a single team booking the good instrument every afternoon.
