How to track fluid and salt intake consistently

Almost nobody fails at this because they cannot drink water. They fail because the record falls apart by Thursday, and by the appointment there is nothing to show but a vague sense of having tried. This guide is about the record: how to keep one that is accurate, takes seconds a day, and survives the weeks when everything else slips.

This guide is about tracking, not about what to consume. How much you should drink, and whether adding salt is appropriate for you, is a clinical decision. Fluid and sodium intake interacts with blood pressure, kidney and heart conditions and several medications, and more is not automatically better for anyone. If a clinician has asked you to increase fluids or salt, this is how to actually keep track of it. If nobody has asked you to, do not start because of a website — ask first, then come back and track what you were told.

Start by writing down what you were actually asked

Before the first glass, record the instruction itself: the exact wording, the date, and who gave it. “Increase your fluids” and “aim for a specific daily volume” are different instructions and produce different logs. If the advice was vague, that is worth capturing too — it is a reasonable thing to ask about at the next appointment, and it stops you quietly inventing a target of your own.

This single line at the top of your log does a lot of work later. It tells a clinician reading the record what you were tracking against, and it stops the target drifting upward over months the way self-set numbers tend to.

Pick one unit and one vessel, and stop deciding

The most common reason intake logs are wrong is not laziness, it is arithmetic. A day made of a mug, a can, a sports bottle, two sips from someone else's glass and a cup of tea requires you to convert five things into a total, in your head, while feeling unwell.

So remove the conversion. Choose one unit — millilitres, ounces, whatever your clinician used — and measure your normal glass or bottle exactly once with a measuring jug. Now you know what one refill is worth, and every entry for the rest of the year is a tally mark rather than a calculation. Two bottles and a mug is a thing you can count while lying down. “About two litres, I think” is not.

If you use more than one vessel, calibrate each one once and write the numbers on a sticky note in the kitchen. Ten minutes, once, and the estimation problem is gone permanently.

Log at the moment, not at the end of the day

Evening reconstruction feels efficient and is reliably wrong. People remember drinks that were events — the morning coffee, the bottle they carried around — and forget the half-glass at the sink. Worse, the error is not random: retrospective logs tend to round toward the number you were hoping for.

The fix is to make the entry cost less than the guilt of skipping it. One tap, one tally mark, as the drink is finished. If logging takes longer than fifteen seconds, the system is too heavy and it will not survive a flare.

Salt is the harder half. Count sources, not milligrams

Fluid is easy to count because it comes in containers. Salt does not. It is spread across cooking, bread, sauces, snacks and anything prepared, and the numbers on packaging are per serving, in units that vary by country, sometimes as sodium and sometimes as salt. Trying to reach a milligram total by mental addition is how tracking dies in week two.

Unless you have been given a specific numeric target — in which case track exactly that, using package labels and nothing else — count salt events instead. A salt sachet. A cup of broth. An electrolyte drink. A deliberately salted snack. Three ticks in a day is a real, checkable fact about your day. An estimate of 4,300 mg is a fiction with decimal places.

Two rules keep the tally honest. Count only the deliberate additions, not background salt in ordinary meals, and define each tick once and never redefine it. Consistency between your Tuesdays matters more than precision within any one of them, because the whole value of the record is comparison over time.

Anchor the habit to something that already happens

A new habit floating in an empty schedule fails. One tied to a fixed event survives. Use the four points that happen anyway: waking, each meal, and bed.

On waking — the first entry of the day, before the day gets a chance to start.
At each meal — you are already sitting down, already holding a drink.
At bedtime — a ten-second close-out: is the number right, and if not, why not.

Keep one visible container as the day's marker. A bottle on the desk that you refill and count beats a mug you wash between uses, because you can see the state of the day without opening anything. Visibility is a real mechanism, not a productivity slogan — brain fog makes invisible progress impossible to reconstruct.

The five things that break it

The all-or-nothing collapse. One missed day becomes three, then the log is abandoned because it is “ruined”. A record with holes in it is still useful. A record you deleted is not. The rule that saves it: never miss twice.

Weekends and travel. Routines are built on weekday scaffolding and Saturday knocks it over. Decide in advance what the weekend version looks like — even if it is just the bedtime close-out.

Illness and flares. Exactly when the data matters most, you have the least capacity to record it. Keep a fallback mode: one number, once a day, nothing else. Something beats nothing by a wide margin.

Logging only the good days. This is the quiet one. If you skip entries on the days you fell short, the record says you did well every day you bothered to write, which is worse than useless at an appointment.

Over-engineering. Colour-coded spreadsheets with six fields per drink last about a fortnight. Track the smallest number of things you can defend, and let the rest go.

Review weekly, not daily

Daily numbers bounce around for reasons that have nothing to do with anything: heat, sleep, a long errand, a bad night. Looking at a single day invites you to draw conclusions from noise. Once a week, look at the run instead — how many days landed near the target, which days did not, and whether there is a shape to the misses. Weekends? The days after a big outing? That shape is the useful finding, and it is the kind of thing worth raising at an appointment.

Do not go looking for a relationship between your intake and how you felt. Days influence each other, symptoms lag, and a self-kept log is exactly the kind of dataset in which people find patterns that are not there. Record it, describe it, and let a clinician who knows your history do the interpreting.

What to bring to an appointment

Not thirty screenshots. A single page: what you were asked to do, how many days out of the last month landed near it, what the low days had in common, and any specific question that came out of it. If you are also running stand tests at home, keeping the intake log on the same timeline is worth the small extra effort, because it makes the tests interpretable rather than free-floating.