New Standards compliance
Owners, PMC firms and government PMOs are expected to follow internationally recognised project and contract management practice. PMWEB turns that practice into records, workflows and reports, so every step is done the same way, approved by the right person and kept as evidence. Below, process by process, is how PMWEB supports three of them, and where each one is shown in our articles.
The RICS guidance for contract administrators and quantity surveyors, from commencement to the final account and ICMS 3 cost reporting.
The CMAA Construction Management Standards of Practice, function by function, for PMC firms and owners’ representatives.
The National Project Management Office framework for government, semi-government and PIF entities in Saudi Arabia.
Working to another standard or framework? Tell us which one, and we will show how PMWEB supports it, process by process.
Request a standardEach mapping shows how PMWEB supports the practice a standard describes. It is not a certification. Compliance stays with the organisation, its people and its procedures, and PMWEB is configured to those procedures. CMCS and PMWEB are not affiliated with or endorsed by RICS, CMAA or Mashroat.
RICS · Contract administration
Based on the RICS Contract Administration Services schedule (2022) and RICS guidance on change control, interim valuations, extensions of time, loss and expense, the final account and ICMS 3. Open a stage to see each process, the PMWEB record, how it is delivered and the article that shows it.
| RICS process | PMWEB record | How PMWEB supports it | Delivery | Shown in |
|---|---|---|---|---|
| Collect background information and client constraintsObtain the client’s background information and constraints before the contract starts. | Projects, Document Manager, Issues | Project record holds client data and constraints; supporting documents filed in a governed folder structure; open constraints logged as Issues. | Out of the box | Art. 2 |
| Agree the contract administrator’s authority to instructAgree and record the level of authority the CA has to instruct works. | Workflow configuration (DoA matrix); pre-commencement checklist | CA spending authority per instruction held on the commencement record and used as a workflow condition. | Workflow / DoA | Art. 2Art. 9 |
| Clarify team roles and responsibilitiesClarify the roles of the client, consultants and contractor. | Companies & Contacts registers; roles and security | Parties held once in the Companies register; workflows route to roles, not named people, so changes of staff do not break the process. | Out of the box | Art. 2 |
| Pre-commencement checklistConfirm the documents and information required before the works start are in place. | Pre-commencement checklist (Adaptive Form) | Header plus checklist grid: each item with evidence reference, date obtained, PMWEB location and status; mandatory lines block approval while open. | Adaptive Form | Art. 2 |
| Professional indemnity and project insurancesConfirm PI insurance and advise on project insurances. | Insurances and securities register (Adaptive Form) | One record per policy with insurer, cover, expiry and renewal evidence; linked to the commitment. | Adaptive Form | Art. 2Art. 10 |
| Performance security, advance payment guarantee, parent company guaranteeObtain and track the securities required by the contract. | Insurances and securities register (Adaptive Form) | One record per instrument: type, issuer, amount, validity, release conditions; advance payment guarantee reduces as advance is recovered. | Adaptive Form | Art. 2Art. 5 |
| Letters of acceptance, notice to commence, letters of intentIssue the formal commencement documents and control the use of letters of intent. | Word letter templates merged from the Commitment | Letters generated from the contract record so names, values and dates match the commitment. | Out of the box | Art. 2 |
| Permits, consents and statutory obligationsEstablish planning, building regulation and other statutory obligations. | Permits and consents register (Custom Form); Document Manager | Register of each permit with authority, reference, validity and the document that proves it. | Custom Form | Art. 2 |
| RICS process | PMWEB record | How PMWEB supports it | Delivery | Shown in |
|---|---|---|---|---|
| Establish the procurement routeAdvise on the procurement route, form of contract and risk allocation. | Procurement module; Commitments (contract type, form of contract) | Procurement route and form of contract recorded on the bid package and carried into the commitment. | Out of the box | Art. 2 |
| Tender documents and invited biddersIssue consistent tender documents to the selected bidders. | Procurement: bid packages | Bid package holds tender documents, BOQ and invited bidders; documents released together. | Out of the box | Art. 2 |
| Tender clarifications and addendaManage bidder queries and addenda fairly and on record. | Procurement: pre-bid records | Clarifications and addenda held as records and shared with all bidders. | Out of the box | Art. 2 |
| Receipt and comparison of bidsCompare bids on a like-for-like basis. | Procurement: online bidding, bid levelling | Priced submissions received online and compared line by line; bids can be structured on ICMS 3 codes. | Out of the box | Art. 2Art. 8 |
| Contract awardAward the contract within approved authority. | Procurement award; Commitments | On award the package becomes a Commitment with its schedule of values, each line coded to the cost breakdown structure. | Out of the box | Art. 2Art. 9 |
| Contract record and schedule of valuesHold the contract sum and its breakdown as the basis for valuation and change. | Commitments | Contractor, contract type, form of contract, dates, retention and payment terms on one record; line items form the schedule of values. | Out of the box | Art. 2 |
| RICS process | PMWEB record | How PMWEB supports it | Delivery | Shown in |
|---|---|---|---|---|
| Initial programmePrepare an initial programme for the project. | Scheduling | Programme built in PMWEB Scheduling or imported from Primavera P6 or Microsoft Project. | Out of the box | Art. 6 |
| Obtain and review the contractor’s programmeObtain the contractor’s programme and review it for completeness and sequencing. | Scheduling; programme review checklist (Custom Form) | Contractor programme imported; review checklist records each check and the outcome. | Custom Form | Art. 6 |
| Monitor progress and advise on delay riskMonitor progress against programme and advise on delay risk and expected completion. | Scheduling updates; Power BI time dashboard | Progress updates compared to baseline; forecast completion and slippage visible to the employer. | Reporting | Art. 6Art. 10 |
| Extension of time applicationsAssess extensions of time against the contract, with notice, evidence and a reasoned determination. | EOT application (Adaptive Form); Scheduling (fragnets); notices register | One record per application: relevant event, linked notice, evidence checklist, delay analysis method, fragnet, CA assessment and determination; assessment sections restricted to the CA. | Adaptive Form | Art. 6Art. 10 |
| AccelerationAdvise on the cost and contractual effect of an acceleration instruction. | Acceleration record (Adaptive Form) | Target dates, contractor quotation, schedule fragnet and CA advice held on one record linked to the change chain. | Adaptive Form | Art. 4 |
| Delay damagesTrack entitlement to damages for delay alongside extensions granted. | Scheduling; EOT records; progress invoices | Completion date adjusted by granted EOTs; delay damages handled under the contract and shown separately on the certificate where applicable. | Custom Form | Art. 5Art. 6 |
| RICS process | PMWEB record | How PMWEB supports it | Delivery | Shown in |
|---|---|---|---|---|
| Daily recordsKeep dated daily records of labour, plant, weather, progress and events. | Daily Reports | Each daily report is a dated, approved record of manpower, equipment, weather, work in progress, visitors and incidents. | Out of the box | Art. 3 |
| Site visits and inspectionsRecord site inspections with date, attendees, observations and actions. | Inspections (checklist-based) | Inspections run on configured checklists with photographs and pass/fail results. | Out of the box | Art. 3 |
| Meetings and minutesChair and record project meetings and the actions arising. | Meeting Minutes; Action Items | Attendees, agenda, decisions and actions on one record; each action has an owner, due date and can link to a schedule activity. | Out of the box | Art. 3 |
| Contractor queries (RFIs)Answer contractor queries promptly and involve the CA where the answer may affect cost, time or the contract. | RFIs | Each RFI carries flags for cost, time and contractual impact; when set, the CA is added to the review automatically. | Out of the box | Art. 3 |
| Site directions and contract instructionsIssue instructions in writing, and convert site directions into formal contract instructions. | Site direction and contract instruction (Adaptive Form) | Site direction recorded on site and converted into a numbered contract instruction linked to the change chain. | Adaptive Form | Art. 3 |
| Notices and time barsTrack contractual notices and their time limits. | Notices and time-bar register (Custom Form) | One line per notice: clause, event, date of awareness, date notified, deadline and status. | Custom Form | Art. 3Art. 7 |
| CorrespondenceKeep letters and e-mails with the contract record. | Correspondence | Letters and e-mails filed to the relevant contract and records. | Out of the box | Art. 3 |
| Submittals (drawings, materials, samples)Review contractor submissions against the contract. | Submittals and submittal sets | Submittals with review codes, revisions and reviewer comments. | Out of the box | Art. 3 |
| Health and safetyComply with health and safety obligations and monitor the contractor. | Safety | Safety observations, incidents and inspections recorded as structured records. | Out of the box | Art. 3 |
| RICS process | PMWEB record | How PMWEB supports it | Delivery | Shown in |
|---|---|---|---|---|
| Set up change control proceduresEstablish a change control procedure so the employer decides with full information before instructing change. | Change Events; Potential Change Orders; Budget Requests; Commitment Change Orders | Four connected records: identify (Change Event), price (PCO), fund (Budget Request), commit (Change Order). | Out of the box | Art. 4 |
| Identify and record change eventsRecord each potential change once, with its budget and cost impact. | Change Events | One event carries the owner-side budget impact and the cost impact on every affected contract. | Out of the box | Art. 4 |
| Price change before instructionObtain and assess the price of a change before it is instructed. | Potential Change Orders (PCO) | Proposed and assessed value side by side; each line records its basis of valuation (bill rate, star rate, daywork, quotation). | Out of the box | Art. 4 |
| Fund change from contingencyKeep the employer informed of the effect of change on budget and contingency. | Budget Requests | Moves money from contingency or risk allowance to the cost code affected. | Out of the box | Art. 4 |
| Formal variation (change order)Value and formalise variations under the contract rules. | Commitment Change Orders | Updates the revised contract sum and becomes billable in the next valuation. | Out of the box | Art. 4 |
| Omissions and savingsShow omissions separately and keep them out of contingency. | Change Orders; Budget Requests | Omissions recorded as negative change; released budget returns only through an approved budget request. | Out of the box | Art. 4 |
| Provisional sumsSpend provisional sums only by instruction and omit unused amounts formally. | Commitment lines; Change Orders | Provisional sum lines tracked against instructions; balance omitted by change order. | Custom Form | Art. 4 |
| DayworksAccept dayworks only on signed, timely sheets. | Daywork sheet (Custom Form) | Labour, plant and materials with CA signature, linked to the PCO line it supports. | Custom Form | Art. 4 |
| Running estimate of the final adjusted contract sumKeep a running record of the anticipated final account, including anticipated variations. | Change Control Register; Cost Worksheet | Approved, pending and anticipated change by category with net value and EOT days, from original to anticipated sum. | Reporting | Art. 4Art. 7 |
| Contractor-proposed changes and value engineeringAssess contractor proposals before they become instructions. | Contractor change proposal (Adaptive Form) | Proposal with the CA’s technical and commercial assessment, kept off the commercial record until accepted. | Adaptive Form | Art. 4 |
| RICS process | PMWEB record | How PMWEB supports it | Delivery | Shown in |
|---|---|---|---|---|
| Interim valuationValue work fairly and impartially under the contract. | Progress Invoices (against the Commitment) | Each line valued by measured quantity, schedule percent complete or assessment, with the method recorded. | Out of the box | Art. 5 |
| Variations in the valuationInclude approved variations in interim valuations. | Progress Invoices; Change Orders | Approved change orders appear automatically as billable lines. | Out of the box | Art. 4Art. 5 |
| Materials on and off sitePay for materials only with evidence of title, storage and insurance. | Materials evidence (Custom Form) | Evidence form linked to the valuation line: delivery, storage, insurance and title. | Custom Form | Art. 5 |
| RetentionDeduct and release retention under the contract. | Progress Invoices (retention) | Retention calculated per invoice and released at completion and end of the defects period. | Out of the box | Art. 5Art. 6 |
| Advance payment and recoveryRecover advance payments as the contract requires. | Progress Invoices; securities register | Advance recovered line by line; linked guarantee reduces accordingly. | Out of the box | Art. 5 |
| Certificate for paymentIssue certificates on time, showing how the amount was calculated. | Progress Invoices; SSRS certificate | Application and Certificate for Payment produced from the record, worded to the form of contract. | Out of the box | Art. 5Art. 10 |
| Certifying on time and continuityCertify within contractual periods, including when approvers are absent. | Workflow (durations, delegation) | Each step has an allowed duration; delegation to a named alternate with an end date. | Workflow / DoA | Art. 5Art. 9 |
| Other project costsAccount for costs not paid through the main contract. | Miscellaneous Invoices | Authority fees, utility charges and other costs captured against the cost breakdown structure. | Out of the box | Art. 5 |
| Payment statusConfirm that certified amounts were paid within the contractual period. | Payments; ERP integration | Payment status and date returned from the ERP to the contract record. | Integration | Art. 5Art. 10 |
| RICS process | PMWEB record | How PMWEB supports it | Delivery | Shown in |
|---|---|---|---|---|
| Practical / substantial completionCertify completion against defined criteria and prerequisites. | Completion certificates (Adaptive Form); Punch Lists | Certificate type, prerequisite checklist, decision and formal certificate on one record. | Adaptive Form | Art. 6 |
| Sectional completion and partial possessionHandle completion of sections or partial handover. | Completion certificates (Adaptive Form) | Same form with certificate type for section or part. | Adaptive Form | Art. 6 |
| Snagging and outstanding worksRecord outstanding works and snags at completion. | Punch Lists | Classified items (outstanding works, snagging) with location, responsible party and photographs. | Out of the box | Art. 6 |
| Defects during the rectification periodNotify and track defects until rectified. | Punch Lists (defect classification) | Defects notified to the contractor with the period for rectification. | Out of the box | Art. 6 |
| Release of retentionRelease retention at completion and at the end of the rectification period. | Progress Invoices (retention release) | Release lines generated at the agreed stages. | Out of the box | Art. 6 |
| RICS process | PMWEB record | How PMWEB supports it | Delivery | Shown in |
|---|---|---|---|---|
| Loss and expense claimsAscertain loss and expense separately from extensions of time. | Loss and expense claim (Adaptive Form) | Claim heads, evidence from daily records and notices, CA assessment and decision. | Adaptive Form | Art. 7 |
| Dispute registerRecord disputes and their route to resolution. | Dispute register (Adaptive Form) | Parties, contract reference, subject, value, route (negotiation, adjudication, arbitration) and status. | Adaptive Form | Art. 7 |
| Rolling final accountBuild the final account progressively during the works. | Cost Worksheet; Change Control Register | Contract sum, variations, provisional sums and claims brought together per contract and cost code. | Reporting | Art. 7 |
| Statement of final accountProduce the statement of final account in a clear structure. | Statement of final account (Custom Form) | Rolls up PMWEB records into the RICS final account structure. | Custom Form | Art. 7Art. 10 |
| Final account timescalesMeet contractual time limits for final account submissions. | Notices and time-bar register | Final account deadlines held as register lines. | Custom Form | Art. 7 |
| RICS process | PMWEB record | How PMWEB supports it | Delivery | Shown in |
|---|---|---|---|---|
| Cost reports to the clientPrepare regular cost reports. | Cost Worksheet; budgets; commitments; SSRS | Budget, commitments, changes, invoices and forecasts on one cost breakdown structure. | Reporting | Art. 8 |
| Cost breakdown structure coded to ICMS 3Report capital cost in a consistent, comparable structure. | Cost codes / CBS mapped to ICMS 3 | Every budget, commitment and invoice line carries a cost code mapped to ICMS 3. | Custom Form | Art. 8 |
| Adjusted contract sum and capital cost reportingReport the adjusted contract sum and total capital cost. | Commitments; Change Orders; Cost Worksheet | Original sum, approved and pending change and forecast final cost per contract. | Reporting | Art. 8 |
| Benchmarking across projectsCompare costs across projects on a common basis. | Portfolio reporting; Power BI | Projects coded to ICMS 3 attributes compared without re-coding. | Reporting | Art. 8 |
| Contingency and risk allowancesManage contingency and risk allowances transparently. | Budget lines; Budget Requests; Risk register | Contingency held as budget lines; drawdowns via budget requests linked to risks or changes. | Out of the box | Art. 4Art. 8 |
| RICS process | PMWEB record | How PMWEB supports it | Delivery | Shown in |
|---|---|---|---|---|
| Obtain the client’s decisionsObtain and record client decisions. | Workflow on every record | Each record type carries a business process: roles, durations, actions and conditions. | Workflow / DoA | Art. 9 |
| Delegation of Authority enforcementAct within delegated authority. | Business Process designer; DoA conditions by value | Approval route set by value and record type; the person whose authority covers the value must approve. | Workflow / DoA | Art. 9 |
| Allowed durations and overdue actionsAct promptly within contractual and internal timescales. | Workflow durations; workflow dashboard | Allowed days per step; overdue steps visible across all projects. | Workflow / DoA | Art. 9 |
| Audit trailKeep an accurate and accessible record of decisions. | All PMWEB records | Every action, comment and change is recorded with user and time. | Out of the box | Art. 1Art. 9 |
| Bespoke services and client-specific processesDeliver services specific to the appointment. | Custom Form Builder; Adaptive Forms | Client-specific registers, checklists and forms built as first-class PMWEB records. | Adaptive Form | All articles |
| RICS process | PMWEB record | How PMWEB supports it | Delivery | Shown in |
|---|---|---|---|---|
| Progress, quality and cost reports to the clientPrepare regular progress, quality and cost reports. | SSRS library (150+ reports); Power BI | Formal outputs from SSRS; decision dashboards in Power BI refreshed from live data. | Reporting | Art. 10 |
| Contractor master dataKeep contractor and vendor data consistent with finance. | Companies register; ERP integration | Contractor record synchronised with the ERP vendor master, including bank and tax details. | Integration | Art. 2Art. 10 |
| Certified amounts to financePass certified amounts to finance once, accurately. | Progress Invoices; ERP integration | Approved certificates posted to the ERP; payment details returned. | Integration | Art. 5Art. 10 |
| Management dashboards for the employerGive the employer timely management information. | Power BI inside PMWEB | KPIs such as EOT days pending, certificates due, securities expiring and change exposure. | Reporting | Art. 10 |
| RICS process | PMWEB record | How PMWEB supports it | Delivery | Shown in |
|---|---|---|---|---|
| Drawings, office files and photographsKeep project documents organised and controlled. | Document Manager; Drawings; Transmittals | Folder structure mirroring the handover format; version control and role-based access. | Out of the box | Art. 3 |
| Handover and archiveHand over complete records at completion. | Archive module; Document Manager | Archive exports the folder structure and records at close-out. | Out of the box | Art. 3 |
The complete RICS mapping as a spreadsheet. All 74 processes with the RICS expectation, workflow and DoA control, evidence and audit trail, standard outputs, RICS reference and article, plus a coverage summary.
CMAA · Construction management
The CMAA Construction Management Standards of Practice set out what a construction manager is expected to do in each function. Each PMC firm executes them its own way, and PMWEB is configured to the firm’s procedures, with the Standard as the reference.
| CMAA function | How PMWEB supports it | Delivery | Shown in |
|---|---|---|---|
| Delivery methodsRoles, responsibilities and approval routes defined for the delivery method: CM agency, CM at-risk, design-build or PPP. | Project set-up per delivery method: parties, roles and workflow routes; design packages reviewed against checklists that reference the owner’s requirements. | Workflow / DoA | Art. 2 |
| Project managementA CM Plan and procedures manual; meetings, correspondence and lessons learned managed consistently. | Each procedure becomes a record type, form, workflow, numbering rule, report or dashboard; meeting actions carry forward; the practice library is reused per mandate. | Custom Form | Art. 3 |
| Cost managementBudget, estimates, commitments, change, contingency and final cost reconciliation. | One linked cost model: budget, commitments, changes, actuals and forecast; the contingency log shows every drawdown, its reason and its approver. | Out of the box | Art. 4 |
| Time managementBaseline review, schedule updates, time impact analysis and extension decisions. | Schedules from Primavera P6 or MS Project; baselines and updates reviewed by workflow and archived with time impact analyses and extension decisions. | Integration | Art. 5 |
| Quality managementSubmittals, inspection and test plans, non-conformance and commissioning. | Inspection and test plans become checklists; each NCR records what, where, against which requirement and who is responsible; warranty and asset registers carry into operations. | Out of the box | Art. 6 |
| Contract administration IRFIs, change management and payment certification. | RFIs as structured records; potential change to change order in one chain linked to the schedule; payment applications assessed against site records and approved by workflow. | Out of the box | Art. 7 |
| Contract administration IIContractual notices, claims avoidance and closeout. | Each notice is a structured record with its dates and linked correspondence, changes and claims; closeout checklists configured to the owner; dashboards of open claims. | Out of the box | Art. 8 |
| Safety managementOwner safety requirements verified through the contractor’s plan, permits and site inspections. | Safety plan reviewed through the submittals workflow; permit checks and inspections on the mobile app; findings notified, tracked and escalated; links to the risk register. | Adaptive Form | Art. 9 |
| Risk managementRisk identification, analysis, response and regular review. | Risk register with owners, responses and review dates; reminders and escalation by workflow; analysis results recorded against the project. | Out of the box | Art. 10 |
| Sustainability and resiliencySustainability requirements, basis of design and commissioning evidenced through delivery. | Requirements and basis of design held as review comments and action items; inspection checklists for sustainability practices, with NCRs for shortfalls. | Custom Form | Art. 11 |
| Programme managementConsistent governance and reporting across a programme of projects. | The same forms and value lists on every project; funding by source and year; budget transfers under the DoA; programme dashboards with no reconciliation. | Reporting | Art. 12 |
| Technology managementA technology plan, integration and data governance for the project. | Integration with ERP, scheduling and GIS through open REST and SOAP APIs; validation, ownership, retention and archiving rules; a structured record at closeout. | Integration | Art. 13 |
| Beyond the Standard: AINot a CMAA function. The records above are what AI needs to work on. | PMWEB 2026 AI finds, opens, creates and helps on the structured CM record, with summaries and risk identification on project data. | Out of the box | Art. 14 |
NPMO · Mashroat
Mashroat, the National Project Management Office, defines the processes government, semi-government and PIF entities in Saudi Arabia are expected to run across the project life cycle, with accountability and transparency built in. PMWEB is where those processes are carried out, approved and reported.
| NPMO area | How PMWEB supports it | Delivery | Shown in |
|---|---|---|---|
| Process architectureThe life-cycle processes, from need and business case to procurement, design, construction, handover and operation, run as defined. | Each process configured as a form, a workflow and a report, mapped across the life cycle. Configuration, not customisation. | Workflow / DoA | Art. 2 |
| AccountabilityEvery decision attributable to an authorised person, within the delegation of authority. | DoA enforced as workflow logic at the point of transaction; every approval time-stamped; ageing of pending actions with automatic escalation. | Workflow / DoA | Art. 3 |
| TransparencyStakeholders see the contract and project position without waiting for a report. | The contract held as a record; role-based visibility; contractors and consultants transact directly in PMWEB, so nothing is re-keyed. | Out of the box | Art. 4 |
| Real-time reportingReporting from current data across the portfolio. | Dashboards and 150+ SSRS reports run on live records; portfolio consolidation without a monthly data call. | Reporting | Art. 5 |
| Budget, commitment, certification and cashPublic funds governed from budget to payment. | Budget, commitments (including pending commitments), certified payments and cash flow linked in one model, integrated with the ERP. | Integration | Art. 6 |
| Schedule governanceThe schedule used as a governance instrument, with contemporaneous delay records. | Entity-side obligations tracked as activities with owners and dates; schedule integration; delay events recorded as they happen; cross-project dependencies visible. | Integration | Art. 7 |
| Records and document controlDocuments and correspondence controlled as evidence, with provable transmission and a complete handover. | Document control, transmittals and correspondence as contract records; handover packages assembled from the records. | Out of the box | Art. 8 |
| Risk, quality and safetyRisk, quality and safety managed as part of delivery, not as separate reports. | Risk register, inspections, non-conformance and safety observations on the same project record. | Out of the box | Art. 9 |
| Data for AIA governed data foundation before AI is applied to project decisions. | Structured, approved records as the substrate for PMWEB 2026 AI and partner AI. | Out of the box | Art. 10 |
| Portfolio control towerPortfolio oversight across delivery data, geography and site. | PMWEB data combined with GIS through project coordinates, and site cameras linked to project records. | Integration | Art. 11 |
| Implementation roadmapMoving from an optional tool to an obligation, in a realistic sequence. | A phased 180-day plan: phase-one processes, process owners and the DoA agreed at executive level first. | Workflow / DoA | Art. 12 |
Request a standard
Tell us which standard, framework or regulation your organisation follows, and we will show how PMWEB supports it, process by process, in the same way as above.
Your request
Next step
We demonstrate the processes behind the standard you work to, configured the way your organisation runs them.
