Schedule Team scrimmages

Who this is for

Team Captains and Members

When you’re done

Both Teams agree on the schedule and every Member can answer Yes, No, or Maybe.

Team scrimmages are private appointments between two independent Heir Teams. They do not enroll either Team in a League, reserve a game server, change Elo, or prove that a match was played.

Scrimmage availability can differ between Heir sites, so follow what Calendar offers you. If it says scrimmages are unavailable, they are not offered there. If it says they are paused, you can still read and manage agreements you already have while new requests, extensions, and availability changes wait. No League or Team setting turns scrimmages on.

Request a scrim

Team Captains open Calendar, choose Create event → Scrimmage, select the Team they captain, and choose:

1. The opposing Team and game. Search by Team name or tag; results include Team identity and include only public Teams accepting requests. A selected Team stays visible while the search refreshes. A Team can schedule different games on different dates; no League or linked game identity is required.
2. A date, start time, duration, and IANA time zone.
3. A one-off appointment or a bounded recurring series. Recurring requests support selected weekdays and intervals of one to four weeks, ending on a date or after a fixed number of occurrences.
4. Optional format, player-count goal, location preference, agenda, and meeting instructions.

Review every generated date before sending. Duration is 15 minutes to 24 hours; an optional player-count target is 1–100 per side; and a custom game label is at most 80 characters. The request form accepts up to 1,000 characters each for the agenda and meeting instructions, up to 100 characters for a region or location, and a valid HTTP(S) meeting link. Keep a region to 2–80 characters so it is accepted. Once a scrimmage is agreed, its details editor allows longer agendas and meeting instructions, up to 2,000 characters each. Heir warns about known calendar and availability conflicts, but a warning does not block a request. A series can contain at most 104 dates and cannot extend beyond one year.

The opposing Team's current Captain receives an actionable notification in Heir and, when Discord DMs are available, an embed with Accept, Decline, and View. The first valid response wins. Reading or clearing the notification does not accept or decline it.

Pending requests expire at the earlier of seven days after creation or their proposed start. The requesting Captain can withdraw a pending request. If Discord delivery fails, the request remains fully usable in Heir.

Accept a recurring series once

Accepting a recurring request approves the displayed series once. Each date remains a separate occurrence with its own attendance, cancellation, and rescheduling history.

Extending a series, changing its opponent or game, or changing the time requires a new agreement. A declined reschedule leaves the original appointment intact. Cancelling one date does not cancel the remaining series; Captains can also cancel all future dates while preserving past history.

Either Captain can edit the agenda, desired player count, region, meeting instructions, or validated meeting link without another approval. Heir records an accepted details revision and notifies future invitees, but preserves every date and RSVP. Timing, game, opponent, and recurrence cannot be changed through the details editor.

Heir keeps the series at its local wall time across daylight-saving changes. For example, 8:00 PM in America/New_York remains 8:00 PM there even when its UTC offset changes.

Respond to attendance

After acceptance, Heir invites every current Member of both Teams—including both Captains—to each occurrence. Captain acceptance never answers attendance for anyone.

• Yes means you intend to attend.
• No means you do not intend to attend.
• Maybe means you are unsure.
• Unanswered is a separate state and still needs a response.

Members can change their own response until the occurrence starts. An optional Apply to remaining dates action creates a default for future dates in the current series revision; an individual date can still override it. A material schedule change clears affected current responses and asks Members to respond again while retaining the old response in history.

Members of the same Team can see each other's response lists. The opposing Team sees only aggregate counts, not individual names or private reasons. If you belong to both Teams, a Yes or Maybe response must identify which Team you intend to attend for so you are never counted twice.

New Members receive invitations for relevant future dates. Members who leave lose access to future private details and reminders, while historical records remain.

Use Team and personal calendars

Open Calendar and use the workspace switcher to choose either Your calendar—everything you are involved with—or one Team's calendar. Team profile calendar links open the same shared calendar with that Team selected; there is no second calendar implementation.

Week is the desktop default; month, day, and agenda views use the same events. The agenda view is the compact default on narrow screens. Filters for game, Team, event source, and state change what is displayed—not what you are authorized to see. Calendar links use stable scrim and occurrence IDs, so Team renames and single-date reschedules do not break them.

Pending requests are tentative holds. Confirmed, pending, cancelled, League, and tournament events use labels as well as color. A scheduled time becomes Past after it ends; Heir does not call it played or completed without match evidence.

Share Team availability

Under Manage Team → Scheduling, Captains mark only available time. Leave a gap for a break; existing weekly unavailable blocks are converted into gaps. Paint on the weekly timeline, right-click empty time to add a one-hour block, or use Add block. Drag a block to move it, and drag its top or bottom edge to resize. Overlapping or touching blocks for the same game merge automatically.

Moving and resizing use 15-minute steps. Click or right-click a block to edit exact minutes or remove it. Moving an exact-minute block snaps its endpoints back to the 15-minute grid. The Add-block editor is also the keyboard alternative to dragging. The compact timeline shows all 24 hours without its own scrollbar; on narrow screens, pick a day to edit.

The availability timeline uses your local time zone automatically, like your calendar. Blocks may cross midnight and can apply to every game or one game. Date-specific available or unavailable exceptions sit below the weekly pattern with balanced disclosure spacing. The same Scheduling tab holds incoming-request policy and scrimmage notification preferences; calendar views stay focused on events.

Availability is advisory. It is not an RSVP, reservation, or automatic reschedule. Opposing Captains see only availability the Team intentionally shares, never Member calendars or private conflict reasons. Conflicts across every game remain visible even while a game filter is active.

League Roster availability is separate and continues to describe the slots that one Roster can play in one League. Set Roster availability explains that workflow.

Notifications and reminders

Both Captains receive request outcomes and material changes. Every invited Member gets an in-app attendance action and best-effort Discord DM. Yes, Maybe, and Unanswered invitees receive reminders approximately 24 hours and one hour before the start; No responses skip routine reminders. Captains receive a readiness summary rather than a DM for every Member response.

Routine Discord reminders can be muted in notification settings without removing the in-app action. A closed DM or removed bot access never changes the scrim state. Retry through the event page if an old Discord button reports that its revision has expired.

A Captain can configure a Team webhook to post selected event updates to Discord. Everyone with access to the destination channel can read those posts, so choose a channel appropriate for the Team's information. Manage attendance and responses in Heir.

Cancel safely

Either Captain can cancel a confirmed occurrence or future dates. Heir invalidates old actions and reminders, notifies affected Members, and retains the audit history. Disbanding either Team withdraws pending requests and cancels future confirmed obligations; it does not erase past occurrences.

Next: Create a Team, manage Team Members, or connect a Team Discord.