A portfolio review starts with eight projects and a 45-minute Google Meet slot. Each project lead gives a careful update. By minute 38, the group reaches the question that affects the whole portfolio: two teams need the same designer next week. The host asks for a quick answer because the call is ending.

A portfolio review stalls when a status presentation receives the same live time as a cross-project choice. Stable status belongs in the pre-read. Work that forces another project to change belongs in the meeting.

Filter Status Before the Call

PMI's project review guidance recommends defining the review objective, preparing the agenda, and allocating time to its topics. The Project Group describes portfolio meetings as forums for important portfolio decisions and notes the need for decision-makers and current, prepared data.

Discuss a project live when its change forces another project to change.

That includes a dependency collision, shared-capacity conflict, material priority change, or a sponsor decision. A completed milestone, stable budget line, or project with no changed dependency can remain in a written update. It stays visible without taking the time needed for trade-offs.

Keep the Decision List Small

Limit a 45-minute review to three cross-project decisions. Five minutes establish the decision list and ten minutes record owners and dates. That leaves 30 minutes, or about ten minutes per decision: 45 - 5 - 10 = 30; 30 / 3 = 10.

Status signal Where it goes What the group needs
On plan, no dependency change Pre-read Visibility only
Milestone threatens another team's work Live review Priority or sequencing decision
Budget or capacity conflict Live review Trade-off and owner
Missing evidence Follow-up Owner and due date

For example, a project lead reports that a launch moved by one week and now needs the designer booked for another initiative. The room should choose which deadline moves or what scope changes. A project that remains on plan belongs in the pre-read so the conflict has room.

Time the Google Meet Review Around Choices

Time Segment Output
0-5 Read changes since the pre-read Decision list confirmed
5-35 Three cross-project choices Priority, trade-off, owner
35-45 Record decisions, dependency updates, and follow-ups Usable portfolio record

Minute Minder starts a timer from the connected Google Calendar event when the host joins Google Meet. Its AI agenda can turn an invite into timed steps when the review has a known decision list. Configure the host's reminders like this:

  • Minute 30: “15 min left: stop status updates and finish remaining choices.” Sound on.
  • Minute 35: “10 min left: record priority, owner, and dependency change.” Sound off.

Custom reminders and color cues help the host move from discussion to decision capture without another tab. Meeting analytics can show where this review repeatedly runs over. Minute Minder does not choose portfolio priorities or read project data.

Use a Deeper Status Review Deliberately

A new portfolio, recovery program, or major replan can need a temporary status-heavy session. State that purpose in the invitation and shorten the decision claim. Once the group has reliable pre-reads, stable updates can move back out of the live call.

The 38th-minute choice becomes manageable when the people who own competing work receive time to make it, then leave with a recorded decision.

Sources

FAQ

What should a project portfolio review meeting cover?

Cover changes that require a cross-project decision: dependencies, capacity conflicts, priority shifts, and material risks. Put stable status in the pre-read.

How long should a portfolio review meeting be?

A 45-minute review can work for three prepared decisions. Larger portfolios may need separate decision groups or a longer session.

How can I keep a Google Meet portfolio review on time?

Send the status pre-read in advance, cap the live decision list, and protect a final window for owners and dependency updates. Minute Minder can provide the host's calendar-based timer and reminders inside Google Meet.