Captured Notes and the Inbox

Covers notes you send from a phone during practice and the inbox for notes without a clear match.

Coach Guides Captured Notes and the Inbox
Opposition
Opposition
On This Page How a Capture Travels Tokens Sending a Note How Routing Decides The Inbox The Queue Inbox Keys Related

How a Capture Travels

Follows a note from the phone to an event, a team or the inbox.

Capture
A note sent from a phone. Coach Binder stores its text exactly as sent.
Token
A key that lets an app on your phone send notes to Coach Binder in your name.
Inbox
Holds each capture without a clear match. The capture stays in the inbox until you file or discard the capture.
  1. An app on the phone, such as a shortcut, sends the note's text with a token.
  2. Coach Binder stores the text exactly as sent. Nothing ever edits the stored text.
  3. Coach Binder matches an event or team first, then the players the note names.
  4. A confident match becomes a private note in the token owner's name. An uncertain match goes to the inbox for you to file.

Tokens

A token is a key for another app, such as a phone shortcut. The app uses the token to send notes to Coach Binder in your name.

  1. Click the account icon at the top right, then the Tokens tab. On a phone, click Settings in the menu.
  2. Make one token for each app.
  3. Click New Token at the top of the page. Cancel closes the form.
  4. Enter a Label and click Add Token. The token appears once.
  5. Copy the token into the app immediately. The token never appears again.
  6. Click I Copied It to close the token box.
Coach Binder keeps no copy of the token.
Example A live token and a revoked one.
Label Created Last Used Status
Shortcut on phone Sep 3, 2026 Oct 6, 7:42 pm Live
Old tablet Aug 12, 2026 Revoked
Label
The name of the app that uses the token. Use a name you will recognize later.
Owner
The member who created the token. Every note sent with the token carries the owner's name.
Teams
Notes match only to teams the token's owner can see.
Created and Last Used
The date each token was created and the last time an app used the token.
Status
Live or Revoked. A revoked token no longer sends notes.
Revoke
Opens a confirm band. Click Revoke It to turn the token off. Coach Binder then refuses every note the app sends.

Sending a Note

Any app that makes web requests can send a note. The request needs only the text and the token.

POST /api/notes
Authorization: Bearer <your token>
Content-Type: application/json

{"text": "10U: great gap control from 12 tonight",
 "occurred_at": "2026-10-06T19:42:00-07:00"}
text
Required. The note's text, up to 4000 characters.
occurred_at
Optional. The time you made the note. Leave the field out to use the arrival time.
external_id
Optional. Your app's own id for the note. Sending the same id again with the same token creates nothing new.
event_id, team_id
Optional. Files the note to that event or team when the token's owner can see that event or team.
source
Optional. A short label for the sending app, up to 60 characters. The inbox shows this label.
Routing matches events by occurred_at. Use an app that queues notes and sends each note's time.
Put the token in the Authorization header and nowhere else. Coach Binder refuses a token in the address.

The reply carries a short summary, such as the player and team, for the app to show.

A refused note gets a reply with an error code and a message.

error
A short code the app can check, listed below.
message
A plain sentence the app can show to you.
details
Sent with invalid only. Names each field that failed and why.
CodeHTTP StatusMessage
unauthorized 401 The note did not save. The token is not valid.
rate_limited 429 The note did not save. Too many notes arrived this minute. Wait 1 minute.
paused 402 The note did not save. This workspace is paused. A workspace owner restarts the workspace on the Billing page.
invalid 422 The note did not save.

How Routing Decides

Coach Binder checks these steps in order and stops at the first match.

