6 Free User Story Templates for Word, Excel & PDF (2026)
Download 6+ ready-to-use user story templates for different scenarios and industries. Each template includes examples and best practices.
What is a user story template?
A user story template is a reusable format for writing feature requirements from the user’s perspective. The standard structure is “As a [user], I want [function], so that [benefit],” usually paired with acceptance criteria and delivery notes.
Best for
- PMs turning PRDs into backlog items
- Product teams writing acceptance criteria
- Teams that need Word, Excel, or PDF formats
How to choose the right user story template
Use the basic template
Use the standard story format when you need a simple backlog item that can move quickly into grooming or sprint planning.
Use the epic template
Use an epic template when the work spans multiple stories, dependencies, or milestones and needs shared business context.
Use acceptance criteria templates
Use Given-When-Then or checklist formats when alignment with design, QA, and engineering matters more than speed alone.
Jump to Templates:
📋 User Story Template Overview
The Standard User Story Format
This simple three-part structure ensures your user stories are clear, focused, and valuable. Each component serves a specific purpose in communicating user needs effectively.
User Type
Who is the user? Be specific about their role, needs, and context.
Functionality
What does the user want to do? Focus on the action or feature needed.
Benefit
Why does the user need this? What value or outcome will it provide?
📝 Basic User Story Template
Template Structure
As a [user type/persona]
I want to [functionality/feature]
So that [benefit/value]
Acceptance Criteria:
- Given [context/state]
- When [action/trigger]
- Then [expected outcome]
- And [additional conditions]
Definition of Done:
- [ ] Feature implemented
- [ ] Tests written and passing
- [ ] Documentation updated
- [ ] Code reviewed
- [ ] Deployed to stagingExample
As a online shopper
I want to save items to a wishlist
So that I can purchase them later when I'm ready
Acceptance Criteria:
- Given I am viewing a product page
- When I click "Add to Wishlist"
- Then the item is saved to my wishlist
- And I see a confirmation message
- And I can view my wishlist from the account menu
🎯 Epic Template
Epic Structure
Epic: [Epic Name]
Business Value: [Why this epic matters to the business]
User Value: [Why this epic matters to users]
Epic Description:
[High-level description of the epic and its goals]
User Stories in this Epic:
- [Story 1]: As a [user], I want [feature] so that [benefit]
- [Story 2]: As a [user], I want [feature] so that [benefit]
- [Story 3]: As a [user], I want [feature] so that [benefit]
Success Metrics:
- [Metric 1]: [Target value]
- [Metric 2]: [Target value]
- [Metric 3]: [Target value]
Dependencies:
- [Dependency 1]
- [Dependency 2]
Timeline:
- Start: [Date]
- Target Completion: [Date]Example
Epic: Mobile App Redesign
Business Value: Increase user engagement and reduce churn by 25%
User Value: Provide a modern, intuitive mobile experience that users love
Epic Description:
Complete redesign of our mobile app with modern UI/UX, improved performance, and new features based on user feedback.
User Stories in this Epic:
- As a mobile user, I want a faster app so that I can complete tasks quickly
- As a mobile user, I want an intuitive navigation so that I can find features easily
- As a mobile user, I want offline functionality so that I can use the app without internet
✅ Acceptance Criteria Templates
Given-When-Then Template
Given [initial context/state]
When [action/trigger occurs]
Then [expected outcome]
And [additional expected outcomes]
Example:
Given I am logged in as a premium user
When I try to access the advanced analytics feature
Then I should see the analytics dashboard
And I should be able to export data to CSVChecklist Template
Acceptance Criteria:
- [ ] [Specific requirement 1]
- [ ] [Specific requirement 2]
- [ ] [Specific requirement 3]
- [ ] [Error handling requirement]
- [ ] [Performance requirement]
Example:
- [ ] User can create a new account with email and password
- [ ] System validates email format before submission
- [ ] User receives confirmation email within 5 minutes
- [ ] System shows error message for invalid email format
- [ ] Account creation completes within 3 secondsRelated Resources
📚 User Story Examples
See real user story examples from successful product teams across different industries.
View Examples🤖 User Story Generator
Use AI to generate user stories and acceptance criteria for your features.
Try Generator🎯 User Story Generator Prompt
Get the AI prompt to generate user stories with ChatGPT and other AI tools.
Get Prompt📋 PRD Templates
Complete Product Requirements Document templates that include user stories.
View PRD Templates📥 Downloadable Template Formats
Word Templates
Ready-to-use Microsoft Word templates for user stories, epics, and acceptance criteria.
Excel Templates
Spreadsheet templates with formulas for tracking and managing user stories.
PDF Templates
Print-ready PDF templates for physical story cards and documentation.
All templates are free to download and customize for your team's needs.
Related Resources for Product Managers
📝 User Story Examples & Tools
See these templates in action with real examples and AI-powered tools.
📊 Product Requirements & Planning
Use these templates alongside comprehensive product planning resources.
🔬 Research & User Insights
Understand your users to create better user stories with these research tools.
🚀 AI-Powered Product Management
Accelerate your user story creation with AI tools and automation.
📋 Get weekly user story templates and product management resources
Join 5,000+ PMs getting the best AI content every week
Frequently Asked Questions About User Story Templates
What is the standard user story template?
The standard user story template is: “As a [user], I want [functionality], so that [benefit].” Most teams also add acceptance criteria, dependencies, and a definition of done.
When should I use a user story template instead of a PRD?
Use a PRD when you need product context, goals, scope, and tradeoffs. Use a user story template when you are breaking that larger plan into implementation-ready backlog items for design and engineering.
What should a good user story include?
A good user story includes a clear user, clear action, clear outcome, and acceptance criteria that remove ambiguity for engineering and QA. It should explain value, not just output.