Engagements

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 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.

On project completion, PM closes open project tasks, moves Project to Status: Closed, resolves open Issues and Risks, finalizes lessons-learned, and triggers final Invoice + final revenue recognition. Open resource assignments move to Rolled Off and the consultants become bench or roll onto their next engagement. Client completes a final project status report acknowledgement.

An engagement can begin from a confirmed CRM opportunity and later need a revised delivery date or additional scope. Keep source opportunity with the project so the handoff can be retried without creating a second engagement. The project manager reviews the resulting client, practice, legal entity, billing policy and baseline before work becomes active.

A later request to extend delivery should identify which phases and tasks are affected. Record the proposal in change orders with its amount, hours and date implications. Keep the original baseline available while the request waits for the applicable internal decision and client acceptance. A comment in a status report cannot apply the contract change.

At close, distinguish completed delivery from outstanding obligations. A project may have no open tasks while a client decision, supplier invoice or financial acknowledgment remains unresolved. Record the reviewed close plan and the owner of each remaining exception. Releasing resource assignments does not erase their historical cost and allocation context.

• My Projects — Review owned engagements, delivery dates and current project health.