Project Management Series | [11]: How to Efficiently Manage Different Requests in Projects

Dr. Abdussalam Alhabeeb | Updated: 06 August 2025

Project Management Series

Managing formal requests such as Non-Conformance Reports (NCR), Requests for Information (RFI), Change Orders (COR), and Submittals is a crucial part of project success. Below is a comprehensive guide to best practices for efficiently managing these requests, along with essential fields in the forms.


Best Practices for Managing Requests:


  1. Use a Central Document Management System:
  2. Utilize systems to track all requests and store them in a central location, such as Aconex, Procore, SharePoint, or ProMaster.

  3. Use Standardized Forms:
  4. Forms should include standardized fields such as request number, date, description, target response date, and signature.

  5. Define Responsibilities:
  6. Assign who is authorized to submit each type of request and who is responsible for review and approval.

  7. Track Status and Deadlines:
  8. Use schedules or software to monitor the status and deadlines, and remind involved parties.

  9. Link Requests to Relevant Documents:
  10. For example, link NCRs to drawings or RFIs to inspection reports.

  11. Code Requests:
  12. Use a logical coding system like RFI-PROJ001-023 for easy tracking.

  13. Maintain Organized Records:
  14. Create records for RFIs, NCRs, and others in the used system, whether Excel or another platform.

  15. Track Changes and Versions:
  16. Document every change in requests and maintain control over versions of attached files.

Essential Forms for Managing Requests:


  1. Request for Information (RFI) Form.

  2. - Request Number.
  3. - Project Name.
  4. - Submission Date.
  5. - Requesting Party.
  6. - Subject/Title.
  7. - Inquiry Details.
  8. - Reference Documents or Drawings.
  9. - Required Response Date.
  10. - Response (to be filled by the relevant party).
  11. - Status (Open/Closed/Pending).

  12. Non-Conformance Report (NCR) Form.

  13. - Report Number.
  14. - Project Name.
  15. - Issue Date.
  16. - Person Reporting the Issue.
  17. - Description of Non-Conformance.
  18. - Reference Documents.
  19. - Proposed Corrective Action.
  20. - Consultant/Engineer Comments.
  21. - Status (Open/Under Review/Closed).

  22. Change Order Request (COR) Form.

  23. - Request Number.
  24. - Submission Date.
  25. - Applicant.
  26. - Description of the Requested Change.
  27. - Justification for Change.
  28. - Impact Analysis (Time/Financial).
  29. - Client/Project Manager Approval.
  30. - Status (Submitted/Approved/Rejected).

Supporting Tools and Techniques:


ToolUsage
ProcoreManagement of RFIs and CORs, request tracking.
AconexManagement of workflows, correspondence, and request records.
Excel / Google SheetsTracking requests and creating simple records.
SharePointFile sharing and version management.
Power Automate / ZapierAutomating alerts and actions.
ProMasterIntegrated management of all procedures between owner, consultant, and contractor.


Share this article