One of the project control processes included in most project management office manuals is the Project Critical Items Action Report (CIAR). The CIAR is a focal point for management’s control of the project and is one of the most important tools of the project controls program. The CIAR is the subject of a weekly project team meeting to discuss corrective actions or alternatives to eliminate or alleviate the schedule and/or cost impact of the critical items. The CIAR should be used to capture the top 10-12 actual and potential impacts or opportunities to the project schedule outcomes that need immediate management attention and drive them to resolution within the required timeframes.

These items are defined as items that pose a risk to project performance or represent a potential opportunity. Each item should be specific and actionable, must be assigned to a specific individual owner, should clearly identify the ongoing or potential impact to the project (e.g. delay performance testing by 2 weeks) and has specific actions and completion dates by which the issue is proposed to be resolved

It is not intended to be an extended action item list or a punch-list of to-go works which would dilute the focus on the critical items. The CIAR is also not meant to be exclusively a listing of schedule activities on the critical path though some of these would certainly be included in the CIAR. Other reports, studies, or status information should be used to resolve project problems of a minor nature on a day-to-day basis.

The potential sources of critical items include schedule updates and critical path review and analysis,

  • Production, release, delivery, and installation curves
  • Trend Reports, and Risk Registers Reports
  • Contract and Permit Compliance matrix
  • Medium Term schedules and Work Front Analysis
  • Progress reviews, weekly reports and monthly dashboard reports
  • Prime Contract/Subcontract reviews
  • Level 5 Schedule:
    • Engineering Tracker
    • Specification/Drawing Logs
    • Exception Reports
    • code requirement changes
    • Material Requisition
    • Register Reports
    • Expediting Reports
    • Vendor Data status
    • 3 Week Look ahead,
    • Quantity Tracker
  • Project team communications or general correspondence,
  • Non-Conformance Reports, Unsatisfactory, Overage, Shortage & Damage (UOS&D)
  • Back-charge notices
  • Current studies/evaluations and Customer, Community, and Labor Relations

The Critical Issues Action Report (CIAR) should provide the project team with real-time single version of the truth status of all CIARs, issue and action description, responsibility, due, forecast, and actual action dates, category they are associated with, project schedule activity they will impact and status.

PMWeb 7 Critical issues Action Report (CIAR)

Project Management Information Systems (PMIS) like PMWeb which is used to manage the many business processes needed to manage capital construction projects delivery, will be also used to manage the Critical Issues Actions Report. PMWeb ready to use meeting minutes will be perfect for managing, monitoring, evaluating and reporting on CIARs.

The meeting minutes header will be used to capture the overall details of each CIAR meeting for which the type fields will have the CIAR as one of the meeting types. Similar to other meetings, meeting date, time start and time end, location or venue, those required to attend and those who have attended and other details that could be needed.

The main change will be done in the meeting business items where the default description field will be removed and instead add two fields for Critical Issue and Action. Also, a field for Forecast, No. of Forecast Dates Changed and Criticality fields will be added. The fields for assigned to will be used to assign the individual responsible for the action, category will be used to select the CIAR category, task to link the relevant project schedule activity, completed to record the Action actual date and Done to highlight if this CIAR item was completed or not. Of course, there are many other fields like Notes, Subject, Reference and others could have been kept as well as additional user defined fields could have been added, if needed.

PMWeb 7 Forms Meeting Minutes CIAR Meeting Main

For each CIAR item all supportive documents will be attached as well as other relevant PMWeb records and imported MS Outlook emails will be linked. All those documents can be uploaded and stored in their relevant folder or subfolder in PMWeb document management repository. PMWeb allows to select what attached PDF or Picture file documents to be displayed on the CIAR form.

PMWeb 7 Forms Meeting Minutes CIAR Meeting Attachments

A workflow can be assigned to the Critical Issues Action Report (CIAR) form, or meeting minutes form, to ensure that the reported critical issues, actions, responsibilities, and other details have been reviewed and approved by the project manager. PMWeb workflow will be used to create a workflow to map the submit, review and approvals tasks along with the duration set for each task and the individual accountable to perform the task.

PMWeb 7 Forms RFIs Conflict

One of the important functions in the PMWeb meeting minutes module is the ability to generate the next CIAR meeting agenda. All critical issues for which the action was completed by selecting the option “Done”, will be excluded and only those with pending actions will be listed in the next meeting.

This enables the project team to maintain history of each critical issue, updates to the actions and update to the forecast date. In addition, it eliminates the redundant effort of adding the details of the meeting as well as the list of attendees. Of course, attachments from the previous CIAR meeting will not be copied to the new CIAR meeting.

PMWeb 7 Forms Meeting Minutes Critical Issues Actions Report Meeting Main


PMWeb

The world’s top organizations are selecting PMWeb because of its comprehensive features, functionality, and ease of use. Since 2007, PMWeb has been used by tens of thousands of users to manage their Plan | Build | Operate lifecycles.