Weekly Agency Portfolio Review Template for Client Work

Download the blank agency portfolio scorecard spreadsheet. No account is required. Save a copy before adding your project details.

A useful portfolio review answers four questions: Which commitments are at risk? Which clients or teammates owe a decision? Where do deadlines collide? Which action would unblock the most important work?

Consider a fictional five-person studio managing Juniper, Orbit Bikes, and Leo. Each project may look healthy when reviewed alone, but Juniper's launch and Orbit Bikes' campaign may both need the same developer on Thursday. Portfolio-level visibility reveals the conflict before it reaches the client.

Asana's project status reporting guidance emphasizes summarizing progress, blockers, and next steps for stakeholders. A portfolio review uses the same principle across multiple simultaneous engagements.

The Project Management Institute discusses managing multiple projects as a resource-allocation and prioritization problem in addition to individual project execution. This is why the agency review should compare engagements rather than merely summarize each one.

The agenda is a starting framework, not a guaranteed ideal meeting length. A small agency can shorten or extend it based on the number and complexity of projects.

Send a small portfolio snapshot beforehand so participants are not discovering the project list during the meeting. If the same person can make every decision alone, a written review may be sufficient.

Use one row per active project. The sample data is fictional and does not represent Noddis customer outcomes.

Health is a judgment explained by evidence. “At risk” should identify what is threatened and why. A percentage alone does not explain project health or client acceptance.

Before the meeting, gather the latest milestone dates, open client commitments, blocked tasks, proposed scope changes, and near-term team capacity. Identify questions that genuinely need a decision. Do not recreate the whole task list in a slide deck.

A useful pre-read is one page:

This week: Juniper's homepage approval is at risk; Orbit Bikes and Juniper both need developer QA Thursday; Leo remains on schedule. We need decisions on Juniper's review date and Thursday's QA allocation. No other items require group discussion.

That is enough to direct attention to the work that matters.

Close with an action register containing decision, owner, and due date. If a client must decide, record the teammate responsible for requesting the answer and the agreed next check date.

Do not list “follow up” without naming the topic and desired outcome. That creates another reminder that requires context reconstruction later.

Avoid reading every completed task, debating colors, collecting unsolicited design feedback, or duplicating client-facing updates that already exist. Those belong in focused project conversations. The group review is for cross-project tradeoffs and decisions.

Also avoid allowing a loud client to determine priority simply through message volume. Review deadlines, dependencies, consequences, and the commitments actually made. The multiple client projects guide explains the daily cross-project sweep; this weekly meeting addresses the team-level decisions that the daily sweep identifies.

Noddis is a project management app with Portfolio views, project-focused Execute, Upcoming, and Follow-Up. Use Portfolio to compare active client projects and Follow-Up to find recorded promises or missing responses. A project can still need a manual capacity conversation; the app does not determine which client deserves priority on its own.

For day-to-day work, link to the client project tracker guide. The live demo shows how connected workspaces separate oversight from execution.

Run the next review with only the scorecard and action register. If a topic cannot change a decision or commitment, move it out of the meeting.