Key takeaways

  • Shared resources like rooms, laptops, and vehicles are easy to own and hard to share, and spreadsheets break the moment two people want the same one.
  • Raley Bookman adds self-service booking to the JSM portal on top of JSM Assets, so people reserve from the Help Center they already use.
  • Each reservation becomes a Jira ticket linked to the asset, so a slot can only be held once and the audit trail builds itself.

Somewhere in your company right now, a laptop is "definitely booked," a meeting room is hosting two teams who both have it in writing, and a spreadsheet called bookings_FINAL_v3.xlsx is quietly lying to everyone.

Shared resources are easy to own and hard to share. Raley Bookman fixes the sharing part by putting reservations where your team already works: the Jira Service Management portal. It adds self-service booking on top of the assets you already track in JSM Assets. People open the portal, see what is free on a timeline, pick a slot, and get a confirmation. Each reservation becomes a Jira ticket linked to the asset, so a room, a loaner laptop, or a fleet vehicle can only be held by one person at a time.

The real cost of booking by spreadsheet

Most companies still book internal resources with some mix of spreadsheets, a shared calendar, and a hopeful email to whoever "looks after" the thing. That works until two people want the same resource at the same time, which is to say it works until lunchtime. Three things go wrong, every time:

  • Downtime. Two bookings collide, someone loses, and a meeting starts ten minutes late while people find another room.
  • Wasted spend. Nobody can see what is actually free, so teams buy a sixth loaner laptop while five sit in a drawer.
  • Annoyed people. Booking a desk should not require knowing which colleague secretly controls the calendar.

How Bookman works

Bookman sits between your JSM Assets database and the service portal. Your assets already live in JSM Assets, with their capacity, location, and details. Bookman makes those assets bookable, so people reserve them from the same Help Center they already use to raise IT and HR requests. No new tool, no second login.

What you get

Four things do the work:

  1. A real-time timeline. People see availability at a glance, pick a slot, and get an automatic confirmation, all inside the portal.
  2. Asset-linked reservations. Every booking ties to a specific asset in JSM Assets, so details like "seats 10" or "has a projector" stay attached to the reservation.
  3. Conflict prevention by design. Once an asset is held for a slot, Bookman will not hand the same slot to anyone else. Double-bookings stop being possible rather than being discovered.
  4. Booking rules you set. Define booking windows (say, 8am to 5pm) and maximum durations so one person cannot reserve the demo room for a fortnight.

Every reservation also creates a Jira ticket, which gives you a searchable record of who booked what and when. That record is genuinely useful later, when someone asks whether the third-floor room is worth keeping.

Where teams use it

Bookman handles any asset you track in JSM Assets, not only meeting rooms:

  • IT: loaner laptops, test devices, VR headsets, anything that gets checked out and (eventually) returned.
  • Facilities: meeting rooms, hot desks, parking spaces.
  • Operations: pool vehicles and shared equipment for off-site events.

It runs on your existing Jira, so going from five rooms to five thousand devices is a matter of adding assets, not adding infrastructure. You can also read how one team used Raley Bookman to end meeting-room double-bookings.