BoatBalance Support Center

Use the account and environment your team provided. BoatBalance Dev and BoatBalance are separate environments; a Development sign-in does not establish a Production account.

Use Forgot password on the sign-in screen if needed. In the browser, open Account → My Profile. On iPhone or iPad, open More → Profile. Never share your password or verification codes in a support request.

Use the Request account deletion link below. You do not need to sign in or reinstall the app to make a request. Support verifies ownership before acting. Deleting an individual account does not automatically delete shared team records; the request page explains the current process and retention limitations.

Check the selected team before working with events or lineups. If you belong to more than one team, use the team selector. Ask your team administrator about membership or role changes.

Ordinary members can use the features available to their membership. Coaching, guest management and attendance-management controls require the appropriate team role. A missing management control is not a request to sign in as someone else. Help and support remain available without a selected team.

Open an event to check its name, date, event-local time, time zone and location. Check the current details again after an organizer changes or reschedules an event.

Planning events and unpublished changes are staff preparation, not member-facing announcements. Authorized staff publish an event or its saved update when ready. Publishing event details and sending a notification are separate actions.

Eligible members can respond Yes, Maybe or No to a published event while responses are open; an invitation is not required. Save the response and check the displayed answer. If the event changed while you were editing, refresh before trying again.

Authorized staff can manage attendance and record a response on a member’s behalf. Staff may prepare permitted responses during Planning. Member views do not expose staff-only response history, timestamps or management actions.

Yes since represents the current continuous Yes period. Leaving Yes clears that priority. Returning to Yes starts a new period; explicitly reconfirming an existing Yes preserves it.

A fresh confirmation round asks eligible current Yes/Maybe members to reply again. Its reply status is separate from the attendance answer. You can reconfirm your existing answer or change it.

A reminder is for outstanding replies in that round, not a new round. An initial No is not an unanswered confirmation, and a delivery failure is not proof that someone chose not to reply. Schedule preparation does not itself grant Send authority or enable delivery.

These are the core coach actions in BoatBalance. Controls differ between browser, iPhone and iPad; use the controls available on your device.

1. Open an event.
2. Select a boat.
3. Search Available and Assigned paddlers.
4. Assign, move, replace, or swap paddlers.
5. Tap to edit, or long press and drag on supported mobile layouts.
6. On iPad, drag and drop assignments. Drag an assigned paddler into the Event roster column to move that person back to the roster.
7. Review Side Balance and Front / Back weights.
8. Save changes.
9. Finalize the saved lineup.
10. Dock or reactivate a boat.
11. Manage attendance.
12. Use an override warning only when the event assignment is intentional.
13. Contact support when you need help.

Saving an editable lineup and publishing it are separate steps. Members see the lineup available to their role and publication state, not every staff draft. A later staff edit does not silently replace a previously published snapshot.

Review missing crew, attendance and balance warnings before finalizing. A saved or published demonstration lineup is not a guarantee that a crew is safe or fully staffed. If another person changes the lineup, refresh and review rather than overwriting their work.

Calculations use the available accepted calculation weights of assigned occupants. Empty positions contribute nothing. An assigned occupant without an accepted weight is excluded. Partial and one-sided boats are valid. If no accepted weight contributes, the computation is unavailable: it does not declare a winner or an equal result. Existing accepted guest reference-weight rules still apply.

Side Balance compares available Left and Right paddler weights. Drummer and Steer are not part of this side comparison. Its existing coach-configured thresholds, colors, symbols, and equality behavior remain unchanged. Coaches edit Side Balance Thresholds in the separate iPad setting; the phone does not include that threshold editor.

On a ten-row boat, Front includes Drummer and Rows 1–5; Back includes Rows 6–10 and Steer. On a five-row boat, Front includes Drummer and Rows 1–2, Back includes Rows 4–5 and Steer, and Row 3 contributes half its accepted weight to each end. Total Weight includes all available accepted assigned weight, including Drummer and Steer. It appears only in Front-Back Balance.

