As we’ve taken a more intentional approach in figuring out sustainable engagement in governance, we’ve come across a few clarifying questions recently about what is in fact expected of Stewards, and so this post is designed to canonically answer that.
On the surface, Stewards are in charge of listening to their constituents, evaluating and 
voting on proposals. But the level of responsibility tends to go much deeper - Stewards are where the buck stops for GitcoinDAO. They are the protectors of the legitimacy of the DAO, they are responsible for keeping the DAO on track to accomplish its mission, and they are final enforcers of responsibility for everyone working on the GitcoinDAO’s mission"
Tangibly - a minimum threshold of steward duties are:
<ol>
<li>actively listening to their constituents (continuously - through own means/via the gov forum)</li>
<li>follow what’s going on <a href="http://gov.gitcoin.co">gov.gitcoin.co 2</a> (~1x/week to keep on top of current events)</li>
<li>attend the monthly stewards call (1x/month) - <a href="https://www.addevent.com/calendar/pz351122">you can add the GD event calendar here 4</a>
</li>
<li>participate in the steward council once it gets ratified and if you are part of it (reviewed and renewed every quarter) + take actions outlined in the council meeting (1x/month) - <a href="https://gov.gitcoin.co/t/introducing-the-steward-council/9485">more info here 5</a>
</li>
<li>should stewards come across conversations relevant to the GD mission/or where GD could help, bring the DAO into the conversation</li>
</ol>
As stewards’ duties evolve over time, the plan is to update this post so it will always be a canonical source of truth for stewards to understand their responsibilities and more importantly, encourage newcomers in GD to engage in the governance process.
Please feel free to comment, acknowledge or discuss the range of duties and add any other relevant ones that you may have taken on or observed as beneficial within the ecosystem.

GD Steward Roles & Duties As we’ve taken a more intentional approach in figuring out sustainable

GD Steward Roles & Duties

# Gitcoin DAO Governance Process v2 - updated Previous versions and discussions: 
 
 
 v0 here . 
 
 v1 here . 
 
 v2

# Gitcoin DAO Governance Process v2 - updated

