When a project selects a document-management system, Procore and other global platforms often appear alongside systems built for the Arabic-native workflow, such as Mutamad. Brand recognition and feature-list length do not settle that comparison. The useful question is how well each option executes the project’s requirements and what it costs to close any gap between the system and the approved procedure.

Start with the procedure, not the product name

Turn the contract and document-control procedure into testable scenarios before any demonstration. Create a SUB, route it from contractor to consultant, issue an outcome under the project’s A/B/C/D matrix, revise it, and export its history. Repeat the exercise with a MIR, COR, and NCR. The committee can then compare observable work rather than sales claims.

What should the selection committee agree first?

Not every organisation faces the same decision. A contractor running one project has different priorities from a group controlling a portfolio across several countries. Before requesting proposals, agree the weight of each criterion and identify who has authority to accept it.

How closely the contractor → consultant → owner route matches the contract’s authority matrix.
Whether Arabic-speaking teams can create, review, search, and export the record without a side process or duplicate entry.
How MIR, SUB, COR, NCR, PQD, and CPR records are controlled, numbered, and revised.
Whether the project’s definitions of A/B/C/D can preserve both the outcome and the comment on the governing revision.
The integration, identity, hosting, retention, and export requirements imposed by the organisation or contract.
Expected total cost as user, project, supplier, and data volumes change.

An Arabic interface or an Arabic-native record?

Translated buttons do not answer the language question by themselves. Test the fields people actually complete, form direction, Arabic-name search, number and attachment order, PDF output, and the register. A translated interface can read correctly while the underlying procedure still assumes an English record that the project team must copy or explain in Arabic.

Test the approval chain defined by the contract

A committee should not assume that “configurable workflow” means its required route is ready or simple to configure. Ask every candidate to perform a real case in front of users: who opens the record, who can route it, who can respond, how resubmission appears, and when the owner sees the history. Record manual steps and exceptions beside the result.

Compare forms as connected records

Accepting a file labelled MIR or SUB is not enough. Inspect its controlled number, revision, status, attachments, current owner, and links to related records. For example, a reviewer should be able to follow an NCR into its corrective action, correspondence, and prior history without rebuilding those relationships in an external register.

How do you compare pricing models without assumptions?

A proposal may price by project, user, module, data volume, or a combination. Do not attribute a current model to any vendor from memory. Request a written offer that defines a counted user, supplier and consultant access, storage limits, archived-project cost, support, configuration, and integration, then calculate at least three growth scenarios.

When is a global platform the right call?

A global platform may be the logical choice when the contract mandates a particular system, when an organisation has already standardised a multi-country portfolio and accepts the adaptation work, or when central integration and governance requirements outweigh rapid setup of the native procedure. In those cases, identify language and workflow gaps explicitly and assign an owner and budget to close them.

When should an Arabic-native system take priority?

An Arabic-native system deserves priority when the Arabic record drives daily work, control centres on the contractor–consultant–owner chain and its established forms, and the project must onboard many parties without redesigning its procedure. “Arabic-native” is not proof by itself: apply the same numbering, permission, retention, and export tests.

Decide through one controlled project trial

Give every candidate the same data, roles, and test window, then ask contractor, consultant, and document-control users to score the result. Start with the document-management selection guide, read why Mutamad was built, or book a working demo to run the scenario against your project.