A weekly client report is more likely to be useful when it answers a small number of questions in familiar language: what was recorded, what the client wanted to discuss, and what the next agreed step is. It should be short enough to read and honest about missing entries and estimates. A one-tap approval can make the review action quick, but a fast button is only useful when the report has first been checked by the nutritionist.
Write for the client, not the dashboard
A report should help a person remember the conversation and understand the next step. It does not need to reproduce every chart, data point or internal note. Ask what the client would want to know when opening the summary after a busy day. Often, a few clear observations and one agreed action will be easier to use than a long list of metrics.
Prefer everyday phrases. “You recorded lunch on Tuesday and Thursday” is understandable. “Diary adherence was 29%” may imply a judgement and can be hard to interpret without context. If a count matters, explain what it counts and avoid suggesting that it measures the client's effort or character.
Use short paragraphs and headings that answer practical questions. Keep each point connected to an entry or a conversation the client recognises. If a report includes a detail that needs explanation, write the explanation beside it instead of assuming the client will infer its meaning.
Keep the report within the record
The report must distinguish what the diary contains from what it does not. If only a few meals were logged, say which meals are included. Do not write “this week you ate…” as if the entries cover every meal when they do not. A blank date is unknown; it should not be interpreted as a day without food or as evidence of a particular choice.
The same care applies to portions and preparation. “Two roti and dal” may be a useful client description, but roti size and dal recipe vary. If nutrition values are included, state that they are estimates. Keep the assumptions visible and avoid presenting a calculated figure as a measured fact about the client's intake.
Do not attribute a client's individual estimate to IFCT 2017 or another food-composition reference as if the source measured their home-cooked meal. A reference can inform a calculation, but the client's recipe and portion may differ. If the report cannot explain the estimate simply, consider whether that number belongs in the summary at all.
A simple structure clients can scan
A concise report can follow a repeatable sequence. The exact layout should reflect what the nutritionist and client have agreed to review, but the following structure keeps the summary grounded:
- What was recorded: the dates or meals present in the diary.
- What stood out to discuss: one or two neutral observations tied to those entries.
- What remains uncertain: gaps, approximate portions or unknown preparation details.
- What happens next: the next agreed action or question.
Avoid turning this structure into a fixed template that repeats irrelevant sections. If there was no new diary activity, do not manufacture a finding to fill the space. A short note saying there was nothing new to review may be more honest than a generic summary that implies an assessment took place.
The nutritionist review before sharing
Any report that is sent to a client should be reviewed for accuracy, tone and fit with the conversation. A quick approval control is helpful when it allows the nutritionist to inspect the actual content, make a correction, and confirm that sharing is appropriate. Approval should not be reduced to tapping through an unseen generated summary.
Before approving, check the client identity, reporting period and entries included. Confirm that the report does not treat an estimate as exact, fill gaps with assumptions, or turn observations into health or outcome promises. Read it from the client's perspective: could they understand each sentence, and would they recognise the meals being described?
If the system provides a draft, treat it as a draft. The practitioner owns the decision to share. Where the report is wrong or incomplete, edit or withhold it and follow up through the agreed method. A one-tap action should represent a real review, not pressure to approve quickly.
Choose observations that invite a conversation
Good report language is descriptive and open to correction. “You noted poha on two mornings” is grounded in the record. “You have improved your breakfast” adds a judgement and a conclusion that may not match the client's experience. “You marked Friday's lunch as uncertain” gives the client a chance to explain what they remember.
Keep recommendations within the scope of the consult and the nutritionist's professional judgement. A report should not make a promise about what will happen if the client follows a suggestion. It should state what you discussed and invite the client to raise questions. If the summary introduces an idea that was not discussed, review whether it belongs before sharing.
Reports can acknowledge effort without grading it. “Thank you for noting those meals; they give us a starting point for our next discussion” recognises the contribution. It does not imply that the client must log more or that a missing day is a failure.
Make the approval workflow responsible and practical
Decide who reviews reports and when. A solo nutritionist may check them before the next consult; a team may assign a reviewer. The action should be visible in the workflow so a draft is not mistaken for a report already shared. Keep an understandable state for drafted, reviewed and sent items if the system supports those states.
Check whether the report is going to the right client and through the communication method they expect. Avoid exposing meal details in a notification preview. If a client has asked not to receive summaries, respect that preference. The convenience of a button does not replace consent and correct recipient handling.
Review the report after it is shared if the client asks a question or points out a mismatch. Correct the record or explain the estimate in plain language. A report is part of an ongoing conversation, not the final authority on what happened.
A sample report review
Dr Meera Iyer reviews a draft summary for Priya S. The diary contains two lunch entries: one says “2–3 roti, dal,” and one says “rajma chawal.” Meera checks that the dates are right, that the report calls the first serving approximate, and that it does not describe the entries as the whole week. She shortens the wording and includes their agreed question about how Priya wants to describe portions next time.
Only after checking the content and recipient does Meera approve the summary. If Priya later says the second entry included another serving, Meera can incorporate that clarification into the next discussion. The report helps preserve a shared thread without pretending that the record was complete.
How Shellel helps
Shellel gives nutritionists a place to review a client's diary and continue the discussion around recorded meals. A report should remain grounded in those entries and any agreed next step, with estimates clearly treated as estimates. Learn how Shellel supports nutrition practices at /nutritionists. For a focused review routine, read how to review a client's week.
Quick answers
Asked and answered
How long should a weekly report be?
Long enough to capture the entries and next step that matter, and short enough for the client to scan. The right length depends on the conversation; avoid adding sections only to fill a template.
Can a one-tap approval replace reading the report?
No. Approval should follow a review of the client, dates, record coverage, estimates, wording and recipient. A quick action can simplify the final step, not remove the nutritionist's responsibility.
Should reports include nutrition totals?
Only when they are useful and can be explained with their assumptions. Nutrition numbers from meal descriptions are estimates and should not be presented as direct measurements.
