AI-assisted practical guide. Examples are hypothetical; proposed workflows are editorial suggestions.
New volunteers need to know what changed and why. A shared garden change log can preserve decisions that would otherwise disappear into conversations. Keep it short enough to use, but specific enough to guide the next shift.
Record one change at a time
Include the date, location ID, action, reason, and person responsible for follow-up. Link a photograph or map revision where useful. Distinguish a proposed change from an approved one and from completed work.
Keep the original decision visible when it is revised. A replacement note should explain what changed rather than silently overwrite the earlier plan.
Trace a hypothetical task
Imagine volunteers move a path marker to improve access. The log records the new position and the matching map update. Without that connection, a later helper may restore the old marker because their printed instructions still show it there.
If the reason is uncertain, write the known action and leave the rationale unresolved. Do not invent consensus after the event.
Make the log part of the handoff
Ask new volunteers to read recent changes before beginning work. Keep private contact details elsewhere. At a review meeting, use the log to identify unfinished follow-ups and obsolete instructions. Its value is continuity: people can understand the current arrangement without needing to find the one person who remembers every previous conversation.