Before a community project begins, write this one-page brief

Column one: distinguish need from assumption

Describe the situation you hope to address in one sentence, with its source, date and the person or role still needed to check it. Holding a talk is a method, not a need. Difficulty finding clear participation information is a question that can be investigated. If you have not established the need, mark it for confirmation rather than defining another person's difficulties.

Include only the general information needed to discuss the idea. Do not attach names, photographs or personal experiences of students, families or service recipients. Identify the information or support to explore without deciding anyone's medical condition, eligibility or willingness to receive assistance.

Column two: define tasks that can be checked

For each task, record its starting condition, responsible role, deliverable and handover method. For example, a checked index of existing public resources is a concrete deliverable; increasing awareness is not a sufficient task description. Separate preparation from work on the activity day so that the full workload is visible.

Add an out-of-scope box for services or commitments the project will not provide. Where specialist staff, venue permission or other arrangements are needed, record them as unconfirmed conditions. Do not describe proposed support as an established partnership. Begin with the smallest useful task that has a responsible person.

Column three: show the resource gap honestly

Resources can include time, supplies, space, writing skills and on-site guidance. Mark each as available, awaiting confirmation or missing, and assign someone to check it. For borrowed items, record quantities, collection and return times, and the role receiving them. A message saying someone will bring them is not a complete handover record.

Where costs are involved, note the purpose and the contact who must confirm arrangements. Do not invent funding, donation accounts or reimbursement promises. The brief should expose unresolved needs rather than hide them behind a budget that looks complete.

Column four: give each question a place for a reply

Choose a coordinating role and a contact point for external enquiries. This prevents volunteers sending inconsistent versions. Write answerable questions, such as whether a wheelchair user can reach the activity area. Record the date and meaning of the reply. An unanswered question remains open; silence does not establish agreement.

Give discussion copies a date and version. For each revision, state what changed, who confirmed it and which previous arrangements no longer apply. Share one external summary. Keep internal working notes according to the team's arrangements and avoid distributing private contact details to every recipient.

Column five: define the finish before starting

State what counts as completion, who receives the work and who takes over unfinished items. Ongoing work needs a next confirmation date. A one-off task also needs a clear boundary explaining which matters fall outside the commitment and how corrections to the deliverable can be raised.

Ask a teammate who did not develop the idea to read the page and explain the need, first task, missing resources and next action. If their understanding differs, revise the brief before expanding arrangements. A clear starting point and handover are more useful than a page filled with slogans.

Continue reading

• A corporate volunteering proposal: align the need before the headcount
• A volunteer handover sheet that saves the next person starting again