The season schedule almost never arrives as a calendar file. It arrives as a message: eleven practices, four games, two of them away, a note about the week of Thanksgiving, and a time change in the last paragraph that contradicts the first one. The job is to get all of it onto a calendar in one pass rather than typing sixteen entries at 10pm.
Open the Cue bar, paste the whole message in, and what comes back is a set of proposed events you look over and save. The thing that goes wrong quietly in a pasted season is the end date: "practice Tuesdays and Thursdays through November" has no day in it, so the series can land a week wide, and you find out when a reminder fires for a practice on an empty field in December. That check, and three others like it, are what this guide is about. It is one move inside the wider method for a family's schedule; everything below is specific to a season that arrived as text.
Paste more than you think you need
The instinct is to trim the message down to the dates. Do the opposite. Paste the whole message, greeting and sign off included.
The sentences around a schedule are where the information that makes the dates usable is hiding. The year is often only in the subject line or the opening sentence. The location is often stated once, at the top, and then never again. The words "all practices are at the boathouse unless noted" do more work than any individual row, and cutting them costs you eleven addresses.
If the schedule came as two messages, paste them one at a time rather than stitching them together yourself. A capture counts once Cue has read it, even if it finds nothing to add.
The repeating rows are the point
A season is mostly repetition. "Practice Tuesday and Thursday, 5:30 to 7:00, through November 14" is one line that stands for about twenty four evenings, and a repeating event is what you want out of it, not twenty four separate rows.
That matters later rather than now. When the coach moves practice to 6:00 in October, a repeating event lets you change one occurrence or the whole series, and Looped In asks you which you mean, the way the calendar app you already use does. Twenty four separate events means twenty four edits and one you will miss.
So the first thing to check in what comes back is whether the practices arrived as a series or as a pile. If the message described them in one sentence, they usually arrive as a series.
The second thing to check is the end date. An end written as "through November" is genuinely ambiguous, and a series that runs a week past the real end of the season is the error worth looking for every time. Fix it now, once, at the series level.
The dates with no year on them
"Sept 8" is a real date to a person reading it in August and a guess to anything reading it later. A date with no year is read as the next one that has not happened yet, which is correct while a season is starting and wrong when you are pasting a schedule from last spring to plan against.
The check takes ten seconds and it is the one worth doing every single time.
- Look at the first event's year.
- Look at the last event's year.
- A season that crosses New Year is the case to watch. A schedule that starts in November and ends in February should show two different years, and if both ends say the same year, one of them is wrong.
Fix the year before you save rather than after. After means finding the events again.
Times, and the events that come back without one
If a row says 5:30 and does not say whether that is the start or the whole thing, you get a start time and no end. That is fine. Add an end if you want the block on your calendar to look right.
If a row has no time at all, the event comes back with no time rather than with a guessed one. This is deliberate and it is the behavior you want, even though it looks like something went wrong. A tournament row that reads "Saturday, Riverside" genuinely does not say when, and an event that quietly invented 12:00pm would be worse than an event that says it does not know. Treat a timeless event as a question to take back to the coach.
Away games need the address, and the drive
An away game is two problems. The game, and the hour before the game.
Check that the location came through on the away rows specifically, because they are the ones where it was written once in a different format from everything else. If the message gave you a school name and no street, that is what you have, and it is worth turning into a task while you are looking at it: look up the address, add it to the event. A task with a due date two days before the game is the version of that thought that survives.
The drive itself is not an event and should not be one. What it is, usually, is the reason a Thursday game collides with something else, which is a thing you want to see when you look at the week rather than a thing you want on your calendar as a separate block.
Put it in its own place
Give the season its own Loop, named after the real thing: the club, the team, the season. Not "Sports". The point of a season having its own hub is that it ends, and when it does the whole thing goes quiet without you unpicking anything.
Once the events are saved, the ones that need to be on the calendar you already check are the games and anything unusual. The card Cue hands back carries a switch that adds an event to your iPhone calendar, so you can put the four games on your calendar and leave the twenty four practices in the Loop where they are not burying every other thing in your week. That is a judgment call and worth making deliberately rather than by default.
Practices are predictable. Games are the ones that move things.
What a whole season costs you to try
One season sheet is one paste, so the free three a day is enough to run this on the schedule sitting in your messages right now and see every date it pulls out before you decide anything.
Anyone you invite uses the Loops you share with them free, for as long as they are a member, which matters more for a team than for anything else. Starting Loops of their own is Looped In Plus, the same for them as for anyone. Sharing a season schedule covers what a member can actually do with it.
One last pass before you close the app
Read the saved list against the original message one time, top to bottom. You are looking for three things: an event on a date the message does not mention, a date in the message with no matching event, and a time that reads as suspiciously round. Sixteen events takes about ninety seconds to check, and this is the last cheap moment to catch a misread.
If something is wrong and you have just saved, an Undo button stays on screen for sixty seconds and takes out everything the capture added. After that, editing the one wrong event is quicker than starting over.
A schedule that came in as a message is now a season you can see. The next one that changes will arrive in the same thread it always does, and what to do when the group text is the schedule is about that.
