Plan a Community Event Information Desk Enquiry Workflow

An information desk runs best on one short, repeatable sequence that every volunteer follows: find out what the visitor needs, check the current approved information, give the confirmed answer, refer anything unanswered to a named owner, agree any follow-up, and record when the enquiry is closed. Urgent matters skip the queue and go straight through the event's approved escalation arrangements. This guide covers the materials that sequence depends on, how to set them up before the desk opens, and how to check the plan for gaps. It applies to tournaments, festivals, fairs and similar community events where volunteers answer questions from players, spectators, families and vendors.

The enquiry workflow at a glance

• 1. Establish the need: ask what the visitor is trying to do or find, and confirm you have understood before answering.
• 2. Consult the approved record: check the current version of the desk reference, schedule or event information, not memory or word of mouth.
• 3. Give the confirmed answer: share only what the approved record says.
• 4. Refer what you cannot answer: pass the question to the named owner for that topic instead of guessing.
• 5. Agree follow-up if needed: tell the visitor who will respond, how, and roughly when.
• 6. Record closure: log the enquiry and mark it closed once the visitor has an answer or the referral is resolved.
• Urgent matters: go directly to the event's approved escalation route rather than working through the steps above.

The steps only work if volunteers have something reliable to consult and someone specific to refer to. Most of the planning effort goes into those two things.

Inputs to gather before the desk opens

• Question categories: the topics visitors are likely to ask about, such as schedule and match times, venue layout, registration and check-in, results, lost property, accessibility, and vendor or exhibitor questions. Adjust the list to your event.
• An approved information record: the schedule, maps, policies and announcements volunteers may quote, each with a location and a version or last-updated time.
• A responsible contact for each category: a named person or role who answers questions the record does not cover.
• An escalation route: the agreed way to raise urgent matters, set by the event lead together with whoever holds safety and venue responsibilities.
• An update owner: the person who changes the approved record and tells the desk when it has changed.
• Accessibility arrangements: ask your accessibility owner to confirm which communication arrangements the desk can actually offer, so volunteers do not promise something unavailable.
• Privacy approval for the log: ask whoever handles privacy for your organization to approve which follow-up details the desk may record and how they are stored and disposed of.
• Desk staffing: shift times, a desk lead per shift, and a handover point between shifts.

Some of these are organizer choices, such as the categories and the log layout. Others may be set by your venue, a governing body or local requirements, especially escalation routes for safety and how personal information is handled. Confirm those with the people responsible rather than writing your own version.

Build the desk reference sheet

The desk reference tells a volunteer, for any question type, where the approved answer lives, who to ask when it does not, and who keeps it up to date. Keep it to one page if you can. The rows below are placeholders to show the layout; replace them with your own categories, roles and locations.

Question category	Approved information (location and version)	Responsible contact	Escalation route	Update owner
Schedule and match times	Master schedule, desk binder, version and time shown in header	Schedule coordinator	Event lead	Schedule coordinator
Venue layout and facilities	Site map, desk binder	Venue liaison	Event lead	Venue liaison
Registration and check-in	Registration list and policy sheet	Registration lead	Event lead	Registration lead
Accessibility	Confirmed accessibility arrangements sheet	Accessibility owner	Event lead	Accessibility owner
Lost property	Lost property procedure	Desk lead	Event lead	Desk lead
Anything urgent or safety-related	Escalation card at the desk	Approved escalation contact	As set in the event's escalation arrangements	Event lead

Use roles in the printed version and keep the matching names and contact methods on a separate staff sheet. That way the reference stays valid if a person swaps shifts, and personal contact details are not left on a public-facing desk.

Set up the enquiry log

The log exists so that referred questions do not get lost between shifts and so the team can see which questions keep coming up. It does not need to capture every quick direction to the restrooms; many events log only enquiries that were referred or need follow-up. Decide that rule in advance and brief it.

