Construction Contracts: A Technical Checklist Before Signing

Construction Contracts: A Technical Checklist Before Signing

A clear idea of your project still needs documents people can build from and review. “Complete finishing” leaves important questions unanswered. Which drawings will be used? What work is included? Who selects materials? How will a decision that changes after work starts be handled?

This is a technical and organisational discussion checklist. It is not a contract template, an explanation of Egyptian law or a substitute for legal and technical advice suited to the project. An item in this guide is not an Al Mansour commitment. The agreement, reviewed by its parties, defines their obligations.

1. Which documents describe the work?

Identify the intended drawings, specifications, schedules and appendices by version and date. A filename may not be enough where several versions exist.

Raise any difference between a drawing and an item description before signing. Ask the legal reviewer how the agreement handles conflicts between documents rather than assuming an order of precedence. Technical review can identify a discrepancy; its contractual effect needs appropriate drafting and advice.

2. Where does the scope begin and end?

Review the work room by room or system by system, as appropriate. Record exclusions and open decisions as well as inclusions.

A refurbishment may need clear boundaries between removal, repair, preparation and new installation. For supply and installation, clarify materials, transport, storage and necessary accessories. These are questions to establish responsibilities, not assumptions that every offer includes them.

3. Who decides and approves?

Identify the people or roles involved in design, materials, changes and inspections. If someone will act for you, discuss the scope of that authority with the legal reviewer. Membership of a message group should not be treated as a substitute for that discussion.

Organisationally, everyone should know where decisions are recorded and which document version to use. This article does not determine whether a particular signature or message is legally effective. That depends on the agreement and circumstances.

4. Where are unresolved decisions recorded?

If selections remain open when the agreement is prepared, identify an appendix that records them and the role responsible for approving their completion. This is not another comparison of alternatives. Its purpose is to prevent an unresolved field appearing as a final specification in the signed version.

5. How is the programme described?

Look beyond the completion date. Ask about starting conditions, linked activities and what must be checked before hidden work is covered or the next activity begins. Establish how programme updates and their reasons will be recorded.

Where a duration is proposed, ask what scope and assumptions it covers. This guide provides no standard durations and confirms no company-specific completion period. The aim is a programme people can understand and monitor, not simply an attractive early date.

6. Where are pricing and change procedures defined?

Identify the agreement document defining the pricing basis and change approval process, and ask the legal adviser to review the effect of that reference. For an explanation of reading items and quantities, use the finishing bill of quantities guide rather than redefining them in the agreement.

7. What will be checked, and by whom?

Work with the appropriate specialist to identify checks needed before concealment or later activities. Agree which records or test results fit those works. This article does not prescribe a universal test schedule.

Where photographs or reports are requested, define their purpose and what they cannot establish alone. A photograph does not replace specialist inspection or a suitable test. Nor does a contractor having photographs establish an obligation to deliver a particular file unless agreed.

8. How are inspection and handover described?

Discuss the inspection scope, how observations will be recorded, who follows up corrections and which documents are to be delivered if agreed. Ask the legal reviewer to check the relationship with payments. We do not infer a right to withhold a sum or a particular percentage here.

Where warranty cover is proposed, read its scope, exclusions, conditions and responsible party. Do not assume a duration or coverage from a general advertisement. The word “warranty” alone does not define the obligation.

Prepare for the discussion

Collect:

  • Current project documents, identified by version and date.
  • Required work, exclusions and unresolved choices.
  • Questions about responsibilities, approvals and supply.
  • Questions about the programme, changes, checks and handover.
  • Points needing independent legal advice rather than a technical discussion alone.

Ask for a specific answer to each point. Then check that the final documents reflect what was agreed. Do not fill a missing answer with an assumption or an untraceable verbal promise.

Frequently asked questions

Can this article be used as a contract?

No. It is a technical and organisational preparation checklist. Drafting the agreement, understanding its effect and checking its suitability require independent legal and technical review.

Does every project need the same documents?

The detail should suit the scope, stage and risks. Discuss this with specialists rather than copying another project's document package without review.

What if materials have not been selected?

Make the open choices visible. Discuss their pricing basis, approval process and programme effects. A temporary assumption should not be treated as a final specification.

Next step

Prepare your project file and questions before discussing scope with Al Mansour. Use the published service pages and contact details to identify the work required, then have the proposed agreement reviewed by appropriate specialists before committing.

Sources and limits

These are suggested preparation questions, not statements of legal rules or company obligations. For published service scope:

Reviewed: 23 October 2026.

Related articles

Need advice for your project? Have a question about your project? Talk to Our Team