<h2>
<a name="abstract-1" href="#abstract-1"></a>Abstract</h2>
When GTC launched in May, governance over the Gitcoin platform was handed over to the community via a group of individuals known as Stewards. Stewards are trusted community leaders with delegated voting power to make decisions on behalf of the community.
This post looks at the potential creation of a steward council as a move towards a more active and engaged participation mechanic in governance. This council will consists of the most engaged stewards as exemplified by the engagement scorecards with a rating above 8/10. An open application process will also be in place for community members to join the forum provided their engagement score is 8/10. (*details on engagement scores below)
Note that GTC allocations will be distributed to the forum via a number of mechanisms which will evolve over time.
This proposal is split into the following sections:
<ul>
<li>Motivation: Why setup a steward council</li>
<li>Specification: A roadmap for implementing mechanics</li>
<li>Distribution: allocations for stewards work based on engagement (measured via the engagement cards)</li>
</ul>
The various sections of this proposal will be divided into separate Snapshot polls so any section that may require further discussion does not block other moving parts.
<h2>
<a name="motivation-2" href="#motivation-2"></a>Motivation</h2>
Over the past six months, the Gitcoin community and Stewards have been working tirelessly to build the first pillars of Gitcoin governance. There has been a lot of engagement on the Gitcoin forum and Discord, as well as wider discussions but the need for a sustainable engagement model is clear. Not just for Gitcoin DAO but DAOs in general.
The reality is there is just so much happening in crypto and the DAO space so there needs to be a way to not only keep track of it all but enable engagement through simple, non overly taxing yet highly valuable engagement flows. This is a first step towards that.
While we’re grateful for the hard work and time that has been committed thus far, we are swiftly realizing all of the Stewards have jobs, projects and commitments outside of Gitcoin which demand their attention. We have found that it is important to more actively involve not just those Stewards who are participating in Gitcoin day to day, but also those who can offer more of an outsiders’ perspective.
For this reason, we believe that it is both necessary and justified to begin rewarding Stewards for their time and energy in the form of additional governance rights.
The principle is simple: those who have participated in such a nascent system and are shaping its core functions would be some of the best people to guide it to a stage where broader contributions are possible.
It’s worth noting that these rewards are intentionally distributed in the form of governance weight with no economic value.
<h2>
<a name="specification-3" href="#specification-3"></a>Specification</h2>
<h3>
<a name="stewards-council-overview-4" href="#stewards-council-overview-4"></a>Stewards Council Overview</h3>
The first Stewards Council will be active from the time the proposal passes for a period of 120 days, with an evaluation in view of potential extension at the 90 day mark. The 120 day cadence matches the quarterly events in the Gitcoin DAO calendar such as grants rounds and offers a great opportunity to reflect, expand and amplify the mission of GD.
A formal structure to future forums will be presented at the end of the 120 day mark, assuming the model is deemed valuable by the community and any essential and valuable learnings are incorporated in the model.
Steward council responsibilities:
<ul>
<li>
Keeping a ‘docket’ of ongoing proposals / their current status
</li>
<li>
Ensuring proposals follow template(s) / creating any necessary adjustments to template(s) (a proposal geared towards proposal simplification and standardisation will be posed shortly)
</li>
<li>
Coming to an initial y/n answer on the proposal itself
</li>
<li>
Bi-weekly sync calls for better alignment &amp; broader DAO strategy discussion
</li>
</ul>
This splits the responsibilities of the stewards as follows and ensures a more manageable curated governance flow:
Steward forum: governance contribution / decision making
Steward top 5: governance ratification / execution (putting proposals up on Tally for now)
<h3>
<a name="steward-selection-5" href="#steward-selection-5"></a>Steward Selection</h3>
The selection will also take into account information from the steward engagement cards - in time, this will need to include better/finer metrics:
<ul>
<li>Evaluate how often the steward votes with the majority in Snapshot votes</li>
<li>Track not only the number of forum posts, but the steward’s reputation on the forum based on likes and replies</li>
<li>Better curation of voting engagement needs - notifications when a new prop is up and then measure the voting speed</li>
</ul>
Community members who sit outside of this threshold are welcome to submit a proposal to join, with incoming applications reviewed by the existing Stewards group (or a committee dedicated to onboarding).
<h3>
<a name="engagement-cards-6" href="#engagement-cards-6"></a>Engagement Cards</h3>
This is the current format of the steward engagement cards - <a href="https://stewards.eth.limo/">https://stewards.eth.limo/ 
 48</a> 
The aim is to diversify and expand measured engagement angles and even have the stewards update their cards with relevant information in the context of the council mandate and their tenure in the council. As a first step towards this, we will look at a baseline engagement score of 8 out of a possible 10 for participation in the forum.
<div><a href="/uploads/db4391/original/2X/d/d491559c423953fa9356f91a323abbfb9a8a7978.png"><div>
768×635 170 KB
</div></a></div>
<h2>
<a name="first-forum-distribution-7" href="#first-forum-distribution-7"></a>First Forum Distribution</h2>
The proposal is that a pool of GTC is allocated across the Stewards council for the term. This is to cover gas costs incurred in voting and offer fair allocation for the group as long as they fulfil their functions outlined above.
Separate Snapshot proposals will be made outlining further detail around these allocations, their timelines and their distribution.
To begin with, we can look at three options in terms of compensation:
A. 5,000 GTC 
B. 10,000 GTC 
C. 15,000 GTC
The options are there for the community to assess what a fair level of compensation might be in the context of the steward forum and its mandate. Please include thoughts on these levels in comments.
<h2>
<a name="tldr-8" href="#tldr-8"></a>TL;DR</h2>
This proposal looks to start a conversation around a Steward Council that would use representation and incentives as a main driver for sustained and increased engagement in the governance process.
It is designed to be a first attempt at a more engaged governance dynamic and by no means the only step forward. I would like to see a discussion around this followed by experimentation with a first forum. Lessons learnt will not only serve GD but the DAO space at large in terms of evolving DAO tooling and progressing our ecosystem.

