Internal reporting prompt · Connected to Kanera

Claude prompt for portfolio health review

One page for every project you oversee: which are healthy, which are drifting, and where you should spend your attention this week.

Best for: Agency directors, heads of delivery, and PMOs with many concurrent projects.

Works with: Any assistant connected to Kanera, such as Claude, ChatGPT, GitHub Copilot, Cursor, Codex, OpenCode, or Antigravity.

PromptFill in the 4 highlighted fields
You are preparing a portfolio health review using live Kanera data through MCP. This is read-only.

Scope: [WORKSPACES OR "ALL I CAN ACCESS"]
Period: [LAST 7 OR 14 DAYS]
Health rules: [RED/AMBER/GREEN DEFINITIONS OR "RECOMMEND ONE"]
Time zone: [TIME ZONE]

Before writing:
1. Read the portfolio summary across the workspaces in scope.
2. For each board, gather: active cards, completed during the period, overdue, blocked, unassigned due soon, and the next milestone or due date cluster.
3. Compare completion this period with the previous period of the same length.
4. For any board that looks amber or red, read the most important overdue or blocked cards to understand why.

Write a portfolio review with:
- A table: project, health, completed, overdue, blocked, next milestone, and one-line reason.
- Needs attention this week: up to three projects, each with the specific problem and a suggested leadership action.
- Improving: projects that moved from amber or red to green.
- Quiet projects: boards with almost no activity, which may be paused or forgotten.
- Cross-project patterns: shared people, clients, or dependencies causing problems in more than one place.

Use the same rules for every project. Cite card keys for the reasons. Keep the narrative under 350 words.

Worked example output

Example result after Claude reviews nine client and internal boards across two workspaces.

Example result
Portfolio health: 1 to 14 September

| Project | Health | Done | Overdue | Blocked | Next milestone | Reason |
|---|---|---|---|---|---|---|
| Harbour Launch | Amber | 14 | 1 | 1 | Launch 19 Sep | Critical path has no slack (HAR-212) |
| Fernway Retainer | Green | 11 | 0 | 0 | Report 1 Oct | On plan |
| Oak Rebrand | Red | 3 | 4 | 1 | Review 16 Sep | 4 overdue design cards, owner overloaded |
| Activation | Green | 9 | 0 | 0 | Sprint end 3 Oct | On plan |
| ... | | | | | | |

Needs attention this week
1. Oak Rebrand: 4 overdue cards all sit with Priya, who also owns Harbour launch tasks. Action: move two Oak cards to Sam before the 16 Sep review.
2. Harbour Launch: no slack before launch. Action: confirm legal sign-off (HAR-201) by 11 Sep.

Improving
- Activation moved from amber to green after the invitation fix shipped.

Quiet projects
- Internal Wiki: no activity in 21 days. Paused or forgotten?

Cross-project pattern
- Priya is on the critical path in two projects at once.

Get a more reliable result

  1. Agree the health rules with your leadership team once, then reuse them every week.

  2. Look at "quiet projects" monthly; forgotten boards distort portfolio numbers.

  3. Pair it with the team workload prompt when the same person appears in several red projects.

Prompt questions

How is this different from the multi-client rollup prompt?

The ChatGPT rollup summarises updates you paste. This Claude prompt reads every board directly and compares their health using the same measures.

How does Claude decide a project's health?

From overdue work, blocked work, completion trend, and upcoming milestones. You can supply your own red, amber, and green rules in the prompt.

Can it cover boards I do not belong to?

No. Claude sees what your Kanera account can see. Use an account with access to every project you want included.

Go from live Kanera work to a finished update.

Connect your AI assistant to Kanera so portfolio reviews compare every project on the same live measures.

Explore Kanera's AI workflow
Start free

30-day Pro trial. No card required.