# Contractor delay: the records needed to understand what happened Build a factual chronology from programmes, decisions, site records and correspondence before asking advisers to assess delay and responsibility. Bunyady · 2026-10-15 When a home project appears late, the first useful step is to establish what was planned, what actually happened and what information supports the difference. A collection of frustrated messages rarely provides that picture by itself. This guide helps an owner organise a factual file for discussion with the project team and advisers. It does not decide fault, compensation or a right to terminate. Those questions require the actual contract, relevant law and a proper assessment of the circumstances. ## Find the programme that was actually agreed Collect the original agreed programme and later revisions, with their dates and approval status. Identify the milestone or completion point being discussed and the assumptions attached to it. A draft programme or an informal target may not describe the same commitment as the reviewed contract. Ask the adviser to clarify that relationship. Keep superseded versions rather than replacing them, because the sequence of revisions can help the team understand when expectations changed and which information was available at each stage. ## Create a dated record of actual progress Gather dated site reports, inspection records, delivery notes and photographs that identify locations. Arrange them against the activities under review. Separate work observed from work merely reported in conversation. If a record is missing, mark the gap rather than filling it with an uncertain memory. Ask the supervising professional to explain technical progress in terms the owner can understand. The purpose is a reliable chronology, not a photo contest in which the largest number of images is assumed to prove the strongest account. ## Track decisions and information requests List requests for drawings, selections, approvals or clarification, recording when they were raised and answered. Link each to the work the team says it affected. Include owner decisions as well as contractor and designer actions so the file does not begin with an assumed conclusion. Preserve the actual messages or formal records behind the summary. A request date alone does not establish its effect on completion; the appropriate professional needs to assess the sequence and relationship to other activities. ## Record constraints without assigning blame prematurely Create a separate list for reported constraints such as access issues, unconfirmed procurement, design revisions or specialist review. Record who reported each issue, when, what response was proposed and what evidence supports it. Treat these as matters to investigate rather than proven causes of the overall delay. Ask the project team to explain which activities were affected and whether other work could proceed. This keeps the discussion specific and gives advisers a stronger basis for assessing competing explanations. ## Preserve notices and meeting outcomes Keep formal notices, meeting minutes and agreed action lists in date order. Ask the legal adviser which contractual communication requirements are relevant rather than guessing from a general article. After a progress meeting, record the actions, responsible people and next review points through the agreed process. Distinguish a proposed recovery plan from an accepted change to contractual dates. The owner needs clarity about what the team will do next without accidentally treating every planning discussion as a settled agreement on legal responsibility. ## Prepare a neutral summary for professional assessment Summarise the agreed baseline, observed sequence, unresolved questions and documents available. Separate facts, reported explanations and your own concerns. Provide the contract and amendments with the record, using official legal sources for the adviser’s review. Ask for an assessment of the actual situation and the appropriate next steps. Avoid publishing accusations or selecting a remedy from an online checklist. A concise, evidence-linked file helps the professionals focus on the issue and helps the owner understand the reasoning behind their advice. ## Your practical checklist 1. Keep agreed and revised programmes with their status. 2. Link actual progress, requests and constraints to dated evidence. 3. Separate facts from explanations before seeking advice. ## Frequently asked questions ### Does a missed target date prove contractor fault? Not by itself. The actual agreement, programme status, events and their effects need professional assessment before responsibility or remedies can be determined. ### Should I include delayed owner decisions in the file? Yes. A complete chronology includes relevant actions by all parties. The reviewer can then assess their actual significance rather than working from a selective record. ### What is the best first document to prepare? Create a dated chronology referencing the agreed programme and supporting records, with gaps and disputed explanations clearly marked for the project and legal reviewers. ## Sources and further reading - [Bureau of Experts — Civil Transactions Law](https://laws.boe.gov.sa/BoeLaws/Laws/LawDetails/655fdb42-8c96-422b-b8c4-b04f0095c94c/1): Official legal reference. Case-specific interpretation requires a qualified adviser. [Journal](https://bunyady.com/blog/) · [Request a quote](https://bunyady.com/#requestaquote) [English](https://bunyady.com/blog/records-to-understand-contractor-delay/) | [العربية](https://bunyady.com/ar/blog/records-to-understand-contractor-delay/)