Daily context is scattered.
Movement, meals, totals, and progress lose meaning when each uses a different route.
Independent product · Web
Keep two personal health records clear inside one shared daily view.
Open the website ↗Information model, controls, states, and privacy
Shared health and food record
One date pattern across the product
With distinct personal records
Project value
Keep Day, Food, and Progress easy to reach.
Show one person’s food record at a time.
Use the same date controls in every daily view.
Movement, meals, totals, and progress lose meaning when each uses a different route.
Two people can use one dashboard only when each record stays clear.
Keep three main views, one date pattern, and direct person selection.
Design decisions
The public dashboard keeps Day, Food, and Progress as its main routes.
Place the most common daily questions one step away.
Person tabs show only the selected person’s totals and meals.
Prevent a shared meal record from becoming a mixed personal record.
Day, Food, and Progress place previous, next, calendar, and Today controls in the same position.
Let users change dates without relearning each section.
The visible dashboard stays read-only. Protected agent and back-office routes handle imports and writes.
Keep everyday review simple while limiting sensitive actions.
Product proof
The current date leads movement, status, and any urgent review cue.
Totals, meals, and the selected person stay together during date changes.
The same arrows, calendar, and Today action support comparison over time.
Result
The production product uses the approved Day, Food, and Progress structure.
The visible dashboard stays read-only while private routes manage data changes.
Track date changes, review cues, corrections, and repeat visits. Public usage results are not available.