Define the variation being reviewed
A Dubai project file may contain several overlapping changes described by different names. Give each alleged variation a stable reference and record the work said to have changed.
Identify the relevant contract, amendments, and instructions. The review should follow the actual agreement and applicable law, not assume that a familiar standard form applies unchanged.
Build the evidence sequence
Collect the instruction, notice, quotation, response, approval, site record, and payment material. Record dates and participants with source references.
Keep the date an event occurred distinct from the date it was recorded. Missing documents should remain visible as evidence gaps.
Test an informal instruction
Suppose a meeting note records a request to change a specification, while the formal approval appears later or is absent. The chronology should show both facts without deciding that the meeting note necessarily authorised the work.
Ask counsel to assess the contractual effect and the project team to confirm what happened. Do not convert a sequence of events into a conclusion about entitlement without that review.
Separate entitlement and amount
Identify the basis claimed for additional time or payment, then review the supporting valuation separately. A well-supported cost figure does not by itself establish a right to recover it.
Where expert input is needed, provide the source records and assumptions. Keep technical calculations with the qualified reviewer.
Prepare the issue file
Give the team the event sequence, relevant clauses, evidence gaps, and questions for legal or technical review. Record any agreed position and its source.
Use the same structure for later variations while preserving the facts of each one. A portfolio matrix helps comparison only if it does not flatten distinct instructions and approvals into a generic status.
Sources and next steps
This is an editorial workflow guide for legal professionals. The suggested checks are our practical recommendations, not a statement that a regulator requires a particular software workflow.
Explore Timeline Builder and Review Matrix, or review Judicio's regional coverage and limitations. Check the underlying source and your organisation's approved process before relying on an output.