Saturday, October 18, 2025

Chapter 7: Communication, Reporting, and Documentation

 Part 3: The People Side of Projects, management in Action.

Chapter 7: Communication, Reporting, and Documentation

7.1 Why Communication Matters More Than Concrete

A project can have good engineers, strong materials, and perfect plans —
but without communication, everything falls apart.

Most site problems aren’t due to bad work — they happen because someone didn’t inform, didn’t record, or didn’t follow up.

“The best engineer isn’t the one who knows everything —
it’s the one who keeps everyone informed.”

7.2 The Flow of Information on a Construction Site

Think of a construction project as a living network —
messages constantly moving up, down, and sideways.

DirectionWho CommunicatesPurpose
UpwardSupervisor → Engineer → PM → ClientProgress, issues, approvals
DownwardPM → Engineer → Supervisor → WorkersInstructions, targets, safety rules
SidewaysBetween departments (Civil, Electrical, Plumbing, QA/QC)Coordination, sequencing, clarifications

A smart site team keeps these channels clear, short, and factual.

7.3 The Three Golden Rules of Site Communication

  1. Be Clear – Avoid technical jargon when not needed. Say exactly what needs to be done.

  2. Be Quick – Information delayed is information lost.

  3. Be Confirmed – Always document instructions in writing — on WhatsApp, email, or site log.

“If it’s not written, it’s not remembered.”

7.4 Daily Reporting – The Pulse of the Site

Every day, before leaving site, the engineer or supervisor should fill a Daily Progress Report (DPR).

Typical DPR Includes:

  • Date, weather condition

  • Manpower count (skilled / unskilled)

  • Activities completed

  • Materials received

  • Equipment used

  • Concrete poured (m³) / work done (sqm or rm)

  • Problems or delays

  • Next day’s plan

Example:

DateActivityQuantityRemarks
18/10/2025RCC Slab (Block A – 2nd Floor)38 m³Completed by 6:30 pm, cube samples taken
18/10/2025Masonry Work (Block B)25 m²Shortage of sand – delivery expected tomorrow

This small record becomes invaluable for billing, planning, and dispute resolution.

7.5 Weekly and Monthly Reports

While DPRs show daily progress, Weekly and Monthly reports summarize the big picture.

ReportPrepared ByPurpose
Weekly ReportSite Engineer / Planning Engg       Highlights progress vs. schedule
Monthly Report          Project Manager   Sent to client or HO for review and billing

These reports include:

  • Cumulative quantities achieved

  • Manpower and machinery summary

  • Major issues and corrective actions

  • Site photographs

  • Cash flow / material consumption chart

A well-prepared report builds the PM’s credibility and earns client trust.

7.6 The Power of Photographs

A photo is better than a thousand explanations.
Document every milestone, activity, and problem with clear photos.

Tips for Useful Site Photos:

  • Add date, location, and description in filename.

  • Take before, during, and after shots.

  • Capture not just beauty, but also issues (for evidence).

  • Keep photos organized in monthly folders.

Example Folder Structure:

/Photos
  /2025_Oct
     /Concrete_Work
     /Brickwork
     /Safety
     /Snag_List

Visual documentation protects your work, helps during audits, and showcases professionalism.

7.7 Communication Tools – Old and New

ToolUsageAdvantage
Site DiaryDaily written record of instructions & eventsLegal backup
Drawing Issue RegisterTracks revisions & issuancePrevents confusion
WhatsApp / Email GroupsReal-time coordinationFast and traceable
Notice BoardsDisplay schedules, safety charts, team infoKeeps workers informed
Site MeetingsDiscuss progress, problems, solutionsBuilds teamwork
Minutes of Meeting (MoM)Written record after each meetingAccountability

Even if technology changes, one rule stays the same — “Record before you forget.”

7.8 Reporting Problems – The Right Way

Every site has issues — delays, material shortages, design mismatches.
How you report them decides how fast they get solved.

Right Way:

“Masonry stopped due to shortage of 1000 bricks. Request urgent supply by 10 AM tomorrow.”

Wrong Way:

“No bricks, work stopped.”

Clear, specific, solution-oriented messages build respect and trust.

7.9 RFIs (Request for Information)

Whenever there’s a doubt or mismatch in drawings, engineers raise an RFI to the consultant or design team.

Example:

“RFI No. 12 – Column C4 reinforcement differs between Structural (8 bars Ø16) and Architectural (6 bars). Please confirm correct detail.”

Keep an RFI Register with date, subject, status (Open / Closed).
Timely RFIs prevent rework and disputes later.

7.10 Documentation – The Silent Shield

Documentation may seem boring, but it’s your defense when problems arise.

Keep these records properly:

  • Material test reports

  • DPRs, Weekly & Monthly Reports

  • Inspection checklists

  • Cube test results

  • NCRs (Non-Conformance Reports)

  • Work permits & safety records

  • As-built drawings

  • Subcontractor bills and measurement sheets

Store both hard copies and soft copies.
A clean record system can save crores in disputes.

7.11 Site Meetings – Turning Talk into Action

Meetings are only useful when they lead to action.

Good Meeting Habits:

  • Keep it short — 30 minutes max.

  • Bring updated data, not excuses.

  • Note minutes and assign responsibilities.

  • Review last meeting’s points before closing.

Pro Tip:
End every meeting with “Next Actions & Deadlines.”
Otherwise, it’s just talk.

7.12 The Chain of Communication

LevelMain Reports / UpdatesFrequency
Worker / Foreman → SupervisorWork done, material needsDaily
Supervisor → EngineerActivity progress, labour summaryDaily
Engineer → PMDPR, testing results, RFIsDaily / Weekly
PM → Client / HOProgress summary, billing, key issuesWeekly / Monthly

When everyone respects this chain, confusion disappears and accountability grows.

7.13 The Human Side of Communication

Construction sites mix people from different regions, languages, and skills.
Good communication means:

  • Using simple language that everyone understands.

  • Giving instructions face-to-face whenever possible.

  • Listening — not just talking.

  • Appreciating small efforts publicly.

“Respectful communication builds loyal teams faster than any bonus.”

7.14 The Three Golden Habits

  1. Write it down. – What’s written becomes real.

  2. Send it early. – The sooner it’s shared, the sooner it’s solved.

  3. Follow it up. – Every report means nothing unless followed up.

A disciplined engineer doesn’t just complete work — he completes communication.

7.15 Key Takeaways

✅ Clear communication prevents chaos.
✅ Daily and weekly reports are the pulse of your project.
✅ Always document — photos, reports, and approvals.
✅ Respect the communication chain.
✅ Listen as much as you speak.

“Drawings build structures.
Words build teams.”


at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Appendix A: Job Description Library – Key Site Roles

Appendix A: Job Description Library – Key Site Roles A.1 Project Manager (PM) Reports To: Client / Corporate Office Direct Reports: Site En...