FIDIC 2017 Notice Register: 28/84-day workflowni claim yo'qotmasdan boshqarish

28-day rule deyarli hammaga tanish. Uni ham ko’pchilik bir xil o’tkazib yuboradi: event ko’rildi, meetingda muhokama qilindi, “keyin letter tayyorlaymiz”, planner band, QS raqam kutyapti, legal ko’proq facts so’rayapti. Bir oy o’tib jamoa claim kuchli bo’lishi mumkinligini tushunadi, lekin notice allaqachon risk zonasida.

Muammo odatda Clause 20 o’qilmaganida emas. Muammo shundaki, loyihada notices uchun operating system yo’q.

FIDIC 2017 Notice Register event, awareness date, 28-day notice, records, 84-day fully detailed claim va keyingi decision trailni bitta boshqariladigan zanjirga bog’laydi.

Bu 28-day maqolasidan nimasi bilan farq qiladi

28-day rule haqidagi asosiy maqola notice nega critical va time-bar nega xavfli ekanini tushuntiradi.

Bu maqola operational workflow haqida: notice bitta contract manager xotirasiga bog’liq bo’lmasligi uchun loyiha qanday tizim quradi.

Deadline bilish - legal literacy. Deadline boshqarish - contract administration.

Notice Register nima yozishi kerak

Minimal register yetti-sakkiz savolga javob beradi:

Field	Nega kerak
Event ID	event correspondence ichida yo’qolmasin
Event description	qisqa factual description
Date of event	event qachon bo’ldi yoki boshlandi
Date of awareness	notice period boshlanishi mumkin bo’lgan sana
Potential entitlement	time, cost, both yoki other relief
Notice due date	28-day deadline control
Detailed claim due date	84-day yoki contract-specific deadline
Evidence owner	records kim yig’adi
Status	watching, notice issued, particulars pending, submitted, determined, disputed

Real loyihada affected activities, clause reference, responsible person, correspondence link, Engineer response, claim value, risk rating qo’shiladi. Lekin minimum bo’lmasa, jamoa claimsni inbox orqali boshqaradi.

28 kunni qulay sanadan hisoblamang

Eng xavfli savol - awareness date. Jamoa ko’pincha muddatni cost yoki time impact aniq bo’lgan kundan hisoblashni xohlaydi. Bu kech bo’lishi mumkin.

Register uch sanani ajratishi kerak:

1. Event date - event bo’lgan sana.
2. Awareness date - tomon event haqida bilgan yoki bilishi kerak bo’lgan sana.
3. Impact confirmation date - consequences aniqroq bo’lgan sana.

Notice full calculationni kutmasligi kerak. Uning vazifasi huquqni saqlash va boshqa tomonni ogohlantirish. Calculation va causation fully detailed claimda ochiladi.

84-day workflow

FIDIC 2017da notice entry point. Keyin og’irroq qism boshlanadi: substantiation.

Har notice uchun:

• event file ochiladi;
• records owner tayinlanadi;
• affected activities programme bo’yicha tekshiriladi;
• daily reports, photos, manpower/equipment logs yig’iladi;
• correspondence va instructions bog’lanadi;
• direct cost evidence umumiy shikoyatlardan ajratiladi;
• chronology tuziladi;
• draft claim narrative tayyorlanadi;
• fully detailed claim deadline nazorat qilinadi.

Notice yuborilib, evidence workflow boshlanmasa, jamoa faqat vaqt sotib olgan bo’ladi. Claim hali isbotlangan emas.

Batafsil: Claims substantiation.

Register kimniki

Yomon register “legalda kimdadir” bo’ladi. Yaxshi register loyiha instrumenti.

Rollar:

• Contract Manager notice logic va correspondence statusni yuritadi.
• Planner activity impact, baseline/revised programme va critical pathni tekshiradi.
• QS/cost team quantum evidence yig’adi.
• Site team daily records, photos, manpower, equipment va disruption facts beradi.
• Project Manager commercial decision qiladi: notice, reserve rights, escalation yoki close.

Yurist yordam beradi, lekin yo’q recordsni keyin yaratib bera olmaydi.

Event watching

Notice Register loyihani conflict factoryga aylantirmasligi kerak. Shuning uchun watching status kerak.

Late drawing impact bermasligi mumkin. Minor access issue float bilan yutilishi mumkin. Lekin event time, cost yoki rightsga ta’sir qilishi mumkin bo’lsa, uni watchingga qo’ying va deadline belgilang.

Weekly rhythm

Notice workflow weekly contract meetingga kirishi mumkin:

1. Yangi events review.
2. Approaching 28-day deadlines.
3. Issued notices review.
4. Har open event bo’yicha records status.
5. 84-day/detailed claim tracker update.
6. Events close, notice yoki escalation decision.

Bu rhythm ishlasa, claim readiness loyiha boshqaruvining bir qismi bo’ladi, DAAB oldi yong’in emas.

FAQ

Notice Register faqat contractor uchunmi?

Yo’q. Employer va Engineer ham events, notices, determinations, payment issues va dispute exposureni ko’rishdan foyda oladi.

Excelda yuritsa bo’ladimi?

Ha, agar owner, weekly review, document links va deadline control bo’lsa. Muammo Excelda emas, file boshqaruv jarayoniga kirmaganida.

Har kichik eventga notice berish kerakmi?

Yo’q. Lekin har potentially material event tez baholanishi kerak. Time, cost yoki other relief ehtimoli bo’lsa, event va deadline yozib qo’yiladi.

Bridge Consult FIDIC 2017 bo’yicha notice register, claims workflow va records disciplineni qurishda yordam beradi.

Sources and further reading

• Society of Construction Law, Delay and Disruption Protocol, 2nd Edition.
• World Bank, Project Procurement.
• World Bank, Contract Management: Practice Procurement Guidance, Second Edition, May 2024.
• FIDIC, Conditions of Contract for Construction, 2017 edition.
• Shuningdek qarang: 28-day rule, Claims substantiation va Notice Deadline Calculator.