Worked example 06 · Client communication & handoffs

The client is waiting.
So is your team.

A kickoff is useful only when the right information, decision authority and acceptance criteria reach the people doing the work.

$27,120

Potential net savings / year
After recurring control costs.

Research-based composite. Business figures, savings and risk ratings are modeled assumptions. Proposed controls have not been validated with a business.

The bottleneck

Where the work gets stuck.

The proposed bottleneck is the handoff from a client request to an executable, authorized decision. Information is incomplete, decision ownership is uncertain and the schedule does not show when a response becomes critical. A client portal alone would move the same unresolved questions into a different tool.

The proposed improvement

Change how the work moves.

Agree client requirements and decision authority at kickoff, set approval deadlines and verify handoffs and acceptance.

20 to 14Open decision queue · modeled

8 to 3Paid coordinator overtime hours / week · modeled

Read the business situation

Sales records the customer’s needs in email, the PM inherits a broad scope, and field teams discover missing operating requirements after mobilization. Different client contacts give conflicting direction. Approval requests lack a latest-response date or a named authorized decision maker. Crews return to completed work and the coordinator spends evenings reconciling messages. The issue is a shared process for reaching decisions, rather than simply sending more updates.

40 employees, four active commercial projects and 20 client decisions required per week. Fictional composite; quantities and outcomes are assumptions.

Follow the work.

Proposed workflow: make the next action and responsibility explicit.

01Structured kickoffRequirements + authority

02Complete requestOptions + impacts

03Decision gateApprove / hold / escalate

04Controlled handoffTeam acknowledges

05Verified acceptanceEvidence + follow-up

What needs to change

Kickoff acceptance checklistPM and authorized client contact agree requirements, exclusions, acceptance evidence, contact roles and response expectations. Carry unresolved items into a dated log.

Decision-ready requestsEach request includes the precise question, latest drawing reference, options, relevant cost/schedule effect, named reviewer and response need-by date. Technical alternatives require qualified review.

Escalation and release ruleReview approaching decisions daily. Escalate overdue critical items to the authorized backup; hold affected work and resequence approved work. Silence is never treated as consent.

Close the loopRecord the decision and authority, update scope and schedule, obtain field acknowledgment and review acceptance evidence with the client. Follow up after handover and adjust the process.

How to verify the bottleneck

Hypothesis	Evidence to inspect	Proposed test
Requests are incomplete	Audit 30 requests for scope, revision, options and an explicit decision.	Compare completion time for complete and incomplete requests.
Approval authority is uncertain	Compare client contacts with the contract and written delegation.	Ask client to nominate an authorized primary and backup.
The need-by date is invisible	Trace request, required decision date and affected work.	Pilot a decision log on one project and review overdue items daily.
Poor workmanship causes callbacks	Compare defect records with decision-related repeat visits.	Separate technical defects from client-information and authorization errors before selecting controls.

The capacity calculation

Measure	Calculation	Modeled implication
Decision workload	20 decision requests / week x 1.0 week average response	20 open decisions, assuming stable arrivals and completions
Proposed queue	20 requests / week x 0.7 week average response	14 open decisions; six fewer waiting
Coordinator overtime	8 less 3 paid hours / week	5 hours/week of payroll removed if verified
Field capacity	Avoid four repeat visits/month x two technicians x two hours	16 regular-time technician hours/month released; not monetized

Example: client decision and acceptance log

Decision / requirement	Need-by and owner	Release evidence
HVAC-17 / occupancy schedule for controls	Tuesday 2 PM / client facility manager	HOLD programming until written approved schedule; confirm technical implications
ELEC-09 / equipment location	Wednesday 10 AM / authorized client PM	Approved marked-up drawing; PM confirms installation team acknowledgment
CLOSE-04 / handover evidence	Before commissioning / contractor PM	Agreed test reports, manuals and training record; client acceptance status recorded

The implementation plan

Days 1–7PM + client contact

Audit 30 decisions and recent repeat visits; agree authority, communication route and acceptance evidence.

Evidence: Baseline queue, response times, verified contact/authority matrix and cause-coded costs.

Days 8–14PM + field lead

Pilot the request template and decision log on one project; hold unresolved affected work.

Evidence: Every critical request has a named approver, evidence and need-by date.

Days 15–30Operations manager

