Chapter 47: Lateness
Part VIII: Case Maps
A late arrival can be a practical problem before either partner says a word about it. Someone may have missed an appointment, spent another half hour caring for a child, or been left without the information needed to make a different plan. A case map should preserve those consequences, not transform them into mere misunderstandings.
The following case is fictional. It illustrates one possible way of examining recurring conflict using Break the Loop (BTL). It is not a report of research participants or a clinical case. The thoughts attributed to each person are provisional parts of the illustration, not access to either person’s actual private experience.
The situation
Taylor and Jordan live together and share responsibility for collecting Jordan’s niece from an after-school activity on certain evenings. On Tuesday, Taylor agreed to arrive home by 5:30 p.m. so Jordan could leave for the pickup. At 5:43, Taylor arrived without having sent a message. Jordan had already made an alternative arrangement with the child’s parent. The child was safe because Jordan arranged backup coverage, but Jordan had been left to reorganize a commitment that Taylor had agreed to cover.
The issue is not whether Jordan reacted perfectly to lateness. The stated time was missed, and advance notice did not happen. Those are concrete facts of the invented case. Taylor’s explanation might affect what a reasonable future arrangement looks like, but it cannot erase that practical consequence.
1. Issue: What must still be addressed?
Jordan wants to know what happened, whether the 5:30 agreement was realistic, and what should happen next time a delay becomes likely. Taylor may need to account for an unexpected workplace demand or may have misjudged the trip home. The story does not settle which explanation is correct. They still need a workable plan for child pickup, notice, and backup coverage. A changed tone alone cannot arrange transportation.
2. Launch: What was noticed?
Taylor walks through the door. Jordan says, “I needed you here at five-thirty. Why didn’t you tell me you were late?” For Taylor, the Launch might be the question, Jordan’s raised voice, or the sight of Jordan holding a phone. The Launch names Taylor’s experience of what occurred, not proof that Jordan intended an attack. Jordan has a legitimate reason to ask.
For Jordan, a different Launch occurred earlier: the agreed time passed without Taylor or an update. This matters because each person may begin noticing a different part of the same event.
3. Overload: What started narrowing?
Taylor may notice a fast urge to explain everything at once. Listening to Jordan’s actual question becomes harder as Taylor thinks through the last hour at work and anticipates criticism. These are possible experiences, not signs that all capacity for choice has disappeared. Taylor can still decide how to respond.
Jordan, having managed the missed pickup plan, may also be impatient and less able to listen slowly. The example does not require that the two people have the same intensity of reaction or the same practical responsibility.
4. Old Story: What familiar meaning becomes influential?
Taylor might begin hearing, “Nothing I do is enough. I’m already in trouble before I can speak.” That familiar prediction may or may not accurately describe what Jordan thinks. It is not established by the question alone.
Jordan might think, “When I need you to follow through, I end up handling it myself.” The case deliberately leaves open whether this is a well-founded account of a longer history, a partially accurate interpretation, or a prediction intensified by the immediate problem. An Old Story is not automatically false, and the real missed commitment should not be denied simply because it carries emotional meaning.
5. Protection Move: What happens next?
Taylor says, “You have no idea how much I had to get done today. I can’t control every minute.” Taylor then gives a detailed account of work before answering why no text was sent. The immediate function may be to protect a sense of competence or avoid feeling unfairly judged. That explanation of possible function does not excuse failing to give notice.
Jordan answers, “You always have an excuse.” That statement is a more sweeping accusation than the facts of this single evening can prove. It may also make a useful conversation about timing harder. The map can describe both statements while retaining the initial broken agreement and any unequal responsibility for it.
6. Partner experience: How might the move be received?
Jordan may hear Taylor’s detailed defense as an attempt to make the late arrival irrelevant. The observed fact is that Taylor explained work before acknowledging the notice failure. Whether Taylor meant to dismiss Jordan remains uncertain.
Taylor may hear “always” as confirmation that Jordan has already decided Taylor is unreliable. Again, that experience is not proof of Jordan’s private intention. Neither interpretation should substitute for asking what each person actually meant or for evaluating the original commitment.
7. Next Launch: How can one response become another starting point?
Taylor’s extended defense can become Jordan’s next Launch: “You’re not even answering the part about texting.” Jordan’s global accusation can then become Taylor’s next Launch: “So now everything I do is wrong?” The illustration shows how one Protection Move may be experienced as the other person’s next Launch. It does not establish a measured causal sequence or divide responsibility equally between them.
8. Recurring pattern: What might repeat when details change?
Two days later, Jordan is late to an agreed dinner because an appointment runs long. Jordan sends a text ten minutes before the reservation, but Taylor feels overlooked and says sharply, “I guess the plan never matters.” Jordan responds by withdrawing and saying very little. This second incident differs from Tuesday in who is late, the seriousness of the practical consequence, whether advance notice was attempted, and the form of the next response.
Within BTL, the recurring Loop is the underlying sequence Launch → Overload → Old Story → Protection Move. The topics, events, emotions, meanings, beliefs, and actions at each point may vary from one occasion to another. We could tentatively map the dinner exchange as a noticed delay, growing difficulty staying curious, a familiar prediction about being unimportant, and an accusing or withdrawing response. But these two invented scenes do not demonstrate scientifically that this couple has a recurrent sequence. They show how a reader might examine that possibility. Shared labels alone do not make two separate incidents equivalent.
The practical difference also remains important: a late pickup with no notice and a later dinner with some notice may reasonably require different responses. Pattern recognition should not flatten differences in seriousness.
9. Possible interruption: Where might another choice enter?
Suppose Taylor notices the explanatory rush after the first question. Taylor could say, “You’re right that I missed the time, and I should have messaged. I want to explain what delayed me, but I can answer that part first.” This is a possible choice, not a scripted guarantee of a productive response.
Using the BTL educational interrupt sequence, Taylor could NAME IT by recognizing the urge to defend; SLOW IT by pausing rather than immediately giving a long explanation; CHECK IT by separating the thought “I’m being attacked” from what Jordan actually asked; and CHOOSE IT by acknowledging the missed notice and discussing what the evening required. Formally, the sequence is NAME IT → SLOW IT → CHECK IT → CHOOSE IT.
The interruption could happen later. Taylor might realize the pattern only after another sharp exchange and return to the specific responsibility. Jordan could also choose to avoid a global “always” claim while still asking directly for follow-through. Neither choice obligates Jordan to stop being concerned about an unmet agreement. The framework has not been independently demonstrated to prevent future late arrivals or improve the outcome of this particular interaction.
10. Unresolved issue: What still needs a practical answer?
The partners still need to know whether the original schedule was feasible, who is responsible for contact when plans change, what counts as sufficiently early notice, and who can provide backup child care without placing that burden automatically on Jordan. A specific agreement might include a message as soon as a delay becomes apparent and a separate contingency plan for a time-sensitive pickup. That is a proposal for their fictional situation, not a universal rule.
Time is not simply a matter of attitude. A U.S. time-diary study found that the amount of time married adults spent with a spouse varied across work and parenting circumstances, and that adjusting for work on the diary day reduced some apparent differences between work-arrangement groups (Flood & Genadek, 2016). That study measured individuals’ time use, not these characters, late arrivals, relationship motives, or the BTL sequence. It is a reminder to examine actual constraints before assuming that every missed plan reflects a person’s priorities.
11. Aftermath and repair considerations: What would follow?
If Taylor acknowledges the missed obligation but makes no change to the notice process, Jordan may reasonably continue to worry about dependability. A later apology may matter, but it is not the same as a completed pickup plan or reliable follow-through. Chapter 42 discusses acknowledgment, accountability, and return to an issue more fully.
The case also allows an imperfect ending. Jordan may still be irritated. Taylor may be embarrassed. They may need another conversation after the immediate logistics are settled. The educational aim is not a perfectly calm couple or instant forgiveness, but a more careful distinction among what happened, what it began to mean, what happened next, and what remains to be done.
What this map cannot tell us
A map of lateness cannot tell whether Taylor actually had an unavoidable delay, whether Jordan’s account of previous missed commitments is correct, or whether either person is intentionally disregarding the other. It cannot establish how common this particular sequence is or predict whether another response would change future behavior. The fictional timing details are teaching details, not research measurements.
Nor should an ordinary case map be imposed where lateness is bound up with coercion. Deliberately preventing a partner from working, withholding access to transportation, using location tracking to threaten, punishing a partner for a delay, or making a person fear retaliation is not merely a reciprocal argument about punctuality. In circumstances involving coercive control, threats, stalking, violence, sexual coercion, or fear, safety and appropriate individualized support take priority over mutual Loop exercises. A person is not required to negotiate a shared pattern with someone who makes disagreement unsafe.
The central distinction
The issue is the missed time, inadequate notice, and concrete impact on another person’s responsibilities. A possible Loop concerns how each person experiences the event, assigns meaning, and responds during the disagreement. Either can matter without replacing the other. The reader can use this case to notice a possible repeated sequence while remaining uncertain about motives, making space for accountability, and returning to the real scheduling problem. Chapter 44 explains how to read a case map; Chapter 24 examines work and time constraints in greater depth.