The kitchen renovation wraps up, you write the final check, and four months later a cabinet door starts to sag. You email the contractor asking about the warranty. They email back asking what brand the cabinets were and what the order date was — they install a lot of jobs, they don't remember the specifics. Now you're looking through a year of email threads, a stack of invoices, and the change-order PDF you signed at some point in the spring.
Most people doing a renovation run into this version of the problem. The information about every job — what was bought, what was decided, what changed mid-project, what the warranty covers, who said what when — exists across email threads, contractor texts, signed documents, and the part of the project where you swore you'd remember. The moment you actually need a specific record, it's never where you'd think.
A vault that holds one parent page per project, with the budget, the communication log, and the receipts, fixes most of it. The agent does the searching when something comes up.
One project page, with the structure you'll actually use
In Docapybara, each renovation project gets its own parent page. The kitchen, the bathroom, the deck, the basement finish. Pages nest with no depth limit, so each project can have child pages for Budget, Communication, Change orders, Materials, Permits, Warranties, and Daily log.
For people doing more than one project at a time (or in rolling sequence), group them under a Renovation parent page. Each project keeps its own scope; the agent searches across when you need to remember a contractor or a brand from a past job.
If the renovation overlaps with broader homeownership tracking — maintenance schedules, appliance warranties, paint colors — see AI Notes for Homeowners: Maintenance, Contractors, and Renovations for the wider shape this fits inside.
A budget that holds together as scope changes
The budget page is the workhorse. An inline database via the :::database::: directive lets a small spreadsheet live alongside the prose. Columns for line item, original estimate, actual cost, change-order amount, vendor, status (paid, pending, scheduled), and notes.
The agent can update this from voice or text. "Add a line for the upgraded faucet — $340, paid Tuesday, vendor is Plumbing Plus." Row appears. "What's the running total for the kitchen project so far, and what's still scheduled to be paid?" You get a real answer, grounded in the actual entries.
The reason this matters more than a spreadsheet is the cross-cut analysis. "What's the variance between original estimate and actual on the cabinetry line?" "Show me everything that's come in over estimate so far, and by how much." The agent reads across the database and answers, which is harder to do mid-project from a static budget document.
For projects with a tight budget where overruns matter, having the running total available on demand changes the conversation with the contractor. You're not asking "are we over?" — you have the number. For the broader pattern of comparing major options before you commit — including renovations themselves — that decision shape sits naturally alongside this one.
Change orders, captured the moment they happen
Change orders are where renovation budgets quietly fall apart. The contractor mentions in passing that the subfloor under the old tile was rotted and needs replacing — "shouldn't add too much, maybe $800" — and you nod, the work happens, and three weeks later it's a $1,400 line on the invoice. By then it's done.
A change-orders child page captures these as they're discussed, before they're invoiced. Date, what changed, who said what, the verbal estimate, whether you signed off in writing. Voice notes work well for this because the conversation usually happens in person or on the phone. "Contractor flagged subfloor rot under the old tile; says it'll add roughly $800 and a day. Verbally agreed. Asked him to follow up with a written change order before doing the work."
When the change order arrives in writing, drop the PDF on the same page. PDFs convert to markdown automatically, so the agent can read them and answer questions later. "What did the third change order on the kitchen actually cover and what did it cost?" The answer comes back with the document attached.
This shape pays off most when something disputed comes up later. The verbal agreement is captured, dated, with what was said. That's the version of the record contractors usually don't have either, and having it changes how the conversation goes.
A communication log that survives the project
Contractor communication happens across email, text, in-person conversations at the site, and phone calls. Reconstructing what was actually agreed to is hard once it's spread across four channels.
A Communication child page per project holds the substantive exchanges. Forward emails. Paste text threads. Voice notes after in-person conversations. Don't try to capture everything — the schedule emails and the "running 30 min late" texts can stay in their original channels. Capture the decisions, the design choices, the timeline commitments, the "yes do that" moments.
For longer phone calls or in-person meetings, audio recording with the contractor's permission is genuinely useful. You get a transcript with speaker labels — so a walkthrough about which way the cabinet doors should swing comes back as actually attributed conversation, not a fuzzy memory of who proposed what. The transcript stays searchable forever.
The agent can pull from this later. "What did we decide about the under-cabinet lighting — was that included in the original quote or did it get added?" The answer comes back with the exchange it came from. That's a question that's painful to answer from email and easy to answer from a vault.
Receipts, invoices, and the warranty trail
Every paid invoice and material receipt drops on the project page (or a child Receipts page if there are a lot). Most contractors email PDFs; most suppliers email or hand over receipts that scan well. PDFs convert to markdown, so the agent reads them as text.
This is the section that pays off most when something needs warranty work months later. "When did we install the dishwasher and what was the model number?" The answer comes back from the receipt. "Is the cabinetry still under the manufacturer warranty?" The answer requires the install date and the warranty terms — both of which are on the receipt and the manufacturer's PDF, both of which are searchable.
For appliances and major fixtures, the manufacturer documentation is worth keeping on the same page. Manuals, warranty terms, registration confirmations. "What's the maintenance schedule for the new HVAC system?" gets a real answer if the manual is on the page.
This pattern overlaps with the broader Estate Planning and Will Preparation shape — the records you keep mean someone else can find what they need too, if they ever have to.
Permits, inspections, and code records
Projects that involve permits — additions, structural work, electrical, plumbing — generate a paper trail that the city or county will sometimes need to see again. Refinancing, selling, a future renovation that touches the same systems, a code violation notice years later.
A Permits & inspections child page holds the issued permits, the inspection sign-offs, and any plans the city stamped. Drop the PDFs. The agent can pull specific records — "When was the electrical panel inspected and signed off, and by whom?" — when you need them.
For the inspection moments themselves, voice notes capture what the inspector said. They often mention small things that aren't in the formal sign-off — "by the way, the smoke detector spacing here is fine but you'll want to add one at the top of the basement stairs whenever you finish that" — and those off-record comments are the things you'd otherwise forget by the time the related work starts.
A daily log that helps when you need a timeline
A Daily log child page with one entry per notable day becomes invaluable when something needs a timeline. The water leak that started the day after the dishwasher install. The delay that pushed the cabinet delivery from Tuesday to the following Monday. The week the contractor's crew wasn't on site. The day the inspector signed off on rough plumbing.
Voice is the right tool. "Wednesday — cabinet install day two, doors aren't aligning on the corner unit, contractor's coming back tomorrow morning to look at it." Thirty seconds, transcribed, dated. When the punch list gets disputed three months later, the timeline is grounded in real notes.
This isn't about distrust — it's just memory. Even the best contractors have a lot of jobs, and your specific timeline isn't theirs. Having your own log means the conversation about what happened when stays grounded.
A starter shape that works on day one
If you're starting a renovation tomorrow and want a vault that holds together through it:
- One parent page for the project.
- A budget database with line items, estimates, actuals, vendors.
- A change-orders page captured as conversations happen, before they're invoiced.
- A communication log with substantive emails, texts, and voice notes.
- A receipts page where invoices and warranty documents land.
- A permits page if applicable.
- A daily log for the timeline.
That's it. No template, no taxonomy beyond the project name. The vault grows day by day; the agent finds the answer when something comes up.
The point isn't to turn the renovation into a record-keeping project. It's that the small amount of structure you keep means the warranty claim has the install date, the change-order dispute has the verbal agreement, the next project has the suppliers and the lessons, and the cabinet door that sags four months in gets fixed without a week of email archaeology.
Try Docapybara free — start the page before you swing the first hammer, and the project will arrive at its end with most of the records already in place.