Count the places your family's next two weeks are written down. Five is a normal answer: the school's email, a sports team's app, a group message thread, a paper flyer stuck to the fridge, and the calendar on your phone that only has half of it. None of the five knows about the other four, so the only complete copy of your family's schedule is the one in your head, and that copy is the one that wakes you up at 2am.
The fix is not a better calendar, and the failure this guide is written against is the opposite one: pouring everything into the calendar until it is full of all-day entries that say "order form?" and nobody trusts it. What actually works is a rule about where things land, a habit that takes fifteen minutes a week, and a way to get a date out of a photograph without typing it. This guide is the whole method, start to finish. Six shorter guides go deeper on the individual moves, and they are linked at the bottom.
First write down where it actually lives
Before you move anything, spend ten minutes on an inventory. Open a blank note and list every place a date about your family has arrived in the last month. Be specific. Not "school" but "the weekly email from the office, the teacher's paper newsletter, and the principal's text alerts". Not "sports" but "the team app, and the coach's message thread where the real changes happen".
You are looking for three things.
- Which places are announcements and which are conversations. An announcement arrives once and is final. A conversation buries the change in message 340. They need different handling.
- Which places you cannot leave. The team app is not optional if the coach posts there. The school email is not optional. Accept those and plan around them.
- Who else is looking. A date only you can see is a date you are personally responsible for at all times.
The list usually comes out shorter than it felt, and lopsided: a handful of sources, one or two of which produce nearly all of it.
Pick the one place that has to be right
You need a single place that is complete enough to answer "what is happening Thursday" without checking anything else. For almost everyone that should be the calendar already on your phone, the one that shows you tomorrow when you glance at your lock screen. Not because it is a good place to organize things, but because it is the place you already look, and a system that depends on you remembering to look somewhere new is a system that quietly stops working in week three.
So the calendar is the output, not the workspace. Things are sorted somewhere else and the dated ones get pushed onto it. That distinction is the one decision in this guide worth arguing about, and it is easy to get backwards: make the calendar hold everything, including the things that are not dates, and within a month it is full of all-day entries that say "order form?" and nobody trusts it.
What belongs on the calendar: anything with a time and a place that would cause a problem if it were missed. What does not: the task, the reminder, the address you will need, the fact that the away game is a forty minute drive.
Draw the lines by context, not by person
The tempting structure is one calendar per person. It feels tidy for about two weeks. Then you notice that your kid's rowing season and their chemistry class and the family trip in March have nothing to do with each other, all three change on different schedules, and the people who need to see each one are three different sets of people.
Split by context instead. A context is a real thing in your life with a start, an end, and a group of people attached: the season, the class, the committee, the trip, the street. In Looped In, that is what a Loop is, and the test for whether two things belong in one Loop is simple.
If you would send the same message to everyone involved in both, they are one context. If you would have to explain who you are talking about, they are two.
That gives you a handful of Loops rather than a handful of calendars, and the crucial difference is that a context ends. When the season is over, the whole thing goes quiet without you having to unpick a shared calendar somebody else is still using.
Three or four Loops is a normal starting number. If you have eleven, you have split too finely and you will not keep it up.
Stop retyping, because retyping is where this fails
Every one of the five places produces the same thing in the end: a date, a time, a place, and often a job for you. The work is not in knowing that. It is in moving it, character by character, into a form your calendar accepts, at 9:40pm, from a photograph of a piece of paper.
That is the part to remove. There are four ways something arrives, and none of them should involve typing it twice.
- It arrived as text. A message from the coach, a paragraph in an email, a schedule someone typed into a thread. Copy it and paste the whole thing in. Pasting more context is better than pasting less: the surrounding sentences are often where the year, the location or the "except the week of the 14th" is hiding.
- It arrived on paper. Photograph it. Your phone reads the text off the page itself using Apple's text recognition, on the device, and it is the recognized text that goes on to be sorted rather than the picture.
- It is a screenshot you already took. You screenshotted the team app in April and never looked at it again. Pick it out of your photo library. The backlog in your Screenshots album is a to-do list nobody wrote down.
- It is in your head and you are driving. Say it out loud. Speech is transcribed on your device and the audio never leaves your phone.
In each case what comes back is a set of proposed events, tasks and notes, already filled in, for you to look over. Cue proposes and you confirm. Nothing is created until you tap, and after you save, an Undo button stays on screen for sixty seconds and takes out everything the capture added.
Two honest notes about what comes back. Dates are the thing to check first, because a flyer that says "September 8" and nothing else is genuinely ambiguous about the year. And when the source does not state a time, the event comes back without one rather than with a guessed one, which is the correct behavior and occasionally looks like a mistake. An event with no time is telling you the page did not have a time on it.
Decide what happens to the things that are not dates
Half of what arrives is not an event at all. It is a job, or it is a fact you will want in six weeks.
Jobs become tasks with a name on them. The point of the name is not accountability theater, it is that "bring the water" sitting on a shared list with nobody's name on it is a job everyone assumes somebody else took. Give it an owner and a due date and the assumption goes away.
Facts become notes. The gate code. The coach's preferred way of being reached. The fact that the uniform order closes before the first practice. These are the things that are genuinely hard to find later, because they were never a date and so they never made it onto anything.
The reason to keep all three in the same hub rather than scattering them is not tidiness. It is that in March, when you need the gate code, you will remember the season, not the app.
The weekly pass
Set aside fifteen minutes on the same day every week. Sunday evening is a good default, because it is the last moment the coming week is still editable.
The pass has four steps, in this order.
- Empty the inbox of the week. Every screenshot you took, every flyer in the bag, every message you starred. Capture them. This is usually ten minutes of the fifteen.
- Look at the next two weeks in one view. Not one month. Two weeks is the horizon where a conflict is still solvable and a decision still has to be made.
- Find the collisions. Two things at 5:30 on Thursday. A game an hour away that starts twenty minutes after school ends. These are the reason the pass exists.
- Hand off what you cannot do. Anything you have found a collision in needs a second adult, and that conversation is far easier on a Sunday than on the Thursday.
If you can only keep one habit from this whole guide, keep this one. The capture tools make the pass fast. The pass is what makes the system true.
A week, worked through
Here is what the method looks like on an ordinary Sunday, using a household with two kids, a swim club and a school.
The bag by the door has two notices in it. One is picture day, a Friday in three weeks, with a line about an order form due the Wednesday before. The other is a field trip with a cost on it and a permission slip. Both get photographed, one page per photo, and both come back as an event plus a task plus a fact. Picture day and the trip go into the class Loop. The order form and the permission slip become tasks with a name and a due date two days before each event. The cost of the trip becomes a note, because in five weeks somebody will ask.
The phone has four screenshots on it since last Sunday. Two are a meet schedule from the swim club's app, one is a confirmation, and one is a picture of somebody's dog. Three get captured into the swim Loop, one gets deleted.
Then the two week view. Picture day is fine. The trip is fine. But the Thursday meet starts at 5:15 and the younger kid's lesson is at 5:00 on the other side of town, which is the collision, and it is the only thing on this list that actually needed a human. That is the conversation to have on Sunday rather than on Thursday, and the reason the whole pass exists is to surface it four days early.
Total time: about twelve minutes, most of it the screenshots.
Get the other adults looking at the same dates
A schedule one person maintains is a schedule one person is on call for. The way out is to make the other adults readers rather than requesters, and to do it without asking anyone to sign up for something.
Invite them into the Loop. They get a link, and anyone you invite uses the Loops you share with them free: they see everything in those Loops and add, change and finish their events, tasks and notes without paying, for as long as they are a member, with no cap on how many people you add. Starting Loops of their own is Looped In Plus, the same for them as for anyone. Inviting the grandparent who does Wednesday pickup costs nothing and takes the Wednesday question off your phone.
The important part is social rather than technical. Do not make joining a condition of being told things. Tell people what you are doing, send the link once, and keep telling the ones who do not join in whatever way you already do. An invite you have to chase costs you more than the person would have added.
What this does not fix
Three things this method genuinely will not do, said plainly so you can plan around them.
It will not read a schedule nobody gave you. If the coach never posts the away game addresses, no amount of capture produces them.
It will not make a bad source good. A screenshot of a month view in another app, where the rows are compressed and the times are small gray text, is a hard read and sometimes the times come back wrong. A list view from the same app is a much better photograph to take. When you have a choice, take the picture of the list.
And it will not organize other people. A thread where six adults are still deciding is a thread that has to finish deciding. What this does is stop the outcome from living only in that thread.
Where to go next
Each of these takes one move from above and goes deep on it.
- Getting a sports season schedule into your calendar from a text, including the repeating practices and the dates with no year on them.
- Turning the flyer on the fridge into a calendar event, and how to photograph paper so it reads cleanly.
- Clearing the screenshots you took and forgot, which is the step that turns up dates you did not know you had missed.
- Setting up one place for the school year before the September paperwork arrives.
- Sharing a season schedule with the other parent and the team, and what a member can actually do.
- What to do when the group text is the schedule, without trying to move the conversation.