Introducing the Steward Council 
  Abstract 
 When GTC launched in May, governance over the Gitcoin platform

Introducing the Steward Council

<h2>
<a name="tldr-1" href="#tldr-1"></a>tl;dr</h2>
You can explore the initial proposal <a href="https://gov.gitcoin.co/t/introducing-the-steward-council/9485/11">introducing the Steward Council here. 33</a>
This proposal seeks to select the members of the GD Steward Council, approve its mandate and tenure. We currently have 14 stewards elligible for a seat on the council.
This proposal is split into the following sections:
<ul>
<li>Engagement score updates: How the engagement scores have evolved based on community conversations and input</li>
<li>Formation: Who qualifies to be in the council &amp; selection</li>
<li>Mandate &amp; term: What are the requirements for council members + GTC allocation</li>
</ul>
<h2>
<a name="engagement-score-updates-2" href="#engagement-score-updates-2"></a>Engagement Score Updates</h2>
This council looks to elevate the participation of the most engaged stewards as exemplified by the engagement scorecards and looking at stewards with a rating above 8/10 (*details on engagement scores below). The scores have evolved to take into account more granular engagement beyond voting mechanics and delegation power.
The motivation behind this evolution is that engagement is manifold and contributors should be recognised for their work beyond on chain governance action points. We have also taken into account any drop off in engagement in the previous season (quarter) and will be working to make sure the cards are a real time reflection of engagement as this essential piece of DAO tooling evolves.
The following are adjustment scores contributing to overall ranking per steward:
<ul>
<li>Workstream lead role +5
</li>
<li>Workstream contributor role +3
</li>
<li>Lack of meaningful contributions, not taking part in voting or discussion in the previous season -3
</li>
</ul>
In future, to maintain a +8 rating, a steward will need to be active in a workstream or in DAO-wide discussions, a -1 deduction will be applied per 1 month of inactivity. As seasons kick in this quarter, this will be mkeasured/season.
<h2>
<a name="formation-3" href="#formation-3"></a>Formation</h2>
The current lineup of stewards with scores 8/10 and over is as follows:
<ul>
<li><a href="/u/disruptionjoe">@DisruptionJoe</a></li>
<li><a href="/u/pop">@Pop</a></li>
<li><a href="/u/krrisis">@krrisis</a></li>
<li><a href="/u/seedphrase">@seedphrase</a></li>
<li><a href="/u/bobjiang">@bobjiang</a></li>
<li><a href="/u/tjayrush">@tjayrush</a></li>
<li><a href="/u/sirlupinwatson">@Sirlupinwatson</a></li>
<li><a href="/u/helloshreyas">@HelloShreyas</a></li>
<li><a href="/u/lefterisjp">@lefterisjp</a></li>
<li><a href="/u/linda">@linda</a></li>
<li>griff *</li>
<li>Fishbiscuit*</li>
<li>kyle*</li>
<li>austingriffith*</li>
</ul>
(*apologies here stewards, only 10 can be tagged in one post)
<aside>
 <header>
 

 <a href="https://www.daostewards.xyz/" target="_blank">daostewards.xyz</a>
 </header>

 <article>
 

<h3><a href="https://www.daostewards.xyz/" target="_blank">The Steward Health Cards provides the most valuable metrics on engagement for... 11</a></h3>

 Stewards Health Cards


 </article>

 <div>
 
 
 </div>

 <div></div>
</aside>

