FIDIC claimsni asoslash: contemporary records va evidence architecture

FIDIC claim odatda faqat yuridik pozitsiya zaifligi sababli yutqazilmaydi. Ko’pincha muammo oddiyroq: jamoada event, responsibility, causation va claim amountni bitta tekshiriladigan hikoyaga bog’laydigan records yo’q.

Shuning uchun substantiation - dispute oldidan tayyorlanadigan oxirgi PDF emas. Bu loyiha birinchi kunidan ishlaydigan evidence management tizimi.

Nimani isbotlash kerak

Amaliy FIDIC claim to’rtta ustunga tayanadi:

1. Contractual entitlement - qaysi clause time, money yoki boshqa relief beradi.
2. Event - nima bo’ldi, qachon bo’ldi, kimga notice berildi va event qanday rivojlandi.
3. Causation - event muddat, resurs, cost, sequence yoki productivityga qanday ta’sir qildi.
4. Quantum - summa qanday hisoblandi va nima uchun aynan shu xarajatlar event natijasi.

Bitta ustun yetishmasa, claim pozitsion xatga aylanadi. U ishonchli eshitilishi mumkin, lekin Engineer, DAAB yoki tribunal uchun uni tekshirish qiyin bo’ladi.

Contemporary records - arxiv emas, infratuzilma

Contemporary records - event paytida yoki unga yaqin vaqtda yaratilgan yozuvlar. Ularning kuchi shundaki, ular conflict boshlangandan keyin “tarixni yozib qo’yish”ga o’xshamaydi.

Asosiy evidence architecture:

• daily site reports;
• labour va equipment logs;
• sana, joy va activityga bog’langan photo/video;
• Engineer va Employer bilan correspondence;
• meeting minutes;
• instructions va RFI responses;
• updated programmes;
• progress records;
• cost records, timesheets, invoices, payroll evidence;
• alohida notice register va event register.

Maqsad hujjat ko’pligi emas. Maqsad zanjir: event -> notice -> impact -> record -> calculation -> claim.

Notice claimni isbotlamaydi

28-day rule haqidagi maqola notice nega muhimligini tushuntiradi. Lekin notice faqat kirish bileti. U huquqni saqlaydi, lekin summa va causationni isbotlamaydi.

Notice keyin jamoa quyidagilarni qilishi kerak:

• event file ochish;
• evidence owner tayinlash;
• har kuni qaysi data yig’ilishini belgilash;
• eventni programme activity IDlari bilan bog’lash;
• direct costsni umumiy shikoyatlardan ajratish;
• instructions, decisions va consequences chronology yuritish.

Bular darhol qilinmasa, uch oy o’tib claim xotira asosida yig’iladi. Bu qimmat va zaif.

Claim narrative qanday bo’lishi kerak

Yaxshi claim narrative uzun bo’lishi shart emas. U tekshiriladigan bo’lishi kerak.

Struktura:

1. Executive summary.
2. Contract basis.
3. Chronology.
4. Cause and effect.
5. Records matrix.
6. Time / cost analysis.
7. Relief sought va appendices.

Records matrix claimni tartibga soladi: asosiy da’vo uchun record bo’lmasa, uni tasdiqlash yoki olib tashlash kerak.

Tipik xatolar

• notice yuborilgan, ammo keyingi records yig’ilmagan;
• daily reports juda umumiy;
• photos sana, joy va activitysiz;
• programme updates real sequence ko’rsatmaydi;
• cost data bir nechta sababni aralashtiradi;
• quantum bor, causation yo’q;
• event-by-event analysis o’rniga global claim ishlatiladi.

Global claim qulay ko’rinishi mumkin: “hamma eventlar loyihani buzdi”. Lekin tekshiruvchi uchun bu umumiy commercial natijani Employerga o’tkazishga urinishdek ko’rinadi.

Minimum records matrix

Element	Nima yoziladi
Event ID	unique event number
Contract basis	clause / Particular Conditions
Notice	date, addressee, letter reference
Affected activities	programme activity IDs
Site evidence	daily reports, photos, manpower/equipment logs
Cost evidence	invoices, timesheets, subcontractor records, payroll
Decision trail	instructions, approvals, determinations
Current status	open / submitted / agreed / disputed

Bu jadval claimni almashtirmaydi. U claimni boshqariladigan qiladi.

FAQ

Ideal records bo’lmasa claimni isbotlash mumkinmi?

Ba’zan mumkin, lekin proof cost keskin oshadi. Jamoa chronology ni bilvosita dalillardan tiklaydi, opponent esa ko’proq tanqid imkoniyatiga ega bo’ladi.

Hamma narsani saqlash kerakmi?

Yo’q. Document dump emas, event, activity, cost va decision bilan bog’langan tizim kerak.

Evidence architecture kimniki?

Odatda Contract Manager, Planner, QS va site team birga yuritadi. Yuristlar yordam beradi, lekin daily project discipline o’rnini bosa olmaydi.

Bridge Consult project teamlarga claim register, records matrix va evidence architecture qurishda yordam beradi.

Sources and further reading

• Society of Construction Law, Delay and Disruption Protocol, 2nd Edition, February 2017.
• World Bank, Contract Management: Practice Procurement Guidance, Second Edition, May 2024.
• FIDIC, Conditions of Contract for Construction, 2017 edition.
• Shuningdek qarang: 28-day rule, EOT va delay analysis va Notice Register workflow.