Scoring

Scoring Transparency

Read-only reference for score formulas, inputs, caps, confidence labels, and data boundaries.

Safety Boundary

Scores are operating signals

Scores help explain capacity, execution, and backlog pressure. They are not medical diagnoses, treatment advice, training prescriptions, or automated commands. WHOOP is one objective input; manual symptoms remain first-class.

Back to Settings

Score Logic

Daily Operator Score

Overall daily operating signal for execution capacity and follow-through.

Body ScoreOutput ScoreAlignment Score

Formula

  • Body Score: 30%
  • Output Score: 30%
  • Alignment Score: 20%
  • Calendar completion: 10%
  • Capture backlog score: 10%

Inputs Used

  • Body capacity and load
  • Output execution
  • Alignment practices
  • Completed minutes out of planned minutes
  • Unprocessed capture backlog

Caps / Penalties

  • Body Red or High Load Signal can cap the score at 70.
  • Manual crash/load level >= 7 can cap the score at 60.
  • Capture backlog over 10 subtracts 10 points.
  • Calendar completion below 50% subtracts 5 points when planned minutes exist.

Data Sources

  • Body Score
  • Output Score
  • Alignment Score
  • Calendar metrics
  • Capture metrics

Score Logic

Body Score

Capacity/readiness signal for how much the day can reasonably absorb.

WHOOP recovery, sleep, cycle, and workout tablesManual symptom logsManual and WHOOP-linked training responses

Formula

  • objective readiness 40%
  • objective load 15%
  • manual nervous system signals 30%
  • manual training response 15%

Inputs Used

  • WHOOP recovery score
  • Sleep performance
  • HRV and resting heart rate support
  • Cycle strain and workout strain
  • Symptom sliders and crash/load level
  • Mental fatigue, blurred vision, balance issues, heart-rate spikes
  • Felt during, felt 2 hours after, felt next morning

Caps / Penalties

  • Crash/load >= 8 caps at 55.
  • Crash/load >= 7 caps at 60.
  • Symptom average >= 7 caps at 60.
  • Symptom average >= 6 caps at 65.
  • Mental fatigue >= 7 caps at 65.
  • Blurred vision >= 6 caps at 70.
  • Balance issues >= 6 caps at 70.
  • Felt next morning <= 4 caps at 70.
  • Felt next morning <= 3 caps at 60.

Data Sources

  • WHOOP recovery, sleep, cycle, and workout tables
  • Manual symptom logs
  • Manual and WHOOP-linked training responses

What This Does Not Mean

  • Manual symptoms can reduce or cap the score even when WHOOP looks strong.
  • This is an operating signal, not a medical readiness score.

Score Logic

Load Signal

A plain operating signal for whether load pressure is low, moderate, or high.

WHOOP strain and workout strainManual symptom logsManual training responses

Formula

  • Combines symptom average, weighted symptoms, crash/load level, cycle strain, workout strain, perceived exertion, and next-morning response.
  • Outputs Low, Moderate, or High.

Inputs Used

  • Symptoms
  • Crash/load level
  • WHOOP strain
  • Workout strain
  • Perceived exertion
  • Next-morning response

Data Sources

  • WHOOP strain and workout strain
  • Manual symptom logs
  • Manual training responses

What This Does Not Mean

  • Not a diagnosis and not a treatment recommendation.

Score Logic

Output Score

Follow-through and work-output signal for the day.

Output daily log

Formula

  • Deep work score: 35%
  • Sales/activity score: 30%
  • Completion score: 20%
  • Total activity score: 15%

Inputs Used

  • Deep work blocks
  • Focused work minutes
  • Calls, connects, follow-ups, Looms, applications, interviews, offers
  • Most important work completed
  • Sales training and notes

Data Sources

  • Output daily log

Not Included Yet

  • Broader sales pipeline quality beyond currently tracked fields.

Score Logic

Alignment Score

Daily spiritual and relational alignment signal.

Alignment daily log

Formula

  • Prayer minutes: 30%
  • Journaling: 20%
  • Screen discipline: 25%
  • Peace rating: 25%

Inputs Used

  • Bible/prayer minutes
  • Journaling complete
  • Screen discipline
  • Peace rating

Data Sources

  • Alignment daily log

Score Logic

Calendar Completion

Follow-through score for planned time blocks.

calendar_events

Formula

  • Planned minutes are the total visible event duration.
  • Completed minutes are visible events marked Completed.
  • Missed minutes are visible events marked Missed.
  • Completion percentage = completed minutes / planned minutes.

Inputs Used

  • Manual calendar events
  • Google synced events
  • Completed/Missed/Planned status
  • Hidden state

Data Sources

  • calendar_events

What This Does Not Mean

  • Hidden events are excluded from normal completion metrics.

Score Logic

Task Metrics

Task pressure and priority visibility.

tasks

Formula

  • Counts total tasks, completed tasks, Must Do remaining, overdue tasks, and due-today tasks.
  • Top Must Do sorting prioritizes overdue, due today, due tomorrow, future due date, then no due date, with In Progress before Not Started when dates tie.

Inputs Used

  • Task priority
  • Task status
  • Due date
  • Category

Data Sources

  • tasks

Score Logic

Capture Metrics

Inbox pressure and capture-processing visibility.

capture_inbox

Formula

  • Counts total, new, unprocessed, classified, processed, archived, and failed classification records.
  • Capture backlog contributes to Daily Operator Score through a backlog score.

Inputs Used

  • Capture status
  • Classification status
  • Suggested type

Data Sources

  • capture_inbox

Score Logic

Weekly Score / Trends

Historical trend context for weekly debrief and pattern review.

daily_score_snapshotsweekly_reviews

Formula

  • Weekly trends use daily_score_snapshots when available.
  • If snapshots are missing, weekly trend UI falls back to sample/demo data and labels it accordingly.
  • Snapshots are generated manually for now.

Inputs Used

  • Daily Body, Output, Alignment, and Operator scores
  • Calendar/task/capture metrics stored in snapshots
  • Weekly review fields

Data Sources

  • daily_score_snapshots
  • weekly_reviews

Confidence Labels

Real, mixed, fallback, demo

Real

Primary data sources are available, such as WHOOP plus manual inputs for Body.

Mixed

Some real data exists, but one or more important inputs are incomplete.

Fallback

System fallback values are being used because real source data is missing.

Demo

Sample/demo data is being used for display or trend context.