Review late decisions with client weekly; remove duplicate reporting and correct missing handoffs.

Evidence: Written decisions and field acknowledgment for all sampled releases.

Days 31–60PM + payroll

Compare matched project phases, verify invoice/payroll savings and follow up with client.

Evidence: Sustained cost reductions with comparable output, safety, quality and client response.

What to measure

Measure	Definition	Target	Owner / review
Decision completeness	Requests with scope, options, authority and need-by date / all requests	At least 95%	PM / weekly
Response time	Average business weeks from complete request to authorized response	1.0 to 0.7 weeks; track 90th percentile too	PM + client / weekly
Decision queue	Open decisions at end of each workday	20 to 14 average at stable workload	Coordinator / daily
Repeat visits	Client-information-related repeat visits with cause evidence	6 to 2 monthly	Field lead / monthly
Client acceptance	Milestones accepted with agreed evidence / milestones submitted	At least 95%; investigate rejection	PM + client / milestone

How to validate the result

Use four baseline weeks and a four-week pilot at comparable project phases. Confirm that the request arrival rate and technical complexity remain comparable. Reconcile reduced overtime to payroll and removed repeat-visit expenses to invoices. Record client response, field rework and acceptance quality so a faster process is not achieved by bypassing review.

Show the financial effect.

This models avoidable operating expenditure. Time released without a reduced payment is reported separately as capacity.

Financial line	USD
Coordinator overtime avoided	$12,000
Nonlabor repeat-visit cost avoided	$18,720
Gross annual benefit	$30,720
Recurring annual control cost	$3,600
Annual net run rate	$27,120
First-year net benefit	$16,600

What if the improvement is smaller?

Adjust the share of the modeled improvement achieved. Control and setup costs stay the same.

Modeled improvement achieved100%

ANNUAL NET ESTIMATE$27,120FIRST YEAR AFTER SETUP$16,600

First year: 10 benefit months, less the full setup allowance. Results are illustrative, not a guarantee.

Payroll savings require five fewer paid coordinator overtime hours per week with comparable workload and service. The repeat-visit allowance covers only incremental vehicle, travel and consumable costs; regular-time technician labor is excluded.

Baseline inputs and calculations

These inputs describe the 100% modeled case. The slider changes the share of the proposed improvement achieved.

Illustrative assumption	Value	Units
Coordinator overtime before	8	hours/week
Coordinator overtime after	3	hours/week
Avoidable overtime cost	50	USD/hour
Operating weeks	48	weeks/year
Repeat visits before	6	per month
Repeat visits after	2	per month
Nonlabor cost per repeat visit	390	USD/visit
Calendar months	12	months/year
Recurring control cost	300	USD/month
One-time implementation allowance	6,000	USD
Benefit months in first year	10	months

Coordinator overtime avoided: (8 - 3) x $50 x 48

Nonlabor repeat-visit cost avoided: (6 - 2) x $390 x 12

Gross annual benefit: Payroll + separate nonlabor travel costs

Recurring annual control cost: $300 x 12

Annual net run rate: Gross less recurring control cost

First-year net benefit: $27,120 x 10/12 - $6,000

What is included and excluded

No client lifetime value, additional sales, fixed payroll, faster payment or regular-time field capacity is monetized. No recovered change-order revenue is included, keeping this illustration distinct from Case 2. The setup allowance includes internal process design, client alignment and provisional support; it is not a LeanLine quotation.

The six-month dispute illustration is separate from the annual operating model. Remedial work, travel and administration may overlap annual benefits. Do not add the figures.

Make each risk actionable.

Eight modeled risks. Assessment horizon: one six-month project.

0Critical4High4Moderate0Low

Current ratings are scenario assumptions. Select a risk to see its mitigation, owner and response.

01AcceptanceUnagreed acceptance criteria lead the client to reject completed work, causing remedial costs and a dispute.12 · High

The risk: Unagreed acceptance criteria lead the client to reject completed work, causing remedial costs and a dispute.

Existing control · assumed: Broad scope and informal meeting notes.

Proposed mitigation: Define milestone acceptance evidence at kickoff; confirm changes through the authorized route.

Owner & timing: Project manager
Day 7 from pilot start.

Warning trigger: Client and PM disagree on acceptance criteria before the affected milestone.

