Project-Based Engagement Delivery Playbook
The Complete Operational System for Scoping, Staffing, Managing, and Closing Fixed-Scope Consulting Engagements That Deliver on Time, on Budget, and on Promise
The project-based engagement has a specific failure mode that differs from every other type of consulting work.
In time-and-materials work, scope expansion is a billing conversation. In advisory retainers, the service is defined relationally rather than deliverable-specifically. In project-based work, the scope is fixed, the price is fixed, the timeline is fixed, and the risk of everything between the signature and the final delivery is borne by the consulting firm.
The fixed-price project engagement that goes wrong does not go wrong because the consultant was incompetent — it goes wrong because the scope was under-specified at the outset, because the timeline did not account for client delays that were predictable, because the change management process for scope modifications was not established at the beginning of the engagement, or because the staffing plan assumed more efficiency than the actual work required.
All of these failures are foreseeable. All of them are preventable with the right processes applied at the right points in the engagement lifecycle.
The Project-Based Engagement Delivery Playbook from Jeruk Purut Pro is the operational system for every stage of the fixed-scope engagement — from pre-proposal scoping through final delivery and close.
📥 Jeruk Purut Pro exclusive. Instant digital download.
THE PLAYBOOK — PHASE BY PHASE
PHASE ONE: PRE-PROPOSAL SCOPING AND RISK ASSESSMENT
The Scope Definition Protocol
The most consequential work in a fixed-price engagement happens before the proposal is written. The scope definition protocol is the structured process for understanding the full scope of work required before committing to deliver it at a fixed price.
The protocol covers seven scoping dimensions:
The deliverable specification: The precise description of every deliverable the engagement will produce — not “a strategic plan” but “a strategic plan document of approximately forty to sixty pages, organized in five sections [specified], including a three-year financial model [specified format], validated with client leadership in two rounds of review, and presented to the board in a formal presentation [specified format and duration].” The specification that means both parties understand what “done” means before the engagement begins.
The data and access requirements: Every data source required for the analytical work, confirmed as accessible before the price is committed. The engagement that is priced on the assumption of access to management accounts, operational data, and customer survey results that are ultimately unavailable or available only in a form requiring significant additional work to use is an engagement that will overrun budget before the second milestone.
The client contribution requirements: The specific work the client must perform for the engagement to succeed — the time commitment from named client-side participants, the data they must provide and the timeline for provision, the decisions they must make at specified milestones, and the internal communication they must conduct to support the engagement. Specified and agreed before the contract is signed, not assumed and hoped for after it is.
The dependency mapping: The external dependencies that could delay the engagement timeline — the third-party data, the regulatory approvals, the technology system access, the board approval cycles. Each dependency mapped, the probability of the dependency becoming a delay estimated, and the contract language addressing delay rights and remedies drafted.
The stakeholder complexity assessment: The number and diversity of client-side stakeholders whose input, approval, or alignment is required for the engagement to succeed, and the assessment of the current alignment level among those stakeholders. The engagement priced on an assumption of client-side alignment that does not yet exist is an engagement that will require significant additional facilitation investment that the fixed price does not cover.
The novelty assessment: The extent to which this engagement type is familiar from prior comparable engagements versus novel in ways that create estimation uncertainty. The honest estimation of the percentage of the engagement scope that falls outside the consultant’s direct prior experience, and the risk adjustment applied to the estimate to account for that uncertainty.
The client readiness assessment: The evaluation of the client organization’s readiness to engage productively with the engagement process — the senior sponsor’s active commitment (not nominal support but actual engagement), the internal team’s capacity to contribute, and the organizational culture’s receptivity to the type of work the engagement will require. The engagement that is technically within scope but requires a client organization that is not ready to participate effectively is an engagement that will produce a technically correct deliverable that has no impact — and a client relationship that deteriorates as the consultant and client become frustrated with each other. ⚙️
The Proposal Risk Pricing Framework
The method for converting the scoping assessment into a proposal price that reflects the actual risk profile of the engagement: the base estimate (the effort required if all scoping assumptions are correct), the risk additions by dimension (the additional margin applied for each risk factor identified in the scoping assessment), and the contract terms that allocate specific risks to the client rather than absorbing them entirely in the price.
The framework produces a price that is defensible in commercial negotiation, covers the risk actually present in the engagement, and does not require scope reduction to be profitable when the risks materialize.
PHASE TWO: THE ENGAGEMENT LAUNCH SYSTEM
The Kickoff Architecture
The engagement kickoff is the most underutilized opportunity in project-based consulting. The kickoff that simply introduces the team and reviews the project plan accomplishes a fraction of what is available in the first intensive engagement with the client. The kickoff architecture covers:
The alignment session: The structured conversation at kickoff that confirms alignment between the consultant’s understanding of the engagement scope and the client’s understanding — the divergences surfaced and resolved before they become mid-engagement conflicts.
The success definition session: The conversation that establishes what the client actually means by a successful engagement — the outcomes they hope to achieve, the criteria against which they will evaluate the work, and the things that would make them feel the engagement was not worth the investment. The success definition that may be different from the proposal’s scope definition and that, where different, must be reconciled before delivery begins.
The working protocol establishment: The agreement on how the engagement will operate — the communication frequency and format, the decision escalation process, the document management approach, the meeting structure, and the expectations for client responsiveness to requests. The working protocols established at kickoff are the reference point for managing client behavior throughout the engagement.
The risk disclosure conversation: The explicit conversation with the client about the risks identified in the scoping assessment — the dependencies that could create delays, the assumptions that the project plan is built on, and the client behaviors that are required for the engagement to stay on schedule. The conversation that prevents the client from being surprised by a risk materializing that the consultant knew was present from day one. 🚀
The Engagement Governance Structure
The governance framework that manages the engagement from kickoff through close: the project governance document (the reference document that specifies the engagement scope, the timeline, the deliverables, the decision rights, the change management process, and the escalation process), the meeting rhythm (the frequency and format of progress meetings, the agenda structure for each meeting type, and the decision-making authority present at each meeting), and the reporting framework (the format and frequency of written progress reports and the dashboard that gives the client real-time visibility into project status).
PHASE THREE: THE IN-ENGAGEMENT MANAGEMENT SYSTEM
The Scope and Budget Tracking System
The real-time monitoring of engagement progress against the plan: the budget burn rate tracking (the weekly comparison of hours or cost incurred against the plan, with the forecast-to-complete updated weekly), the milestone progress tracking (the status of each milestone against the planned completion date), and the scope change log (the record of every scope modification — the requests made, the decisions reached, and the commercial treatment of each modification).
The early warning indicators: the budget burn rate exceeding the planned rate before the engagement is proportionally complete (the indicator that the engagement will overrun budget if the trend continues), the milestone slipping by more than one week without a clear recovery plan (the indicator that the timeline is at risk), and the scope change log accumulating volume that is not being commercially addressed (the indicator that the engagement is expanding without corresponding fee adjustment). 📊
The Change Management Protocol
The structured process for managing scope change requests — the most common source of project-based engagement profit deterioration:
The change identification step: The discipline of identifying scope changes in real time rather than absorbing them as “being helpful” and then discovering at the end of the engagement that the budget has been exceeded by the accumulated weight of small additions. Every request for something that is not explicitly within the agreed scope is identified as a potential scope change at the time it is requested.
The assessment step: The analysis of each potential scope change — the additional effort required, the impact on the timeline, and the impact on other workstreams.
The commercial decision step: The determination of whether the scope change is within the contingency already priced into the engagement, requires a formal change order with additional fee, or can be accommodated through a scope substitution (removing something from the current scope to accommodate the addition without additional fee).
The documentation step: Every scope change decision documented in the scope change log regardless of the commercial treatment — the record that prevents post-engagement disputes about what was agreed and what was delivered.
PHASE FOUR: THE ENGAGEMENT CLOSE AND TRANSITION SYSTEM
The Delivery Quality Assurance Protocol
The structured review process applied to every engagement deliverable before client submission: the technical accuracy review (the validation of every analytical conclusion and data representation), the scope completeness review (the confirmation that every element of the agreed deliverable specification has been addressed), the communication quality review (the assessment of the document’s clarity, organization, and professional presentation), and the strategic coherence review (the confirmation that the conclusions and recommendations are internally consistent and appropriate to the client’s context and capacity).
The Client Acceptance Protocol
The process for formally completing the engagement and establishing client acceptance of the deliverables: the formal delivery meeting (the structured presentation and review of final deliverables), the acceptance period (the agreed period during which the client reviews the deliverables and raises any completion concerns), the snag list management (the structured process for addressing any reasonable concerns raised during the acceptance period), and the formal acceptance confirmation (the written acknowledgment that the deliverables have been accepted and the engagement is complete).
The client acceptance protocol that ensures the engagement close is clean — no lingering ambiguity about whether the work is complete, no invoices contested because the acceptance was not formally established. 🏁
The Knowledge Capture and Transition Brief
At the close of every project-based engagement: the knowledge capture process (the engagement debrief feeding the knowledge base described in the Knowledge Base product above), the client transition brief (the document provided to the client that gives them the information needed to continue the work internally — the reference guide that demonstrates the engagement’s value continues beyond the delivery date), and the post-engagement relationship plan (the three to six month plan for maintaining the client relationship through the natural gap between engagement close and the next engagement opportunity).
📂 COMPLETE JERUK PURUT PRO FILE SUITE
⚙️ Complete Project-Based Engagement Delivery Playbook PDF | 📋 Pre-Proposal Scoping Protocol Template — all seven dimensions (editable) | 💰 Proposal Risk Pricing Calculator (Excel + Google Sheets) | 🚀 Engagement Kickoff Architecture Agenda Template (editable) | 📜 Project Governance Document Template (editable) | 📊 Budget and Scope Tracking Dashboard (Excel + Google Sheets) | 🔄 Change Management Protocol and Log Template (editable) | ✅ Delivery Quality Assurance Checklist (editable) | 🏁 Client Acceptance Protocol Template (editable) | 📖 Client Transition Brief Template (editable)
100% digital. Instant download from Jeruk Purut Pro. The operational system for the fixed-scope engagement that delivers on its promises.
Reviews
There are no reviews yet.