Organizations that manage shared resources — vehicles, meeting rooms, laptops, tools, or event spaces — quickly discover that spreadsheets and calendar invites don't scale. Double bookings happen. Equipment goes missing. Managers have no visibility into who has what, for how long, or whether resources are being used efficiently. MVC Booking Manager solves all of this with a purpose-built ASP.NET Core MVC application that models the real-world lifecycle of booking a resource, from request to return.
Organization Hierarchy Setup
Before any resource can be booked, the system needs to know who is booking and under what organizational context. MVC Booking Manager supports a multi-level organization hierarchy — departments, divisions, cost centers, or any custom structure — so that bookings are always tied to the right unit. Administrators define the hierarchy once, assign users to nodes, and all subsequent bookings inherit the organizational context. This means reports can slice utilization by department, cost center, or team without any manual tagging.
The hierarchy also drives approval routing: a booking request from a user in the Engineering department can automatically route to the Engineering manager for approval. This eliminates the need for users to know who to ask — the system already knows.
Resource Catalog: Vehicles, Rooms, and Equipment
The resource catalog is the heart of the system. Each resource has a type — Vehicle, Room, Equipment, or a custom category you define — along with attributes like capacity, location, hourly or daily rate, and availability windows. Vehicles carry additional fields like license plate, seating capacity, and fuel type. Rooms include floor plans, AV equipment lists, and capacity. Equipment tracks serial numbers, condition status, and maintenance schedules.
Resources can be grouped into pools. For example, a fleet of 10 sedans can be managed as a single pool where any available car can be assigned to a booking. The system handles the assignment automatically, picking the first available resource that matches the booking criteria. This pooling approach drastically reduces scheduling friction compared to booking individual resources by name.
Booking Lifecycle: Draft to Completed
Every booking moves through a well-defined six-state lifecycle that mirrors how organizations actually work:
- Draft — The user starts a booking request, filling in the resource type, dates, times, and purpose. Nothing is reserved yet.
- Submitted — The user submits the request. The system validates availability and routes it for approval if required.
- Approved — A manager or designated approver reviews and approves the booking. The resource is now tentatively reserved.
- Assigned — The system (or an administrator) assigns a specific resource from the pool. The resource is now locked for that time window.
- In Use — The user checks out the resource. The clock starts on utilization tracking.
- Completed — The user returns the resource via check-in. Condition is recorded, utilization is logged, and the resource is released back to the pool.
Each state transition is guarded by validation rules. A booking cannot jump from Draft to In Use, nor can it be approved if the requested time window overlaps with an existing assignment. These guards are enforced at the domain level, not just the UI, ensuring data integrity regardless of how the system is accessed.
Booking Creation with Resource Availability
When a user creates a booking, the system checks resource availability in real time. Here is the core pattern for creating a booking with an availability guard:
public async Task<BookingResult> CreateBookingAsync(CreateBookingCommand cmd)
{
var overlapping = await _db.Bookings
.Where(b => b.ResourceId == cmd.ResourceId)
.Where(b => b.Status != BookingStatus.Draft)
.Where(b => b.Status != BookingStatus.Completed)
.Where(b => b.StartTime < cmd.EndTime && b.EndTime > cmd.StartTime)
.AnyAsync();
if (overlapping)
return BookingResult.Unavailable("Resource is already booked for this time window.");
var booking = new Booking
{
ResourceId = cmd.ResourceId,
RequestedById = cmd.UserId,
StartTime = cmd.StartTime,
EndTime = cmd.EndTime,
Purpose = cmd.Purpose,
Status = BookingStatus.Submitted
};
_db.Bookings.Add(booking);
await _db.SaveChangesAsync();
return BookingResult.Created(booking);
}The overlap query excludes Draft and Completed bookings — only active and upcoming reservations block availability. This means cancelled drafts never hold resources hostage, and completed bookings don't interfere with future scheduling.
Check-In and Check-Out Process
The check-out process transitions a booking from Assigned to In Use. The user confirms they are taking physical possession of the resource. The system records the exact timestamp, and if the resource has condition-tracking enabled, prompts for a pre-use condition photo or note. For vehicles, this might include the current odometer reading and fuel level.
Check-in reverses the process. The user returns the resource, records the post-use condition, and the system captures the return timestamp. Any discrepancies between the before and after condition are flagged for review. This creates an accountability chain: if a laptop comes back with a cracked screen, the damage is documented and attributed to the right booking. The resource can also be flagged as needing maintenance before it can be booked again.
Utilization Reports and Analytics
Data-driven decisions require visibility. MVC Booking Manager includes built-in utilization dashboards that answer questions like: which resources are booked the most? Which departments are the heaviest users? What percentage of the fleet sits idle on a typical Tuesday? Reports can be filtered by date range, resource type, department, or individual resource. The system calculates utilization rate as booked hours divided by available hours, giving managers a clear picture of whether they have too many or too few of each resource type.
Trend reports show utilization over time, helping organizations plan for seasonal demand — more vehicles during conference season, more meeting rooms during quarterly planning cycles. Export options include CSV for further analysis in Excel or BI tools.
Approval Workflow Configuration
Not every booking needs approval. MVC Booking Manager lets you configure approval rules per resource type, resource pool, or even individual resource. A high-value item like a company truck might always require manager approval, while a meeting room booking under two hours could be auto-approved. Approval chains can be single-step (manager only) or multi-step (manager then department head). Approvers receive notifications and can approve or reject directly from the dashboard with optional comments explaining their decision.
Key Takeaways
- Organization hierarchy drives booking context and approval routing automatically
- Resource catalog supports vehicles, rooms, equipment, and custom types with pools for auto-assignment
- Six-state booking lifecycle enforces real-world workflows from draft to completion
- Check-in/check-out with condition tracking builds an accountability chain for every resource
- Utilization reports give managers data to optimize resource allocation and reduce idle time
FAQ
What types of resources can be booked? The system ships with Vehicle, Room, and Equipment types out of the box, and you can define custom resource types with their own attributes. Each type supports pools so you can manage fleets and collections, not just individual items.
How does check-in/check-out work? Check-out records when a user takes possession of a resource, optionally capturing condition photos and notes. Check-in records the return, compares condition against the pre-use state, and flags discrepancies. Both timestamps feed into utilization reports.
Can bookings be approved by managers? Yes. Approval workflows are configurable per resource type or pool. Single-step and multi-step approval chains are supported, and approvers can act directly from the dashboard with full context on the booking request.