Resource Requests: Mastering Demand vs. Capacity
In a matrix organization, the most frequent point of failure is the "staffing gap"—the disconnect between what a Project Manager needs to hit a deadline and what a Team Manager can realistically provide.
The Resource Requests engine is more than a ticketing system; it is a Professional Staffing Workflow. It transforms staffing from an informal "email and chat" process into a formal, auditable contract between Project Managers and Resource Owners.
The Strategic Staffing Workflow
Professional staffing requires a hand-off of responsibility. Resource Management codifies this into a stateful workflow that ensures no request is lost and every assignment is validated against real capacity.
The "Staffing Contract" Lifecycle
- Demand Definition (PM): The Project Manager defines the specific skill profile, time window, and priority.
- Feasibility Analysis (TM): The Team Manager reviews the request against the team's actual availability (calendars, other project commitments).
- Resource Proposal (TM): The Team Manager proposes specific individuals and their allocation percentages.
- Contract Acceptance (PM): The Project Manager accepts the proposal. This "Acceptance" becomes the Staffing Baseline used to track actual worklogs against planned effort.
Governance: Roles and Access Control
To maintain integrity, the system implements a strict Separation of Concerns.
| Role | Governance Responsibility | Visibility & Authority |
|---|---|---|
| Project Manager | Demand Owner. Responsible for defining the need and accepting the final staffing plan. | Views requests for their projects. Can Create, Submit, Accept, and Cancel. |
| Team Manager | Capacity Owner. Responsible for protecting team health and ensuring feasible assignments. | Views requests for their teams. Can Assign, Send for Review, and Reject. |
| Instance Admin | Portfolio Governor. Ensures the staffing process is being followed across the organization. | Global visibility. Full override authority. |
The Power of the Capacity-Aware Timeline
The Timeline View is the primary diagnostic tool for Team Managers. It solves the "Over-Allocation" problem by integrating Real-Time Capacity Signals.
1. Precision Capacity Tracking
Unlike simple spreadsheets, the capacity view calculates availability with 1-minute precision, accounting for:
- Global & Team Calendars: Holidays and company-wide shutdowns.
- Individual Availability: Approved time-off and partial-time contracts.
- Cross-Project Load: Hours already committed to other parallel projects.
2. The "What-If" Assignment Mode
Team Managers can enter an interactive assignment mode where they can drag-and-drop resources into a request. As they do, the Remaining Capacity bars update instantly. This allows the manager to answer:
"If I assign Sarah to this project at 50%, who else on the team becomes overloaded?"
3. Managing the "Slippage" Risk
By visualizing requests as bars on a timeline, PMs and TMs can spot Temporal Bottlenecks—periods where too many projects demand the same skill set simultaneously—allowing them to shift project start dates before the conflict occurs.
Practitioner's Perspective: The Audit Trail & Actuals
🛡️ The Audit-Friendly History
In large portfolios, "Who promised what and when?" is a frequent point of contention. Every request in Resource Management maintains a Chronological Audit Log. This records every status change and every actor involved, transforming the staffing process from a "he-said-she-said" argument into a documented history of agreements.
📈 From "Accepted" to "Actual"
The true value of a Resource Request is realized in the Timesheets. Once a request is Accepted, the allocated hours become the Baseline. When resources log time in Jira, Resource Management compares the Actual Worklogs against the Accepted Request.
This allows PMOs to track "Staffing Variance":
- Under-utilization: We promised 20h/week, but only 10h were logged. Is the task easier than thought, or is the resource distracted?
- Over-utilization: We promised 20h/week, but 40h were logged. Is the scope creeping, or is the resource inefficient?
Workflow Status Reference
| Status | Governance State | Next Action |
|---|---|---|
| New | Draft / Internal Review | Submit to target team |
| Submitted | Demand Handoff | Assign resources or Reject |
| Resource Assigned | Proposed Staffing | Send for Review to PM |
| Review | PM Validation | Accept as contract or Reject |
| Accepted | Baseline Established | Move to execution (Jira tasks) |
| Rejected/Edited | Negotiation Phase | Modify and Resubmit |