The tables behind Resource Planning System

The person-level resource record — one row per billable or chargeable person on the delivery roster. References the canonical Employee in Core HR but extends with delivery attributes (Practice, Role, resource type, bill rate, cost rate). Pay Runs and HRIS lifecycle live elsewhere; this row exists so staffing has a working record.

Read-only identity mirror from Core HR; employment records and payroll remain owned by HR.

The catalog of named skills used to describe what a Resource can do and what a resource request needs. Practice-tagged for search-narrowing but not Practice-scoped — a single Skill (e.g. Python) crosses Practices.

The Resource × Skill matrix with proficiency, last-used, and a self-or-manager attestation. The grain that powers skill-match-suggester and the Skill Inventory report.

Formal certifications backing a resource skills row — the issuer, the certification number, the issue and expiry dates. Drives the certifications-expiring report and the Source: CertificationDerived proficiency bumps.

Per-Resource per-Week capacity grid. Computed nightly by capacity-recompute from BaseHoursPerWeek - PTO hours - holidays. The denominator for utilization and the source of truth for “is this Resource available?”

Inbound feed from hrms-leave-attendance — approved leave and holidays per Resource per day, used by capacity-recompute to deduct PTO hours and holiday hours from weekly capacity. Read-only here; the source of truth lives in the leave app.

The staffing record — a Resource on a Project at a Role at an allocation percentage over a date span. Spawned from an approved resource request. The unit of capacity consumption.

Week-by-week allocation rows for an Assignment. Generated on approve; the granular hours that roll up into weekly capacity and Utilization. Reconciled to actuals from pm-time by time-sync-from-pm-time.

Demand from a Project — “we need a Senior Data Engineer with Snowflake + dbt at 50% from May 1 through July 31.” Routes to the matching Practice’s Resource Manager for approval and a match.

Required skills for a resource request with minimum proficiency. Drives skill-match-suggester scoring.

Top-N candidate Resources scored by skill-match-suggester for a resource request. One row per suggested Resource with the composite match score and component breakdown (skill match, proficiency delta, capacity fit, bill-rate fit) plus rank. The Resource Manager picks one of these to set ResourceRequests.MatchedResource.

Scoped delivery-project mirror used for staffing; tasks, delivery approvals and billing remain in the connected project app.

The staffing record — a Resource on a Project at a Role at an allocation percentage over a date span. Spawned from an approved resource request. The unit of capacity consumption.

Week-by-week allocation rows for an Assignment. Generated on approve; the granular hours that roll up into weekly capacity and Utilization. Reconciled to actuals from pm-time by time-sync-from-pm-time.

A formal swap mid-Assignment — Resource A rotates off, Resource B rotates in. Captures the from / to, the effective date, and the reason. The original Assignment goes Substituted; a new Assignment is created for the inbound Resource.

Demand from a Project — “we need a Senior Data Engineer with Snowflake + dbt at 50% from May 1 through July 31.” Routes to the matching Practice’s Resource Manager for approval and a match.

Versioned rate cards per Practice (and optionally per US region). A rate card has effective dates and a set of rate card rows. The active card on Assignments.StartDate prices the assignment.

Per-Role rate row inside a rate card. The lookup grain for pricing an Assignment.

The staffing record — a Resource on a Project at a Role at an allocation percentage over a date span. Spawned from an approved resource request. The unit of capacity consumption.

Week-by-week allocation rows for an Assignment. Generated on approve; the granular hours that roll up into weekly capacity and Utilization. Reconciled to actuals from pm-time by time-sync-from-pm-time.

Organizational practice unit — a Practice owns a set of Resources, Roles, and rate cards. Examples: Data Engineering, Cloud Infrastructure, Business Consulting, Design.

Immutable approved source-time observations for one assignment period; corrections retain source revision and reversal linkage.

Week-by-week allocation rows for an Assignment. Generated on approve; the granular hours that roll up into weekly capacity and Utilization. Reconciled to actuals from pm-time by time-sync-from-pm-time.

Per-Resource per-Period rollup of allocation, billable hours, and utilization percentage. Written weekly by utilization-rollup. The grain that backs the Utilization report and the executive dashboard.

Derived (workflow-written) row per Resource flagged as under-utilized over the next 4 weeks of forward bookings. Used for the bench digest and the bench-report. Refreshed weekly by bench-detection.

Per-Resource per-Week capacity grid. Computed nightly by capacity-recompute from BaseHoursPerWeek - PTO hours - holidays. The denominator for utilization and the source of truth for “is this Resource available?”

Generic role catalog — Senior Engineer, Tech Lead, Project Manager, Solution Architect — with a default bill rate that rate cards can override per Practice / region. Roles are the demand language: a resource request asks for a Role, not a person.