Independent review of design packages, cost estimates and contracts against the building codes of your region. Conflicts between disciplines, unsupported quantities and permit risks are identified before they affect the budget, the schedule or the loan.
Design, cost and contract documentsEach party reads the same documents for a different reason. Select your role to see the tasks we cover.
Select a stage to see which documents are reviewed and what is checked.
For banks and other project lenders: independent technical review of the borrower's design and cost documents before the credit decision and during the facility, without building an in-house technical team.
Financed projectsCheck the design package and the cost estimate of a project against the code framework of its region before you commit.
The developer shares a project with the lender account. The lender sees the review conclusions, and cannot change them.
Financial monitoring view with the conclusions of all shared projects: critical findings first, one place for the credit file.
Pay applications and change orders can be reviewed before a disbursement is approved.
Quantities, unit rates, duplicated items and markups in the cost estimate and the bill of quantities.
Americas, Europe and Asia-Pacific projects are reviewed against their own codes, with the regional lending context in view.
Create a lender account, ask the developer to share a project, and open its conclusion from the financial monitoring view. Each review keeps its findings, severity and code references.
Open the cabinet →Listed for orientation: regulators and rules that shape construction lending in each region, next to the codes used in the technical review. Your credit policy and local counsel prevail; MEXUM does not give legal or financial advice.
Pick a sample document. The conclusion lists each finding, its severity and the reference behind it.
Tap a document type to see what it covers.
Photographs: Pexels.
Prices are in US dollars. A single trial review needs no subscription; plans cover a set number of reviews per project.
One document, one-time
Projects of 500–5,000 sq m
Projects of 5,000–50,000 sq m
Developers and large projects
Everything happens in your account: upload, review, conclusion and a place to keep it.
Choose the region of your project so that the right code framework is used.
PDF, DOCX, DOC, XLSX or XLS, up to 50 MB per file.
Fifteen disciplines read the documents together and compare them with each other and with the code.
A PDF within 48 hours: findings by severity, code references and a short plain-language summary.
If your question is not here, ask Victoria in the chat.
A reasoned conclusion in PDF is delivered within 48 hours.
