Describe what you want to track each day, from meals and portions to hunger, energy, digestion, and other symptoms. Makeform turns your instructions into a repeatable daily food log that a dietitian, coach, or individual can adjust before sharing.
Route daily entries to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose the closest daily food log, edit the prompt, or send it to the Makeform builder. The field structure is an example you can tailor.
Audience
Clients recording meals between appointments
Format
One daily check-in with repeatable meal sections
Prompt size
446 chars
Example form structure
One daily check-in with repeatable meal sections
Date, wake time, and sleep time
Meal time, foods, drinks, and portion
Hunger before and fullness after
Energy, digestion, or other symptoms
Anything your dietitian should review?
Suggested routing tags
Daily entries
Coach review
Follow-up needed
Ask for meal time, portion description, and symptoms on the same entry. That shared timeline makes later review much clearer than separate lists.
Step 1
Record
meals, drinks, portions, and times
Step 2
Add context
hunger, symptoms, sleep, and activity
Step 3
Submit
one consistent entry for the day
Step 4
Review
filter entries and discuss observed patterns
Why structure matters
A list of foods cannot show when a meal happened, how much was eaten, or what else was going on. A structured daily food log keeps those details together without asking the writer to invent a format each day.
Required dates and repeatable meal prompts prevent entries from switching between detailed notes one day and an unlabeled photo the next. Consistent fields make side-by-side review practical.
Conditional logic can reveal symptom timing and intensity after someone answers yes, or open preparation details for a home-cooked meal, keeping routine entries shorter.
Meal time, symptom start time, and submission date create an ordered record. Reviewers can compare observations while avoiding claims that one event caused another.
Choose your logging style
A detailed dietitian record and a two-minute personal diary should not feel identical. Start with the purpose, then choose how much structure the daily routine can support.
Use structured meal sections, portion descriptions, hunger and fullness scales, symptom details, and a field that flags questions for the next appointment.
Connect food entries with agreed routines, barriers, wins, and a conditional follow-up request so a coach knows which submissions need a response.
Keep the date required and make richer details optional. Plain-language portions and optional photos reduce friction when precision is not the point.
Place time, intensity, duration, and context beside the meal timeline. The form documents what was noticed; it should not label a diagnosis or claim a cause.
Build the daily routine
Begin with the questions that will actually be reviewed, test the form on a phone, and give each day a clear beginning and end.
Tell Makeform who will complete the log, who will read it, whether entries are daily or per meal, and which details matter. Name specific fields instead of asking for a generic nutrition form.
Choose fixed breakfast, lunch, dinner, and snack sections or a shorter repeatable meal pattern. Set the date as required, define scale labels, and make sensitive context optional when it is not essential.
Complete the log on the device participants will use. Check that portions allow everyday descriptions, symptom follow-ups stay hidden when irrelevant, and the full routine is manageable.
Publish the link, explain when to submit, and route responses to the right reviewer or spreadsheet. Use client identifiers and dates consistently so multiple days stay easy to sort.
Pick a format
The best format is the one a person can complete consistently and a reviewer can understand later. A generated form balances a guided entry experience with structured submissions.
Field guide
Start with the details that serve the review goal. Six compact sections usually produce a clearer record than one large box asking someone to describe everything they ate.
Day & identity
A date is the minimum anchor. In a professional workflow, add the client identifier the reviewer already uses, while avoiding extra personal data that has no purpose in the review.
Meals & drinks
Give breakfast, lunch, dinner, snacks, and drinks recognizable places. If fixed meal names do not suit the audience, use meal one, meal two, and additional snack prompts with time fields.
Portions
Not every participant weighs food. Accept practical descriptions such as one bowl, half a sandwich, one handful, or a package size, and provide a separate unit field when numeric amounts are expected.
Hunger & fullness
A number without endpoints is hard to compare. Define what the lowest and highest choices mean, keep the same scale each day, and ask at a specific moment such as immediately before and after a meal.
Symptoms & context
If symptoms are in scope, ask what happened, when it began, how strong it felt, and how long it lasted. Also capture relevant context selected by the form owner, without implying that a food caused the observation.
Reflection & routing
A brief reflection lets the writer preserve circumstances that fixed fields miss. For coached or dietitian-led logs, add a clear way to request follow-up rather than expecting the reviewer to infer urgency from notes.
Related tools
Pair food entries with a suitable intake, wellness check-in, dietary request, or program form while keeping each workflow focused on its own purpose.
Collect starting context and goals once, before asking someone to submit repeated daily entries.
Open toolPrepare for a consultation with structured questions that do not belong in every daily log.
Open toolCollect dietary requests for an event, program, or service in a dedicated workflow.
Open toolRegister participants and collect program preferences before recurring check-ins begin.
Open toolCreate a broader self-reported questionnaire when a daily meal timeline is too narrow.
Open toolUse a separate ordering form when the task is selecting meals rather than recording them afterward.
Open toolFAQ
Practical answers for dietitians, coaches, and individuals setting up a repeatable food diary.
A useful starting set is the date, meal or snack time, foods and drinks, portion description, and optional context such as hunger before, fullness after, energy, or symptoms. A dietitian or coach may also add client identification, agreed routines, questions for follow-up, and a short end-of-day reflection. Include only fields that someone plans to review; unnecessary detail makes a daily routine harder to maintain.
Use one daily submission when the writer can reliably return at the end of the day and the reviewer wants a complete day in one record. Use one submission per meal when timing needs to be captured close to the event or when a long daily form would be inconvenient. State the expected rhythm beside the form link, and keep identifiers and dates consistent so entries remain sortable.
Allow everyday descriptions such as one bowl, two slices, half a plate, one handful, or the package size. You can offer an optional amount and unit field for people who know it, but do not force false precision. Add a brief example in the field description so different participants understand the level of detail you expect.
Yes. Ask first whether a symptom occurred, then conditionally show fields for the symptom, start time, intensity with labeled endpoints, duration, and notes. Keeping these observations beside meal times creates a useful timeline for discussion. The log should record what the person noticed without diagnosing a condition or claiming that a particular food caused the symptom.
Yes. Add an optional file upload to each meal section or one upload area at the end of the day. Pair photos with written fields for time and portion context because an image alone may not show ingredients, amounts, drinks, or what was eaten. Explain whether photos are optional and who will review them before you share the form.
Require only the date and the few fields central to your purpose. Use checkboxes and labeled scales for common answers, hide symptom details until they apply, and reserve long-answer prompts for information that cannot be captured another way. Test a realistic day on a phone and remove questions that will not change a later conversation or decision.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses with your daily food log. The paid tier removes the Makeform badge; it does not unlock continued form use after a limited trial or response allowance.
Use the same client identifier and date fields on every entry, then send submissions to a consistent inbox or connected spreadsheet. Add a yes-or-no follow-up request and routing tags for entries that need attention. During review, compare recorded observations and circumstances, and avoid treating a repeated sequence as proof that one item caused an outcome.
Turn scattered notes into a consistent daily routine.