For a recognized standard ten-row, 20-paddler boat, Front includes Drummer and Rows 1–3, Middle includes Rows 4–7, and Back includes Rows 8–10 and Steer. Both sides of every row are included. Front and Back each contain 7 positions; Middle contains 8. Each percentage uses total available accepted Section weight, without rounding before calculation. Percentages display one decimal place and may sum to 99.9% or 100.1% independently. Only Front and Back are compared; Middle is not ranked, and equal thirds are not an ideal target. Five-row and custom or ambiguous templates are unavailable; saved selections are retained.

When complete names and values need a compact arrangement, the same card shows each full section name with its reference: 1 for Front, 2 for Middle, 3 for Back. The conclusion uses that reference without repeating the long name. Every weight, unit and percentage remains associated with its name; accessibility keeps the full name and canonical section wording. The names never alter the 7 / 8 / 7 mapping.

In More → Settings → Balance Display, coaches may give Front, Middle and Back custom display names or restore the defaults. A blank field restores that section’s default. These account-scoped, device-local names do not change which rows belong to a section, section order, calculation values or comparison direction. Front still includes Drummer and Rows 1–3; Middle still includes Rows 4–7; Back still includes Rows 8–10 and Steer. Accessibility announces each custom name together with its canonical Front, Middle or Back meaning. Unsupported boats retain the saved names until Length 3-Section Balance is available again.

Length Factor Balance describes longitudinal balance using BoatBalance’s model. Factored Weight (FW) is a comparison score, not a physical weight, so it has no lb or kg suffix. Higher Front or Back FW describes the modeled position relationship; there is no universal good/bad target.

Balance uses the team’s existing display unit, not a personal unit preference. FW values are rounded for display. Changing lb to kg changes the numerical score but not which end is higher, the relative ordering, or the modeled position relationship.

These computations describe different aspects of the assigned lineup. No universal ideal Front or Back target is implied. Front-Back, Section, and Factor results do not use Side Balance severity thresholds or symbols.

The wide Balance band shows one saved View with two calculations. Choose a card title to change that slot. Swipe left or right to move one View at a time; navigation does not wrap or advance automatically. Keyboard arrows and accessibility Previous View and Next View actions are also available. In a sidebar, all four calculations appear in canonical order and scroll independently when needed. Returning to the wide band restores the selected View. More → Settings → Balance Display configures one to six Views, ordering and both slots. Repeated calculations are allowed. These account-scoped, device-local choices do not change lineups, assignments or weights. Unavailable calculations retain their saved selection.

Authorized staff can add one guest or multiple guests to a specific event. Use a recognizable name, an actual or explicitly identified reference weight, and the appropriate preferred side. Record attendance deliberately and review validation or duplicate warnings before saving.

An event-only guest does not automatically become a permanent team member, receive a user account or invitation, or acquire notification consent. Do not invent a contact destination for a guest. Guests are not automatically added to another event.

Eligible event guests can appear in that event’s lineup using their accepted weight information. Review existing assignments and the removal confirmation before removing a guest. Retained event history is not erased merely by removing someone from the current working list.

Push notifications require device permission, the BoatBalance account preference and a current registration for the signed-in account and environment. Check notification settings if alerts are unavailable. Operating-system permission alone does not establish delivery readiness.

Verifying a telephone number confirms ownership; it does not record WhatsApp consent or enable notifications. WhatsApp consent is a separate affirmative choice, and delivery can remain unavailable even after consent is recorded. Use the app’s current consent controls to review your choice.

An SMS verification code is not an ordinary SMS event notification. Push, WhatsApp and SMS permissions are separate. Do not send verification codes, private message content or telephone numbers to support unless specifically needed through an agreed private process.

Preparing an event, lineup or confirmation schedule does not automatically send a message. Sending requires current authority, the applicable team and delivery settings, and an eligible recipient route. Preview the actual audience and content. If a submission’s outcome is uncertain, do not repeat it just to see whether it worked.