The schedule is only half the job. A season one person maintains is a season one person is permanently on call for, and the questions arrive at the worst possible times: the night before, in a message, from someone who has the same information you do and cannot find it.
Getting everyone onto the same dates is mostly a social problem with a small technical part. The technical part is one link. The part that decides whether it works is what you send with it: an invite into a half built Loop, with no explanation of what a member can do, gets opened once and never again, and you do not get a second first impression of it. This guide is about that half as much as the link.
Invite the people, not the roles
Open the Loop's menu and choose Invite People. You get a link to send, and a short code you can read out loud to someone standing in front of you, which is the better option at the side of a field.
Send it to actual people rather than broadcasting it once and hoping. The list for a season is usually shorter than it feels.
- The other parent or guardian, always, first.
- Whoever else drives that child on those days. The grandparent who does one pickup a week counts.
- The coach or the organizer, if they want it. Many do not, and that is fine.
- The other families, if the group is one where families coordinate directly with each other.
There is no seat count to manage and nobody meets a paywall for taking part, so the calculation of whether a person is worth inviting is purely "would it help", never "does it cost".
Say what joining does before you send it
Spend two sentences setting expectations. An invite gets ignored when the person cannot tell what is being asked of them, and two sentences is the whole cure.
Say three things.
What they will see. The season's dates, the jobs, and anything else in that one context. Not your family's other things, not your personal calendar. A Loop is one context and that is all a member gets.
What they can do. A member is a full participant. They can add an event, fix a time that is wrong, and check off a job. They are not a read only audience, which is worth saying out loud, because that is the assumption most invites arrive carrying.
What it costs them. Nothing for the Loops you share with them, for as long as they are a member. Starting Loops of their own is Looped In Plus. Worth saying explicitly, because everyone has been invited into something that turned into a bill.
Then send it once and stop. An invite you have to chase is an invite that is about to become a small resentment.
Give the jobs names
The reason to share a schedule is rarely the schedule. It is the jobs around it: bringing the water, collecting the fees, confirming the away address, being the one who checks whether the game moved.
A task in Looped In carries an owner and a due date. Use both, every time. A due date with nobody's name against it quietly slides. A name with no due date turns up on the day it was needed rather than the evening before.
Two practices that make this work on a real team.
Assign in public and early. Give out the season's jobs at the start, when nobody is under pressure, rather than the Thursday before each one.
Put the unglamorous thing on yourself first. The list reads very differently when the person who made it took the first job.
Decide where announcements happen, and say so
The thing that breaks shared schedules is ambiguity about where a change is announced. If half the team learns about the time change in the Loop and the other half learns in the message thread, both places are now unreliable and people go back to asking the organizer.
Pick one place for announcements and one for the record, and tell people which is which. In practice that usually means the thread you already have stays the place people talk, and the Loop is the place where the current truth lives. When something changes in the thread, one person moves it into the Loop, and the thread can say "updated in the Loop" so people know to look.
That handoff is the whole discipline. What to do when the group text is the schedule is about how to do it without trying to move a conversation that is not going to move.
What happens when somebody changes something
A member can edit, and occasionally somebody will edit something you would rather they had not.
Two things make this a small problem rather than a reason to avoid sharing.
Repeating events ask what you mean. Change or delete one occurrence of a weekly practice and Looped In asks whether you mean this event or all events, the way the calendar app you already use does, so a person fixing one week cannot silently move the whole season.
Deleting is reversible. A deleted Loop sits in Recently Deleted for 30 days and can be restored there, and anything else deleted, like an event or a task, is kept for 30 days too, so support can bring it back. A wrong swipe is an inconvenience, not a loss.
The remaining risk is two people editing the same thing in different directions, and the fix for that is the same as it has always been: one person owns the schedule, everyone else fixes what they know to be wrong. Say who that person is.
What the other parent pays
Nothing, and that is the only cost figure that matters on this page: the person who set the Loop up pays for Looped In Plus, and everyone they invite uses that Loop free, for as long as they are a member, with no limit on how many. Starting Loops of their own is Looped In Plus, the same for them as for anyone. A schedule that costs the other parent money to read is a schedule they will not read, which is why collaboration is not the thing being charged for.
Before you send the link
Do these five things first, in this order. An invite into an empty or half wrong Loop is one people bounce off and do not come back to.
- Get the season in. Paste the coach's message rather than typing sixteen events.
- Check the years and the end date on the repeating practices. This is the one thing that will be visibly wrong to everybody at once.
- Add the two or three jobs you already know about, with names on them.
- Name the Loop after the real thing, so the invite says something recognizable when it lands.
- If the Loop itself does not exist yet, start with the wider method for a family's schedule, which is where the structure comes from.
Then send it, with the two sentences about what it is. That whole sequence is about twenty minutes and it is the difference between a shared schedule people use and a link nobody opened.
