A small volunteer project becomes known for being helpful. Soon it receives requests beyond its original purpose, and every polite “we will try” becomes work that someone is expected to do. A clear way to decline protects both the project and the people relying on its answer.
Define the service people can actually expect
Write a short description of what the project does, who it serves, when it operates and what falls outside its role. Review that description against actual volunteer time and resources. A broad mission statement is not a promise to accept every related task.
Agree who can make an exception and what happens when the project is full. Volunteers should not have to invent a new boundary in every conversation or feel personally responsible for accepting work they cannot safely complete.
Make the answer useful without pretending
A response can acknowledge the request, state the limit and offer a verified next step where one exists. For a fictional repair café: “We can assess small household items during our monthly session, but we do not provide home visits. The next session is on the published date.” Do not invent another organisation’s availability simply to soften the refusal.
If there is a waiting list, explain what joining it means. Is it an expression of interest, a provisional place or a confirmed booking? Avoid collecting sensitive information that the project does not need.
Use repeated requests as evidence
Keep a simple, privacy-conscious count of requests outside the current scope. At a planned review, consider whether they reveal an unmet need worth discussing with partners or funders. That is a separate decision from stretching this week’s volunteers beyond their capacity.
A respectful decline is not a failure of community spirit. It gives people an honest answer while preserving the reliability of the service you do provide. The strongest promise is one the project can keep consistently.