Example The steps in order. The first match files the note.
  1. Named in the RequestThe event or team the request names comes first.
  2. Team at the StartA note starting with 10U files to that team.
  3. One Event RunningCounts as running from 15 minutes before the start to 30 minutes after the end. Players match that event's rosters.
  4. UnsureTwo events at once, a tie between players, or no event and no team. The note goes to the inbox.
  1. An event or team named in the request comes first.
  2. Next comes a team named at the start of the note, such as 10U:. The note files to that team's running event, or to the team itself.
  3. If exactly one event was running when you made the note, the note files to that event. An event counts as running from 15 minutes before it starts to 30 minutes after it ends.
  4. If two or more events were running, the note goes to the inbox. The exception is a note that names the team of one of those events.
  5. If nothing was running but one event is within 90 minutes, the note goes to the inbox. The inbox suggests that event.
  6. Otherwise a team named anywhere in the text files the note at team level. With no team named, the note goes to the inbox.

Coach Binder matches players only against the rosters at that event, or the team's roster for a team note. Coach Binder never searches every player in the workspace.

Coach Binder never guesses between two players. A tie, or any uncertain match, goes to the inbox.
The inbox fills faster as a result. Coach Binder prefers a fuller inbox over a note filed about the wrong child.

The Inbox

Holds phone notes that Coach Binder could not match to a player or event. Click the inbox icon at the top right of any page to open it. Its badge counts the notes waiting.

Review card
Shows one capture with its text and Reason.
Reason
Says why Coach Binder did not file the note.
Event
The event the note goes on. Select Team Note to file the note on the whole team.
Earlier This Week
Marks events from the seven days before the note. The marked events appear only when the note's own day has no event.
Team Note for any team
A note that names no team offers a Team Note for each of your teams. Selecting a team matches the note's names against that roster.
Event names
Each event shows its rink or location. The rink tells apart two events at the same time.
Player
The players the note is about. Select Nobody for a note about no player.
Visibility
Who reads the note. Private is you only. Staff adds the other coaches.
Attach
Files the note and opens the next capture. Attach stays off until an event or a team is selected.
Queue tags
Each note in the queue carries a short reason, such as No Event Then. The review card gives the full reason.
Deleted events
A deleted event never takes a note, from the phone or the inbox.
Back and Skip
Move to the previous or next capture in the queue.
Discard
Closes the capture without filing the note. Coach Binder still keeps the capture and its text.
Remember Alias
Saves the word in the note as another name for the chosen player. Appears only when a match came from a close spelling.
WhoWhat They See in the Inbox
Staff Their own captures.
Members and Roles at Edit Everyone's captures.
Families Never see the inbox.

An empty inbox says what appears there and how to sort each note.

Example The inbox with nothing to decide.
Unmatched phone notes appear here. Select a player or event to sort each note.

The Queue

Lists every capture in the inbox (oldest first), beside the review card. Click a row to open that capture.

Example Three captures. The first is a tie between two players. The last is marked Sure.
great gap control from 12 tonight, keep him on the left side Oct 6 7:42 pm Alex Moreno and Alex Kim match the note equally. Coach Binder never picks between tied players. Select the right player.
work on backchecking for everyone next practice Oct 6 9:15 pm No event was happening at the note's time. The note does not name a team. Select an event or click Discard.
10U: Sam strong on the forecheck Oct 8 7:05 pm The note matched an event. The note did not save. Check the choices and click Attach. Sure
Sure
Marks a capture whose event or team matched with at least 90% confidence. Every player in the capture also matched.
Attach N Sure Notes
Files every Sure capture together. The button is at the top of the page. Confirm in the band that opens.
Keep Them in the Inbox
Closes the band without filing anything. Press Esc to do the same. The inbox keys stay off while the band is open.
Visibility
Notes you attach from the inbox are Private or Staff. The inbox never shares a note with families.

Inbox Keys

Lists the keyboard keys for the review card. A touch screen hides the key hints.

KeyAction
Enter Attaches the note.
← or ↑ Goes back to the previous capture.
→ or ↓ Skips to the next capture.
1 to 9 Selects a player, or an event when no players are offered.
0 Selects Nobody.
S Switches the note between Private and Staff.
A Saves the alias, the same as Remember Alias.
D Discards the capture.
Esc Closes the Attach Sure Notes band.

Related