Prompt & template library

15 Claude Whiteboards Templates You Can Copy

Start with a practical prompt for meetings, project planning, product strategy, data organization, and team reviews. Adapt each template to your own context.

15 copy-ready prompts5 categoriesUpdated
Template collectionIllustrative examples
Plan · Organize · Review
Meeting notes
Decisions
Roadmap
Milestones
KPI board
Metrics
Quarterly review
Next steps
Copy-ready library

Find a template for your next task

Every prompt is visible on the page and can be copied without creating an account. Replace the context with your own project details.

MeetingTasksMilestones
Meetings

Meeting Notes to Board

Turn rough meeting notes into decisions, action items, and owners.

Convert the meeting notes below into a collaborative whiteboard. Create separate areas for meeting goals, key discussion points, decisions, action items, owners, and due dates. Group related items, highlight unresolved questions, and do not invent missing owners or deadlines.
How to use ↗
WeeklyOwnersRisks
Meetings

Weekly Team Sync

Create a visual agenda and follow-up board for a weekly team meeting.

Create a weekly team sync whiteboard with sections for wins, priorities, blockers, decisions, and next actions. Group action items by owner and flag anything that needs follow-up. Leave unknown details clearly marked as TBD.
How to use ↗
MeetingTimelineReview
Meetings

Meeting Follow-up

Make responsibilities and next steps easy to scan.

Turn this meeting summary into a follow-up board. Separate decisions from tasks. For every task, show the owner, due date, dependency, and status when provided. Highlight tasks with missing information.
How to use ↗
ProductDecisionsActions
Planning

Product Launch Roadmap

Map milestones, dependencies, owners, and launch risks.

Create a visual product launch roadmap. Include objectives, phases, milestones, task owners, target dates, dependencies, and risks. Arrange phases in chronological order and visually distinguish critical-path tasks.
How to use ↗
EventGoalsNext steps
Planning

Event Planning Board

Coordinate an event from preparation to follow-up.

Create an event planning whiteboard with workstreams for venue, speakers, promotion, registration, logistics, and post-event follow-up. Add owners, deadlines, dependencies, and a day-of-event timeline where information is available.
How to use ↗
ProjectTasksMilestones
Planning

Project Timeline

Turn a project brief into a clear timeline.

Convert this project brief into a visual timeline. Identify phases, milestones, deliverables, owners, dates, and dependencies. If dates are missing, use relative sequencing and ask me to confirm the schedule.
How to use ↗
FeatureOwnersRisks
Product

Feature Prioritization

Compare product ideas by impact, effort, and confidence.

Create a feature prioritization board. Group features by impact and effort, show confidence and evidence where supplied, and separate assumptions from validated facts. Do not fabricate scores.
How to use ↗
UserTimelineReview
Product

User Journey Map

Visualize a user's steps, questions, and pain points.

Create a user journey map for the audience and product described below. Organize stages, user actions, questions, emotions, pain points, and opportunities. Highlight moments of friction and areas that need research.
How to use ↗
ProductDecisionsActions
Product

Product Strategy Map

Connect goals, audiences, bets, and success measures.

Create a product strategy whiteboard connecting target users, problems, strategic bets, initiatives, risks, and success metrics. Make dependencies visible and distinguish confirmed decisions from hypotheses.
How to use ↗
CSVGoalsNext steps
Data

CSV to Visual Board

Summarize supplied rows into meaningful visual groups.

I will provide a sample of tabular data as text. Help me identify categories, patterns, outliers, and useful groupings, then organize the findings into a visual whiteboard. Do not claim to import a CSV file directly; ask me to paste or provide the data in a supported way.
How to use ↗
KPITasksMilestones
Data

KPI Planning Board

Define metrics, owners, targets, and review cadence.

Create a KPI planning board. For each metric, show its definition, owner, baseline, target, measurement cadence, and data source. Mark missing definitions or targets as unresolved.
How to use ↗
BusinessOwnersRisks
Data

Business Process Map

Map a process from trigger to outcome.

Create a business process map from the description below. Show the trigger, steps, decision points, responsible roles, handoffs, exceptions, and final outcome. Use arrows to make sequence and dependencies clear.
How to use ↗
QuarterlyTimelineReview
Review

Quarterly Review

Turn quarterly results into a structured retrospective.

Create a quarterly review whiteboard with goals, outcomes, wins, misses, lessons, risks, and next-quarter priorities. Separate measurable results from opinions and identify follow-up actions.
How to use ↗
SWOTDecisionsActions
Review

SWOT Analysis

Organize strengths, weaknesses, opportunities, and threats.

Create a SWOT analysis board for the business described below. Use four clearly labeled areas. Keep internal factors separate from external factors and flag statements that need evidence.
How to use ↗
DecisionGoalsNext steps
Review

Decision Matrix

Compare options against explicit decision criteria.

Create a decision matrix whiteboard for the options below. List decision criteria, weights if provided, evidence, trade-offs, risks, and open questions. Do not assign arbitrary scores; ask for missing weights or criteria.
How to use ↗

These are independent prompt examples, not official Anthropic templates. Boards can't be imported from a file, so for the data examples paste the rows into the chat. To work with the CSV itself, import it into Claude Sheets.

Make the output better

Give Claude enough context

A useful prompt describes the goal, audience, constraints, and what a good result should contain.

A simple prompt formula

Context: What are you working on?

Structure: Which sections should the board contain?

Constraints: What should Claude avoid assuming?

Output: How should the information be grouped and connected?