WordCamp Nepal 2027 Table Leads: Application and Preparation Guide

The deadline and the role

The official call for Contributor Day table leads lists November 25, 2026, at 11:59 PM Nepal time as the application deadline. Contributor Day is scheduled for January 29, 2027, at Siddhartha Cottage in Nepalgunj. The announcement welcomes first-time table leads and says tables can be led in English or Nepali.

The role includes preparing suitable tasks, helping participants get started and sharing progress with the relevant team afterward. The organizer also describes a preparation call and support during the event. These details were checked on November 13, 2026; use the official page for updates and the application link.

Leading a table is different from giving a talk. Your preparation needs to help several people make progress at different speeds. The workflow below is an independent planning suggestion, not an official event timetable.

Decide whether you can guide the process

You do not need an answer to every possible question, but you should know how your chosen contribution area works. Can you explain where tasks live, what a useful submission looks like and who reviews it? Can you recognize when a question needs another person’s help?

Try walking through a small task yourself. Note every account, instruction and decision you encounter. The steps you have learned to do automatically may be exactly where a newcomer gets stuck.

If your own understanding is incomplete, identify the gaps before applying. You can explain your experience honestly and ask the organizing team about support. Do not describe yourself as a team representative or reviewer unless that is actually your role.

Choose tasks with a visible finish line

A good introductory task has a clear starting point and a result someone can recognize. “Help improve documentation” is a broad aim. “Identify the confusing step in this sample instruction and propose a clearer version” is easier to begin.

Prepare a small range of tasks rather than one difficult exercise for everyone. A newcomer might review instructions, while someone more experienced investigates the underlying behavior. Keep both connected to a genuine contribution workflow so the simpler task is still meaningful.

Check task availability near the event. Public issues can be resolved or reassigned. Have alternatives ready and confirm that your table’s proposed work is useful to the relevant team rather than creating submissions that nobody has asked for.

Build a one-page onboarding note

Write down the minimum setup, the first task, where to ask questions and how to submit work. Link to the authoritative team instructions rather than copying a long handbook that may become outdated. Label anything you wrote yourself as a local explanation.

Test the note with someone who does not already know the process. Watch where they stop and what they ask. If they need you to explain every line, the document is not yet doing its job.

Keep the page usable on a small screen. Short paragraphs and descriptive links are easier to follow than a wall of URLs. Where setup involves several tools, separate what is required now from what may be needed for an advanced task.

Plan the opening conversation

Begin by asking what people have done before and what they hope to learn. A quick introduction helps you avoid giving an advanced explanation to someone who is still creating an account. It also identifies participants who may be comfortable helping a neighbor.

Explain the shape of the work: first setup, then a small task, then review and a record of the next step. Use your own flexible sequence rather than presenting a minute-by-minute schedule that the organizers have not confirmed.

Make it easy to say “I am stuck.” People should not have to wait until everyone else finishes to ask a basic question. Tell them how you prefer questions to be raised while you are helping someone else.

Keep account setup from consuming the whole day

Some participants will arrive ready; others may face login trouble or slow downloads. Prepare an activity that can be discussed while setup is underway, such as reading a public issue and identifying what information is missing.

Do not ask people to share passwords so you can move faster. Guide them through their own account steps. If a technical problem cannot be resolved promptly, offer a task that does not depend on the blocked tool.

A paired exercise can help, but make the roles explicit. One person can describe the expected result while the other follows the steps, then they can swap. The goal is participation and understanding, not having one experienced attendee do all the work.

Give feedback that points to the next action

When reviewing an early attempt, identify what already works and one concrete improvement. “This needs more detail” is difficult to act on. “Add the browser version and the steps before the error appeared” tells the contributor what to do next.

Separate your suggestions from the team’s formal acceptance decision. You may be able to help prepare a submission without having authority to approve it. Explain that distinction so participants do not leave thinking their work has already been merged.

When you do not know an answer, say so and show how to find the right person or source. That teaches a contribution skill as valuable as the immediate technical solution.

Handle mixed experience without splitting the table apart

Prepare optional extensions for people who finish quickly. They might improve a reproduction, check a related case or review the clarity of the onboarding note. Avoid making newcomers feel that they are delaying everyone else.

Ask before inviting experienced participants to help others. They may have come to work on a particular task and should not silently become unpaid assistants to the whole table. A clear, limited request is easier to accept or decline.

Keep brief notes on blockers across the group. If several people encounter the same issue, pause for a shared explanation. If only one person is affected, handle it individually while others continue.

Close with an honest progress record

Before participants leave, help each person save the link to their work, its current status and the next action. Distinguish drafted, submitted, reviewed and accepted work. A useful day does not require every item to reach the final stage.

A simple wrap-up can record completed tasks, unresolved questions and improvements needed in the setup instructions. Share appropriate information through the team’s agreed channel. Do not publish participant contact details or private conversations in the progress report.

Ask what would have made the first step easier. That answer can improve the next contribution session and reveal barriers you no longer notice as an experienced participant.

Preparing your application

Describe your contribution area, relevant experience and how you would help someone complete a first task. Include accurate public examples where appropriate. Explain any support you would need instead of promising a polished session you cannot yet deliver.

Use the official table-lead call for requirements and current status. For a presentation-based role, compare the responsibilities in our [speaker proposal guide](/wordcamp-nepal-2027-speaker-proposal-guide). A table lead facilitates ongoing work; a speaker prepares a structured presentation. Choose the role that fits how you can contribute.