Record hindrances while the evidence is still available

Record what happened, where, when it was first observed and which work appeared affected. Identify the reporter, responsible follow-up owner and available evidence. Use concrete descriptions: the access gate was unavailable to the specified work front, a drawing revision was pending, or a utility conflict was encountered.

Avoid unsupported conclusions about responsibility in the initial record. The site team can describe an instruction or restriction without deciding contractual liability. Preserve the source of the information and distinguish direct observation from a report received from another party.

The Procore daily log overview describes records for site events and operating information. Such records can support a hindrance file, but the project still needs to link the relevant entries and assess their significance.

An event's first recorded date may differ from when it began. Record that uncertainty. Likewise, an email saying access is available does not necessarily establish when the crew could practically resume work. Keep the evidence for both the restriction and its removal.

Identify the affected activity, location and planned quantity where possible. A restriction at one front may leave other work available. Record what continued, what stopped and what resources were redeployed. That operating detail helps the planner assess the effect later.

Use a status such as ongoing, condition removed or assessment pending. Removing the physical hindrance does not complete the schedule or commercial review. A closed event can still have unresolved cost evidence or a notice follow-up.

Consider a synthetic work front planned to operate from Monday through Wednesday. Access is unavailable throughout those three days, and the required drawing is also unavailable during the same period. The event register should contain two linked records, each with its own evidence.

The observed overlap spans three days, not six distinct calendar days. Even three days of event overlap does not by itself prove three days of project completion delay. The planner must examine logic, float, actual progress, available alternatives and other relevant facts using the appropriate method.

If the drawing remains outstanding on Thursday after access is restored, record that additional period separately. Preserve the changing condition rather than applying one broad end date to both events. This makes later analysis more accurate and easier to review.

Some events may trigger contractual notice or reporting requirements. Link the event to the contract obligations register and ask the authorised commercial reviewer to assess the relevant clause, timing, recipient and required content.

Do not wait for a fully quantified claim before checking whether an earlier notice is required. Conversely, do not present an ordinary site email as a compliant notice without reviewing the contract. The register should show the assessment, action and evidence of issue where applicable.

Keep entitlement, valuation and time assessment as separate review outcomes. An event can be well documented while its contractual consequence remains disputed. That is a legitimate status and should remain visible instead of being forced into an approved/rejected checkbox too early.

Document the alternatives considered, decisions made and actions taken. The team may resequence work, move resources, seek clarification or arrange temporary access. Record who decided, when and on what assumptions.

Show the effect of the response where evidence supports it. If a crew moved to another front, record the work performed and any mobilisation or productivity consequences. Do not assume that redeployment eliminated all impact, or that idle time automatically represents a recoverable cost.

Mitigation records are useful even when a claim is never pursued. They explain how the project managed disruption and help future planning. They also prevent later discussions from relying only on memories of what might have been possible.

Link daily reports, photographs, correspondence, instructions, drawing status, resource records and relevant schedule versions. Use stable references and dates. A folder containing hundreds of files is less useful than a short event chronology explaining why each item matters.

Preserve original records and add corrections transparently. If a date or description is revised after review, retain the earlier entry and the reason. Avoid rewriting contemporaneous records to match a later claim narrative.

Protect personal and commercially sensitive information through appropriate access controls. The register needs enough evidence for authorised review, not unrestricted circulation of every message or personnel detail connected with the event.

Choose a resolved hindrance and ask a planner who was not present to reconstruct the affected period and work. Ask a commercial reviewer to identify the relevant notice assessment and communications. Missing links will reveal where the capture process needs improvement.

Test an event with no completion impact, two overlapping events and an event that changes location over time. The register should support all three without forcing a standard number of delay days. Review the age of events awaiting analysis so evidence does not become harder to obtain.

A strong hindrance register gives the project a trustworthy chronology and a clear next action. Schedule effect and contractual consequence can then be assessed against evidence rather than inferred from a count of event days.

1. Capture the event, location, timing and affected work promptly.
2. Preserve overlapping events as separate, linked records.
3. Route notice questions to the authorised reviewer without delay.
4. Record mitigation and the work that remained possible.
5. Close factual, schedule and commercial reviews through their own evidence.