Checks built in
What Resource Planning System enforces at each step.
- Self-service cannot verify its own credentials.
- Mandatory requirements remain eligibility gates.
- Restrict personal rates and employment context.
Prepare verified profiles before comparing people against project requirements.
When Core HR creates an Employee marked as billable / chargeable, the Core HR onboarding handoff writes a draft Resources row with Employee, full name, Email, Practice, primary role, resource type (FTE / Contractor / Vendor / Intern), Location, home state, base hours per week, manager of record, and start date. Resource Manager reviews delivery attributes and the permitted bill rate; Finance supplies the protected cost rate. The authorized onboarding service flips Status: Pending start → Active on the start date. Vendor / Contractor Resources without an Employee record leave resource employee null and carry the same delivery attributes.
The new Resource fills in resource skills self-service — Skill, Proficiency 1-5, years of experience, last used at — and uploads skill certifications (certification name, Issuer, issued at, expires at, evidence URL). Manager (or Resource Manager) reviews and attests, flipping resource skill source: Self reported → manager attested and skill certification status: Pending verify → Active. Verified certifications can bump a related resource skills row to Source: Certification derived with the proficiency uplift the certification implies.
On request creation, the skill-match-suggester workflow runs the configured matching service to score every active Resource against the request skills (skill match, proficiency delta, capacity in window from weekly capacity, bill rate fit, Practice match, location preference) and writes the top 10 candidates as request suggestions rows (one per candidate, each with match score, skill match pct, proficiency delta, capacity fit pct, bill rate fit pct, and Rank). The Resource Manager reviews the suggestions on the request detail view, picks the right Resource, sets matched resource, and approves (Status: Pending approval → Approved) only after an atomic capacity recheck. Missing inputs block approval. Overcommit is rejected unless the practice explicitly permits it and an independent Resource Manager records the current conflict and reason. On reject, sets Status: Rejected with rejection reason; the Project Manager can revise and resubmit.
What Resource Planning System enforces at each step.
Start free, then use Proto to change fields, steps and approvals before your team goes live.