The idea is old and it is sound: write down what you eat and how you feel afterwards, and after a while the two columns start to explain each other. The reason most food and mood journals die inside a week is not the idea. It is the cost of the writing. This page is about keeping the idea and losing the cost.
We are building an app that does half of this work with a camera, so treat the enthusiasm accordingly. But the method below works on paper too, and worked on paper long before phones — it is just slower there.
What a food and mood journal is actually for
Not weight, mostly. People keep one because something keeps happening that they cannot pin down: the afternoon slump that arrives some days and not others, the evening where focus is gone by nine, a stomach that is settled all week and then suddenly is not, sleep that goes ragged after certain dinners. The suspicion is always the same — it is probably something I ate — and the journal exists to turn that suspicion into something you can look at.
One boundary before anything else: a journal is a record, not a diagnosis. It can show you that two things keep happening near each other. It cannot tell you why, and a pattern in a diary is not a food intolerance. If you suspect a real allergy or you are unwell, that is a conversation with a professional, and no notebook — paper or software — replaces it.
Why the paper version dies
Do the arithmetic that the enthusiastic first entry never does. Three meals a day, each wanting the food written down, the time, and a feeling noted a few hours later — that is six or more writing moments every day, indefinitely, most of which record a day that was exactly like yesterday. The signal you are hunting lives in a minority of meals: the unusual ones. The routine ones mostly add pages.
What to write down
The meal, with the least effort available
A photograph is enough, and it is better than prose — it remembers the portion, the sauce and the sides without you describing them. On paper: name the meal and the one thing unusual about it.
A few hours later, one line about how it sat
Pick one or two axes and keep them stable: energy, mood, digestion, fullness. A single word does it — even, low, settled, off. The gap matters: right after eating, everything reads as fine. Two to three hours later is where the information is.
Your own words for anything that stood out
The prewritten scales are for counting. The margin note — “the kind of tired where reading is hard” — is what you will actually recognise a month later. Write it the way you would say it.
Once a week, read for pairs
Look for things that keep landing near each other: fried and a slow next morning, the second coffee and the three-o’clock dip, the late dinner and shallow sleep. You are counting co-occurrences, not proving causes.
What a real pattern looks like
Smaller and more boring than the internet suggests. You will probably not discover a dramatic intolerance. You will discover that one café’s coffee sits fine and another’s does not, that portion size moves your evening more than ingredients do, that the difference between a good and a bad Thursday is mostly what Wednesday’s dinner was. Boring, specific, and yours — which is exactly what makes it usable.
Hold the finding at the strength the record supports. “Digestion read lower after fried, eight times now” is a fact about your diary. “Fried food wrecks my gut” is a theory wearing the fact’s clothes. Two entries are an anecdote; keep counting before you rearrange your eating around one.
Where Plateknow fits
Plateknow is this journal with the writing removed. The meal half is a photograph — calories and macros read from the picture, as a range, correctable in one tap. The feeling half is a twenty-second check-in that arrives a few hours after the meal and accepts one tap or your own words. Skipping it is always allowed; a skipped check-in is a quiet day, not a broken streak.
And the reading-for-pairs step is done for you, with the same restraint described above: after about twenty plates and ten check-ins, the app starts surfacing what kept landing together — “focus reads higher after coffee, before noon” — always as a count of what you recorded, never as a cause, never as an instruction to cut anything. Before that threshold it shows a counter filling up, because guessing early would be inventing patterns you have not earned yet.
Before the App Store
Get it before it is public — and tell us what to build.
Early access on TestFlight, and no charge during the beta.
Do I have to log every meal?
No, and for most people logging every meal is the reason the journal dies. Log what varies. A stable routine is its own baseline — one entry for “the usual” per week is plenty to anchor it.
How long until I see something?
Count entries, not days. A few dozen varied meals with their check-ins is usually enough for the first pair to show up. A week of identical meals tells you almost nothing — not because you failed, but because nothing varied.
Can it tell me what to stop eating?
No, by design. A diary that starts issuing instructions has become a diet app wearing a journal’s clothes. Plateknow shows you what you recorded together and lets you decide what, if anything, to do about it.
Is this a substitute for an elimination diet or an allergy test?
No. Those are structured clinical processes and belong with a professional. A journal is the thing you bring to that conversation — weeks of specific, dated observations instead of “I think it might be dairy?”