Business Risk Cue
A communication choice that increases financial, legal, or reputational exposure if left unaddressed.
Project 14
Build and operate one customer-communication process for an active residential project that manages schedule updates, disruption points, change requests, owner decisions, complaints, payment matters, and quality issues — with every material conversation preserved in a written, retrievable job-file record.
These cues appear at the point of work. They identify compliance, professional-review, jurisdictional, and documentation issues before a communication becomes an unauthorized promise or an unrecorded commitment.
A communication choice that increases financial, legal, or reputational exposure if left unaddressed.
An action that must not be taken, or must be stopped, until a specific legal or contract condition is satisfied.
Practical controls that keep customer communication consistent as the project is actually performed.
Overdue-payment, lien, and dispute procedures vary by state and municipality. Verify current requirements before relying on this chapter.
A point where an attorney, insurer, or other qualified professional must be consulted before a communication is sent.
A conversation, decision, or commitment that must be written down, dated, and retained in the job file.
This project produces one operating customer-communication process for a single active residential project. The finished work product is a controlled communication calendar, a standard project-update format, a documented selections log, a complaint-intake and response procedure, and a preserved job-file record of every material conversation, decision, disruption notice, and change discussed with the customer while work is underway.
You will confirm the customer's authorized decision makers, build a communication calendar tied to the project schedule, report progress accurately without concealing delay, explain disruption before it happens, route every scope request through the Chapter 10 change system, document every owner decision in writing, handle complaints through a defined intake-to-closure procedure, and preserve every meaningful conversation in the job file.
This project runs from job start through final walkthrough. It depends on the signed contract and scope of work from Chapter 9, the change-order and allowance system from Chapter 10, and the job startup packet from Chapter 13. It feeds directly into the final walkthrough, punch list, invoice, and warranty handoff in Chapter 19.
This project begins the moment the job-start packet from Chapter 13 is approved and mobilization is authorized. It runs continuously through the active-job cost review in Chapter 18 and closes into the final walkthrough, punch list, and warranty handoff in Chapter 19. Every schedule statement, disruption notice, decision record, and complaint response produced here becomes part of the job file that Chapter 19 relies on to reconcile the final account and Chapter 18 relies on to investigate cost variance tied to customer-caused delay or scope change.
The same discipline used in Chapter 10 — writing a decision down before acting on it — controls this project. A verbal understanding with a customer is not a record. Only a written, dated entry in the communication log or job file counts as documentation for this project's acceptance standards.
This project covers:
This project does not authorize the learner to:
Any communication that cannot be supported by the signed contract, the approved scope of work, or a properly authorized change order must be corrected before it is sent to the customer.
Establish these references before operating the communication process, and do not change their meaning mid-project.
| Term | Definition |
|---|---|
| Baseline schedule | The approved schedule date from the job startup packet, used as the fixed reference point for every later update |
| Current forecast | The contractor's present best estimate of a schedule date, which may differ from the baseline and must be labeled as a forecast, not a promise |
| Commitment date | A schedule date the contractor has affirmatively promised the customer in writing; used only when the contractor can actually deliver it |
| Disruption point | Any noise, dust, odor, utility shutdown, access, delivery, parking, security, or room-use condition that will affect the customer's normal use of the property |
| Owner decision | Any selection, approval, refusal, deferral, or access restriction made by an authorized decision maker |
| Complaint | Any customer-raised concern about contract deficiency, warranty item, punch item, damage, design preference, scope dispute, schedule, or billing |
| Job file | The single controlled archive of every email, text, platform message, meeting note, photograph, approval, and notice for this project |
Before the communication process is activated, record the following on the communication calendar template:
Project name/address: ______ Customer decision maker(s): ______ Preferred contact method: ______
Baseline schedule source: ______ Responsible project manager: ______ Job-file location: ______
Every customer-management failure traced in this chapter's troubleshooting section comes back to the same root cause: a conversation happened and was not written down, or a promise was made outside the contract, scope, and change-order controls established in earlier chapters. This project does not create new legal terms — it operationalizes the terms already approved in Chapter 9 and the change procedure already approved in Chapter 10, applied consistently for the life of one active project.
A schedule date, disruption notice, or decision is only considered communicated when it appears in the job file in writing. A conversation that happened only by phone or in person is documented the same day with a written summary sent to the customer. If the customer does not dispute the summary within a reasonable time stated in the summary itself, the summary stands as the record of that conversation.
After any phone call, site conversation, or meeting that touches schedule, price, scope, selections, access, or a complaint, write a same-day summary and send it to the customer through the established communication channel. File a copy in the job file. Do not rely on memory of the conversation at a later date.
Do not allow field personnel to promise free added work, a schedule acceleration, a substitution, or a payment-term change during a site conversation. Any such request must be routed through the Chapter 10 change-order and allowance system before it is confirmed to the customer.
Maintain a single controlled job file for this project's communications, consistent with the company record system established in Chapter 2. Do not allow separate, informal message threads to substitute for the job file. Chapter 18 and Chapter 19 both depend on this single record.
Overdue-payment, lien, work-stoppage, and dispute-escalation communications must use attorney-approved language for the applicable jurisdiction. Do not send an unreviewed threat of lien, collection, permit action, or abandonment.
PC-079 – PC-084
Customer Communication / Project Execution Control
Quantity: one communication calendar, one standard project-update format populated for the current reporting period, one selections and owner-decision log, one complaint intake and response log, and one preserved job file, each maintained continuously from job start through final walkthrough.
| Document | Quantity | Format | Content Required | Preparation / Purpose |
|---|---|---|---|---|
| Communication Calendar | 1 per project | Dated schedule | Kickoff, weekly updates, selection deadlines, inspections, billing dates, walkthrough, closeout | Fixes when the customer will be contacted so no update is missed |
| Standard Project-Update | 1 per reporting period | Written report, consistent format | Completed work, current work, next work, decisions needed, deliveries, inspections, changes, risks, access conditions | Keeps every update accurate and comparable to prior updates |
| Selections and Owner-Decision Log | 1 per project | Table | Product, price effect, lead time, approval, date, and authorized decision maker for each item | Prevents undocumented showroom or verbal decisions |
| Complaint Intake and Response Log | 1 per project | Table | Date, description, classification, responsible manager, response deadline, closure date | Ensures every concern is acknowledged, investigated, and closed |
| Job File | 1 per project | Physical or digital archive | Emails, texts, platform messages, meeting notes, photographs, approvals, notices | Single source of record for Chapter 18 and Chapter 19 |
| Check | Standard |
|---|---|
| Schedule reporting | Every schedule statement is labeled baseline, current forecast, or commitment, and no known delay is concealed or presented as guaranteed |
| Disruption notice | Every disruption point is explained to the customer with reasonable advance notice consistent with the contract and circumstances |
| Change routing | Every scope request is routed through the Chapter 10 change-order system; no field-level promise of added work, schedule change, or substitution is made outside that system |
| Decision documentation | Every selection, approval, refusal, deferral, or access restriction is recorded in writing with date and authorized decision maker |
| Complaint handling | Every complaint is acknowledged, classified, assigned a responsible manager and deadline, investigated, and closed with documented confirmation |
| Record preservation | Emails, texts, platform messages, meeting notes, photographs, approvals, and notices are filed in the job file at the time they occur |
Inspect the operating communication process using the same checks regardless of project size or type.
Complete the Communication Process Review Worksheet in the Inspection Checklist section below at every billing cycle and before beginning the final walkthrough in Project 19.
Probable cause: a schedule date was given verbally without a written label of baseline, forecast, or commitment, and was not entered in the job file.
Confirmation: search the job file and communication log for a written record of the disputed date.
Correction: send a written clarification restating the current forecast and its basis, and file the clarification in the job file.
Reinspection: repeat the schedule check on the next update and confirm every future date is labeled and recorded.
Probable cause: a site conversation was treated as an approved change without routing it through the Chapter 10 system.
Confirmation: compare the field team's statement against the approved change-order log.
Correction: notify the customer in writing that the item requires a change order, process it through Chapter 10, and correct the field team's understanding of the routing requirement.
Reinspection: repeat the change-routing check on the next several field conversations.
Probable cause: the selection was made verbally at a showroom or on site and was not entered on the owner-decision log.
Confirmation: check the owner-decision log and job file for a written record of the selection, its price effect, and its approval.
Correction: document the current understanding in writing, obtain the customer's confirmation, and enter it on the log with the actual decision date noted as best known.
Reinspection: repeat the decision check on all pending selections before further procurement.
Probable cause: the complaint was addressed informally in conversation without a corresponding log entry, responsible manager, or closure record.
Confirmation: compare the customer's account of the complaint against the complaint log.
Correction: open a log entry with the correct date, classify the complaint, assign a responsible manager and deadline, and document the investigation and closure going forward.
Reinspection: repeat the complaint check on all open items at the next project meeting.
Probable cause: a payment reminder escalated into a lien or collection threat without attorney-approved language.
Confirmation: review the sent communication against the attorney-approved template for the applicable jurisdiction.
Correction: send a corrected communication using approved language, and route any further escalation through counsel.
Reinspection: repeat the professional-review check before any further overdue-payment communication is sent.
Probable cause: the standard update format was not used consistently, or one department communicated directly with the customer without checking the job file.
Confirmation: compare recent messages from each department against the job file and the standard update format.
Correction: issue a single corrected message reconciling the conflict, and route future customer communication through the responsible project manager.
Reinspection: repeat the record check at the next billing cycle and confirm one consistent message source.
This project remains active for the life of the job, but each reporting period ends with the record filed for reuse, not left as informal notes.
| Competency | Independent Pass Standard | Not Demonstrated | With Assistance | Independently |
|---|---|---|---|---|
| PC-079 | Communicates schedule updates using baseline, forecast, and commitment language and does not conceal known delay, verified against the job file | |||
| PC-080 | Explains disruption points to the customer with reasonable advance notice, documented in the job file | |||
| PC-081 | Routes every scope request through the Chapter 10 change-order system with no field-level promise made outside it | |||
| PC-082 | Documents every owner decision, selection, refusal, deferral, and access restriction in writing with date and decision maker | |||
| PC-083 | Handles complaints through a defined intake, classification, investigation, and closure procedure with documented results | |||
| PC-084 | Preserves a complete, organized, retrievable job file of communications, decisions, and notices for the active project |
Mark one column per competency. Only Demonstrated Independently awards the competency; Demonstrated with Assistance authorizes additional supervised practice but does not complete the requirement.
| Item | Standard | Complete (Y/N) | Notes / Correction |
|---|---|---|---|
| Communication calendar current | All planned contact points through the current period are dated and complete | ||
| Standard updates issued | Every reporting period has a completed, filed project update | ||
| Schedule statements labeled | Every date is marked baseline, current forecast, or commitment | ||
| Disruption notices given | Reasonable advance notice documented for each disruption point | ||
| Change requests routed | No field-level promise exists outside the Chapter 10 change log | ||
| Owner decisions logged | Every selection, approval, refusal, deferral, and restriction recorded | ||
| Complaints classified and closed | Responsible manager, deadline, investigation, and closure documented | ||
| Escalations routed | Legal, insurance, injury, or discrimination matters referred to professionals | ||
| Job file complete | Emails, texts, messages, notes, photographs, approvals, and notices filed for the period | ||
| Pre-closeout review completed | All open decisions, complaints, and changes resolved before Chapter 19 |
Communication process reviewed complete for this period: ______ (Pass/Fail) Date: ____________ Project manager: ____________
Reviewing professional (if applicable): ____________ Next scheduled review point: ____________
At every billing cycle and before the final walkthrough in Project 19, review the operating process against the Acceptance Standards table and confirm every schedule statement is labeled and undelayed statements are supported, every disruption was explained with reasonable notice, every scope request was routed through the change-order system, every owner decision is logged with date and decision maker, every complaint is classified with a responsible manager and closure record, and the job file contains the period's communications. Complete the Communication Process Review Worksheet and correct any failed item before the next reporting period. If an item fails, identify whether the gap is in schedule labeling, disruption notice, change routing, decision documentation, complaint handling, or record preservation before correcting the process.
You have completed the fourteenth project in the professional-contractor sequence: managing customer expectations during construction. This project required you to communicate accurate schedule updates (PC-079), explain disruption points in advance (PC-080), manage change requests through the approved routing system (PC-081), document owner decisions (PC-082), handle complaints professionally (PC-083), and preserve communication records in a complete job file (PC-084).
You now have an operating communication calendar, a standard update format in active use, a selections and owner-decision log, a complaint intake and response log, and a preserved job file. This record carries directly into the next project: building a professionally reviewed employee and worker onboarding system that verifies classification, training, PPE, supervision, and emergency readiness before workers are assigned to this and future active projects.
Keep this project's communication calendar, update log, decision log, complaint log, and job file active and current. Chapter 18 and Chapter 19 both depend on the completeness of these exact records.