As part of the discussion on the initial proposal, it’s important to understand who among these stewards feels like they have the bandwidth to take the council role on for its first season. The initial proposal was looking at a council formed of 10 stewards and the current lineup is at 14 - another point here is do we extend numbers or based on steward self-signalling re availability, do we stick to the original plan of 10.
Please express your opinions on the makeup of this council and whether you strongly feel other stewards should be included.
<h2>
<a name="mandate-term-4" href="#mandate-term-4"></a>Mandate &amp; Term</h2>
The first Stewards Council will be active from the time the proposal passes for a period of ~180 days, in line with the seasons cadence established as part of the proposal. One council should cover 2 seasons and there should be 2 councils/year.
The rough 180 day cadence matches the quarterly cadence of the Gitcoin DAO calendar and offers a great opportunity to reflect, expand and amplify the mission of GD. Cadence as follows:
<ul>
<li>Season 13 - 2.1 to 4.30 (GR13 | 3.9-3.24)</li>
<li>Season 14 - 5.1 to 7.30 (GR14 | 6.8-6.23)</li>
<li>Season 15 - 8.1 to 10.30 (GR15 | 9.7-9.22)</li>
<li>Season 16 - 11.1 to 1.31 (GR16 | 11.30-12.15)</li>
<li>and ongoing - any changes for holidays or other interruptions would be voted on</li>
</ul>
A milestone report will be presented at the end of the 180 day mark, ensuring the model is deemed valuable by the community and any essential and valuable learnings are incorporated in the model.
Steward council mandate:
<ul>
<li>Keeping a ‘docket’ of ongoing proposals / their current status</li>
<li>Ensure proposals follow <a href="https://gov.gitcoin.co/t/gitcoin-dao-workstream-accountability-flow/9644/14">template(s) 3</a> / creating any necessary adjustments to template(s)</li>
<li>Perform an in-depth analysis of budget requests by workstreams. This includes:</li>
</ul>
<ul>
<li>workstream performance and delivery(from the milestone reports included in the proposals)</li>
<li>funds left over from previous seasons and taking them into account for the season</li>
<li>list of contributors to workstream</li>
<li>value of ask</li>
</ul>
<ul>
<li>Consult on workstream performance/workstream leads’ milestone progress - address any workstream issues that may occur within a season</li>
<li>Participating in active discussion around proposals, timely voting</li>
<li>Availability for Tally proposal creation and ratification once a proposal has passed Snapshot</li>
<li>Participation in a council call that will be scheduled halfway between the monthly steward call (aka every two weeks) for better alignment &amp; broader DAO strategy discussion.</li>
</ul>
This mandate will evolve to take into account any learnings from the first council activity as we evolve the structure and the model based on optimum balance.
<h2>
<a name="first-forum-distribution-5" href="#first-forum-distribution-5"></a>First Forum Distribution</h2>
The proposal is that a pool of GTC is allocated across the Stewards Council for the term. This is to cover gas costs incurred in voting and offer fair allocation for the group as long as they fulfil their functions outlined above. The funds can also be allocated to everyone voting as highlighted by some of the comments on the initial version of the council proposal. This action can be decided on by the council as one of their first joint proposals.
A Snapshot proposal will be made separately around the allocation for the first council term. Based on the comments on the initial post, an overall agreement was option A. 5,000 GTC for the whole council for the whole mandate. We can potentially include all 3 options in the Snapshot for broader agreement.
*A. 5,000 GTC 
B. 10,000 GTC 
C. 15,000 GTC
*These options are here for the community to assess what a fair level of compensation might be in the context of the steward council and its mandate.

The Steward Council - Formation & Mandate 
  tl;dr 
 You can explore the initial proposal  introducing the

The Steward Council - Formation & Mandate

