Collect Input Before an Optional Decision
Define what the consultation can change
Before asking a group for input, write which choice remains open, who can make it, and what participation does not commit anyone to do. Consultation is not a promise of unanimity or permission to make commitments for absent people.
In a fictional example, you offer to organize one free, optional sketching walk for adult friends. You have agreed with them that you may choose the route for the invitation; each person remains free not to attend. There are no bookings, shared payments, employment links, transport obligations, or dependent participants. Saturday afternoon is the time you can offer. Riverside and town-square routes remain possibilities.
Tell people that the time is fixed for your offer and the route is open. If the time is not actually fixed, do not call it fixed to discourage input. If you lack authority to make the choice, identify who has it or leave the decision unmade.
Ask for relevant input without enrolling people
You might write in the existing planning thread:
I can offer a sketching walk on Saturday afternoon. The route is still open between the riverside and the town square. Is there a route preference or practical constraint you'd like me to consider? This isn't an attendance commitment.
Use only a channel already appropriate for this plan. Do not demand personal explanations for constraints. Someone can say a route does not work without describing health, finances, or family circumstances. An answer about route preference is not a yes to attendance, material costs, or another task.
Do not invent an urgency deadline. If a real planning limit matters, explain what you will decide and when, within your actual authority. A deadline for your decision is not a rule that silence becomes consent.
Keep a minimal decision note, not a response register
A private note can help you compare the actual input. Its purpose here is choosing the offered route, not measuring anyone's cooperation. Only you need to see the note; do not circulate named responses or a public list of people who have not answered.
Record the minimum content needed: “Riverside preferred for drawing views; town square preferred for a shorter route; further input not received.” Keep an expressed objection distinct from an unknown preference. Do not infer that a missing reply means approval, indifference, or deliberate obstruction. You need not keep a list of people who haven't replied or chase unanswered requests.
For this example, stop retaining the private comparison once the invitation is settled or the plan is dropped. Do not reuse it as a profile of friends' reliability. Other ordinary plans may need a different, explicitly justified record or none at all; there is no general recordkeeping duty.
Make disagreement visible without manufacturing agreement
Suppose the received preferences conflict. You can leave the walk unoffered, or use the route-selection authority already agreed and explain the relevant basis. For example, if you choose the town square because you can offer the shorter route that day, say that. Do not announce “Everyone agreed” when they did not.
Sharing the chosen route does not require naming whose preference was not adopted. Describe the choice and its basis without exposing private reasons. Those who preferred another route may decline attendance. Do not promise a later event to compensate unless you actually choose and can make that offer.
Finish within the original authority
If the choice would require a new shared cost, access permission, or duty, pause rather than stretch the consultation into authorization. If no workable route can be selected, “No walk arranged” is a valid result. Employment, essential resources, formal governance, and dependent participation need their own processes. The useful output is an honest optional decision or non-decision, not a compliant group.