Delay-event register
Record the event, dates, owner, affected work fronts, references and current status without losing the original chronology as the issue develops.
Construction claims · delay · EOT
Construction claims and EOT control built around evidence chronology.
ORQIV connects delay events, notices, Primavera P6 schedule status, correspondence, approvals, documents, procurement, field evidence and mitigation actions in one governed record. The objective is to preserve what happened and when, so planners, commercial teams and management can evaluate delay and EOT issues from contemporaneous evidence instead of reconstructing the story months later.
A claims record should preserve the timeline, not just the final narrative.
A credible delay record normally depends on multiple evidence streams. ORQIV keeps those streams connected while leaving contractual interpretation and entitlement with the authorized project professionals.
Notice and correspondence traceability
Keep notices, letters, RFIs, instructions, meeting records and responses connected to the event so the project team can see what was communicated, when and by whom.
Primavera P6 schedule evidence
Connect the event to relevant activities, milestones, critical or near-critical paths, total float, data-date status and the schedule version that existed when the event was assessed.
Approvals and decision history
Track drawing, submittal, material, access and instruction approvals that may influence the event, with owners, due dates and evidence rather than retrospective memory.
Mitigation and recovery actions
Preserve mitigation options, recovery measures, decisions and follow-up so later analysis can distinguish the event from the actions taken to reduce its effect.
Evidence package readiness
Link contemporaneous records such as daily reports, photographs, procurement records, quantity evidence and document revisions to the same event chronology.
Separate delay evidence from entitlement.
A schedule movement can be factual while entitlement still depends on the contract, notice requirements, causation, concurrency, mitigation, responsibility and applicable rules. ORQIV therefore treats claims intelligence as an evidence and project-controls workflow, not as an automated legal opinion.
For Saudi project context, the Expenditure & Projects Efficiency Authority publishes a procedural guide for claims related to project schedules, including considerations around delay-analysis methods and concurrent delay. ORQIV uses such public guidance only as contextual reference; project-specific contractual assessment remains separate.
EXPRO — Schedule Claims Procedural Guide ↗Construction Claims & EOT FAQ
What should construction claims software control?
It should help organize delay events, notices, correspondence, schedule evidence, approvals, records, mitigation and decision chronology. It should not automatically decide contractual entitlement.
Can ORQIV support Extension of Time analysis?
ORQIV is designed to organize EOT-support evidence and schedule context, including event chronology and Primavera P6 references. The selected delay-analysis method and entitlement remain project-specific professional and contractual determinations.
Why is the data date important in delay analysis?
A schedule should be interpreted using the status information and logic applicable to the relevant period. Using a later schedule without preserving the earlier status can distort what was actually known and driving at the time.
Does a delay event automatically justify an EOT?
No. Delay occurrence, schedule effect and contractual entitlement are different questions. Contract terms, notices, causation, concurrency, mitigation and applicable requirements still need professional review.
Can claims evidence be connected to procurement and documents?
Yes. ORQIV is designed to keep schedule, procurement, approvals, document control, field records, commercial change and claims-support evidence in one governed project context.