Purpose: This article explains how Resource Requirements work in Administrate, how they are defined on Course Templates, and how they are used during Event planning and delivery.
Resource Requirements define the resources needed to deliver a course. They act as planning guidance rather than enforced constraints, helping administrators ensure the correct equipment, rooms, or materials are available when scheduling Events.
Contents
- What are Resource Requirements?
- Where Resource Requirements are defined
- How requirements flow to Events
- Resource Requirements table (Event Outline)
- Resource Requirements vs Resource Bookings
- Operational behavior
- Common scenarios
What are Resource Requirements?
Resource Requirements define the type and quantity of resources needed to deliver a course.
Examples include:
- 1 instructor
- 1 training room
- 10 laptops
- 1 projector per session
These requirements describe what is needed for delivery, but they do not allocate specific resources.
Where Resource Requirements are defined
Resource Requirements are configured on the Course Template under the Resources tab.
When defining requirements, you specify:
- resource type
- required quantity
- whether the requirement applies to all sessions or specific sessions
These requirements become part of the reusable course design and are inherited by Events created from the template.
How requirements flow to Events
When an Event is created from a Course Template, its Resource Requirements are carried into the Event structure.
Requirements are then evaluated at the session level within the Event.
Administrators use the Event Outline tab to assign actual resources that fulfill those requirements.
Resource Requirements table (Event Outline)
On the Event Outline tab, Administrate displays a Resource Requirements table when requirements are not fully met.
This table shows:
- resource type
- required quantity
- booked quantity
This allows you to quickly identify gaps between what is required and what has been scheduled.
Once all requirements are satisfied, the table may automatically disappear. It can typically be toggled back on if needed.
Resource Requirements vs Resource Bookings
It is important to distinguish between requirements and bookings:
| Concept | Description |
|---|---|
| Resource Requirement | Defines what is needed (type and quantity) |
| Resource Booking | Assigns a specific resource to a session or event |
Requirements describe expectations. Bookings fulfill those expectations.
Operational behavior
Resource Requirements are a guidance system, not an enforced rule.
- Events can still be created without fulfilling all requirements
- The system highlights gaps rather than blocking progress
- Conflict warnings are shown when overbooking resources
This allows flexibility while still supporting accurate planning.
Common scenarios
- Requirements are defined but no resources appear booked: Requirements do not automatically assign resources. You must book them manually.
- The requirements table disappears: This usually means all requirements have been satisfied.
- Resources are booked but requirements still show: The quantity or session coverage may not match the defined requirement.