In this template:
§1 Blank Requirements Matrix
Fill this matrix during the planning phase to guarantee alignment between project scope and operational capacity.
| ID | Resource | Quantity / Allocation | Assumptions | Comments |
|---|---|---|---|---|
| R-01 | ||||
| R-02 | ||||
| R-03 | ||||
| R-04 | ||||
| R-05 |
Date Prepared: _______________________
Project Title: _______________________
Contents
Project Title: _______________________
§2 Usage Guide
A well-documented resource matrix prevents scheduling bottlenecks and clarifies procurement boundaries early in a programme lifecycle. To optimise this template, apply the following standards when filling out each column:
- ID: Utilise a sequential numbering system (e.g., R-01, R-02) to allow traceability when porting data into scheduling tools or risk registers.
- Resource: Explicitly name the role, specific personnel (if known), software licence, or physical workspace required.
- Quantity / Allocation: Specify the exact burn rate (e.g., "50% allocation", "~60 hours", "3 server instances"). Avoid vague descriptors like "part-time".
- Assumptions: Document the prerequisites that make this resource viable, such as expected seniority levels, specific departmental approvals, or budget caps.
- Comments: Log constraints, holiday risks, interdependencies, or alternative fallbacks if the primary resource becomes unavailable.