Checks built in
What Project Management PSA enforces at each step.
- Preserve the source opportunity identity across retries.
- Reject conflicting or out-of-scope assignments.
- Keep project, phase and task references consistent.
Turn a confirmed client opportunity into a scoped project with reviewed staffing.
When a CRM Opportunity reaches closed won, the integration fires a project-creation handoff. The PM selects a project template and a billing policy, confirms Client/Program/Practice/Office, sets contract value, billing model (TM / fixed fee / Milestone / Retainer), start date, end date, and budget hours/budget cost. Source opportunity is stored for traceback. The Project lands in Status: Planning.
PM creates resource requests for each Role needed, with required skills, dates, and allocation %. Requests go to the Resource Manager, who searches available Consultants matching Role + Skills + utilization target, proposes candidates, and on confirmation creates resource assignments (Status: Soft → Confirmed → Active). Assignments snapshot the effective bill rate. Where internal capacity is short, a subcontractor PO is issued (routed for approval per firm’s delegation-of-authority matrix) and the sub is added as a resource assignment with Subcontractor set.
PM populates project phases (seeded from project template), project tasks, and task dependencies. Milestone amounts are set on phases if billing model = Milestone. Initial risk register is established; baseline is locked. Project advances to Status: Active at kickoff. Kickoff project status report goes out via client portal.
What Project Management PSA enforces at each step.
Start free, then use Proto to change fields, steps and approvals before your team goes live.