A volunteer schedule answers four things for each shift: the role, the time, the number of spots and who to contact. Put them in a table with one row per shift, and add one line that says how to swap.
This page shows how to build the table, what to put above and below it, and how to keep a sign-up sheet honest as spots fill. The examples use roles and never names.
One row for each shift
A shift has several facts that belong together. A table keeps them side by side.
Digital.gov says tables help readers see relationships that are often hidden in dense text. It adds that most readers need only the details that apply to their situation. A volunteer wants to find one shift and read across.
Here is a sample for a one-day book swap.
| Role | Time | Spots | What you do | Meet at |
|---|---|---|---|---|
| Setup crew | 8:30am to 9:30am | 3 | Set out tables and chairs | Community room |
| Welcome desk | 9:30am to 11am | 2 | Greet visitors and hand out maps | Main entrance |
| Refreshment table | 9:30am to 12:30pm | 2 | Set out cups and keep the table tidy | Main room |
| Cleanup crew | 12:30pm to 1:30pm | 3 | Stack chairs and sweep | Community room |
Put the event name and date in a line above the table: "Book swap helpers, Saturday, March 20." Then each row needs only a time.
The GOV.UK style guide writes time ranges with "to", as in "10am to 11am". Give an end time for every shift so volunteers know when they are free.
Keep the table simple to read
Use one header row across the top, and keep it plain. The W3C tutorial says tables with headers that span several columns or rows need extra markup. A simple grid is easier for everyone, and easier to edit later.
The W3C tutorial also explains why header cells matter. It says screen readers speak one cell at a time and refer back to the header cells, so the reader does not lose context. In a word processor, mark the top row as a header row if the program offers the option.
The tutorial adds that table markup is often lost when a file is converted to another format. After you save a schedule as a PDF, open it and check that the table still has its header row. The steps for saving are in how to save a document as a PDF.
Do not rely on color to show that a shift is full. A schedule photocopied in black and white will lose it. Add a word to the row. See printing in black and white for more.
Show how many spots are left
On a sign-up sheet, spots fill over time. Make the status a word, not a blank space.
For each spot, use "Open" or "Taken". A blank cell can mean "nobody yet", "not decided" or "forgot to fill in". The GOV.UK style guide tells writers not to use "N/A" in empty cells and to use plain words such as "no data" or "not applicable" instead. The same thinking applies here: say what the cell means.
A printed sign-up sheet needs space for volunteers to write. Give each spot its own line, and keep the lines wide enough for handwriting.
A public copy on a wall does not need every name. Post roles and times there, and keep the list of names with the coordinator.
Say how to swap and who to contact
Volunteers will need to change shifts. Write the rule once, near the table, in two sentences.
"To swap, find someone to take your place. Tell the volunteer coordinator on or before Thursday, March 18."
Name one contact by role and give one way to reach them. The GOV.UK style guide asks for email addresses to be written in full and in lower case. Do not write "the usual address". On a printed sheet, write out the full address.
Say what happens if nobody can cover. That tells volunteers what to do when a swap falls through. For example: "If you cannot find a swap, tell the coordinator as early as you can."
A before and after example
Before: Helpers are needed for the event on the 20th. Some will be needed early and others later, so let us know when you are free and tell someone if you cannot come.
After: Book swap helpers, Saturday, March 20. Choose one shift in the table below. To swap, find someone to take your place and tell the volunteer coordinator on or before Thursday, March 18.
The first version names no role and no time. It does not say who "someone" is. The second version names the event, the date, the action and the deadline, and the table carries the rest.
Before you share the schedule, run through this list.
- The event name and date sit above the table.
- Every row has a role, a start time, an end time and a number of spots.
- The top row is a header row.
- Status words say "Open" or "Taken", not blanks.
- The swap rule fits in two sentences.
- One contact is named by role, with one way to reach them.
- The file has been opened as a PDF or printout to check the table.
The Easy-Read Editor can help with the sentences around the table, such as the swap rule. Keep them short enough to read at a glance.
Common mistakes
- Describing shifts in a paragraph. Volunteers must hunt for their own time. Use a table.
- No end time. People cannot plan the rest of their day.
- "A few spots." Give the number. "Three" is clear and "a few" is not.
- Blank cells. They mean different things to different readers.
- Color as the only signal. It disappears in a copy.
- Several contacts. Questions go to the wrong person.
- Many versions. Keep one up-to-date copy and write the update date at the top.
For the meeting where volunteers plan their jobs, see meeting agendas that keep everyone on track. For asking people to come in the first place, see writing a clear invitation.
FAQ
How many columns should the table have?
Keep only what a volunteer needs to choose a shift: role, time, spots, a short task and a meeting place. If the table does not fit the page, cut a column. Do not shrink the type.
Should I use a table or a list?
Use a table when each shift has several facts. Use a list when each item has one fact. See when to use a list instead of a paragraph.
How do I show changes after I share it?
Keep one current copy. Put "Updated" and a date at the top, and replace the old copy everywhere it was posted or sent.
Sources
Each page below was opened and read on the date shown. Where a fact comes from one of them, the guide says so.
- Tables - Digital.gov Plain Language Guide Checked November 19, 2026
- Tables Tutorial - W3C Web Accessibility Initiative Checked November 19, 2026
- A to Z style guide - GOV.UK content and publishing guidance Checked November 19, 2026
This guide gives general information about readability. See the Disclaimer. To report a mistake, use the Corrections page.