# Structured Proposal Format
**URL:** https://forum.polkadot.network/t/structured-proposal-format/10198
**Category:** Governance
**Created:** [September 28, 2024, 8:09pm UTC](https://forum.polkadot.network/t/structured-proposal-format/10198 "2024-09-28T20:09:21Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@D0tSama](https://forum.polkadot.network/u/D0tSama)
#### Post date: [September 28, 2024, 8:09pm UTC](https://forum.polkadot.network/t/structured-proposal-format/10198/1 "2024-09-28T20:09:22Z")
To streamline the review process for the **Big Spender, Medium Spender,** and **Small Spender** tracks on the Polkadot OpenGov platform, it is essential to implement a standardized template that clearly presents all relevant information.
I have developed a preliminary version of this standardized template and would greatly appreciate your feedback, suggestions, and any necessary revisions. If the community supports moving forward with this initiative, we will need to establish a method to ensure that proposers/ref creators adopt and utilize this template consistently.
Thank you for your time and input. Cheers!
**Benefits of Using This Structured Template**
**Enhanced Readability:** A standardized format makes it easier to locate and understand key information.
**Efficient Evaluation:** Reviewers can quickly assess each proposal’s merits by following a consistent structure.
**Improved Quality:** Proposers are encouraged to think through all aspects of their project, leading to more comprehensive and viable proposals.
**Transparency:** Clear presentation of funding sources and financial needs builds trust within the community.
## **Standardized Proposal Template**
### **1. Project Overview**
- **Title:** _(Clear and concise name of the project)_
- **Track:** _(Big Spender, Medium Spender, Small Spender)_
- **Submitted By:** _(Name(s) and contact information of the proposer(s))_
- **Submission Date:** _(Date of proposal submission)_
### **2. Description**
- **Summary:** _(A brief overview highlighting the purpose and significance of the project)_
- **Detailed Description:** _(In-depth explanation, including key features, functionalities, and methodologies)_
### **3. Vision and Goals**
- **Vision:** _(Long-term impact and alignment with Polkadot’s ecosystem)_
- **Goals:** _(Specific, measurable objectives the project aims to achieve)_
### **4. Scope**
- **Inclusions:** _(What the project will cover)_
- **Exclusions:** _(What is intentionally excluded to maintain focus and feasibility)_
### **5. Phase Information**
- **Current Phase:** _(Indicate the current stage, e.g., Phase 1, Phase 2, Phase 3)_
- **Phase Details:** _(Specific activities and milestones for each phase)_
### **6. Funding Details**
- **Requested Funding:** _(Amount being requested from the treasury)_
- **Previous Funding:**
- **Amount:**
- **Source:**
- **Purpose:**
- **Seed Rounds:**
- **Investors:**
- **Amounts:**
- **Other Funding Sources:** _(Grants, partnerships, etc.)_
### **7. Resource Requirements and Costs**
- **Human Resources:** _(Roles and number of team members needed)_
- **Technical Resources:** _(Software, hardware, or other technical needs)_
- **Cost Breakdown:**
- **Salaries:**
- **Equipment:**
- **Marketing:**
- **Miscellaneous:**
### **8. Scope and Deliverables**
- **Tasks:** _(Specific tasks to be completed)_
- **Milestones:** _(Key milestones with expected completion dates)_
- **Deliverables:** _(Tangible outputs, e.g., software releases, documentation)_
### **9. Outcome Expected**
- **Impact:** _(How the project will benefit the community or ecosystem)_
- **Metrics:** _(Quantitative and qualitative measures to assess success)_
### **10. Next Steps**
- **Immediate Actions:** _(Steps to be taken following proposal approval)_
- **Long-term Plans:** _(Future developments or expansions post-initial phase)_
### **11. Maintenance Costs**
- **Ongoing Expenses:** _(Costs required to maintain and support the project after initial deployment)_
- **Sustainability Plan:** _(How maintenance will be funded in the long term)_
### **12. Risks and Mitigation**
- **Potential Risks:** _(Identify possible challenges or obstacles)_
- **Mitigation Strategies:** _(Plans to address and overcome identified risks)_
### **13. Appendices**
- **Supporting Documents:** _(Additional materials supporting the proposal, e.g., diagrams, charts)_
- **Team Credentials:** _(Brief bios or resumes of key team members)_
---
### Author:  [@Juba.K](https://forum.polkadot.network/u/Juba.K)
#### Post date: [September 28, 2024, 9:03pm UTC](https://forum.polkadot.network/t/structured-proposal-format/10198/2 "2024-09-28T21:03:16Z")
It’s great to see so many pro-active community members, however, there has been extensive work done in the structuring of OpenGov participations and submissions already - and to continue proposing new frameworks / guidelines without cross-referencing the work that has already been done by entities such as OpenGovWatch will only lead to further confusion and ineffective double work.
The best plan of action is to continue building on established parameters that have been accepted by the community and funded through one of the many platforms - OpenGov or W3F so that we can continue a coherent path forward.
> **[Welcome to OpenGov.Watch | OpenGov.Watch](https://www.opengov.watch/)**
>
> Polkadot is the biggest DAO in the world. We help OpenGov grow up and develop structures and culture. We monitor ongoing developments, publish reports, consult OpenGov participants and provide thought leadership through curating a community-developed...
J.
---
### Author:  [@D0tSama](https://forum.polkadot.network/u/D0tSama)
#### Post date: [September 28, 2024, 9:56pm UTC](https://forum.polkadot.network/t/structured-proposal-format/10198/3 "2024-09-28T21:56:51Z")
Thank you for taking the time read and respond. Appreciate the links you shared.
I am not expecting to change the current guidelines being set. I am just relaying my experience when reviewing these proposals and providing some feedback that hopefully if teams start to use them in addition to the current guidelines will help individuals in reviewing the proposals. My hope ia to bring more people (DOT holders) to use their DOT and vote.
Cureent guidelines are great but if there is a standard template it will be easier for individuals to access and vote on the proposals.
Thanks again!
---
### Author:  [@Juba.K](https://forum.polkadot.network/u/Juba.K)
#### Post date: [September 28, 2024, 10:15pm UTC](https://forum.polkadot.network/t/structured-proposal-format/10198/4 "2024-09-28T22:15:09Z")
@D0tSama - again, believe contacting OGW with ideas with what you see could be improvements on existing templates would be the most helpful.
See existing guide:
> **[Polkadot Spending Proposal - Template](https://docs.google.com/document/d/1O_84mXYFERCavmnJyxbIPKFkG0bVBySRjCVy-d-VKcc/edit#heading=h.v6is2ta0txr1)**
>
> Treasury Proposal: \[TITLE OF THE PROPOSAL\] Proponent: \[Polkadot Address with an On-chain identity\] Date: \[DD.MM.YYYY\] Requested DOT: \[Approximate amount based on Subscan’s price converter\] Short description: \[A single sentence presenting project’s...
J
---
### Author:  [@D0tSama](https://forum.polkadot.network/u/D0tSama)
#### Post date: [September 28, 2024, 10:41pm UTC](https://forum.polkadot.network/t/structured-proposal-format/10198/5 "2024-09-28T22:41:51Z")
Thanks!
---
### Author:  [@lilymendzdev](https://forum.polkadot.network/u/lilymendzdev)
#### Post date: [September 28, 2024, 11:41pm UTC](https://forum.polkadot.network/t/structured-proposal-format/10198/6 "2024-09-28T23:41:05Z")
I think these types of documents should be more accessible through Polkassembly or Subsquare. There should be a section for this, as well as other important links.