What Is a DAO Proposal? How to Write and Submit One

A DAO proposal is a formal, written request for the DAO's community to approve a specific action, such as spending treasury funds, changing a protocol parameter, or funding a new initiative, submitted through the DAO's governance process and ultimately decided by a vote of the relevant token holders.

Proposals are the actual unit of decision-making in a DAO. Rather than an executive simply deciding and announcing a change, anyone meeting a DAO's eligibility requirements, sometimes a minimum token holding to prevent spam, can draft and submit a proposal that the entire community then debates and votes on. Understanding proposals matters whether you plan to submit one yourself or simply want to follow and evaluate what your DAO is voting on, a broader process covered in how DAOs make decisions.

Structuring a proposal that gets read and taken seriously

Proposals that pass smoothly tend to share a similar structure, regardless of the specific DAO:

• A clear, specific title and summary stating exactly what is being requested, avoiding vague language that forces readers to dig through the full text to understand the ask
• Context and motivation, explaining why this change or spend is needed and what problem it solves
• A concrete action or spend amount, specified precisely rather than left open-ended, since vague proposals are harder for a community to evaluate and vote on confidently
• Success metrics or a defined scope, especially for funding requests, so the community and the proposer both have a clear basis for judging whether the funded work delivered as promised
• Risks and alternatives considered, showing the proposer thought through potential downsides rather than presenting only the upside case

The typical proposal pipeline

Most DAOs route a proposal through several stages before it becomes binding: an informal forum draft to gather early feedback, a lightweight temperature check to gauge rough sentiment, a formal off-chain vote often through a Snapshot-style platform, and finally, for anything requiring enforceable execution, a binding on-chain vote followed by a timelock before the change takes effect. Skipping the earlier stages and going straight to a binding vote is usually discouraged, since it removes the opportunity for the community to catch problems or suggest improvements before a proposal becomes final.

Thresholds needed to pass

Passing thresholds vary significantly by DAO and by the type of change being proposed. Routine or lower-stakes proposals often require only a simple majority of votes cast, along with meeting a minimum quorum, a baseline level of total participation, to ensure a small, unrepresentative group did not decide the outcome alone. Higher-stakes proposals, such as upgrading core smart contracts or moving very large sums from the treasury, frequently require a supermajority, such as two-thirds of votes cast, and a higher quorum threshold, reflecting the greater consequence of getting such decisions wrong.

Proposal types compared

Proposal type	Typical threshold	Typical review depth
Minor parameter tweak	Simple majority, standard quorum	Light forum discussion
Treasury grant or spend	Simple or supermajority depending on size	Moderate, budget scrutiny
Core contract upgrade	Supermajority, high quorum	Extensive, often includes a security audit review
Signer or delegate change	Varies, often simple majority	Moderate, focused on trust and track record

Common reasons proposals fail

Proposals often fail not because the underlying idea was bad, but because of how they were presented or timed: requesting funding without a clear scope or success metric, submitting a proposal without first gathering informal community feedback, underestimating how much context voters need to understand an unfamiliar technical change, or proposing something that conflicts with a previously agreed-upon governance token holder priority without acknowledging that history. Proposals that skip the forum discussion stage entirely and go straight to a vote also tend to underperform, since they give opponents no opportunity to raise concerns before positions have hardened around a binding vote.

Amending a proposal mid-discussion

It is common and generally encouraged for a proposer to revise their draft in response to forum feedback before it moves to a formal vote, rather than treating the first draft as fixed. Experienced proposers often explicitly flag which parts of a proposal are open to negotiation and which are firm, helping the community focus its feedback where it can actually change the outcome. A proposal that visibly incorporated community pushback tends to pass more comfortably than one submitted unchanged despite clear objections raised during discussion, since voters can see the proposer engaged seriously with concerns rather than ignoring them.

Bottom line

A DAO proposal is the formal mechanism through which any community member can request a specific action be taken, evaluated and decided through the DAO's governance pipeline rather than a single decision-maker. Clear scope, honest treatment of risks, and following the DAO's established review stages meaningfully improve a proposal's odds of passing and, just as importantly, of being executed well if it does.