Original <a href="https://gov.gitcoin.co/t/gitcoin-dao-workstream-accountability-flow/9644">Accountability flow 7</a>Jan 2022
Tl;dr
- Reasoning behind rework of the flow 
- New format 
- Consultation 
- Evaluation 
- Timeline S15
<h2>
<a name="summary-1" href="#summary-1"></a>Summary</h2>
This proposal seeks to amend, improve and standardize the budget proposal process for Gitcoin DAO following extensive feedback across the steward council, the steward circle and workstream leads/contributors. The purpose of this revision of the accountability flow is to integrate the lessons learnt in S14 and ensure the new budget proposal process delivers the most value, alignment and collaborative consensus across the DAO. It is designed to ensure that any funding requested by workstreams is in service of and in line with the Purpose and Essential Intents of the DAO, improving transparency, accountability and accessibility when it comes to proposal review processes.
<h2>
<a name="motivation-2" href="#motivation-2"></a>Motivation</h2>
A process to uncover, refine and define the purpose of Gitcoin DAO became a necessity as discussions around what should and should not be funded in S14 started to intensify. It became very apparent that any budget request must be made in alignment and with direct contribution to the purpose of the DAO.
As a constantly iterating and innovating force in the web3 ecosystem, improving the accessibility and transparency of DAO flows is the next level in better coordination. For our DAO ecosystem to flourish, it requires a mindful effort to improve on current tooling and to support better ways for DAOs at large to enable governance engagement and accountability across the board.
<h2>
<a name="current-proposal-framework-3" href="#current-proposal-framework-3"></a>Current proposal framework</h2>
Proposals currently vary broadly in their stated goals, format and monetary requests.
This v2 of the Accountability flow aims to establish a better standard template to facilitate review and discussion. It aims to take the alignment started in the run-up to S14 and bring all Gitcoin DAO activity around a clear, transparent, quarterly dynamic for better alignment, contribution and transparency across the organism.
<h2>
<a name="new-budget-proposal-framework-4" href="#new-budget-proposal-framework-4"></a>New budget proposal framework</h2>
As observed in S14, most of the proposals ended up being amended at least once so a better distinction between stages should make the process far clearer. All budget proposals should follow the following format &amp; flow.
<div><a href="/uploads/db4391/original/2X/b/b4b0a4029e1b9a8085f8ccf3b81d097e9d708665.jpeg"><div>
1600×797 102 KB
</div></a></div>
STAGES:
1. The first stage of a budget proposal will be a DRAFT
<ul>
<li>the draft proposal will be posted on the forum showing [DRAFT] in the title and shared in the first steward call of the new season (ex. [DRAFT] Public Goods Funding budget request)</li>
<li>the DRAFT proposal will then enter a period of consultation lasting two weeks. Feedback and discussion will happen both on the forum and in the stewards council call and should involve input from the community, stewards, the council and other workstreams. Workstream feedback is highly encouraged at this stage as cross-stream support could become a key piece of the evaluation flow.</li>
</ul>
2. The second stage of a budget proposal will be INTEGRATED
<ul>
<li>Any feedback from the steward calls and the DRAFT post will be integrated in this proposal and published to the forum - this is to ensure clarity in amendments, changes and evolution</li>
<li>this stage can be on the forum for one week</li>
</ul>
3. The third stage will be ACTIVE
<ul>
<li>a proposal will move to ACTIVE after the consultation period ends and all feedback is integrated. This ACTIVE proposal will be setup directly on Snapshot and be setup with the following format:</li>
</ul>
- [WORKSTREAM] S# Budget Request 
- Full amount - GTC and USDC Equivalent 
- Tl;dr - one paragraph 
- Main season objectives 
- Link to INTEGRATED DRAFT for all info
The Snapshot will be live for a period of five days.
4. The fourth and final stage will be RATIFIED
<ul>
<li>a proposal is RATIFIED once it reaches Tally and the funds are moved into the multisigs</li>
<li>ANY proposal moving into a Tally should PASS. All decisions on yes/no are made in the ACTIVE Snapshot phase.</li>
<li>Format: XXX workstream S# funding request ratification</li>
</ul>
The Tally vote will be live for a period of five days.
5. The fifth potential stage - should a proposal be “denied”
<ul>
<li>In the event of a proposal being denied, a new proposal can be created using the following template. The purpose of the template is to create a clear delineation between maintaining status quo only (current operations and fulfilling OKRs for the season vs any expansion)</li>
</ul>
<div><a href="/uploads/db4391/original/2X/a/aebac88bd36b583d45fedc54824ca5bc8f07f3d1.png"><div>
1494×930 197 KB
</div></a></div>
FORMAT:
<ul>
<li>Which EI (Essential Intent) is the WS in alignment with (ratified current version <a href="https://gov.gitcoin.co/t/update-gitcoindaos-adopted-purpose-and-essential-intents/10984/3">here 3</a>)</li>
<li>A tl;dr section at the top of the proposal summarizing the main focus for the season.This is for increased transparency and a smoother decision making process.</li>
<li>A milestone report containing goals achieved during the previous quarter. The milestone report should include:</li>
<li>who are the current contributors (marked as FT or PT)</li>
<li>funds spent to date/season &amp; overall</li>
<li>any funds carrying over to the next quarter</li>
<li>notable achievements for the quarter</li>
<li>Proposal body</li>
<li>Mentioning initiatives, objectives, and metrics</li>
<li>Budget breakdown</li>
</ul>
<h2>
<a name="example-proposal-template-5" href="#example-proposal-template-5"></a>Example Proposal Template:</h2>
EI
Add the Essential Intent(s) respective Workstream is focused on.
TL;DR
Text section goes here.
Amount
State budget ask in GTC &amp; USD equivalent. This section should include the following note:
The GTC total will be adjusted based on the current market value at the time this proposal is moved to Tally. The vote will be to send the requested $USD amount in GTC at the lower of the current price or the 20 day moving average, whichever is lower.
Milestone Report
Initiative/Dept Objectives Past Season Value Delivered
Proposal Body
Focus on essential work for season you are requesting budget for ONLY
Initiative/Dept EI Objective Current Season Key Results
Budget Breakdown
Budget Category 
(Dept/team) Goal/OKR relevant to EI for season requested Amount GTC Amount USD
<ul>
<li>Visual breakdown (this will be created by <a href="/u/chrisdean">@ChrisDean</a> in collaboration with each workstream - an automation/templating of this endeavour will hopefully be in place by S16)</li>
</ul>
CONSULTATION:
The consultation, evaluation and ratification period for proposals is to be extended from the cadence of ~15 days experienced in S14 (and before) to a longer process as of season 16. This means that DRAFTS would be presented at least one to two months before the end of the previous season.
This is to enable ample discussion, feedback sessions and engagement across the decision making apparatus.
Types of discussion:
Workstream: xx
CSDO: xx
Forum: Comments and feedback should be recorded on the forum as in previous seasons
Stewards Call: a space for discussion involving the stewards - this will involve the steward/workstream allocation we discussed for better insight
Steward Council Call: a space for strategic discussion amongst council members to address any pressing or problematic requests
EVALUATION:
<div><a href="/uploads/db4391/original/2X/f/f8e470ab82cb94fb775c4a7dfff957f83a97b344.png"><div>
Screenshot 2022-07-25 at 13.53.331190×1212 75.6 KB
</div></a></div>
<div><a href="/uploads/db4391/original/2X/f/ffd9b14ea63f023a1b9a237904f4498fbcb8b0b5.png"><div>
Screenshot 2022-07-25 at 13.55.471376×818 75.1 KB
</div></a></div>
*NOTE: not all WS will match ALL EIs
*Any budget request scoring under 4 average across stewards/community may need to revise budget request
Financial Evaluation:
<div><a href="/uploads/db4391/original/2X/c/cabd2995a44a02b0bfbec3ff5d5e1b1c6a631966.png"><div>
1600×650 164 KB
</div></a></div>
A visual report of the budgets for all WS against the treasury will be provided and WS will have it accessible to include in their proposals. A more complex forecasting report could evolve from here where we genuinely look at short | medium | long term.
Timeline
Key dates for <a href="https://docs.google.com/document/d/1GncgmUXmk4QU_SINyy5NO8ogsEn5WM1t40T1FCflEUk/edit">upcoming season (S15) 4</a> :
07/25-08/08 - Review DRAFT proposals
08/08 - INTEGRATED proposals on forum
08/15 - FINAL proposals on snapshot
08/22 - FINAL proposals on tally
S16 learning &amp; dates coming up in v3

