Help & walkthroughs
Start with a private practice event. Rehearse the complete workflow before running a live event.
Quick walkthroughs
Enter the roster
- Open Teams and choose Add team. Enter or search for both partners. Directory search uses saved BracketMesh player records.
- Check names and partner assignments before rebuilding pools. For a missing directory player, use Find / request player; confirm any manually entered rating with the director.
- If you plan to submit results to DUPR, check each player’s DUPR ID and rating before starting play. Keep using the current CSV export and manual upload process.
- Players do not need to sign in or connect a DUPR account to play.
Set up courts
- Open Settings → Event settings and confirm court numbers and the pool/playoff court plans.
- Review the First-event checklist, or Pre-event readiness in Tools & recovery. Resolve blocking issues before starting pool play.
- In Day-of Control, choose Assign open courts. Only available teams are assigned; release a court by submitting its result.
Enter scores
- Confirm the court, both teams and the scoring rule before entering a result.
- Submit once, then wait for Live — server confirmed before announcing the result.
- If saving is pending or conflicting, keep the written score and resolve it before resubmitting. Do not repeatedly submit different scores.
Run playoffs
- Finish every pool result and review standings, tiebreakers and qualifiers.
- Choose End pool play & start bracket. Check the seeded bracket before assigning courts.
- Complete the championship and bronze match if configured, then choose Complete tournament.
Correct a result
- For the most recent incorrect result, use Undo last result and confirm the displayed match. Otherwise use the match correction controls.
- Check affected standings and bracket participants. Downstream results may need an explicit reset; never keep scores for a changed matchup.
- If already exported to DUPR, reconcile the correction there before explicitly re-exporting. A correction is not permission to upload the same result twice.
Export to DUPR
- Export eligible match results as a CSV, then upload it through your authorized DUPR process. BracketMesh does not automatically submit these results.
- Resolve excluded matches and missing or duplicate identities. Download a new batch only after the server confirms it was saved.
- Upload through your authorized DUPR process and record its status. Use the export history when reconciling corrections or a possible duplicate.
Recover safely
- Before play, download the recovery JSON and printable match sheets or schedule. Keep a written score backup.
- If disconnected, retain written scores and wait for connection confirmation. Do not run two competing director desks.
- Open Recovery to download a retained server revision. Review the event ID, date, last accepted score and impact before restoring; contact support when results are at risk.
Troubleshooting
Cannot publish
Check the event payment/release controls. BracketMesh must confirm payment for the current roster. Practice events cannot be published.
Cannot start play
Open Settings → Event settings → First-event checklist, or Tools & recovery → Pre-event readiness. Fix roster, schedule and court issues. For DUPR-reported events, resolve identities and lock ratings at start.
Score pending or conflict
Keep the written result, stop editing that match, reconnect and load the confirmed server state. Resolve the conflict before retrying.
Court will not assign
Check earlier unfinished games, withdrawn teams and current assignments. Both teams must be free.
Bracket does not advance
Confirm all required earlier games are final, including best-of-three games. Review correction/reset warnings.
DUPR export excludes a match
Review the listed identity or match-eligibility issue. Forfeits, disputed or already-exported matches need separate handling.
Support & event-day coverage
Support by arrangement. No published response-time guarantee.
Event-day coverage is available only when BracketMesh confirms it in advance.
For a blocked live event, stop conflicting edits, keep written scores and request support with the event ID, affected match and last confirmed save. Use your agreed event-day contact if coverage was arranged.
Record a support request. In-site requests do not trigger emergency paging. Do not assume event-day coverage until it has been confirmed.