What keeps happening

What it is

Every change to a commitment's date or owner is recorded (by a person, a tracker, the CRM, or a later meeting). Nexa reads the last 90 days of that history and tells you when something repeats: a customer whose dates moved later three or more times across two or more commitments; a team whose dates keep moving across customers (shown as how many of its dated commitments moved); a customer whose own dates to you have passed; work that changed owner within 48 hours of its date, three or more times; everything you owe one customer held by one person; and a customer you kept every dated commitment to.

What it's for

A late commitment is something you see on Work. A pattern is what nobody sees until they read the history of every commitment by hand: the same customer slipping again, the same team handing work over at the last minute. Seeing it early is the difference between fixing a process and apologising to a customer.

How to use it

1. Open Today: patterns appear in Recommended next steps beside the other steps, marked Pattern, with what they are inferred from (for example "Inferred from 6 recorded changes in 90 days").
2. Click Show evidence: each commitment is listed with every recorded move (from which day to which day, and whether a person, the tracker, the CRM or a later meeting moved it). When a message or a meeting gave the new date and someone accepted it, its words are quoted with who said them.
3. Choose a step. For a customer, Accept prepares a reminder and an email draft (new dates you can keep, what you need from them, or what comes next) and nothing is sent until you confirm each one. For a team pattern, Accept records your decision and opens Team insights.
4. The same patterns are on the customer's page, in Team insights (dates moving across customers, late handovers, a customer held by one person) and in Business → Customers and Operations. A decision taken in one place is taken everywhere.
5. After you accept, Nexa looks again on the date shown (for example, in 14 days: did any of these dates move again) and says what it found after acceptance, in numbers ("No date moved again since", "They delivered 1 of 2"). It never claims it caused it.

Tips

• Dismiss with It's wrong when a pattern is not true: that is how Nexa learns which patterns are noise.
• A dismissed pattern comes back only if it repeats again (one more move, one more late handover).
• Ask Nexa "where do our dates keep slipping?" or "which customers are we waiting on?": the answer uses the same patterns, with the same counts.

Good to know

• A pattern is an inference from recorded changes, never a cause. Nexa says Recorded for a change it saw, Said for a reason somebody gave, and nothing more: two things that happen together are reported as happening together.
• Patterns are about customers and teams, never about one person's performance. The one that names a person (everything owed to a customer held by one person) is shown only to the people who run that work, and never to the person it names. It is not part of the Delivery record.
• You see only patterns built from commitments you may see. A department manager's counts are their departments' work; a member sees no team patterns. A reason quoted from a meeting or message appears only if you can open that source.
• Changes are recorded from 21 October 2026, so the first months show a shorter history. Nothing here uses AI or credits.