These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Resource Booking System
- Who it's for
- Shared service operations
Shared service operations
A shared service team may receive work from several internal organizations. Each substantial request can be a booking with its own date window and owner. Work groups separate streams of activity, and assigned items let specialists see their part of the job. The manager can review reserved hours and actual work across the engagements instead of relying on an informal queue.
How Resource Booking System is set up for you
Request context
The organization and booking identify who needs the work and when.
Specialist assignment
Work items carry priority, assignee, due date and reserved hours.
Operating evidence
Submitted usage, review decisions and receipts show how effort was handled.
A shared service team may receive work from several internal organizations. Each substantial request can be a booking with its own date window and owner. Work groups separate streams of activity, and assigned items let specialists see their part of the job. The manager can review reserved hours and actual work across the engagements instead of relying on an informal queue.
Begin with a small set of active requests that have different owners and end dates. Record the requested work as bookings and create the groups used by the team. Assign specific items to specialists, including one that may become blocked by a dependency. The lead should be able to find that item in Blocked Booking Resources, give the related constraint an owner and revisit its mitigation.
Ask each specialist to record time against the correct booking. The Usage Reviewer checks the recorded approval outcomes and failed attempts. At review, compare the work still in progress with pending confirmations and the booking end date. A completed request should have an understandable history of work and decisions, so the next team can see what happened if the organization asks for follow-up.
Features to start with
Roles on the team
- Delivery Lead
- Owns the booking plan and follows delivery exceptions.
- Project Manager
- Coordinates assigned work and checks schedule and progress.
- Team Member
- Maintains assigned work and submits dated usage.
- Usage Reviewer
- Inspects usage outcomes and failed attempts after submission.
- Viewer
- Reads the delivery position without changing operating records.
Set up Resource Booking System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.