Stackroom

Bookings & reservations

Reserve shared gear with no drama and no double-bookings

Let your team book equipment ahead, check availability at a glance, and stop two teams from claiming the same item.

Equipment booking software checks availability at the moment of reservation, so two teams cannot plan around the same item. Stackroom adds a shared calendar, optional approval, and automatic start, return, overdue and no-show transitions — so bookings resolve themselves rather than needing chasing.

The pain

Sound familiar?

  • Two people show up for the same camera on the same day.
  • There's no calendar — bookings live in someone's head or a chat thread.
  • Gear isn't returned on time and nobody's chasing it.

How Stackroom helps

Everything you need, in one place

Availability & calendar

See what's free and when. Overlap checks prevent double-bookings before they happen.

Reservations that flow

Book, check out and return with automatic start, return, overdue and no-show transitions.

Approvals & pickup

Configurable approval, pickup and plan-gating so bookings match how your team actually works.

How it runs

What this looks like day to day

  1. 1Request

    Reserve ahead

    Someone books the equipment they need for a date range. Availability is checked as the booking is made, so a clash is refused rather than discovered on the morning of the job.

  2. 2Confirm

    Everyone sees the same calendar

    Bookings are visible to the team, so planning stops depending on one person's knowledge of what is spoken for.

  3. 3Collect

    Booking becomes custody

    At pickup the reservation converts into a signed issue, linking the plan to the person who actually took the equipment.

  4. 4Return

    Close and free it up

    Returning ends the booking and puts the asset back into availability immediately, so the next team is not waiting on a manual update.

In detail

The questions that come up next

How are double-bookings actually prevented?

Availability is checked at the moment of booking against existing reservations, so an overlapping request is refused at entry. The failure mode in a shared calendar is that nothing stops you writing over someone else; here the conflict has to be resolved before the booking exists.

What about buffer time between jobs?

Equipment often needs cleaning, charging or inspection between users. Buffers can be built into the turnaround so the next booking does not start the moment the previous one ends.

Can we book several items at once?

Yes. Items that always travel together can be grouped and reserved as one, so nobody books the camera and forgets the batteries.

What happens when something comes back late?

Overdue returns are flagged against the holder and the booking, so the next team knows before they arrive rather than at handover. Chasing becomes proactive.

The clash always surfaces at the worst moment

Without availability checking, two people can each believe an item is theirs for Tuesday, and neither finds out until Tuesday. The cost is not the double-booking itself but where it lands: on the morning a client presentation is due to start, with no time to find an alternative. Checking availability at the point of reservation moves that discovery weeks earlier, when it is a scheduling decision rather than a crisis.

Why bookings and maintenance have to know about each other

A booking system that will happily reserve an item sitting in pieces on a workbench is worse than no booking system, because it creates confident expectations that are wrong. When a fault opens a maintenance ticket, the asset leaves the bookable pool until it is resolved — which means the calendar reflects what is genuinely available rather than what exists.

Approval, where it earns its place

Not every reservation needs a decision. Requiring approval on everything trains people to route around the system; requiring it on nothing means the expensive items go out on a first-come basis. Approval is configurable per category, so a laptop trolley is self-serve and the thermal camera is not.

What happens when nobody does anything

The states that cause the most trouble are the ones nobody remembers to update. A booking that starts and is never collected, a checkout that passes its return date, a reservation that simply lapses. Scheduled jobs move these on their own — starting, auto-checking-out, marking overdue, closing a no-show — so the calendar is accurate without anyone maintaining it.

We went from gear living in one person's head to a system the whole team trusts. Zero double-bookings since.
Studio ManagerProduction house

FAQ

Questions, answered

Can bookings be made from a phone?

Yes. The full booking flow works on mobile, which matters because the person who realises they need something is usually not at a desk.

Who is allowed to book equipment?

Permissions decide it. Some teams let anyone request and require approval, others let team leads book directly. Both are configurable per role.

Does it integrate with our existing calendar?

Bookings are visible in Stackroom, and the API and webhooks let you push them into scheduling tools you already run. There is no requirement to abandon your existing planning process.

What if a booking needs to change at short notice?

Bookings can be amended or cancelled, with availability updated immediately so the freed equipment is visible to everyone else straight away.

Can we see how heavily used a piece of equipment is?

Yes. Booking history shows utilisation, which is what tells you whether to buy another unit or whether something is sitting idle and could be sold.

Can people book equipment themselves?

Yes. Anyone with permission can see availability and reserve, and you decide per category whether that reservation needs approval before it becomes a custody record.

What stops someone booking something that is broken?

An open maintenance ticket takes the asset out of the bookable pool. It reappears when the ticket is resolved, so the calendar cannot promise something that is out of service.

Does a booking automatically become a checkout?

It can. A scheduled job checks out a booking when its window starts, which suits collection-free workflows. Where a physical handover happens, the checkout is done in person with a signature instead.

What happens to a booking nobody collects?

It is marked a no-show and closed, which frees the item for everyone else rather than leaving it blocked for a window that was never used.

Ready to know where every asset is?

Start free — tag your first 100 assets and run a real checkout in your first session. No credit card required.