The vet calls on a Tuesday afternoon to confirm an appointment, and asks when your dog last had the booster. You have absolutely no idea. The receipt is somewhere — a folder, an email, a portal you set up once and forgot the login for. You guess wrong, the vet pulls up their record (which only goes back to when you switched practices), and now you're rebuilding history from memory.
Most pet owners run into this version of the same problem. The information exists across a vet portal, a couple of receipts, an email or two, and the part of your brain that's stretched thin. There's nothing structurally hard about pet records, but the moment you actually need one, it's never where you'd think.
A vault that holds one page tree per pet — with vet records, feeding details, training notes, and a daily log — fixes most of it. The agent does the searching when something comes up. (Veterinarians on the other side of these visits use the same shape — see AI Notes for Veterinarians: Patient Records and Client Communication.)
One page per pet, with everything underneath
In Docapybara, each pet gets a parent page. Pages nest with no depth limit, OneNote-style, so a pet's page can have child pages for Vet, Medications, Feeding, Training, Daily log, and Gear. The agent treats this whole nested structure as one searchable pile.
If you have multiple pets, you can group them under a Pets parent page, with one child per animal. Each pet keeps its own history; the agent can answer questions across all of them when needed.
Vet records that survive between practices
The single most useful page is the vet records page. The vet portal works fine until you switch vets, move cities, or the practice changes software. Then your history is fragmented across systems you can't easily search.
Drop every after-visit summary on a Vet page as a child page, dated. Most vets will email a summary or hand you a printout. Both can land on the page — paste the email, drop the PDF. Docapybara converts uploaded PDFs to markdown automatically, so the agent can actually read them and pull specific information later. "When was the last rabies booster?" The answer comes back with the date and which document it came from.
Audio recording handles the visit itself if you want to capture the conversation. Tap record (with the vet's permission), and you get a transcript with speaker labels — so you can review exactly what the vet said about the lump on the leg, instead of trying to recall it three weeks later. The transcript is searchable like any other note.
After the visit, ask the agent: "Summarize today's vet visit — diagnosis if any, what treatment was prescribed, when's the follow-up, what to watch for." You get a clean summary on top of the full transcript. The next time something related comes up, you can search for it instead of relying on memory.
Medications, dosages, and the schedule
Pets on chronic medication need careful tracking. Names, doses, frequency, prescribing vet, refill dates, response to the medication, side effects. Lose track of any of this and the vet visit gets harder.
An inline database inside the Medications page handles it. The :::database::: directive lets a small spreadsheet live alongside the prose. Columns for medication name, dose, schedule, prescribing vet, last refill, next refill due, and notes.
The agent can update it. "Add the new joint supplement Dr. Park prescribed today — name [X], dose half a chew daily, refill due in 60 days." Row appears. When you're at the pet supply store wondering whether you need another bag, ask the agent and you've got the dose, the schedule, and the refill date.
For pets on multiple medications, ask the agent for the daily schedule any time you need it: "What does my dog get and when, on a typical weekday?" Useful if you're explaining the routine to a sitter or a family member who's covering for you. The same shape scales up if you're tracking medication for a person — see Caregiver Notes: Medications, Appointments, and the Care Plan in One Place.
Feeding details, allergies, and what works
Feeding starts simple and accumulates complexity. The food you actually use, the brand changes when something gets discontinued, the treats they tolerate versus the ones that cause problems, the rotation you've worked out, the amount that maintains weight.
A Feeding page can hold prose about the current routine and an inline database tracking what you've fed and how it's gone. For pets with food sensitivities, this page becomes important — when an allergy or intolerance shows up, the vet will want a history of what you've been feeding and when symptoms started.
The agent can pull patterns. "Did the digestive issues last spring start after we switched to the new bag of food?" It reads across the daily log and the feeding page and gives you the chronology. That's a real diagnostic question that's hard to answer without an organized record.
For raw or homemade feeders, the page can hold the recipes, the rationale, and the supplier list. PDFs of nutrition guides can drop on the same page and become searchable.
Training, behavior, and what's working
A training page is genuinely useful for the months you're working on a specific behavior. What you tried, what worked, what made it worse, what the trainer suggested.
Voice capture is helpful here because training tends to happen in moments where typing is awkward — you're at the park, you're mid-walk, your hands are full of treats. Tap record, talk for thirty seconds, get a transcript. "At the park, tried the new recall cue with the long line. Worked twice, third time he saw a squirrel and forgot everything." The transcript lands on the training page with a timestamp.
The agent can summarize progress over time. "Look at the last month of training notes for the recall and tell me if anything's actually improving." You get a summary that's based on the actual notes, not your impression of how it's going.
For dogs working with a trainer, the Training page can hold the trainer's notes, your homework between sessions, and a record of what you've tried. The trainer can be added to the conversation by giving them the page link, if your training service supports that kind of collaboration. (Docapybara is single-user — see the note on collaboration below — but you can export pages or summaries to share.)
A daily log that helps when something's off
A Daily log with one entry per day (or one entry per notable thing) becomes invaluable when something changes — your pet starts limping, eating less, sleeping more, drinking more water. The vet's first question is "how long has this been going on?" and most owners can't answer with confidence.
Voice is the right tool. "Buddy didn't finish his dinner tonight. Second time this week. Otherwise seems normal." Thirty seconds, the note's in. When the appetite issue eventually warrants a vet visit, the log gives you a clear timeline. "It started about two weeks ago, mostly at dinner, no vomiting." That's the kind of detail that helps a vet diagnose.
The agent can pull the timeline. "When did the appetite issues start, and what's the pattern over the past month?" The chronology comes back, grounded in your actual notes.
Gear, food brands, and the recommendations you got
Pet owners accumulate recommendations. The good food brand from the breeder. The harness that finally worked. The boarding place a friend swears by. The trainer who specializes in your dog's specific issue.
A Gear & recommendations page holds these. An inline database with name, type (food/equipment/service), source of recommendation, status (using, considered, tried-and-rejected), and notes. The agent can pull the right list when you need it. "What boarding places have I been told about, and which ones have I tried?"
For products you're researching, the agent's web_search tool can pull current reviews. "Find what current reviewers say about [harness model] for medium-sized dogs." Comes back with sources. Saves the research time when you're trying to decide whether to spend on something.
Two related uses of the vault are worth a mention: a sitter packet and an emergency-contact page. For a sitter, a single child page called Sitter info with the routine, the food amounts, the medications, the vet's contact info, where the leashes live, what's normal versus what's a red flag. You can ask the agent to generate this from your existing pages: "Generate a one-page sitter brief for this week — routine, food, meds, what to watch for, vet contact." You get a clean handout you can text or print. For the more sober case — what happens to your pets if something happens to you — keep an Emergency page with vet info, the names and contact info of people who've agreed to take or care for the pet, any specific instructions about behavior or medications. Hopefully nobody ever needs to read it. If they do, it's there. (For the broader version of "leave a clear record for the people who'll need it," Estate Planning and Will Preparation covers that.)
A starter shape that works on day one
If you're moving from "everything in my head" to a vault, this is what we'd suggest starting with. Per pet:
- Vet — one parent page, one child per visit. Drop summaries and PDFs.
- Medications — one page with an inline database. The agent updates it.
- Feeding — one page with the routine and any sensitivities.
- Training — one page if you're working on a behavior. Otherwise skip.
- Daily log — one page, voice notes when something's notable.
- Gear & recommendations — what you have and what's been recommended.
That's six pages per pet. Nothing colour-coded, no template required. The vault grows the way the pet's life does.
The point isn't to turn pet ownership into a record-keeping project. It's that the small amount of structure you keep means the next vet visit is easier, the next sitter has what they need, and the patterns you'd otherwise miss are findable when they matter.
Try Docapybara free — start with the vet page and the daily log, and the next time the vet asks when something happened, the answer will be right there.