Project Handover Page for a Community Workshop: Leave Unfinished Work Ready for the Next Session

A community workshop often shares one bench, one shelf and one set of tools among many people who arrive on different days. A project started on Tuesday may be continued on Saturday by the same person, or by a helper who never saw Tuesday. The usual solution is a sticky note that says "almost done." That phrase means different things to different readers.

This article proposes a single handover page for each unfinished project. It is an editorial example of a workflow, not a report of how any real workshop operates. Use the parts that fit your space and drop the rest.

What the page is for

The page answers one question: what should the next person do first, and what should they leave alone? It is not a fault report, a repair diagnosis or a record of equipment condition. If a tool seems unreliable, that belongs in a separate note, kept apart from the project so it is not mistaken for a step in the work.

The fields

Keep the page short enough to read standing up. A proposed set of fields:

Project name and a short label that also appears on the item itself.
Owner or lead, shown only as a first name or a member number your workshop already uses. Do not publish contact details on a public page.
Last session date and who worked on it.
Done: what is finished and should not be redone.
Next step: exactly one action, written as a verb phrase.
Waiting on: anything the next person cannot start without, such as a part still to arrive, a decision from the owner or a drying or setting period the owner has chosen.
Do not touch: parts, settings or marked lines that must stay as they are.
Where it is stored and how it is marked.
Open question: one thing the owner wants answered before further work.

The single next step is the most important field. If you find yourself writing three, the project has not been decomposed enough, and the page will fail at the exact moment someone needs it.

Decision branches for the next person

When a member opens the page, they follow a short path.

If the owner field says the owner is returning for the next session, the member reads the page, does nothing, and may leave a note offering help.
If the page names a next step and nothing is listed under Waiting on, the member may carry out that step, then updates Done and writes a new next step.
If something is listed under Waiting on, the member does not start the next step. They check whether the waiting item has arrived. If it has, they note that on the page and ask the owner, a coordinator or the person named on the page whether to continue.
If the Do not touch field covers the area they would need to work in, they stop and ask.
If the next step is unclear or contradicts the item in front of them, they stop and write the mismatch in Open question.

Stop conditions

A helper should stop and hand the work back, rather than improvise, in these cases: the next step cannot be matched to what is physically there, the label on the item differs from the page, a Do not touch area is in the way, or the helper would need a skill or permission your workshop reserves for trained members. Stopping is a correct outcome, not a failure, and the page should say so in one line at the top.

A worked example

Imagine a member building a small wooden stool. The page reads: Done, legs cut to length and marked A to D. Next step, sand the underside of the seat. Waiting on, the owner has not yet chosen a finish, so no finishing work. Do not touch, the pencil lines on the leg tops. Stored on the labelled shelf. Open question, does the owner want the edges rounded?

A helper arriving on Saturday sands the underside, adds that to Done, and writes the new next step as "wait for finish decision." They do not round the edges, because that is an open question, not an instruction.

Keeping the page honest

Update the page at the end of every session, before cleaning up. If a session ends in a rush, write only the next step and any Do not touch line. Retire the page when the owner marks the project collected, and remove personal details at that point.

Small acceptance test

Pick one real unfinished project and write its page. Then ask someone who has never seen the project to read only the page and tell you, without asking questions, three things: what the next step is, what they must not touch, and what they are waiting for. If they answer all three correctly, the page works. If they hesitate on any, rewrite that field and test again with a different person.

A second check: remove the owner's name and see whether the page still makes sense. If it does not, the page depends on memory rather than writing.

Conclusion

A handover page turns "almost done" into one next step, a list of things to leave alone and a clear reason to stop. It costs a few minutes at the end of a session and saves the next person from guessing. Adopt the fields that help, test the page with a fresh reader, and adjust it to the way your workshop already shares its space.