RFI · CR

Digital ticketing for RFIs and change requests with categorisation, SLA, and routing — replacing the email chain.

What it is

Once drawings are issued, the lifecycle of queries and changes begins. Site engineers raise RFIs (Request for Information) when a drawing is unclear or conflicts on the ground. Vendors raise change requests when scope shifts. The module provides digital ticketing with category-based routing, SLA tracking, AI-suggested responses for repetitive queries, and impact assessment for change requests.

Inputs

Triggers

·Drawing version issued in M07
·Site engineer raises RFI with photo and drawing reference
·Vendor raises CR with scope impact
·Consultant response received against open RFI
·CR approval decision recorded

Data reads

·Current drawing version from M07
·Consultant assignment per package from M05
·Project record for RFI context
·Past RFI patterns for AI-suggested classification
·Design Head approval scope for CR thresholds

Artefacts consumed

·RFI submission with photo, location, drawing reference
·CR with scope impact assessment
·Consultant response documentation
·Drawing revision packages

Tools & Techniques

Methods

·Digital RFI ticketing with category-based routing
·AI classification of RFI type (structural-MEP clash, spec query, etc.)
·SLA tracking with auto-escalation
·CR impact assessment workflow — drawings, quantities, schedule, cost
·Drawing revision and re-issuance triggered by approved CRs

Policies

·RFI workflow policy — categories, SLAs, routing rules
·CR approval policy with impact-assessment requirement
·Drawing revision and re-issuance policy

Decision rules

·RFI routes to responsible consultant by package and category
·CR approval requires impact across all four dimensions documented
·CR above scope threshold requires Design Head plus DCO sign-off
·Re-issued drawing closes the originating RFI/CR with link

Outputs

Artefacts produced

·RFI register with status, owner, SLA, response
·CR register with impact assessment and approval
·Drawing revision history linked to closed tickets
·Consultant response performance data

Data writes

·RFI status updated through lifecycle
·CR status updated through approval workflow
·Drawing revision linkage updated on each re-issuance

Downstream triggers

·Approved CR triggers BOQ recalc in M10
·Approved CR triggers amendment workflow in M15
·Drawing re-issuance triggers vendor notification through CPT
·CR with schedule impact updates milestone register in M16

Stakeholders

CM · Site engineersRaise RFIs from site with photo, location, drawing reference
VendorsRaise change requests with scope impact
Design CoordinationRoutes queries to right consultant
ConsultantsRespond within SLA
Design HeadApproves change requests with impact assessment

The flow

01Drawing issuance — versioned, with recipient acknowledgement
02Distribution routing by recipient role
03RFI raised by vendor or CM with site context
04RFI routing to responsible consultant by package
05Consultant response, SLA-tracked
06RFC approval with impact assessment
07Drawing revision and version increment
08Re-issuance with original RFI/RFC closed in register

State change

Before

RFIs sit in inboxes; status visibility is partial; turnaround unpredictable.

After

Every RFI and CR is a tracked ticket with status, owner, SLA, and impact.

Real-world example

BA59 Iris G L7 — site engineer raises RFI #4012 with photo of column-MEP clash on 14 May 9:14 AM. Auto-classified as structural-MEP clash; routed to MEP consultant (Mahindra Consulting). Acknowledged in 4 minutes. SLA: response by 5 PM same day. 156 RFIs portfolio-wide, average response 22 hours.

Artefacts

·Drawing issuance register
·RFI tickets
·Change request tickets
·Consultant response records
·Drawing revision history linked to closed tickets

Pain today

RFIs sit in consultant inboxes; CM does not know they are pending; site stops while waiting. No central register of open queries. Change requests circulate as email chains.

Integrations

ACC (drawing reference)