Editorial standards

Technical content should earn trust.

ORQIV publishes project-controls guidance to help EPC and construction teams make better-informed decisions. This policy explains how public technical content is created, reviewed, localized, corrected and kept separate from project-specific professional authority.

Last reviewed: 11 September 2026 · Editorial owner: ORQIV Project Controls Editorial Team
01

Practical project-controls focus

ORQIV content is written for EPC and construction project-controls work. Guidance should help readers understand planning, schedule assurance, earned value, QS, procurement, field assurance, claims evidence, reporting and governed AI without presenting marketing claims as technical facts.

02

Evidence before assertion

Where a topic depends on a standard, contract, law, vendor specification or current external fact, the source should be checked before publication. When a conclusion depends on project-specific records, the content states that limitation instead of inventing evidence.

03

Technical review

Technical guidance is reviewed for terminology, formula meaning, workflow logic, limitations and consistency with accepted project-controls practice. Review does not convert general information into project-specific engineering, legal, contractual or safety advice.

04

Human authority

AI may assist research, drafting, translation or formatting. Material technical statements remain subject to human review, and ORQIV does not present an AI-generated conclusion as contractual entitlement, engineering approval or safety authorization.

05

Bilingual integrity

English and Arabic pages are maintained as equivalent topic resources. Arabic content is localized for meaning and professional terminology rather than treated as a literal word-for-word translation when that would reduce clarity.

06

Corrections and updates

Pages are updated when material errors are found, when product capabilities materially change or when a technical topic requires clarification. Publication and review dates are shown where useful. Readers can report an issue through the official support channel.

Report a correction

If you find a material technical error, unclear statement or outdated public page, send the page URL and the issue to Support@orqiv.com.