blog img

An Architect of Record (AOR) appointment should identify the architectural work a professional team will undertake, the documents it will deliver and its interfaces with other project parties. For developers and project coordinators, the practical starting point is a written scope that distinguishes design, submission coordination, construction involvement and handover responsibilities.

In Saudi Arabia, project terminology must also be checked against the actual approval route and professional appointments. The label “AOR” alone does not establish who is the appointed design engineering office, supervising office or contractor. This guide explains how to clarify those boundaries and organise project records without promising permits, construction quality or a particular legal outcome.

Ask the proposed team to describe its services through specific activities and deliverables. Identify the project stages covered, the disciplines included and the information others must provide. Record whether the appointment includes design development, architectural documentation, submission support, responses to comments or defined construction-stage services.

Official Saudi building-permit guidance distinguishes the design engineering office, supervising engineering office and construction contractor. It describes a process involving review and possible return of comments. That published route provides context for identifying project parties; the responsible professional must confirm the requirements applicable to the particular building and submission. Reference: official building-permit service guidance.

Check the proposed office’s relevant professional eligibility and the scope of its appointment through the applicable current verification routes. The engineering-practice implementing regulations address professional accreditation and office licensing. Avoid treating a brochure title or an individual’s job description as sufficient evidence of authority for every engineering task. Reference: engineering-practice implementing regulations. Check current applicability before reliance.

The developer should ask who will provide missing surveys, specialist designs, owner decisions and existing approval records. Set a process for accepting those inputs and flagging gaps. Agree how additional work, design changes and extended project duration will be addressed. These are appointment questions, not a substitute for qualified advice on contractual or statutory obligations.

For planning purposes, the design architect may lead the architectural concept and develop the intended spatial and visual requirements. The actual appointment should specify the drawings, models, specifications and decisions that the team produces. Do not reduce the role to appearance alone or assume it has no technical responsibilities. Related service: architecture.

If another team develops or adapts the design, identify the agreed design baseline and the process for resolving departures from it. Record who answers questions about design intent and who authorises changes on the client side. Keep any professional review or authority requirements separate from the developer’s commercial approval.

An AOR scope may include defined architectural documentation, technical review and submission coordination. MTC’s service page describes these categories of work. Confirm which activities are included for the particular project and how they interface with the appointed offices and specialist designers. Do not extend that company description into an approval guarantee.

Clarify who checks the information received, what the check covers and which items require specialist input. Identify the party preparing each deliverable and the person designated to review it. A statement that a document has been “reviewed” is incomplete without its purpose, scope and recorded outcome.

The contractor’s document submissions, construction activities and record information should be defined in its contract and the project procedures. State how requests for information, proposed substitutions and site changes reach the appropriate reviewer. Avoid assuming that a contractor can alter a design because a coordination drawing is convenient to build.

Identify the supervising office separately. Ask what site attendance, inspection records and reporting are included in its appointment and whether the AOR team has any additional agreed role. This article does not allocate liability between those parties. Obtain qualified review where professional duties or contract boundaries are uncertain.

The following table is a coordination example, not a legal allocation of duties. Replace each suggested activity with the appointed organisation, named contact and agreed deliverable. A project may combine services within one organisation, but the separate activities should remain visible in the responsibility record.

ActivityDesign architectAOR scopeContractorOther appointment
Design inputsDefine intended designReview received inputs within scopeProvide agreed site informationConfirm specialist inputs
Coordinated drawingsDevelop appointed design contentPrepare/review assigned packageRaise buildability queriesReview discipline interfaces
Submission commentsRespond on own designCoordinate if appointedProvide requested contractor inputRelevant author resolves comment
Construction queriesClarify design intentReview architectural scopeSubmit referenced querySupervising/specialist roles defined
Proposed changesReview design impactCoordinate assigned documentationSubmit proposal before implementationConfirm required review route
Handover recordsProvide appointed design recordsProvide assigned register and documentsProvide agreed record informationReviewer and recipient nominated

For each row, distinguish preparation, review, submission and acceptance. Authority approval, professional review, contractor coordination and client acceptance serve different purposes; do not use one generic “approved” status for all of them. Identify the applicable reviewer and the evidence needed to close each action.

Include structural, MEP, fire-safety and other specialist parties wherever their work interfaces with the architectural package. The AOR appointment should not silently absorb those disciplines. Ask the project lead to resolve gaps and overlapping instructions through a written coordination decision that is reflected in the relevant appointments. Coordinate this through the agreed project management scope.

Agree a document register with unique references, revision identifiers, issue dates and intended uses. Identify the current issue for each purpose and record which earlier versions have been superseded. Do not assume the latest file received by email is authorised for construction or suitable for an authority submission.

Keep models, drawings and specifications aligned with the agreed issue. Ask each author to identify what changed and which other documents may be affected. Where information conflicts, record a query and assign its resolution before the team relies on it for the affected work.

