Technical reference. For task-based help, see the corresponding user guide.

Documentation status: complete for the current implementation

Reviewed: 2026-07-21

Primary users: premium-enabled families and assigned coaches with analysis access

Surfaces: mobile web app and platform API

Analysis turns a baby's raw care records into totals, averages and time-based plots. Users can inspect all visible trackers together or focus on one, move between comparable date ranges and open an underlying activity to correct it. The feature is permission- and premium-gated; ordinary tracking remains available without it.

The Analysis navigation contains All-in-one, Sleep, Breastfeed, Bottles, Nappies, Pumping, Solids and Medication. A family Home preference that hides a tracker also removes that tracker from Analysis navigation and from All-in-one summary contributions; it does not delete its records.

The screen first loads the family summary and evaluates summary.access.subject.permissions.canViewAnalysis.

1. An inactive family sees the premium-plan explanation and a route to monthly/yearly access.
2. A coach sees the subject's current entitlement/permission state and cannot bypass it by using a family ID.
3. The API independently checks canViewAnalysis before returning analysis activities.
4. Development builds currently default allowInactivePremiumAnalysis to true for local testing. That development override must not be interpreted as production entitlement behavior.

The family uses its persisted selected baby. Coach view-as uses a route-local baby choice that does not change the family's setting. With no baby, Analysis shows an add/select-baby state instead of issuing an unscoped query.

Previous/next shifts by the whole visible range: one day for Single Day, the preset length for presets and the inclusive custom-range length for Custom. All query boundaries are converted from family-local dates to UTC instants. Extra plot buffer may be loaded for smooth panning, but summary metrics remain locked to the labelled visible range.

Single Day uses totals/counts; multi-day ranges use per-day averages and trends. Selecting any statistic opens a plain-language calculation and meaning explanation.

Most non-sleep daily averages divide by days that contain matching data, rather than treating every blank calendar day as a recorded zero. Sleep averages are stricter: they use days containing both day and night sleep when available; a night-only dataset can use night groups, while incomplete mixed datasets show — instead of a misleading average. Overnight sleep is attributed to the product's sleep day consistently with Home/history.

Bottle and pumping volumes can be displayed in ml or oz. Values entered in mixed units are converted for aggregation without rewriting the source activity.

All views use a time-of-day schedule plot. Points/bars retain activity type/subtype colors and can span midnight. Solids points identify linked ladder/stage and reaction state. Users can horizontally inspect the buffered date area; the visible date controls and plots remain synchronized.

Selecting a point opens the shared activity edit sheet. A family with write access can save/delete. A coach also needs canWriteActivities; coach updates preserve the family note and are audited. If realtime reports that the activity changed while open, the sheet blocks overwrite until it is reloaded or closed.

Multi-day Breastfeed, Bottles, Sleep, Nappies and Pumping views add a per-day bar plot:

1. Breastfeed: left/right duration;
2. Bottles: breastmilk/formula volume;
3. Sleep: day/night duration;
4. Nappies: dirty/wet counts (a mixed nappy contributes to each relevant series);
5. Pumping: left/right volume.

All-in-one, Medication and Solids have schedule plots but no daily bar dataset in the current implementation. Single Day also omits the daily bar plot.

GET /analysis/activities requires babyId. It optionally accepts authorized familyUserId, activityType, and an ISO from/to pair. If one boundary is supplied without the other, schema validation rejects the request. The response is not cursor-paginated; the client requests the date-bounded dataset needed for the plot/range.

1. The platform resolves actor and family subject on every query and mutation.
2. Premium entitlement determines analysis access; it does not determine whether the family may continue logging care.
3. Coach analysis access and coach write access are separate permissions.
4. Hidden Home trackers are a presentation preference, not data deletion or API authorization.
5. Statistics are derived from persisted activity details/timezones; the client does not mutate source records to normalize units or dates.

1. Production users without canViewAnalysis cannot load data by navigating directly or calling the API.
2. Range labels, queries, totals and plots use the family timezone and the same inclusive dates.
3. Every statistic exposes a calculation/meaning explanation and handles sparse data honestly.
4. Mixed ml/oz data aggregates into the selected display unit without changing source entries.
5. Schedule points open the exact underlying activity and stale edits cannot overwrite external changes.
6. Daily bars appear only for supported multi-day tracker views.
7. Coach reads/writes remain assignment-scoped and preserve family-authored notes.

• mobile-web/src/routes/AnalysisScreen.tsx
• mobile-web/src/analysis/analysis-model.ts
• mobile-web/src/analysis/analysis-stats.ts
• mobile-web/src/analysis/analysis-plots.ts
• mobile-web/src/analysis/analysis-stat-details.ts
• mobile-web/src/analysis/analysis-units.ts
• mobile-web/src/components/AnalysisCharts.tsx
• platform/apps/api/src/routes/analysis-routes.ts
• platform/apps/api/src/services/analysis-service.ts
• platform/packages/shared/src/analysis.ts
• platform/docs/multi-tenancy/06-existing-app-feature-inventory.md

• 04 — Subscriptions, billing and premium access
• 05 — Family home
• 06 — Baby profiles and switching
• 07 — Activity tracking
• 11 — Allergy ladders