RFIs, Field Change Requests, and Design Change Requests generate a lot of paperwork — but the CCQM exam wants you to see the actual purpose behind tracking them: keeping the project on track while allowing objectives to adapt.
Why this knowledge point trips people up
This question sits in Domain V – Construction, quality plan deployment, at the Apply level. The distractors describe outcomes that either shift liability inappropriately or impose artificial limits unrelated to the tracking process’s real purpose.
Breaking down the concept itself
Applying the process for tracking RFIs, FCRs, and DCRs exists to ensure the project remains on track and its objectives adapt when necessary. It isn’t meant to shift design responsibility away from the architect of record, artificially cap how many change requests get submitted per month, or force closure of open RFIs ahead of a scheduled inspection — each of those distorts the tracking process’s actual function.
Real-life example from construction projects
After the structural engineer answers an RFI about a transfer girder camber discrepancy, a Field Change Request generated to adjust the shoring, followed by a Design Change Request revising the drawings — all tracked in a shared log — demonstrates exactly this purpose: keeping the project moving forward while the design and construction plan adapts to the new information.
Exam Tip
Read the question stem twice before looking at the options — most mistakes come from misreading what’s actually being asked.
Try this practice question on today’s topic
Question: When applying the process for tracking Requests for Information (RFIs), Field Change Requests (FCRs), and Design Change Requests (DCRs), what is the goal?
- A) To ensure the project remains on track and objectives adapt when necessary
- B) To shift design responsibility away from the architect of record
- C) To limit the number of formal change requests submitted per month
- D) To close out all open RFIs before the next scheduled inspection
Correct answer: A
Explanation: Tracking RFIs, FCRs, and DCRs ensures the project remains on track while allowing objectives to adapt when necessary, not to shift design liability, cap request volume, or force closure before inspections.
Frequently asked questions about the CCQM exam
Does tracking RFIs and change requests slow the project down?
The exam frames it the opposite way — proper tracking keeps the project on track by ensuring changes are resolved and coordinated systematically, rather than causing confusion or rework from untracked changes.
Why would capping the number of change requests per month be a wrong answer?
Because the purpose of tracking is to manage and resolve changes as they arise, not to artificially limit how many legitimate issues can be raised.
How does this tracking process relate to design responsibility?
It documents who requested and approved each change and why, but it doesn’t exist to shift design responsibility away from the architect or engineer of record.
Bringing it all together
Keep this concept anchored to adaptability with control: the tracking process exists so the project can adapt to necessary changes while staying on track — not to limit, redirect liability, or force premature closure.
Ready to turn what you read into real exam results? If you are preparing for any ASQ certification, you can practice with my dedicated exam-style question banks on Udemy. Each bank includes 1,000 MCQs mapped to the official ASQ Body of Knowledge, plus a private Telegram channel with daily bilingual (Arabic & English) explanations to coach you step by step.