Templates

Team Role Card Template (RACI-light) — Fillable

A one-page, fillable role card that captures purpose, day-to-day responsibilities, decision authority checklist, lightweight RACI handoffs, onboarding checklist, preferred working norms, and a few measurable indicators. Recommended for small teams and cross-functional pods.

Interactive Tool

Team Role Card - RACI-light

Use this one-page role card to clarify who does what, reduce handoff friction, and prevent role ambiguity. Complete the fields below to create a concise card you can save, share, or copy into team docs. Where helpful, keep entries short — think of this as a single-screen summary you can discuss in a handoff or onboarding conversation.

How to use: Fill the fields, provide clear examples for responsibilities and handoffs, and include simple decision authority statements (yes/no or short limits). The RACI-light handoff slots are intentionally simple — use them for your team's most frequent cross-role handoffs. If you need more rows, copy the card and add additional handoffs.

Short role title used on org charts and team directories. Example: 'Product & Ops Lead'
Describe the primary mission or outcome this role is accountable for. Keep it concise.
List the most important recurring responsibilities. Example bullets: 'Run weekly team standup', 'Approve vendor invoices under $5k', 'Maintain roadmap priorities'
Use these checkboxes to communicate typical decision boundaries. Add details in the field below if needed.
Provide limits, examples, or links to approval policies. Example: 'Can approve contracts under $10k with finance co-sign.'
Short list of must-do items for the first 30 days (accounts to request, docs to read, people to meet).
Examples: best times to meet, preferred channels, response-time expectations, meeting style (decision-focused, brainstorming, async).
Pick a few measurable indicators the role influences. Example: 'Average time to respond to customer incidents', 'Feature cycle time', 'On-time delivery %'.
Provide rows for your most common cross-role handoffs. Example row: 'Release QA -> Responsible: QA Lead | Accountable: Product Owner | Consulted: Dev Lead | Informed: Support'
Who initiates the handoff?
Who receives the handoff?
What event or condition triggers this handoff?
Short R/A/C/I assignment. Example: 'R: Dev Lead / A: Product / C: QA / I: Support'
Optional additional handoff slot.
Optional additional handoff slot.
Optional additional handoff slot.
Optional additional handoff slot.
Add short examples of tricky decisions or links to role-specific SOPs, templates, or org policies.
Who should people contact if role boundaries are unclear? Example: 'Alex R. (Slack @alex, email)'.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.