Exception-Based Tracking: The Trendwell Way

Most tracking apps expect you to log everything every day. That works for a week, maybe two. Then you burn out.

Trendwell takes a different approach: exception-based tracking. You set what "normal" looks like, then only log when something's different.

Here's how it works and why it's more effective.

The Exception-Based Philosophy

Most Days Are Similar

Think about your typical week:

• Same rough bedtime
• Similar eating patterns
• Typical stress level
• Normal activity

Why log the same information repeatedly?

Exceptions Are What Matter

When something's different, that's the signal:

• Late night
• Stressful day
• Unusual eating
• Skipped exercise

These exceptions are what correlate with outcome changes.

Key Insight: Exceptions contain the signal. Normal days are just noise confirmation.

How It Works in Trendwell

Set Your Defaults

First, define your typical patterns:

• Normal bedtime: 11:00pm
• Normal eating window: 7am-7pm
• Normal movement: Yes (if you usually move)
• Normal stress: 2/5

These represent YOUR normal, not ideals.

Daily Confirmation

On normal days:

• Open Trendwell
• Confirm "Normal day" (one tap)
• Done in 5 seconds

Exception Logging

When something's different:

• Note the exception
• "Bedtime: 1am (party)"
• "Stress: 4/5 (work deadline)"

Takes 15-30 seconds for actual exceptions.

What Counts as an Exception

Clear Exceptions

• Bedtime 1+ hours from normal
• Eating window significantly different
• High stress day
• No movement when you usually move
• Movement when you usually don't
• Alcohol when you typically don't drink

Not Exceptions

• 15 minutes variation in bedtime
• Slightly different meal times
• Normal day stress
• Typical behavior

If it's roughly normal, confirm normal.

Why This Works Better

Sustainable

• 5 seconds on normal days
• No logging fatigue
• Years of tracking become possible

Signal Preservation

• Exceptions are highlighted in data
• Normal days provide baseline
• Correlations emerge from exception patterns

Less Obsessive

• Not micromanaging every input
• Focus on what actually varies
• Healthier relationship with tracking

More Accurate

• You remember exceptions better
• Detailed notes when it matters
• Less random error from rushed logging

Exception-Based Analysis

Finding Patterns

When reviewing data:

• Exceptions stand out visually
• Correlate exceptions with outcome changes
• See what actually affected you

Example Pattern

Your BP spike patterns:

• Exception: "Late night + alcohol"
• Next-day BP: Elevated
• Pattern: Party nights → high morning BP

This is clearer than daily detailed logging because exceptions highlight the signal.

Tips for Exception Tracking

Be Honest About Normal

Defaults should reflect reality:

• If you often go to bed at midnight, that's your normal
• If you rarely exercise, "No" is your default
• Accurate defaults = meaningful exceptions

Note the Why

When logging exceptions, add context:

• "Late night - friend's birthday"
• "High stress - project deadline"
• "No movement - sick"

Context helps interpretation later.

Don't Over-Exception

Not everything needs detail:

• Minor variations are still "normal"
• Only note significant deviations
• Keep it simple

Common Questions

"What if I forget an exception?"

Log what you remember. Some data > no data. Your baseline days are still captured.

"How do I know if something is an exception?"

If you're unsure, it's probably normal. Exceptions are usually obvious—you know when the day was different.

"Won't I miss important data?"

You'll capture the data that actually varies. Normal days are valuable as baseline, but don't need details.

Next Steps

• Read: Setting Your Defaults in Trendwell
• Read: Log Less, Learn More: Exception-Based Tracking
• Set: Accurate defaults for your inputs
• Practice: Normal day confirmations + exception notes
• Trust: The system captures what matters

Exception-based tracking is tracking that lasts. Log less, learn more.

---

Last updated: January 2026