Contingency: Hold the affected acceptance/release; convene authorized client, technical and contract reviewers.

How to verify: Signed criteria, milestone evidence and documented acceptance.

Review & status: Weekly during pilot; after every material change.
Proposed; unvalidated.

Modeled current: L3 × I4 = 12. Target: L2 × I4 = 8.

02AuthorityA client contact gives direction outside their authority, leading to disputed or reversed work.12 · High

The risk: A client contact gives direction outside their authority, leading to disputed or reversed work.

Existing control · assumed: The team accepts instructions from whoever is on site.

Proposed mitigation: Record client primary/backup authority and route cost, scope and technical changes to the correct approver.

Owner & timing: Account lead
Before pilot.

Warning trigger: Direction comes from a contact absent from the authority matrix.

Contingency: Pause the affected change; seek confirmation from the authorized representative.

How to verify: Authority matrix and approval records matched to sampled decisions.

Review & status: Weekly during pilot; after every material change.
Proposed; unvalidated.

Modeled current: L4 × I3 = 12. Target: L2 × I3 = 6.

03Response delayAn overdue client decision blocks critical work and triggers recovery overtime.12 · High

The risk: An overdue client decision blocks critical work and triggers recovery overtime.

Existing control · assumed: PM chases requests by email.

Proposed mitigation: Use need-by dates, consequence summaries and escalation to authorized backups before the critical window.

Owner & timing: Project manager
Day 10 from pilot start.

Warning trigger: A critical response is overdue or within two working days of need-by with no commitment.

Contingency: Resequence independent approved work; document impacts and agree a revised plan.

How to verify: Request timestamps, escalation log and actual released-work records.

Review & status: Weekly during pilot; after every material change.
Proposed; unvalidated.

Modeled current: L4 × I3 = 12. Target: L2 × I3 = 6.

04Scope controlA client requirement changes after approval without a revised price or schedule, eroding margin.12 · High

The risk: A client requirement changes after approval without a revised price or schedule, eroding margin.

Existing control · assumed: Informal messages supplement the original scope.

Proposed mitigation: Baseline requirements and route deviations through the existing change-control process before release.

Owner & timing: Commercial manager
Day 10 from pilot start.

Warning trigger: A requested change differs from the approved scope or drawing revision.

Contingency: Hold the changed scope; confirm authorized direction and commercial treatment.

How to verify: Baseline, deviation record and authorized change disposition.

Review & status: Weekly during pilot; after every material change.
Proposed; unvalidated.

Modeled current: L3 × I4 = 12. Target: L2 × I4 = 8.

05Safety / technical Specialist reviewPressure to satisfy the client causes the team to bypass a required technical review or safety authorization.10 · Moderate

The risk: Pressure to satisfy the client causes the team to bypass a required technical review or safety authorization.

Existing control · assumed: Routine safety and engineering review assumed.

Proposed mitigation: Keep engineering, inspection and safe-work approvals independent of commercial response deadlines.

Owner & timing: Qualified technical / safety lead
Before pilot.

Warning trigger: A requested decision affects safety or regulated technical requirements without qualified approval.

Contingency: Stop affected work; obtain the required specialist authorization before restart.

How to verify: Independent technical/safety review and restart authorization.

Review & status: Weekly during pilot; after every material change.
Proposed; unvalidated.

Modeled current: L2 × I5 = 10. Target: L1 × I5 = 5. Impact 5 requires specialist review regardless of total score.

06Information controlIncorrect recipients or stale attachments expose client information or release the wrong requirement.9 · Moderate

The risk: Incorrect recipients or stale attachments expose client information or release the wrong requirement.

Existing control · assumed: Email threads and local files.

Proposed mitigation: Use one controlled record with revision references, role-based access and recipient checks.

Owner & timing: Project coordinator
Day 14 from pilot start.

Warning trigger: Conflicting revision or unauthorized recipient found in an audit.

Contingency: Restrict affected access; correct the issued record and notify responsible parties per the response procedure.

How to verify: Access review and sampled current-revision handoffs.

Review & status: Weekly during pilot; after every material change.
Proposed; unvalidated.

Modeled current: L3 × I3 = 9. Target: L2 × I3 = 6.

07Client adoptionExcessive approval requests burden the client and worsen response times.8 · Moderate

The risk: Excessive approval requests burden the client and worsen response times.

