Why I stopped using spreadsheets and what actually works now
I spent about four years tracking every meal in a Google Sheet before I realized I was spending more time formatting cells than thinking about what I was eating. The breakthrough came when I switched to GoodNotes and built a system that actually fit into my daily routine instead of fighting it. This is how I set it up and what went wrong along the way. The first thing you need to understand is that GoodNotes is not a spreadsheet. It's a digital notebook that responds to pen input, and that changes everything about how you approach tracking. I started by importing a basic food log template from the GoodNotes library, then I spent about three days modifying it until it felt like something I'd actually want to open at the end of every meal. What I ended up with was a five-page spread: one page for daily intake with quick checkbox categories (protein, vegetables, carbs, fats), one page for weekly weight trends with a hand-drawn line graph, one page for workout logs cross-referenced with nutrition, one page for meal prep planning, and one catch-all page for notes about cravings or emotional eating patterns. The whole thing lives in a single notebook that takes about eight seconds to open from my iPad home screen.
Here's the thing nobody tells you about this approach. The pen input matters more than you think. When you handwrite your meals, you process the information differently than when you type it. I noticed this around month two of using the system. My recall of what I ate improved dramatically because the physical act of writing "chicken breast with sweet potato" creates a different memory trace than tapping those words into a text field. That cognitive engagement is what makes the system stick. I use the Lasso tool constantly for rearranging items on my pages. Let me explain why that matters. Say you log dinner as pizza on Wednesday but then remember you had a second slice at midnight. Instead of crossing out half the page and rewriting, I lasso the entry, drag it to the late-night section, and add a note that says "late snack." The page stays clean and the data stays accurate. That workflow takes maybe twelve seconds compared to the erasing and redoing I used to do. My biggest frustration during setup was figuring out how to track macros without turning the journal into a spreadsheet substitute. I tried using tables with calculated fields and gave up within a week because GoodNotes doesn't do math. What actually worked was creating a separate reference page with standard serving sizes and approximate macro counts for foods I eat regularly. I keep it tucked behind the daily logging pages so I can glance at it without leaving the journal. It takes me about forty-five seconds per meal to look up portions and record estimates rather than trying to calculate exact gram counts.
There's a specific problem I ran into around week six that almost made me abandon the whole thing. I was traveling and had no internet connection, which meant I couldn't sync my work to iCloud or any cloud storage. The journal was only on my iPad at that point. I had logged about four days of food without backing up, then my iPad decided to update iOS overnight and the app crashed during startup. All four days were gone. I spent two hours reconstructing what I could remember from screenshots I'd taken incidentally while scrolling through other apps. My workaround was immediate and permanent: I now export the entire notebook as a PDF every Sunday evening and save it to a folder in Dropbox. That process takes about ninety seconds if I've been consistent with my logging throughout the week. I also keep a secondary paper notebook in my bag as a backup for travel days, but honestly the PDF export has been sufficient. I haven't lost any data since implementing that routine. One counter-intuitive insight about this system is that less detailed logging often produces better long-term adherence. I used to try recording every ingredient and preparation method. Within three weeks I was burning out and skipping days. Now I log the main components of each meal and note deviations from my usual patterns. The system rewards inconsistency detection, not forensic documentation. If I eat something outside my normal range, the gap in detail is itself data worth preserving.
Get the Full Details
Another thing beginners miss is the importance of setting up your goal pages before your tracking pages. I made the mistake of starting with food logs and trying to reverse-engineer what goals I was supposedly working toward. It felt arbitrary and directionless. Once I flipped the order and defined my target weight, body composition goals, and performance metrics on dedicated pages first, the daily logging suddenly had context. The numbers on my weight trend page started meaning something because they were tied to dates where I'd also noted training adjustments and dietary changes. Here are the real limitations of this approach. GoodNotes requires an iPad or iPhone with Apple Pencil support, which is a hardware investment. The handwriting recognition feature exists but is unreliable for food terminology, so you're committed to manual entry. Syncing across multiple devices can be sluggish if your notebooks grow beyond twenty pages with heavy annotation. And unlike dedicated nutrition apps, there's no barcode scanning or database lookup, which means portion estimation relies entirely on your own judgment or a reference guide you maintain yourself. For people who need precise macro tracking or have medical dietary requirements, I'd recommend pairing this system with an app like Cronometer for the data-heavy days and using GoodNotes for the behavioral and pattern-tracking aspects. The two approaches complement each other well. I run Cronometer on days when I'm adjusting calories for a competition prep phase and switch to GoodNotes-only when I'm in a maintenance period where awareness matters more than exact numbers.
If you want a starting template, the GoodNotes library has several free food journal layouts you can duplicate and modify. I'd suggest spending the first weekend just experimenting with page layouts rather than worrying about accurate data entry. The system only becomes useful once it feels natural to use, and that typically takes about ten to fourteen days of actual use before the friction drops to a manageable level.
