Logging Best Practices
Write better garden logs that help you plan smarter next season — what to record, when to log, and how the AI uses your notes.
Your logs are the most valuable data in MyVeggieGarden. They're what the AI reads when generating suggestions, and they're what you'll be grateful for when planning next year's garden. Here's how to make them count.
What makes a good log entry
The best log entries answer "what would future-me want to know?"
Great notes
- "Transplanted 6 Cherokee Purple seedlings, about 8 inches tall. Soil temp 62F. Overcast, light rain expected tonight."
- "Powdery mildew on lower zucchini leaves. Removed affected leaves and sprayed neem oil. Third year in a row — try a resistant variety next year?"
- "First ripe tomato! 73 days from transplant. Smaller than expected — maybe needed more calcium."
- "Harvested 4 lbs of green beans. Plants still producing. Best yield from this bed ever."
Less useful notes
- "Looks good" — Good how? Compared to what?
- "Watered" — Unless there's context (drought, new transplants), this doesn't help future planning
- "Planted" — The milestone already records this. What were the conditions?
When to log
You don't need to log every day. Focus on moments that matter:
| When | What to capture |
|---|---|
| Planting/transplanting | Conditions, plant size, soil temp, weather |
| First observations | Germination, true leaves, flowers, fruit — these are milestones |
| Problems | Pests, disease, weather damage, nutrient deficiency — early is better |
| Harvests | Quantity, quality, taste notes |
| Weather events | Late frost, heat wave, heavy rain — things that affect plants |
| Actions taken | Fertilizing, pruning, pest treatment — what you did and why |
Use status sparingly but honestly
Status (Good, Fair, Poor) is a quick health snapshot. Use it to flag trends:
- Good — Thriving, on track. No action needed.
- Fair — Needs attention. Something's not quite right.
- Poor — In trouble. May not recover.
Don't inflate status. A plant you're worried about should be "Fair" or "Poor" — that's what helps the AI suggest "Try differently" during season review.
Tag milestones when they happen
When you observe a lifecycle milestone (germinated, flowering, first fruit), tag it in your log. This builds timeline data the app uses to:
- Predict future timelines ("Cherokee Purple typically flowers 6 weeks after transplant in your garden")
- Compare year over year ("You planted 10 days earlier this year")
- Adjust task timing for next season
Include quantities when possible
Numbers make logs dramatically more useful for future planning:
- "Harvested 4 lbs" vs. "Harvested some"
- "3 of 6 seeds germinated" vs. "Some germinated"
- "Plants are 18 inches tall" vs. "Plants are growing"
- "92F today, plants wilting by 2pm" vs. "Hot day"
Note the negative
Failed experiments are as valuable as successes:
- "Direct-sowed lettuce in July — bolted within 2 weeks. Too hot. Start indoors next year."
- "Planted too close together, couldn't harvest without stepping on other plants."
- "Straw mulch attracted slugs. Try landscape fabric next year."
These notes are exactly what the "Try differently" decision is made from during season review.
How the AI uses your logs
During season planning, the AI reads your log history to:
- Surface problems — Recurring issues get flagged ("Powdery mildew noted 3 times on zucchini")
- Suggest decisions — Plants with consistently poor status get "Try differently" or "No" suggestions
- Inform timing — Your actual milestone dates help predict better schedules
- Generate context — Planning notes include your observations, not just generic advice
The more specific your notes, the more useful the AI's suggestions become.
Frequently asked questions
Do I really need to include numbers in my logs?
They're the single biggest upgrade. "Harvested 4 lbs" lets you compare years. "Harvested some" doesn't. "3 of 6 germinated" tells you to plant more next time. Even rough numbers are better than none.
Is "looks good" a useful log entry?
Not really. A Good/Fair/Poor status rating captures the same information in one click. Save your words for context: what the plant looks like, what the conditions are, what you did and why. That's what helps future-you plan.
Why does the AI care about how I write my notes?
The AI reads your actual words to find patterns — recurring pests, timing correlations, zone-specific problems. "Spotted aphids on lower basil leaves" gives it a date and severity to work with. "Bug problems" doesn't. The more specific your notes, the better the suggestions during season review.
Related
- Tracking and logging — How the logging system works
- Milestones — Lifecycle phases to tag in logs
- End-of-season review — How logs inform season reflection