Scope Proposals

A scope proposal belongs to an engagement and an organization. It gives the team a separate record for a service line, revised scope, proposed fee and validity date. The proposal carries its own revision and moves from draft to submitted, then to an approved or rejected decision. Completed is available after an approved proposal is dealt with. The parent engagement remains the point of reference for the client commitment and the delivery work that follows.

The reviewer decision is a distinct record under the parent engagement. It identifies a source revision, reviewer, decision, date and reason. Read it alongside the proposal revision and status when terms change between submission and acceptance. A returned decision asks the owner to revise and submit again; a rejection records a different outcome. Keep the reviewed revision and decision context clear when several proposals belong to one engagement.

• Owner preparation. Engagement Owner sets the proposed fee, scope revision, service line and validity date against the parent engagement.
• Submitted review. Independent Reviewer reads the submitted proposal and the parent engagement before recording a decision and reason.
• Accepted change. The owner reconciles an approved proposal with the engagement’s agreed fee and scope revision.

Decide how much detail belongs in the scope revision text and which supporting files belong in the engagement’s attachments. Agree whether a proposal that passes its validity date must be revised before approval. Name the reviewer selection rule so the person delivering the engagement does not make the independent decision. Define who updates the parent engagement after an approved proposal; the proposal record alone should not leave the contracted fee ambiguous.

Use the revision field with care. When an owner changes price or scope after submission, the reviewer needs a new revision to assess. Keep the reason on every decision precise enough for the owner to act on it. The service line can help an operations lead compare proposed changes across consulting practices, but it should use a shared naming convention.

A manufacturing client asks to add a second site to its operations assessment. Engagement Owner records the new scope, a proposed fee and a validity date on a proposal linked to the existing engagement. Independent Reviewer sees the proposal in the review queue, checks the parent’s agreed fee and scope, then records an approval or return against the current revision. If the reviewer returns it, the owner revises the proposal and submits it again. If approved, the owner updates the engagement’s contracted scope details before the team delivers the additional work.

Run a second case where a proposed fee changes after the reviewer has read it. The earlier decision retains its recorded source revision, and the owner should request a new review for the changed terms.

• Proposal Review Queue — Submitted changes with scope, fee, revision and validity date.
• Proposal Status Board — Draft, submitted, approved and rejected changes in one working list.
• Approved Proposals — Decisions ready to reconcile with their parent engagements.

Use proposal review for the decision path, then engagement review to acceptance for delivery and final acceptance.