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
- Features
- Organizations and team
Organizations and team
Keep client context and delivery staff ownership close to the booked work.
OverviewBooking Schedule×
Resource Booking System · Organizations and team
New
Booking Schedule
Active waits for the project manager
| Booking number | Booking subject | Starts at | Ends at | Owner | Booking status | |
|---|---|---|---|---|---|---|
| BKN-50702 | Planned bkn-643 | 23 Oct | 26 Oct | Planned | ||
| BKN-80349 | Active bkn-552 | 10 Oct | 13 Oct | Active | ||
| BKN-29575 | At risk bkn-931 | 03 Oct | 06 Oct | At risk | ||
| BKN-25416 | Planned bkn-914 | 24 Oct | 28 Oct | Planned | ||
| BKN-40691 | Active bkn-212 | 20 Oct | 24 Oct | Active |
6 of 6 records
Planned bkn-643Bookings · BKN-50702
PlannedStarts at23 Oct
Ends at26 Oct
What you can do
Know who the work serves
An Organization is the client or internal business unit for which an engagement is delivered. Its name, relationship state and contact details provide context before a Project Manager creates a booking. A team member represents a person doing or owning delivery work. The profile carries practice, role, region, active state and weekly capacity hours. Bookings, work groups, assigned items, confirmations, conflicts and constraints can each point to a team member in the relevant owner or assignee field.
That separation helps a delivery lead review a busy engagement. The booking owner is accountable for the whole engagement. A work group owner can organize one part of it. The person assigned to an item can update that work, while a checkpoint or exception has its own owner. Those assignments can differ, so each record should name the person expected to act. The team profile also shows rollups for assigned and logged hours that can help a manager prepare a discussion about future work.
How the work is organized
- Client context. Organizations give bookings a business owner and contact context.
- People. Team members carry delivery role, practice and weekly capacity information.
- Responsibility. Each operating record points to its relevant owner, assignee, reviewer or actor.
What to agree during setup
Agree who maintains organization contacts and relationship state. Keep internal and client organizations named consistently so bookings can be grouped without duplicate accounts. Decide who maintains team member active state and weekly capacity hours. A lead should confirm that a person is active before giving them new work. Define how a practice lead or manager is represented in your team directory, and review access separately from a person’s delivery role. The Users record governs application identities; a team member profile describes delivery participation.
Check the handoff on an actual case
Create an organization for an upcoming engagement and a team member who will own delivery. Give the booking that organization and owner. Add a work group with a different owner, then assign an item to the person doing the work. In Active Bookings, the Project Manager should find the overall owner. In Booking Resources In Flight, the Delivery Lead should find the assignee. In My Booking Resources, the team member should find their own assignment. A later conflict can be given another owner without changing the booking owner.
When a team member becomes inactive, review their open assignments and exception ownership before changing the profile. An inactive state provides a clear signal for future planning, while the historical bookings and decisions should still be understandable to the delivery team.
What your team sees
- My Bookings — Engagements owned by the signed-in delivery owner.
- My Booking Resources — Assigned work with dates and its current state.
- Active Bookings — Client and internal engagements with accountable owners.
Follow the work through
Start with booking setup and work execution.
What it keeps track of
Data model- Organizations
- Client and internal business organizations that projects are delivered for.
- Team members
- Delivery staff with role, practice and weekly capacity.
- Users
- Users
- Bookings
- Engagements delivered for an organization, with budget and schedule.
- Resources
- Groupings of work inside a project.
- Booking resources
- Individual pieces of work assigned to a delivery team member.
- Confirmations
- Dated checkpoints a project must meet.
- Booking conflicts
- Defects and change items raised against project work.
- Resource constraints
- Project risks with probability, impact, owner and mitigation.
Who uses it
Permissions- Admin
- Maintains identities; Project Manager assigns booking ownership; Delivery Lead follows work across the team.
Set up Resource Booking System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.