Team leadership prompt · Connected to Kanera

Claude prompt to review team workload

See who is overloaded, who has room, and which deadlines collide, then get specific suggestions for moving work before it slips.

Best for: Weekly resourcing checks, agencies juggling several clients, and planning around holidays.

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

PromptFill in the 6 highlighted fields
You are helping me review my team's workload. You are connected to Kanera through MCP.

Workspace or boards: [NAME OR "ALL WORKSPACES I MANAGE"]
Team members: [NAMES OR "EVERY ASSIGNEE IN SCOPE"]
Look-ahead window: [NEXT 1 OR 2 WEEKS]
Known time off: [NAME AND DATES, OR "NONE"]
Estimate field, if any: [FIELD NAME OR "NONE"]
Time zone: [TIME ZONE]

Before analysing:
1. Read active assigned cards for each team member in scope.
2. Read cards due inside the look-ahead window and anything already overdue.
3. Note blocked cards, long time in progress, and unassigned cards that are due soon.
4. Use the estimate field when it exists. Otherwise compare counts and deadlines, and say that you are doing so.

Produce a workload review with:
- A table per person: active cards, due in window, overdue, blocked, and total estimate if available.
- Hotspots: people or days where deadlines collide, especially around time off.
- Spare capacity: people with lighter load in the window.
- Unowned risk: unassigned cards due soon.
- Up to five rebalancing moves, each naming the card, from, to, and the reason. Only suggest moving a card to someone who already works on that board.

Be explicit about the limits of the data. Do not reassign, reschedule, or edit anything until I approve the exact moves.

Worked example output

Example result after Claude reviews a five-person agency team across three client boards for the next two weeks.

Example result
Workload review: 8 to 19 September (count-based, no estimate field)

| Person | Active | Due in window | Overdue | Blocked |
|--------|--------|---------------|---------|---------|
| Mei    | 9      | 6             | 1       | 1       |
| Omar   | 5      | 3             | 0       | 0       |
| Priya  | 7      | 5             | 2       | 0       |
| Sam    | 3      | 1             | 0       | 0       |
| Jonas  | 6      | 4             | 0       | 2       |

Hotspots
- Mei: 4 cards due 11 to 12 September, the two days before her leave.
- Priya: both overdue cards are on Oak Rebrand, which also has the 16 September review.

Spare capacity
- Sam has 1 card due in the window and works on Harbour Launch and Fernway.

Unowned risk
- HAR-220 | Cookie banner copy, due 12 September, unassigned.

Suggested moves
1. HAR-215 from Mei to Sam. Mei is away from 13 September; Sam already works on Harbour.
2. HAR-220 assign to Omar. He wrote the related consent logic (HAR-204).
3. FERN-86 from Priya to Sam. Frees Priya for the Oak review.

Apply any of these?

Get a more reliable result

  1. Add an estimate custom field to your boards if you want hour-based rather than count-based balancing.

  2. Always list time off; it is the most common cause of hidden collisions.

  3. Approve moves one at a time when they affect client-facing owners.

Prompt questions

Does Claude know how many hours each card takes?

Only if your board records it, for example in a numeric estimate field. Otherwise it compares card counts, due dates, and time in progress, and says so.

Will Claude reassign cards?

Not without your approval. It proposes specific moves; you choose which to apply, and Claude reassigns only those cards.

Can I include people on holiday?

Yes. List known time off in the prompt and Claude treats those people as unavailable for the dates you give.

Go from live Kanera work to a finished update.

Connect your AI assistant to Kanera so workload reviews use live assignments, deadlines, and blocked work across every board.

Explore Kanera's AI workflow
Start free

30-day Pro trial. No card required.