When initiating a project review, timing can be a delicate balance. Reviewing too often can lead to frustration among those involved, as it may seem like unnecessary micromanagement if everything has stayed the same. On the other hand, reviewing the project on time can connect what's happening in reality and what the project presents.

Determining the frequency of a project review is contingent on several factors, including the project's complexity, duration, criticality, and the organisation's established practices. While there is no one-size-fits-all answer, here are some general guidelines for the frequency of project reviews:

Regular Progress Reviews: Regular progress reviews should be conducted throughout the project lifecycle to monitor progress, address any issues or risks, and ensure alignment with project goals. These reviews can be conducted weekly, bi-weekly, or monthly, depending on the project's duration and complexity.

Milestone Reviews: Milestone reviews are conducted at key milestones or significant stages of the project. These reviews assess the project's performance against predefined milestones, deliverables, or objectives. The frequency of milestone reviews can vary based on the project timeline and the number of milestones identified.

Phase or Gate Reviews: For projects following a phased or gated approach, reviews are conducted at the end of each phase or gate. These reviews assess the completion of phase deliverables, validate their quality, and determine whether to proceed to the next phase. The frequency of phase or gate reviews depends on the project's structure and the number of phases or gates in the project.

Project Closure Review: A project closure review is conducted at the end of a project to evaluate its overall success, outcomes, and lessons learned. This review typically occurs after project completion and can occur once for each project.

Ad-hoc Reviews: Besides regular and milestone reviews, ad-hoc reviews may be conducted as needed. These reviews are triggered by specific events, critical issues, or changes in project circumstances that require immediate attention and evaluation.

It's important to note that the frequency of project reviews should be balanced to avoid excessive administrative burden while ensuring sufficient oversight and control. In consultation with relevant stakeholders, the project manager should determine the appropriate frequency of reviews based on project characteristics, organisational requirements, and the need for effective project governance.

Regular communication and feedback loops should be established to provide ongoing visibility and address emerging issues throughout the project lifecycle.