---
tags: PRDs
---

| Status | Work in progress |
|-------------- |----------------- |
| **Epic link(s)** | [name](link) |
| **Mockup** | [Figma Page(s)](...) TBD
| **Author(s)** | @author |
| **Initiative(s)** | [name](link) |

# PRD TITLE

# Objective/Goal:
*Why the customer needs it? Explain why are you building this and what do you hope to accomplish.*
...
# Features:
*What is expected by the customer? For each feature, you should include a description, goal and use case. Additional details may be helpful or necessary depending on the complexity of the feature, such as out-of-scope items.*
...
# UX Flow & Design Notes:
*General guidance. This is not the place for pixel-perfect mockups or wireframes that map out every possible scenario. Describe the overall user workflow. Provide links to figma, sketches, assumptions*
...
# System & Environment Requirements:
*Which end-user environments will be supported (such as browsers, operating systems, memory, and processing power, cloud envs, tools, 3rd party integrations etc.).*
...
# Assumptions, Constraints & Dependencies:
*List out what is expected of users, any limits for the implementation to be aware of and any outside elements required for the final solution to be functional.*
...