How to Protect Yourself When Client Causes Delay but Denies It
Client Ne Delay Kiya — Aur Blame Aap Par?
Yeh Nahi Chalega.
2 saal ki mehnat. Hazaron manhours. Aur handover ke din client ne ek line mein bol diya — "Yeh delay aapki taraf se tha." Jaanein kaise ek planning engineer ne AED 2.3 million bachaye — sirf 20 min/day ki smart documentation se.
"Maine apna schedule dekha. Primavera mein sab kuch tha. Lekin jo nahi tha — woh tha ek proper delay notice. Aur usi din mujhe samjha — planning sirf schedule banana nahi hai. Planning apni protection karna bhi hai."
Is Article Mein Kya Hai
Kya aapke saath bhi aisa hua hai? Client ne drawing late di. RFI ka jawab hafton baad aaya. Site access 3 baar postpone hua. Aur phir bhi — handover ke time woh bol rahe hain ki delay aapki wajah se hua. Agar haan — toh yeh article sirf aapke liye likha gaya hai.
Client Delay Hota Kya Hai? — Pehle Yeh Samjho
Bahut se junior engineers sochte hain ki client delay sirf tab hota hai jab client seedha bol de — "Haan bhai, humari wajah se ruka." Real life mein aisa kabhi nahi hota. Client delay zyada tar silent hota hai — aur isiliye dangerous hota hai.
Drawing & Document Delay
Client ne approved drawing 3 hafton baad di. Aapka structure team betha raha. Proof? Zero — kyunki written mein kuch nahi tha.
RFI Ka Jawab Late Aana
Request for Information bheja. Client ne 15 din baad reply kiya. In 15 dinon mein kaam ruka raha. Yeh delay hai — but record nahi.
Site Access Nahi Milna
Area clear nahi tha. Client ki permission pending thi. Aapki team idle rahi. Kaun manega — bina documentation ke?
Scope Change — No Written Order
Client ne verbally kaha — "Yeh bhi kar do." Koi change order nahi. Kaam badha. Time badha. Record zero.
Payment Delay se Resource Withdrawal
Payment aaya nahi. Subcontractor ne kaam roka. Schedule hila. Client bolega — "Yeh aapki planning ki kami thi."
Yeh sab client delay ke forms hain. Aur agar aapne inhe document nahi kiya — toh handover pe aap akele khade honge, baghair kisi saboot ke.
4 Galtiyan Jo Planning Engineer Ko Sabse Zyada Mahnga Padti Hain
Seedha baat karta hoon — main khud bhi yeh galtiyan kar chuka hoon. Aur field mein kaam karne ke baad samjha ki yeh kitni badi bhool thi.
Sirf Verbal Note Karna
Client ne meeting mein kaha — "Drawing agle hafte milegi." Aapne mentally note kiya. Diary mein likha. Email nahi kiya. Confirmation nahi li. Result? Woh hafte ek mahina ban gaya — aur koi formal record nahi tha.
Informal WhatsApp pe Trust Karna
"Bhai kal site ready ho jayegi" — client ka WhatsApp message. Aapne team bheji. Site ready nahi thi. 1 din waste. WhatsApp screenshot tha — but kabhi formally use nahi kiya gaya. WhatsApp screenshot court mein itna strong nahi hota. Email hamesha stronger hai.
Schedule Impact Record Na Karna
Delay hua. Aapne Primavera update kiya. But yeh note nahi likha ki is delay ki wajah kya thi aur schedule pe kya asar padha. Handover pe koi nahi manega sirf updated schedule — wajah bhi chahiye.
MOM Nahi Karna
Meeting hui. Decisions hue. Sab yaad tha. MOM nahi bana. 3 mahine baad — kisi ko kuch yaad nahi. Client ki baat alag. Aapki baat alag. Yeh galtiyan chhoti lagti hain — but project ke aakhri 10% mein atom bomb ban jaati hain.
5-Step Protection System — Aaj Se Shuru Karo
Yeh 5 steps kisi book mein nahi hain. Koi college nahi sikhata. Sirf site ki thappad ne sikhaya — aur ek real case study ne prove kar diya ki yeh kaam karta hai.
Delay Notice Letter Bhejo — Usi Din
Jis din delay hua — usi shaam ek formal email bhejo. Yeh email 3 lines ki bhi ho sakti hai. Lekin yeh 3 lines aapko hazaron dollar ke claim mein bachayengi.
Email mein yeh 4 cheezein zaroor hon: (1) Delay ki exact date aur wajah, (2) Client ki taraf se kya nahi mila, (3) Schedule pe expected asar, (4) Aap client se kya expect karte hain — aur kab tak.
This is to formally notify that works at [Location] have been impacted due to non-receipt of [Drawing/RFI/Site Access] as of [Date].
This delay is expected to impact the project schedule by approximately [X days]. We request your immediate action to mitigate further delays.
Regards,
[Your Name] | Planning Engineer
Daily Site Diary — Har Din, Bina Naagaa
Site diary sirf attendance register nahi hai. Yeh aapka legal document hai. Isme yeh zaroor likho har din: kya kaam hua aur kya nahi hua, exact reason, kaun responsible tha, aur kitne log idle rahe — kitne ghante.
Pro Tip: Site engineer se daily sign karwao. Ek signature — aur yeh document 10 guna powerful ho jaata hai. Yeh diary court mein bhi chalti hai.
MOM — Har Meeting Ke Baad, Koi Excuse Nahi
Meeting ke 24 ghante ke andar MOM — Minutes of Meeting — email karo client ko. Isme likho: kya discuss hua, kya decide hua, kisne kya karna hai aur kab tak, aur pending items.
Agar client MOM pe reply nahi karta — consider karo ki unhone agree kar liya. MOM ke end mein yeh ek line add karo:
Yeh ek line — bahut badi protection hai.
Schedule Impact Record — Primavera Se Sirf Kaam Nahi Chalta
Aapne Primavera update kiya — achha. Lekin kya aapne yeh document kiya ki pehle baseline kya tha, delay ke baad schedule kaise badla, aur critical path impact hua ya nahi? Har delay ke saath ek Impact Analysis Record banao.
| Date | Delay Reason | Activities Impacted | Days Lost | Responsible |
|---|---|---|---|---|
| 15-Jan | Drawing not received | Foundation layout | 4 days | Client |
| 28-Jan | RFI unanswered | Column placement | 2 days | Client |
| 12-Feb | Site access denied | Excavation works | 3 days | Client |
Yeh table handover ke time sona ban jaati hai.
EOT Claim File Karo — Yeh Aapka Contractual Right Hai
EOT — Extension of Time — ek formal request hai jisme aap client se officially kehte hain: "Aapki wajah se X din ka delay hua. Hum contract completion date X din aage badhane ka claim karte hain."
EOT claim mein yeh hona chahiye: delay ki complete timeline, har delay ka documentary proof (emails, MOM, site diary), schedule impact analysis, aur extension calculation ke saath.
EOT file karna matlab yeh nahi ki aap ladai kar rahe hain. Yeh aapka contractual right hai. Jo planner EOT file nahi karta — woh khud apni galti maan leta hai.
Smart Planner Ki Complete Toolkit — 6 Essential Tools
Bahut se engineers sochte hain ki scheduling software hi sab kuch hai. Primavera chal raha hai — toh kaam ho gaya. Nahi. Bilkul nahi. Scheduling tool sirf ek part hai.
Primavera P6
Industry standard. Original baseline preserve karo — wahi aapka sabse bada saboot hai. Float analysis aur critical path track karo.
Excel — Delay Log
Sabse underrated tool. Ek simple sheet — Date, Delay Type, Responsible, Days Lost. Har hafte update karo.
Word / Google Docs
MOM aur formal letters ke liye. Standard template ek baar banao — zindagi bhar kaam aayega.
Aconex / Procore
Bade Gulf projects ke liye. RFI response time automatic record hoti hai — koi argument nahi kar sakta.
WhatsApp + Email Combo
WhatsApp pe important baat? Usi din email mein convert karo: "As discussed on WhatsApp today..." Ab legally valid hai.
MS Project
Agar company Primavera afford nahi karti — equally powerful for small-medium projects. Variance column add karo.
Real Case Study
Theory toh bahut sun li. Ab ek real story sunเคคे hain. Yeh Gulf region ke ek commercial building project ki case study hai. Details anonymized hain — lekin har ek cheez real hai.
Kya Hua?
Month 7 mein client ne structural drawings ki revised set bheji — 47 din late. Revised drawings mein 3rd floor ka layout completely change tha. In 47 dinon mein structural team ka kaam ruka raha. Planning engineer — chalein unhe Ravi kehte hain — ne turant action liya.
Ravi Ne Kya Kiya — Day 1 Se
Day 1: Usi shaam formal delay notice email bheja — timestamp ke saath. Client ne reply nahi ki. Lekin email sent thi.
Week 1: Primavera mein 12 impacted activities identify ki. 4-page Impact Analysis Report banayi. Client ne reply ki: "We will review and revert." Ravi ne yeh email save ki — baad mein bahut kaam aayi.
5 Mahine: Har hafte site diary update, weekly delay report, har meeting ke baad MOM, delay log Excel mein 31 entries.
Handover Ka Din — Asli Test
Client ne kaha: "This delay is due to contractor's poor planning. We will be imposing liquidated damages."
Ravi ne laptop khola. Folder tha — "Delay Documentation." Usne quietly kaha: "Sir, with due respect — here is our formal EOT claim. 47 days. All documented."
20 minute baad — meeting khatam. 3 din baad client ne formally EOT accept kar liya.
| Factor | Bina Documentation | Ravi Ka Approach |
|---|---|---|
| Client Claim | LD imposed — contractor ki galti | EOT accepted — client ki galti |
| Financial Impact | AED 2.3M loss | Zero loss |
| Proof Available | Kuch nahi | 23 emails + 18 MOM + Primavera |
| Daily Time Spent | — | 20–30 minutes only |
| Career Result | Career risk | Promotion |
Ravi koi superhero nahi tha. Woh aap jaisa ek normal planning engineer tha — jo sirf ek cheez mein alag tha. Usne har din 20–30 minute extra lagaye — documentation mein. Aur usi 20–30 minute ne uski company ka AED 2.3 million bachaya.
Ab Aapki Baari Hai — Shuru Karo Aaj Se
Planning sirf schedule banana nahi hai. Planning apna aur apni company ka haq protect karna bhi hai.
Aaj se — kal se nahi, aaj se — yeh 5 cheezein shuru karo:
Jo planner yeh jaanta hai — woh sirf engineer nahi hota. Woh asset hota hai.
Free Templates — Seedha Aapke Inbox Mein
Delay Log Sheet (Excel) · Delay Notice Letter (Word) · MOM Template · EOT Claim Checklist (PDF)
Comments
Post a Comment