Budget Proposal Process for Gitcoin DAO - v2 Original  Accountability flow   7  Jan 2022 
  Tl;dr

Budget Proposal Process for Gitcoin DAO - v2

<h2>
<a name="summary-1" href="#summary-1"></a>Summary</h2>
This proposal seeks to amend, improve and standardise the proposal process for Gitcoin DAO. The purpose of this standardisation attempt is to improve transparency, accountability and accessibility when it comes to proposal review processes.
<h2>
<a name="motivation-2" href="#motivation-2"></a>Motivation</h2>
One of Gitcoin’s missions is to upgrade society’s capabilities to coordinate - with the hope of defeating coordination failure altogether.
As a constantly iterating and innovating force in the web3 ecosystem, improving the accessibility and transparency of DAO flows is the next level in better coordination. For our DAO ecosystem to flourish, it requires a mindful effort to improve on current tooling and to support better ways for DAOs at large to enable governance engagement and accountability across the board.
<h2>
<a name="current-proposal-framework-3" href="#current-proposal-framework-3"></a>Current proposal framework</h2>
Proposals can vary broadly in their stated goals and requests.
*They may ask the community to endorse a specific policy and procedure (e.g. “Should Gitcoin Grants allow VC backed projects?”), or ask the community to build something (e.g. “Building a new software tool” or “Writing improved documentation”).
*They may have no funding requests attached, or make an explicit request for funding (e.g. “We would like to create a workstream focused on building a decentralized architecture for Gitcoin Grants”).
There is currently no formal template for proposals. This document aims to establish a standard template to facilitate review. The proposal also aims to align all Gitcoin DAO activity around quarterly dynamics for better alignment, contribution and transparency across the organism.
<h2>
<a name="new-improved-proposal-framework-4" href="#new-improved-proposal-framework-4"></a>New (improved) proposal framework</h2>
All proposals should ideally follow the following format:
<ol>
<li>
A tl;dr section at the top of the proposal summarizing the main points. This is for increased transparency and a smoother decision making process.
</li>
<li>
If applicable, a milestone report containing goals achieved during the previous quarter. The milestone report should include:
</li>
</ol>
<ul>
<li>number of current contributors (marked as FT or PT)</li>
<li>funds spent to date - perhaps adopting some quarterly reporting?</li>
<li>any funds carrying over to the next quarter</li>
<li>notable achievements for the quarter</li>
<li>have the actions of the workstream brought back value into the DAO/treasury</li>
</ul>
<ol>
<li>The flow of a proposal will still follow the <a href="https://gov.gitcoin.co/t/gitcoin-dao-governance-process-v2-updated/7860">steps laid out in the Gov process 20</a>
</li>
</ol>
These (and other) accountability metrics could form the basis of workstream health cards/reports that may serve not only as a catalyst for self improvement but as an opportunity to bring greater transparency, collaboration and accountability into the DAO ecosystem at large.
<h2>
<a name="standardisation-does-not-aim-to-stifle-creativity-and-originality-it-merely-aims-to-facilitate-better-and-speedier-delivery-of-information-to-promote-better-engagement-in-governance-and-participation-mechanisms-5" href="#standardisation-does-not-aim-to-stifle-creativity-and-originality-it-merely-aims-to-facilitate-better-and-speedier-delivery-of-information-to-promote-better-engagement-in-governance-and-participation-mechanisms-5"></a>Standardisation does not aim to stifle creativity and originality, it merely aims to facilitate better and speedier delivery of information to promote better engagement in governance and participation mechanisms.</h2>
<h2>
<a name="example-proposal-template-6" href="#example-proposal-template-6"></a>Example Proposal Template:</h2>
TLDR
Text of section goes here.
Milestone Report
Text of section goes here.
Proposal Body
Text of section goes here.

GD Steward Roles & Duties

# Gitcoin DAO Governance Process v2 - updated

Introducing the Steward Council

The Steward Council - Formation & Mandate

Budget Proposal Process for Gitcoin DAO - v2

Gitcoin DAO - Workstream Accountability Flow

Got something to add?