Make membership useful
GuildHearth organizes an imagined guild gathering around member responsibilities, teams, written missions and host-verified points. It works best when the story gives people a shared purpose: repairing a map, agreeing a charter or solving a supply puzzle. The activity should make participation clearer rather than require guests to memorize a hierarchy.
Decide what a team needs to accomplish and what each responsibility involves. Navigator, recorder, speaker and timekeeper are useful descriptions only if the host explains the work. The planner assigns labels, not skills, consent or authority over other participants.
Enter the people and the work separately
Use the common event fields for theme, headcount, budget, duration, start and venue. Enter guild missions one per line, unique member names, a list of guild responsibilities and a reward description. Named members cannot exceed the total guest count, so observers and facilitators can remain outside the active roster.
Mission wording should describe a visible outcome. “Agree three charter principles” is easier to verify than “Show loyalty.” Keep private information and real personal disclosures out of the story. If a mission involves a puzzle, supply and test the actual puzzle yourself; a task title does not create a solvable challenge.
Understand how assignments are distributed
The member list cycles through your responsibility labels. Team numbers cycle through ceil(members ÷ 4) groups. Because those two sequences run independently, a team is not guaranteed one person in every responsibility. Nor does the tool rotate roles automatically between activities. Review assignments and keep any deliberate rotation on a host sheet.
Each mission creates one ten-point board entry, assigned cyclically across the team numbers. Unlike HuntTrail, GuildHearth does not create every mission once for every team. Record an evidence note before checking Verified complete. The displayed points total combines all verified mission records; it is not an automatically separated team leaderboard or proof that every member took part.
Fictional example: eight members drafting a charter
Enter eight members in order: Ari, Bea, Cleo, Dev, Em, Fox, Gray and Hale. Add Navigator, Recorder, Speaker and Timekeeper as responsibilities, then four missions: Assemble the map, Solve the supply card, Draft three principles and Read the shared charter. Use 100 minutes from 17:00 and a Paper guild seal reward.
Two teams are created. Team 1 contains Ari, Cleo, Em and Gray; team 2 contains Bea, Dev, Fox and Hale. The cycling responsibilities give team 1 repeated Navigator/Speaker labels and team 2 repeated Recorder/Timekeeper labels. That pattern illustrates why the host must review the allocation rather than assuming complete role coverage in each team.
Missions one and three are assigned to team 1, and two and four to team 2. Each team has twenty available mission points; the whole board totals forty. After a host records evidence on the first mission and verifies it, the displayed combined verified total is ten. The five general schedule blocks are twenty minutes each, ending at 18:40.
Reward cooperation without hiding the rules
If tasks differ in effort, do not use equal ten-point labels as evidence that the competition is balanced. Adjust the real activity design or choose shared recognition. State whether a team can ask for help and how a partially completed task will be treated, because the completion control is a yes/no host record.
Rotate public-speaking duties only with agreement. Offer quiet contributions and keep recognition independent of expensive costume or lore knowledge. The reward field records your intention; it does not issue tokens or unlock future privileges. Save the reviewed plan and keep a backup of any evidence notes that matter. Shared printed sheets should show only information appropriate for the participants.
Questions before you begin
Will each team get all listed responsibilities?
Not necessarily. Roles and teams are assigned by separate cycling rules. Review the combination and manage any deliberate role coverage yourself.
Does every team receive every mission?
No. Each mission is assigned once across the teams. HuntTrail uses a different board structure when every team needs the full task set.
Why can I not check a mission without evidence?
The control requires a host evidence note before verification. Write what was observed rather than using the checkbox as an unreviewed score.
Does the score display choose a winning team?
It shows combined verified points. Compare team records under your published rule if separate recognition is needed; a full team leaderboard is not provided.