What Norian looks for

Norian reads each email in a connected channel and looks for three kinds of moments: commitments, requests, and decisions.

Commitments are something someone said they would do. "I'll send the revised deck by Friday" is a commitment, whether you wrote it or a client did.

Requests are something someone asked for. "Could you share the updated timeline?" is a request, again from either direction.

Decisions are agreements worth remembering. "Let's go with option B" is a decision - useful context for later, but not something anyone owes anyone.

Commitments and requests are actionable. They're the things that can slip, so they're the things Norian watches: they appear on your radar and, if they're at risk, in your daily digest.

Decisions work differently. We keep them on the client's history so the full picture stays intact, but we never put them on your radar and never include them in a digest. There's nothing to act on, so there's nothing to flag.

This split is what keeps the radar useful. A running log of everything said in every email would be noise. Norian only surfaces the things that can genuinely be dropped.

See Quiet by design for how Norian decides when a commitment or request is actually at risk.