Existing control · assumed: Many overlapping emails and meetings.

Proposed mitigation: Agree one communication route; consolidate routine decisions and reserve escalation for consequential items.

Owner & timing: Account lead
Day 14 from pilot start.

Warning trigger: Client response time worsens for two reviews or duplicate requests recur.

Contingency: Review the process jointly, simplify the template and agree realistic response windows.

How to verify: Client feedback, request completeness and response-time trend.

Review & status: Weekly during pilot; after every material change.
Proposed; unvalidated.

Modeled current: L4 × I2 = 8. Target: L2 × I2 = 4.

08MeasurementLower project activity is credited as savings although cost per completed milestone does not improve.9 · Moderate

The risk: Lower project activity is credited as savings although cost per completed milestone does not improve.

Existing control · assumed: Monthly totals without cause or volume matching.

Proposed mitigation: Compare similar phases and request volumes; reconcile actual payroll and separate nonlabor invoices.

Owner & timing: Operations analyst
Day 30 from pilot start.

Warning trigger: Output or complexity differs by more than 10% between baseline and pilot.

Contingency: Extend or rematch the comparison; report unvalidated benefits as assumptions.

How to verify: Matched cohort, payroll reconciliation and cause-coded invoice audit.

Review & status: Weekly during pilot; after every material change.
Proposed; unvalidated.

Modeled current: L3 × I3 = 9. Target: L2 × I2 = 4.

View the risk map

Likelihood ↑

Impact increases →

Each number matches a risk in the register. Select an occupied cell to open a risk.

Higher likelihood and impact move a risk toward the top right. The Target view shows conditional ratings after the proposed controls.

Where several risks share a cell, it opens the first listed risk. All remain available in the register above.

What could one risk cost?

One client acceptance dispute on a six-month project requires additional work and administration.

Scenario	Probability × event loss	Expected loss
Before	30% × $30,000	$9,000
With proposed controls	15% × $30,000	$4,500
Expected-loss reduction	Before less after	$4,500
Separate mitigation cost	Over this risk horizon	$1,500
Net modeled risk benefit	Reduction less mitigation cost	$3,000

The assumed $30,000 event loss comprises $18,000 incremental remedial work and travel plus $12,000 claim administration and specialist review. These are hypothetical financial exposures; probabilities are subjective and uncalibrated. Potential safety harm is not monetized.

The six-month dispute illustration is separate from the annual operating model. Remedial work, travel and administration may overlap annual benefits. Do not add the figures.

How the ratings work

Score = likelihood × impact, each rated from 1 to 5. Scores 1–5 are Low, 6–11 Moderate, 12–19 High and 20–25 Critical. These are scenario judgments over the stated assessment horizon.

Likelihood: 1 below 5%; 2 from 5% to below 20%; 3 from 20% to below 40%; 4 from 40% to below 70%; 5 at least 70%. Impact: 1 below $1,000; 2 below $5,000; 3 below $20,000; 4 below $75,000; 5 at least $75,000 or potentially severe safety consequences. Impact-5 safety or technical issues require specialist review regardless of score.

Research sources & assumptions

What’s your process for dealing with incomplete construction documents? ↗Reddit · r/Construction contributorsPublic thread opened. Anonymous reports; company conditions and outcomes are not verified.
Clients getting more unreasonable? ↗Reddit · r/Construction contributorsIndexed original post reviewed. One perspective; the client account and underlying causes are not independently verified.
Sample Approval Protects Construction Projects ↗LinkedIn · Hamid NawazPublic authored post opened. Practitioner commentary; no independently verified savings or causal evaluation.
Project Handover Requirements Beyond Completion ↗LinkedIn · The Measuring CompanyPublic authored post opened. Commercial practitioner commentary; requirements vary by contract and jurisdiction.

Public discussions informed the problem selection. LeanLine Advisory developed the composite scenario, diagnosis and proposed controls. All company profiles, financial inputs and risk ratings are illustrative assumptions. The sources do not establish an industry-wide ranking of these issues.

One bottleneck.
A measurable difference.

Find a problem that feels familiar.

The crew arrives.
The work is not ready.

The extra work is done.
The revenue is missing.

Machines are busy.
Orders are still waiting.

The drawing changed.
Production did not.

Every decision returns
to the owner.