Who does what on the wedding day, and how everyone knows

On the day, every small job needs a name on it, or it is left to whoever notices, which is usually one of you. Make the list against the timeline of the day, put a person on each job, check nobody is in two places at once, and give each person a sheet with only their own jobs on it. This is written for UK weddings, but none of it is law.

Start from the day

Jobs happen during something: the chairs go out before the ceremony, the candles are lit during the turnaround, the cake knife comes out before the cake. So Delegation starts from your Timeline, listing each part of the day in clock order, and you add a job to the part it belongs to with + Job. If there is no day yet, build it in Timeline first and it appears in Delegation.

Because each job hangs off its part of the day, its time comes from the timeline. Move the ceremony in Timeline and the jobs around it move too.

A name on every job

Pick a job and put people on it, from your guest list or by name. People can be in a team, the caterers or the ushers, and a job can go to a team before you know who in it will do it. Filter the board to the jobs nobody is named on to see what is left.

Nobody in two places

Delegation checks the board as you go. It tells you about a job nobody is on, and one that is on a team but nobody by name, but it still lets you print, because the sheets are often how the gaps get filled.

Two things stop the printing until you fix them: someone on two jobs that run at the same time, and a job left hanging off a part of the day you have since deleted. A sheet that puts somebody in two places is worse than none.

Everyone gets their own sheet

Download a PDF as one job list for the whole day, a sheet per person, or a sheet per team. A sheet per person is the useful one: your brother does not need to read the caterer's jobs to find his own.