> For the complete documentation index, see [llms.txt](https://governance.treasuries.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://governance.treasuries.io/approaches/score-voting-approaches/points-allocation-approaches/single-point-per-proposal.md).
# Single point per proposal
**Overview**
Everyone is given a single point they can allocate per proposal. This will often represent their entire voting power that they can use on any proposal decision.
**Low accuracy & expressiveness (Score - 2)**
Voters would be able to vote on any of the proposals that they prefer and allocate a point towards them. This gives the voter some expressiveness to indicate which proposals they prefer but does not enable them to express the intensity of their preferences. The other concern with this approach is around the accuracy of the outcome as it doesn’t force the voter to select the most important proposals. Instead voters could simply decide to approve every proposal that they want to.
**Very low voting complexity (Score - 5)**
The voting process would be the same for every single decision which makes the voting process simple. Only having one point to allocate means the voting process remains simple. Every voter would get the same experience within a given decision and with any future decisions.
**Very low voting time required (Score - 5)**
There is only one point to allocate and voters would become familiar with the approach. This approach would keep the time required to participate to a minimum.
**Very low game theory risks (Score - 5)**
Bad actors would not get any benefit from diluted voting power as every voter would apply the full voting power on each proposal they approve. Certain voting behaviour would not give these bad actors more influence over others beyond the influence of their own voting power.
**Total score = 17 / 20**
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://governance.treasuries.io/approaches/score-voting-approaches/points-allocation-approaches/single-point-per-proposal.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.