WorkspaceUse browser Print / Save PDF
MATCHGRID.AI DIRECTIONS

Run registration, player check-in, and scheduling

Follow these checklists in order. Tournament directors should finish divisions and fees, go live, then copy the registration link.

Team registration and player check-in

For team managers registering a team and building an approved game-card roster.

  1. 1

    Open the event registration link, sign in, choose the club, age group, gender, and tier. MatchGrid builds the team name from those choices. If another of your club's teams already has that name, add a short team label — the coach's last name works well — so the two teams stay distinct. Then choose the division, enter the coach information, and submit any schedule request.

  2. 2

    Complete payment when Square is connected. A checkout link does not mean payment is confirmed until MatchGrid.ai receives the payment status.

  3. 3

    Open the Team App. On Player roster, take photos or choose images and PDFs of every official roster page. Read the files, then correct anything that was missed. Delete a file if it was the wrong page. Players on more than one file are merged.

  4. 4

    On Player ID passes, upload passes for rostered players the same way. Each pass is matched by name and birth date. Enter the current registration year. Guest roster pages and guest passes go under Guest players, not here.

  5. 5

    On a phone, open Mobile check-in. Photograph the pass, let the photo reader compare it with the roster, and watch the team progress. A guest may use a club pass. The same player can be approved on at most two rosters, and a card number cannot be on a third roster.

  6. 6

    Wait for tournament staff review. Only a fully verified US player pass can appear as checked in. A club-pass guest is badged separately and is not added to the guest pool.

  7. 7

    Check the Team App before the event for the published schedule, standings, weather messages, and final player status.

Guest-player directions

The guest pool is private to the event and uses only fully checked-in players.

  1. 1

    Complete the player’s official-roster and US player-pass verification first. Unverified players cannot enter the guest pool.

  2. 2

    In the Team App roster, select Offer to guest pool for the player. This is an explicit team choice and can be removed later.

  3. 3

    The tournament director reviews the event’s guest-player needs and confirms the player is the correct age for the receiving bracket.

  4. 4

    The receiving team must add the guest to its roster entry and obtain event approval. A guest is not automatically added to a game card.

  5. 5

    After approval, confirm the player does not exceed the two-roster event limit. Only then may the player appear on the receiving team’s game-card roster.

Tournament director: build an event through scheduling

Use this order to keep registrations, fields, brackets, conflicts, and published games consistent.

  1. 1

    Create the event. Set its name, event dates, daily hours, time zone, standard game blocks, full-block display, and normal rest rules.

  2. 2

    Build venues and fields. Enter the city, state, ZIP, venue hours, field format (4v4, 7v7, 9v9, 11v11 younger, or 11v11 older), surface, lighting, and any unavailable time. Duplicate similar fields, then change their names.

  3. 3

    Every new event starts with U7–U19 boys and girls Gold and Silver brackets. Gold and Silver colors and age-based game blocks are already set; delete or add brackets as needed.

  4. 4

    Choose a three-game-guarantee bracket format and select the playoff path: quarterfinals to final, semifinals to final, or straight to final.

  5. 5

    Open Registrations for the team registration link, questions, and waivers. The team list is on that same tab, one line per team, forty teams at a time, with search, filters, and sort. Schedule, scoring, and backups open their own pages. Guest-player, bracket, and accepted-team links are on Publish & Backup.

  6. 6

    Go live at the top of Registrations, then copy the team registration link for your website or a Tiger email. Search by team, coach, or email, and filter by status, fee plan, and division. Open Packet on a team to review documents, return a packet, or grant an exception. Accept a team into a division from the same row. Square payment status stays on Registrations.

  7. 7

    If schedule teams are missing from Registrations, open that tab and choose Create test registrations. Confirm once. It adds one unpaid test row per team that does not already have a registration, including San Antonio Labor Cup, and leaves existing rows and Square payments alone.

  8. 8

    Review official roster photos and US player passes. Confirm the registration year, identity match, age eligibility, and two-roster limit before approving a player for game cards.

  9. 9

    Assign stable coach IDs and review the coach list. Start with coaches who have three or more teams and place their youngest teams first because their game blocks are shorter.

  10. 10

    Generate bracket games. The starting weekend plan is two pool games Saturday and one Sunday for each team; playoff games follow the selected bracket format.

  11. 11

    Run Build schedule. It places coaches with three or more teams first, in play-format order, then everyone else. Review any games left unscheduled, field-format mismatches, field hours, team rest, and coach conflicts.

  12. 12

    Use the drag-and-drop grid for manual adjustments. MatchGrid.ai accepts five-minute drops while showing fifteen-minute grid marks. A move must stay within field hours, use the correct field size, and preserve two game blocks of rest.

  13. 13

    Review standings, points, wildcard rules, advancement, game numbers, and every semifinal/final. Download game cards and the outage kit before publishing.

  14. 14

    Review the constraint graph under the tournament calendar on the schedule page. It checks team, coach, venue, rest, travel, and field issues in the browser. Publish the team schedule once, when the board is ready. After that, field moves save straight to the team link. Send a weather message when delays or field changes affect teams.