Skip to content
EventConsultant.com.my

Building an event competency checklist

Someone is willing to take on a post, and the open question is whether they have actually done something like it before.

Discuss project lead supportOpens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.

The short answer

A competency checklist lists, for each post, the skills it needs and the evidence you have seen that a named person has them. It stops willingness being mistaken for ability, and shows which posts need a trained person, a supplier or a briefing first.

It records what you have seen and asked for. It does not decide who is qualified for regulated work; that stays with the competent party.

Split the skills into three groups

GroupExamplesWho defines the requirement
Ordinary event skillsUsing a registration list, managing a queue, speaking to delegates, keeping time, calm under questionsYou, from your role descriptions
Equipment and system skillsOperating a registration system, a projector or a clicker, using a radioThe supplier or system owner, who can say what a person must be shown
Regulated or safety-related skillsFirst aid, fire marshal duties, food handling, working at height, rigging, driving a vehicleThe venue, the relevant authority or the competent party; you ask what is required and ask to see evidence

How to fill the checklist

  1. List the posts from the staffing plan.
  2. For each, list the skills in the three groups. Write Not needed where that is true.
  3. For each named person, record what you have seen: past experience at the same kind of post, a short practical check, or a briefing completed.
  4. Where a regulated skill is required, ask the competent party what proof is accepted and record what was shown to you, not your own judgement of it.
  5. Mark each post as Ready, Ready after briefing, or Needs someone else.

What counts as evidence

  • A short practical check: the person does the task while someone watches.
  • Experience at the same post in an earlier event, confirmed by someone who saw it.
  • A completed briefing from the supplier or system owner.
  • A document shown to you by the person, where the competent party has said that document is what they require. You note that you saw it, not that it is valid.

What to do with a gap

If someone is not yet ready, options include a briefing, pairing them with an experienced person, moving them to a post that fits, or buying in a supplier. The capacity gap estimator separates specialist gaps from ordinary hours, which makes the choice clearer.

Do not lower the standard because the date is close. Move the person or the post, not the requirement.

Pitfalls

  • Treating volunteer goodwill as competence.
  • Writing a checklist item that names a regulation you have not read. Ask the competent party to say what applies.
  • Using the checklist to rank people. It matches people to posts.
  • Not keeping the record, so the same check is repeated every event.

Worked example · Fictional example

Competency check for a two-room seminar

Fictional organisation and details. Skills and ratings are hypothetical.

A fictional association checks four posts before its seminar, using the checklist with its three skill groups.

PostSkills neededEvidence seenStatus
Registration deskRegistration list, queue handling, polite handling of exceptionsOfficer A ran it last year; Volunteer 1 passed a 10-minute practical checkReady
Room door and cueRadio use, cue timingVolunteer 2 shown the radio by the technicianReady after briefing
First-aid postRegulated: requirement set by venue and competent partyVenue says what is required; no volunteer has shown evidenceNeeds someone else
Green room hostCalm with speakers, knows the programmeOfficer C hosted at two previous eventsReady

Use this yourself

Competency checklist

Copy this into a sheet. One row per post and person. The evidence column must say what you saw or what was shown to you, not an opinion.

  1. Mark every regulated skill with who defines the requirement.
  2. Add the date you saw the evidence.
  3. Set a status of Ready, Ready after briefing, or Needs someone else for each post.
PostSkill neededSkill groupPersonEvidence seen and dateDefined byStatus

Open the tool: Event capacity gap estimator

Handle it in-house, or bring in help?

Your team can usually handle this when

  • Posts are ordinary event tasks that your team has done before.
  • Equipment and system skills are covered by short briefings from the supplier.
  • Someone can keep the record up to date.

Outside planning help earns its fee when

  • Posts involve regulated or safety-related tasks and nobody on the team can say who defines the requirement.
  • You are mixing volunteers, supplier crews and staff, and cannot say who has been checked.
  • Several committee members disagree about who is ready for which post.

Need posts matched to the right people?

A conference project lead can build the competency checklist with you, ask the venue and suppliers what proof is needed for specialist posts, and arrange briefings or cover where a person is not yet ready. The competent party, not the project lead, decides whether a person meets a regulated requirement.

Discuss project lead supportOpens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.Conference project lead

Questions organisers ask

Does the checklist certify anyone?

No. It records what you have seen and asked for. Whether a person meets a regulated or safety requirement is for the competent party to say.

Which posts usually need a specialist or supplier?

Ask the venue and the relevant authority. Typical candidates are first aid, fire safety roles, food handling, rigging and driving, but the requirement depends on your event and venue, so confirm rather than assume.

Can a volunteer be trained for a post on the day?

For ordinary event tasks, a short briefing and say-back may be enough (see volunteer briefing). For regulated or safety tasks, ask the competent party what is needed and arrange cover if it cannot be met.

Related resources

Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.