Change Orders Deliverable QC and Steering Committees

Change Order Process

A change order (CO) is the formal mechanism for modifying scope, schedule, or budget after the original contract is executed.

Scope Creep vs Legitimate Change

Scenario	Classification	Response
Client asks for analysis that’s clearly within the charter	In-scope	Proceed; no CO needed
Client asks for adjacent analysis not in charter but small effort	Gray zone	Discretionary; document in meeting notes; watch for pattern
Client asks for a new deliverable or work stream	Out-of-scope	Formal CO required
Original requirement was unclear and now needs significant rework	Ambiguity	Discuss with client; may share cost depending on who owned the ambiguity

Scope creep is revenue-negative on fixed-fee engagements. Each uncontrolled out-of-scope request eats margin directly. On T&M, scope expansion is revenue-positive — but still requires documentation to maintain professional discipline.

CO Workflow

1. Request: Client or consultant identifies out-of-scope work
2. Impact assessment: Estimate additional hours, duration, and cost for the new work
3. Presentation to client: Present the CO with rationale, hours, cost, and schedule impact
4. Approval: Client sponsor signs the CO (or declines)
5. Baseline update: Project schedule, budget, and scope baseline updated to reflect approved CO
6. Execute: Work proceeds under the updated baseline

Rule: Do not begin out-of-scope work until the CO is signed. “We’ll get to the paperwork later” is how margin disappears.

---

Deliverable Quality Control

Quality control for consulting deliverables prevents the professional embarrassment of errors reaching the client — typos, broken formulas, inconsistent data, unsupported claims.

QC Hierarchy

Level	Check	Who
Self-review	Author checks own work — logic, calculations, formatting	Analyst/consultant
Peer review	Second person checks: numbers, logic, internal consistency	Peer analyst
Structured walkthrough	Brief verbal walkthrough with reviewer who asks probing questions	Engagement manager
Client review draft	Internal final before sending to client; check executive summary matches body	Engagement manager or lead
Client review cycle	Client provides feedback; consultant resolves open items	Both

Common QC Failure Points in Logistics Consulting

• Excel formulas broken or hard-coded: When numbers are pasted as values or formulas reference wrong cells, the model produces wrong answers. QC must include formula audit, not just output review.
• Inconsistent numbers: Executive summary says X, appendix table says X+5%. Numbers must reconcile across a deliverable and across deliverables.
• Unsupported benchmarks: “Industry standard is 15 picks/hour” — source? Unattributed claims invite pushback and erode credibility.
• Jargon mismatch: Deliverable uses industry terms the client team doesn’t use. Always calibrate terminology to the client’s vocabulary.

---

RAG Status Reporting

Red-Amber-Green (RAG) status is the standard governance reporting shorthand for project health.

Status	Meaning	Action Required
Green	On track; no issues	Report as planned
Amber	At risk; issue identified but not yet impacting	Flag to stakeholders; present mitigation
Red	Off track; issue impacting scope, schedule, or budget	Escalate; present recovery plan

RAG discipline: Amber must trigger an action plan, not just documentation. Red must have an owner and a recovery timeline. Green does not mean “I checked everything is fine” — it means “I have evidence everything is fine.”

---

Steering Committee Design

The steering committee is the governance body that oversees the engagement at the executive level. Its purpose is to make decisions that the engagement team cannot — budget changes, organizational decisions, strategic pivots.

Cadence and Structure

Element	Recommendation
Frequency	Bi-weekly minimum; weekly for fast-paced or high-risk engagements
Duration	60–90 minutes
Attendees	Client sponsor + key stakeholders; engagement lead + relevant team members
Chair	Client sponsor (they own the decisions)
Agenda ownership	Consultant prepares and sends agenda 48+ hours in advance

Standard Agenda Structure

1. Status update (10 min) — RAG dashboard; completed deliverables; upcoming milestones
2. Issues and risks (15 min) — open items requiring steering committee decision or awareness
3. Decision items (20 min) — items requiring executive approval
4. Upcoming period preview (10 min) — what happens next; client commitments required
5. AOB (5 min)

Decision Log

Maintain a running log of all decisions made in steering committee and other meetings:

Decision #	Date	Decision Made	Made By	Rationale	Impact
D-001	2026-05-15	Exclude site 3 from network model	Client CFO	Site under evaluation for closure	Reduces model scope by ~15%

Decision log function: Prevents the “but I thought we decided…” conversation. Also provides an audit trail if the engagement is later disputed.

Action Item Log

Companion to the decision log. Tracks open actions regardless of meeting source.

#	Action	Owner	Due Date	Status
A-007	Provide WMS extract for sites 1-2	Client IT (J. Smith)	2026-05-10	Open
A-008	Draft receiving process SOP for review	Consultant (R. Jones)	2026-05-12	Complete

Review the action item log at every steering committee — outstanding client actions are the most common reason consultants fall behind schedule.