Nominate who coordinates submissions and who responds to each technical comment. Maintain a comment record linking the request, responsible author, response, revised document and resulting status. An internal response marked complete does not establish that the relevant authority has accepted it.

The official permit service describes design review and the return of observations for correction. Avoid promising that an AOR appointment removes this review process or guarantees its duration. Confirm current submission requirements and any additional approvals with the qualified professional responsible for the actual project route.

Use a documented route for construction questions. Include the location, affected drawing references, reason for the query and the decision needed. Assign it to the relevant designer rather than asking a single coordinator to answer beyond their appointment or discipline.

For proposed changes, record the architectural and specialist impacts, required reviews and any effect on existing submissions. Identify who can authorise implementation under the project arrangements. Keep the accepted change linked to revised documents and record information. Do not treat a site conversation or an unreviewed mark-up as equivalent to the required formal decision.

Construction Queries And Changes

Define the handover pack early enough for the parties to produce it during the project. A suggested contractual register may include current architectural drawings, submission correspondence, accepted design revisions, construction queries and contractor record information. The required contents depend on the appointments and project requirements; this list is not a universal statutory checklist.

Suggested recordAuthor and review routeStatus fields to retain
Architectural drawing setDocument author / assigned reviewerReference, revision and intended use
Submission recordAppointed coordinatorReceipt, decision and open conditions
Design changesRelevant designer / project reviewerDecision and affected document list
Contractor record informationContractor / agreed reviewerVerification status and limitations
Open itemsNamed action owner / recipientDue date and closure evidence

For each document, identify its author, designated reviewer, recipient and required format. Add the reference, revision, status and any outstanding action. Distinguish a design issue from contractor record information describing what was installed. Agree the verification process and state any limitations rather than relabelling a design drawing “as built” without supporting information.

Keep authority decisions and conditions identifiable. A submission receipt is evidence of submission, not approval. An approval record may include conditions or a limited scope that the receiving team needs to understand. The responsible professional should confirm which records are applicable and how unresolved conditions affect the next project stage.

Agree who receives editable files, published documents and linked model information, subject to the relevant contract and information rights. Identify software or file-format dependencies and check that the recipient can access the agreed deliverables. Avoid promising the transfer of native files or unrestricted reuse without confirming the appointment terms.

At handover, list outstanding documents and issues individually. Assign an owner, target date and required closure evidence. Record who can accept the completed item and how the register will be updated. Do not describe an incomplete pack as closed merely because files have been uploaded to a folder.

The receiving developer or operating team should know which documents are current and whom to contact about remaining questions. Transfer the final register alongside the files. A controlled record of status and limitations is more useful than a large collection of unlabelled drawings with no clear ownership.

Share the project stage, design team structure, available drawings, known submission requirements and intended construction programme with MTC. Ask for an appointment proposal identifying its architectural deliverables, interfaces, exclusions and construction-stage involvement. Confirm the qualified professionals and relevant office roles for the project.

Review MTC’s Architect of Record service page to begin that scope discussion. Ask how the document register, review process and handover responsibilities will be recorded. Keep regulatory statements and contractual responsibilities subject to qualified Saudi professional review.

Does Appointing An AOR Automatically Include Site Supervision?

The AOR label alone does not establish the supervision scope. Check the actual appointments and identify the supervising office required by the applicable project route. Ask what site attendance, inspection records and reporting are included, and distinguish those activities from any separate architectural coordination or review services in the AOR proposal.

Can The Design Architect And AOR Be The Same Organisation?

A project may propose one organisation for several activities, subject to the relevant eligibility and appointment requirements. Record the separate deliverables and review responsibilities even where the organisation is the same. Have the responsible professional confirm the arrangement for the project rather than assuming that a company’s service list establishes every required role.

Who Responds When An Authority Requests A Design Revision?

The project should nominate a submission coordinator and assign technical responses to the relevant document authors or appointed professionals. Record the comment, response and revised issue, then track the resulting authority status. The person sending the package should not be assumed to hold responsibility for every specialist design within it.

Are Contractor Record Drawings The Same As Approved Design Drawings?

They serve different information purposes. A design issue describes the intended design at a stated stage; contractor record information should reflect the completed work through the agreed verification process. Keep their references, status and limitations clear. A filename or an “as built” label alone does not establish that the information was checked.

What Should Happen When Handover Documents Remain Outstanding?

Keep an open register identifying each missing or incomplete record, its responsible party, target date and closure evidence. Identify who may accept the completed item and whether it affects a later project step. Obtain professional advice where approval conditions or contractual completion requirements are involved; avoid implying acceptance through an undocumented file transfer.

Architect of Record (AOR) Services in KSA – Ensuring Compliance and Quality

Leave a Reply