Ref | Time  | Category  | Information consulted        | Referred to          | Promised response | Status  | Closed
001 | 09:40 | Schedule  | Master schedule, latest ver. | Schedule coordinator | Within 30 min     | Open    |
002 | 10:05 | Lost prop | Lost property procedure      | Desk lead            | Next desk check   | Closed  | 10:50

• Reference: a simple running number so volunteers can talk about a specific enquiry.
• Time: when the question arrived.
• Category: matches the desk reference, which makes patterns easy to spot afterwards.
• Information consulted: which record and version the volunteer checked, so a wrong answer can be traced to an outdated source.
• Referred to: the role that now owns the question.
• Promised response: what the visitor was told about timing; keep promises realistic.
• Status: open, waiting, or closed.
• Closed: when and how the enquiry was resolved.

Collect a visitor's contact details only when a follow-up genuinely requires it, and only in the fields your privacy owner approved. If the visitor can simply return to the desk at an agreed time, that is often the simpler option.

Handling an enquiry: what volunteers actually do

• Greet the visitor and ask what they need. If the question is vague, ask one clarifying question, for example which team, session or area they mean.
• Decide quickly whether it is urgent. If it is, use the escalation route immediately and stay with the visitor if that is part of your arrangements.
• Check the approved record for that category and confirm you are looking at the current version.
• If the record answers the question, give that answer plainly. Do not add guesses or rumours heard elsewhere on site.
• If it does not, say so honestly, tell the visitor you will check with the person responsible, and contact the owner listed on the desk reference.
• Agree the follow-up: wait at the desk, come back at a set time, or receive a message if contact details are approved for that purpose.
• Log the referral, then update the entry when the owner responds and the visitor has the answer.

Keep the approved information current

Schedules, courts, rooms and start times change during events, and the desk is usually where the confusion shows up first. Give every source document a version or last-updated time, and make one update owner per category responsible for changing it. When something changes, the owner updates the master record, replaces the desk copy, and tells the desk lead, who briefs anyone on shift. Remove superseded copies from the desk at the same time so nobody quotes an old version. At each shift handover, the outgoing desk lead walks the incoming lead through open log entries and any changes made during the shift.

Illustrative example: a session that has moved

This is a hypothetical scenario to show the workflow in use. A visitor says they heard a session has moved to a different room, but the approved schedule at the desk still shows the original location. The volunteer does not confirm or deny the rumour. They contact the programme owner listed on the desk reference, log the enquiry as open with the programme owner as the referral, and ask the visitor to wait a few minutes or return shortly. Once the programme owner confirms the change, the update owner revises the schedule and the desk copy, the volunteer gives the visitor the confirmed room, and the log entry is closed. Any later visitor asking the same question gets the answer from the updated record.

Turn the workflow into a template and a PDF desk copy

Keep one master version of the workflow, desk reference and log layout in an editable document or spreadsheet that the update owners can change. From that master, export a PDF or print a desk copy for the binder, with the version and date in the header. The editable version is the one people update; the PDF is what volunteers consult and what you hand out at volunteer briefings. When the master changes, export a fresh copy and replace the old one at the desk rather than marking up printed pages by hand. For the log itself, a paper sheet works well if the desk has no reliable device, as long as someone transfers or files it at the end of each day under your agreed privacy practices.

Check the plan for gaps and conflicts

• Every question category has an approved information source, a responsible contact and an update owner.
• No category points to a contact who is off shift or off site during desk hours without a named backup.
• The escalation route has been agreed with the event lead and whoever holds safety and venue responsibilities, and every volunteer knows where the escalation card is.
• The accessibility owner has confirmed what the desk can offer.
• The privacy owner has approved the log fields, storage and disposal.
• Every source document at the desk shows a version or last-updated time, and there is only one copy of each.
• Shift handover includes open log entries and recent changes.
• Volunteers have walked through at least one practice enquiry, including a referral, before the event opens.
• After the event, review the log categories to see which questions came up most and add those answers to the approved record next time.