reph

Templates · Strategy & leadership

Quarterly plan template

Priorities, capacity, milestones and risks for the quarter

Start with this template →Sign in

Opens on reph with the template ready to start. No account needed; sign in to keep your document.

Use it when

A quarter is about to start and a team or company needs ranked priorities, capacity and dated milestones everyone agrees on

Who it's for

ManagerExecutiveProduct manager

Part of a kit

Leadership operating rhythm, step 3 of 6. Strategy, OKRs, quarterly plan, decision memos, the board pack and the monthly company update.

Filled example

The template filled in for a made-up company, so you can see what good looks like.

Platform team plan, Q1 2027

Author: Ravi Menon (Engineering Manager, Pinecrest Labs) · Date: December 15, 2026 · Quarter: Q1 2027

Last quarter recap

We shipped SSO for enterprise workspaces and cut p95 API latency from 480 ms to 310 ms. The billing service migration slipped: 60% of accounts moved, the rest carry over. Search reindexing was dropped when two engineers moved to the EU region work.

Targets

p95 API latency
310 ms
target 250 ms
Accounts on new billing
60%
target 100%
Pages per week
6
target 3

Priorities

  1. Finish the billing migration and turn off the old service.
  2. Bring p95 latency to 250 ms on the five busiest endpoints.
  3. Halve on-call pages by fixing the top three alert sources.

Capacity

Team Headcount Allocation
Platform core 5 60% billing, 40% latency
SRE 2 70% alerting, 30% on-call

Milestones

Milestone Owner Due
Remaining accounts migrated Elena February 6
Old billing service off Elena February 27
Query cache on top endpoints Kwame February 20
Alert noise review complete Jun January 23
Mermaid diagram (drawn as a picture in reph)
gantt
  title Q1 2027 milestones
  dateFormat YYYY-MM-DD
  section Billing
  Migrate remaining accounts :b1, 2027-01-05, 5w
  Turn off old service :b2, after b1, 3w
  section Latency
  Query cache :l1, 2027-01-12, 6w
  section Alerting
  Alert noise review :a1, 2027-01-05, 3w

Dependencies

  • Finance must sign off the invoice reconciliation report before the old billing service goes off (confirmed for February 20).
  • The data team's warehouse change on January 30 touches the same tables as the migration (not yet confirmed; Ravi to follow up).

Risks

  • Enterprise accounts with custom invoicing may not map to the new model. Signal: more than 5 manual fixes in the first migration batch.
  • The query cache could serve stale permissions. Signal: any access test failure in staging; we will not ship without the invalidation test passing.

Not doing

  • Search reindexing (moved to Q2).
  • Kubernetes version upgrade, unless security requires it.
  • New internal admin tooling.

The template

Show the blank template

Quarterly plan

Author: [your name] · Date: [date] · Quarter: [quarter]

Last quarter recap

What shipped, what didn't, and what carries over. This grounds this quarter's plan instead of starting from a blank page.

Targets

The handful of numbers this plan is meant to move, with the end-of-quarter target in the delta. Update the values at the mid-quarter check-in.

Target metric 1
0
target 0
Target metric 2
0
target 0
Target metric 3
0
target 0

Priorities

Ranked, not a flat list. If everything's #1, nothing is. Three to five items, not ten.

Capacity

Team Headcount Allocation

Milestones

Milestone Owner Due

Optional: the same milestones as a timeline, so overlaps and crunch weeks are visible.

Mermaid diagram (drawn as a picture in reph)
gantt
  title Quarter milestones
  dateFormat YYYY-MM-DD
  section Priority 1
  Milestone A :a1, 2026-01-05, 3w
  section Priority 2
  Milestone B :b1, 2026-01-19, 4w

Dependencies

Other teams or external parties this plan relies on. Flag anything not yet confirmed.

Risks

What could blow up the plan, and the early signal that would tell you it's happening.

Not doing

What's explicitly deferred this quarter. This protects the priorities above from scope creep.

Questions

How many priorities should a quarter have?
Three to five, ranked; if everything is number one nothing is
How is this different from OKRs?
OKRs say what outcome you want; the quarterly plan says who does what by when to get there
When do we revisit it?
At a mid-quarter check-in, and again in next quarter's recap

Fill it with your agent

Connect Claude to reph over MCP, then paste this. The draft arrives as suggestions you accept or reject section by section. How to connect Claude.

Find my reph doc "Quarterly plan" with search_docs, then read it with read_doc. Draft the recap from last quarter's plan and check-ins, targets from this period's OKRs, capacity from the team roster and milestones from the linked roadmap. Leave the priority ranking and Not doing list for me. File it with suggest_edit, one replace_section op per section (heading line kept) so each can be accepted alone. Ask each open question (unconfirmed dependencies) with add_comment quoting that section's heading line, then call request_review with a one-line summary.

Related templates

Strategy doc

Diagnosis, guiding policy and coherent actions (Rumelt kernel)

ExecutiveFounderManager

OKRs

Objectives and measurable key results for a period

ExecutiveManagerProduct manager

Decision memo

Frame a decision, options and a recommendation for sign-off

ExecutiveManagerFounder

Board pack

Quarterly board meeting pre-read: metrics, decisions needed, risks, financials, asks

FounderExecutive

Company monthly update

What shipped, the numbers, wins and people news, ready to send as an email newsletter

FounderExecutiveCommunicationsOperations

Competitive analysis

Compare competitors on features, pricing and positioning

Product managerMarketerExecutive

Start with this template →Sign in