PlanRhythm follows the whole working loop: build the plan, see what happened, review the week, keep the conversation and clinical record together, then handle the package and payment. This page explains each part, what it does, and where we have deliberately chosen not to do something.
PlanRhythm is a new product, still being built. Everything below describes what we are building and how it behaves. On a demo call we will show you what is working today and tell you plainly what is not — we would rather lose the sale than describe a screen that does not exist yet.
Plans
Build the week in a grid. Publish it once.
Seven days across, her meal slots down. You fill the cells — early morning, breakfast, mid-morning, lunch, evening, dinner — and see the whole week at a glance instead of scrolling a document. Copy Monday into Wednesday. Save the week as a template and the next client of the same type takes minutes, not an evening.
Household measures
1 katori dal. 2 roti. A cup of oats. A slice of toast. A piece of fruit. A handful of almonds. Your client does not own a kitchen scale and is not going to buy one, so the plan speaks in whatever is already on her shelf — and you write the measures your clients use, wherever they are.
Versions, not overwrites
Change the plan in week four and week three does not disappear. Each published version is kept, dated, and readable later — so when she says "the earlier one suited me better", you can both look at the earlier one.
Published, not sent
You publish the week and it appears in her app. There is no PDF to attach, no file name with a v2 in it, and no doubt about which copy is the current one. The current one is the one she can see.
A day at a time on her side
You work in the week. She reads the day. A seven-day sheet is a lot to hold at breakfast, and most of it is not relevant until Thursday.
A plan that lives in one place can be wrong. A plan that lives in a Word file, a PDF and a chat photo is wrong in three ways at once, and you find out which one she was following only when it matters.
Why we made the published plan the only copy
The client's day
She opens the app and sees today, not a document.
Today's meals in order, with the measures you wrote. The week strip sits above for context, so she knows where she is without being handed the whole plan. Tapping a meal is how she checks in — it is the same screen, not a separate form she has to remember to fill.
No password. She signs in with a one-time code. Nothing to forget, nothing to reset, no support call to you at 9pm about a login.
Works without signal. On a train, in a basement, in a town with one bar — the day still opens and her check-in still saves. It syncs when the network comes back.
English, Hindi and Tamil today. She reads her day in the language she thinks in, and Devanagari and Tamil render properly rather than as boxes. Arabic with a right-to-left layout is what we are building next; European languages come after that. We will not list a language here before it ships.
Tuesday, 12 August
MTWTFSS
7:00
Warm water, 2 glasses
Done
8:30
Poha with peanuts
1 katori · with curd
Adapted
13:30
Roti, dal, sabzi, salad
2 roti · 1 katori dal
16:00
Chana chaat
Tap to check in
This day belongs to a client in Toronto. Her counterpart in Dubai opens machboos and dates, the one in Manchester a jacket potato, and the one in Sydney toast and eggs. Same screen, her food, her measures.
Check-ins
Honest answers, without a grade.
A tick and a cross throw away the only thing you needed. "She swapped the roti for one bhakri" and "she ate something entirely different" should not collapse into the same answer. Each check-in records what actually happened, in neutral language.
Followed the plan
She ate what you wrote. Nothing to discuss — which is itself worth knowing, because it tells you the plan fits her day.
Adapted it
Same intention, workable substitution. Bhakri instead of roti. Rye instead of white bread. Yoghurt instead of buttermilk. Usually a sign the plan is nearly right and needs one adjustment.
Ate something different
A wedding, a client lunch, her mother-in-law's kitchen. This stands on its own rather than being tucked inside “adapted”. An optional note records what she ate and why.
Couldn't do it
The ingredient was not at home, the cook did not come, the meeting ran to three. A logistics problem, not a motivation problem — and it has a different fix.
Skipped
She chose not to eat it. Sometimes appetite, sometimes a fast — Ramadan, Lent, Navratri, Ekadashi — sometimes the meal was simply too much. Worth a question, not a reprimand.
Not recorded
She did not open the app. That is all it means. It is never counted as a failure, never coloured as one, and never rolled into a number about her.
There is no adherence score in PlanRhythm. No grade, no streak, no red day, no percentage next to her name. A person who is failing a scoreboard stops opening the app, and then you lose the information as well as the client.
A product rule we will not trade away, for any customer, at any price
Patient weekly review
The week becomes facts you can discuss.
A useful review answers “what happened?” before anyone asks “how did you do?”. PlanRhythm keeps the counts separate, carries the client's own context forward, and leaves the clinical interpretation to you.
Counts, not a percentage. Followed, adapted, different, could not do, skipped and not recorded remain visible as different facts.
Context beside the pattern. The restaurant meal and the missed lunch stay attached to the days they happened.
No red week. There is no grade, streak or verdict for the patient to fail.
Weekly review · 5–11 August
Meera's week
Meal check-ins and the notes attached to them
Ready to review
26meal check-ins recorded
No adherence score By design
Followed the plan15
Adapted it6
Ate something different3
Couldn't do it1
Skipped1
Wednesday lunch · Ate something different Team lunch at a restaurant; added a photo and one-line note.
Friday dinner · Couldn't do it Reached home late and did not have the ingredients.
Logging & progress
Let her answer in whatever form is easiest at the time.
The client who types a paragraph and the client who sends a photo of her plate are giving you the same information. Both should take ten seconds.
A photo
The plate as it was served. Attached to that meal on that day, so you are not asking her which lunch the picture was.
A voice note
Faster than typing, and much easier for a client who would rather speak in her own language than fight a keyboard in her second one.
A line of text
"Had the poha but no curd, stomach was off." One sentence often explains a whole week of numbers.
Things that do not belong to a meal
Water, sleep, stress and Bristol stool type are logged whenever they happen — no scheduled slot, no reminder nagging her at a fixed hour. If she drinks four glasses before noon, she records four glasses before noon.
These sit alongside the meal check-ins on the same day, so you read one day, not four separate trackers.
Progress drawn in neutral ink
Charts over time, in one colour, on a plain grid. No green zone, no red zone, no line that turns angry when she is above it. The shape of the trend is the information; the colouring would only be a verdict.
You read the chart with her, in the consultation, where the context lives. That is where a number becomes a conversation.
Messages
One thread per client, attached to her record.
Two-way messages with attachments — a lab report, a photo of a food label, a revised list. It sits with her plan, her check-ins and her notes, so six months later the answer you gave is still findable.
What this replaces
The search through three months of chat for the PDF of her thyroid report. The forwarded message you cannot place. The "which client sent this?" moment at 11pm.
What it does not replace
WhatsApp. Your clients live there and that is not a fight worth picking. Keep the chatter where it is easy and keep the things that must survive — reports, instructions, decisions — on the record here.
Consultation notes
A note you wrote a year ago still says what it said.
Write the consultation note, then lock it. After the lock, the note is fixed. If you need to add or correct something, you write an amendment and the amendment is visible as an amendment, with its own date — the original text stays legible underneath.
This is ordinary clinical hygiene, and it is also self-protection. A record that can be quietly edited is a record nobody can rely on, including you.
Lock when you are done
An unlocked note is a draft. A locked one is the record of that consultation.
A revision trail
Every amendment carries who wrote it and when. Nothing changes silently.
In front of you at the next visit
Her last note, her recent check-ins and her current plan on one screen before she sits down.
Intake
The first twenty questions, answered before she arrives.
She fills the intake questionnaire on her phone at her own pace — history, medication, allergies, what her kitchen actually cooks, what she will not eat. You start the first consultation with the answers already in front of you instead of spending fifteen minutes writing them down.
Before
Filled at her convenience
Between two things, on the way home, at whatever hour suits her. Partly done is fine; she can come back to it.
Flagged
A review queue
Answers you have marked as needing a look — a medication, a condition, a pregnancy — land in a queue instead of sitting quietly in a form nobody reopened.
After
Part of the record
What she told you at intake stays attached to her file, next to the notes and the plans, rather than in a form-filling tool you stopped paying for.
Food library & diets
Your foods, tagged the way your practice thinks.
A food library you build up as you work, in the items your clients actually eat and the measures they actually use. Every food carries diet tags, and the tags are yours to define — not a fixed list written by somebody who has never had to plan around Ramadan, Lent, Navratri or a kosher kitchen.
Built once, used everywhere
Add khichdi, or machboos, or overnight oats, with your own portion the first time you use it. It is there, in your measures, for every plan after that — including the ones your staff build.
Diet tags you define
Halal, kosher, vegetarian, vegan, eggetarian, Jain, gluten-free, no onion or garlic, no root vegetables, fasting-day safe — whatever your practice needs, named the way your practice names it. We ship no fixed list, because a fixed list is always somebody else's list. Tag a plan and the library shows you what fits.
Software built elsewhere gives your Jain client, or your halal client, or your coeliac client, a dropdown with "vegetarian" and "vegan" in it and calls the job done. She then spends the next six weeks working out for herself which half of the plan she can eat.
Why the tags are yours and not ours
Conditions & specialisms
The areas of practice the tool serves.
Your clients sit down with you for many different reasons. PlanRhythm's engine — the plan, the daily check-in, the logging, the messages and the notes — is condition-neutral: it supports the daily routine and the conversation the same way whichever reason brought a client in. The condition itself is recorded on her intake and stays on her record. What follows is the areas of practice the tool serves, grouped honestly, because they are not all served in the same way.
Everyday nutrition and lifestyle
The core fit. A published plan, a daily routine, a neutral check-in and a shared thread cover most of what this work asks for.
Obesity and weight lossPortion controlMindful eatingHabit changeVegetarian dietsDigestive disordersFatigue and stressMenopause and women's healthPregnancy and lactationBariatric surgery support
Metabolic and clinical, with structured logging
Here the client logs the readings that matter — glucose, blood pressure, lipids and the rest — against the day they were taken, and her lab results and medications live on her record beside them. The plan and the routine work as they do everywhere else; the difference is that the numbers your care depends on are written down rather than remembered. PlanRhythm records and organises those readings. It does not diagnose, and there is no disease-specific module behind any name in this list.
This is where PlanRhythm's design earns its place. The record never scores, grades or ranks a client, never shows her a red day, and never puts a calorie total in front of her as a verdict. Nothing on her screen tells her she has failed, because there is nothing built to. For someone whose relationship with food is already fraught, a tool that cannot shame her is not a small thing.
Care of this kind belongs with a qualified clinician. PlanRhythm is the tool that clinician works with, not the clinician.
Food allergies
A plan can carry allergen tags, and when a plan item conflicts with an allergy recorded on the client's intake, the app raises an advisory so the clash is in front of you before it reaches her. It is decision support for your judgment — a prompt to look again — not a guarantee and not a medical safety device. You decide; the advisory only makes sure the question is asked.
Pediatric nutrition
The daily routine and the check-ins work here as they do everywhere else, and a parent or carer can log on the child's behalf, so the record reflects what actually happened at the table. WHO growth-percentile charting is being built and is not yet part of the product; we will list it here when it ships, and not before. Nothing on this page implies a growth chart you cannot yet open.
Packages & payments
Packages, sessions, and the way your clients actually pay.
Set up a package — a three-month programme, a six-session block — and see what she has used and what is left. When it is nearly finished you know before the renewal conversation, not after it. Prices carry local taxes where they apply, GST or VAT, on the invoice rather than in your head.
Card payments across markets
Record card payments against the correct client and package wherever you practise. UPI is also live in India, including a static QR and UTR reference. Additional regional rails are not listed before they work.
The reference against the payment
She pays and sends the reference — a UPI UTR, a bank transfer reference, a card receipt number. You record it against her payment, so the receipt and the bank line match when you look them up in November.
Sessions used and left
Per client, on her record. No parallel register, no counting backwards through a chat to work out whether this was the fourth or the fifth session.
Your team & your clients' privacy
Staff see their own clients. Nobody browses the whole book.
PlanRhythm is built for practices from one person up to about twenty practitioners. As owner you see everything. Staff see only the clients assigned to them — not the rest of your list, not each other's notes, not your revenue.
Health data is governed differently in every market we sell into, so we build to the strictest version of the same four things: consent recorded and withdrawable, access logged, data exportable on request (a self-service export button is not built yet), data deletable on request. That is what the GDPR and UK GDPR in Europe, the DPDP Act in India, the PDPL in the UAE and Saudi Arabia, PIPEDA in Canada, the Australian Privacy Principles and the US state privacy laws each ask for in their own words.
PlanRhythm runs on Microsoft Azure, and your practice's data lives in the Azure region for your market — Central India, UAE North, West Europe, East US, Canada Central or Australia East. You choose it at onboarding, it is encrypted in transit and at rest, and it does not move between regions. That is the first question a corporate client or a hospital's contracts team asks, and it should have a one-line answer.
Owner and staff
Two roles that match how a practice really works. Assign a client, and only then does that dietitian see her.
Your region, and only that one
Records sit in the Azure region you chose at onboarding, encrypted in transit and at rest. They do not move between regions, and we will name the region in writing whenever a client asks.
Consent on the record
Consent was in the schema from the first table, not bolted on later — given, withdrawn, dated, and producible when somebody asks to see it.
An audit trail
Who opened which record and when. Useful the day somebody asks, and quiet every other day.
Built for how people actually eat
The local details are not a settings screen. They are the design.
A currency selector does not make software international. The plan still needs to understand household measures, a Ramadan schedule, a kosher kitchen, the foods a family actually cooks and a client with no signal on the morning train. PlanRhythm is built for practices across the US, Canada, Gulf, UK and Europe, Australia and New Zealand.
Measures she thinks in
A katori, a cup, a roti, a slice, a piece, a handful. The plan reads like something a person could cook, not a lab sheet.
Payment as it happens
Cards wherever you practise, UPI in India including the printed QR, and more local rails as we build them. Not a checkout that half your clients cannot use.
Offline by default
Her app works with no network and syncs later. A basement in Dubai and a train in Maharashtra are the same problem.
Languages, stated honestly
English, Hindi and Tamil today. Arabic with a right-to-left layout next, European languages after. Only what has shipped is listed.
Twenty minutes, screen shared, your questions. If it is not right for your practice we will say so — we would rather you stayed on your spreadsheet than paid for something that does not fit.