You've been to four apartment showings this week. By Thursday night, the bedroom that had the great closet is bleeding into the kitchen with the cracked tile and the building with the loud upstairs neighbour. You sort of remember which one had the laundry in the unit. You definitely don't remember which one was on the corner and which one faced the alley.
Apartment hunting and house buying both have the same shape — a lot of fast-moving information arriving in the wrong order. Listings expire. Showings happen back-to-back. The PDF inspection report comes a week later. The mortgage broker emails three rate quotes. By the time a decision is in front of you, what you actually need is the version of yourself who saw each place fresh — and that version is gone.
A vault that holds one page per property, with a comparison table that updates as you add candidates, gets that version back when you need it. (The same "lay options out and pick honestly" pattern is covered in Capture and Compare Options for Any Major Decision.)
One page per property, with everything attached
In a markdown vault like Docapybara, each apartment or house gets a parent page named after the address. Pages nest with no depth limit, so under a single property page you can keep child pages for Listing, Tour notes, Inspection, Negotiation, Photos, and Decision. Drop the listing PDF on the listing page; drop the inspection PDF on the inspection page. The agent reads both because uploaded PDFs are converted to searchable markdown automatically.
If you're early in the search and looking at twenty places, you don't need that much structure on every property — just a page with the address, a few notes from the listing, and a placeholder for the showing. Pages that don't pan out get archived under a Passed on parent. Pages that survive grow more child pages.
Tour notes that actually capture what the place was like
The tour itself is the moment your future self will care about most. The kitchen looked smaller in person. The street was louder than the listing implied. The unit faced the back, not the front. None of that is in the listing.
Audio recording is the right tool here. As you walk through, narrate. "Front door opens into living room, north-facing windows, decent natural light. Kitchen is small but new — gas stove, dishwasher. Bedroom on the left, big closet, single window. Bathroom needs work, tile is cracked. The hallway smells faintly like cat. Landlord seems reasonable, mentioned heat is included."
Two minutes of talking, transcribed automatically with timestamps. If you visited with a partner, speaker labels distinguish who said what. You ask the agent later: "Summarize the tour notes for the Maple Street place — what was good, what was concerning, what we still need to ask about." You get a clean summary that's grounded in your actual recording, not a recreation from memory.
For comparison, the same approach across five properties means five quick recordings instead of trying to remember everything in your head Sunday night.
A comparison table that lives inside the page
Once you have two or three serious candidates, you want to see them side by side. An inline :::database::: directive lets a small spreadsheet live alongside the prose on a Comparison page, with columns for address, monthly cost, square footage, bedrooms, parking, laundry, commute time, neighbourhood notes, and a personal score.
The agent updates it as you go. "Add the Pine Street place — $2,400 a month, 850 square feet, two bed, no parking, in-unit laundry, 25-minute commute to my office, scored 7 out of 10." Row appears.
When the field gets crowded, ask the agent for a sort: "Show me the top five by monthly cost, only those with in-unit laundry." You get a focused list without rebuilding the table.
For house buying, the comparison gets more variables — taxes, HOA fees, school district, age of the roof, condition of the systems. Same shape, more columns. Six column types are available, so you can mix text, numbers, dates, and categorical fields without forcing everything into one format.
The PDFs that show up and how to make them useful
House buying generates a small mountain of PDFs. The disclosure packet. The inspection report. The seller's repair history. The HOA documents. The mortgage estimate from each lender. The title report. Most of these arrive at awkward times and get filed in your inbox where they will not be findable later.
Drop each one on the relevant page. The PDF→markdown pipeline runs in the background — uploaded PDFs are converted automatically, so the agent treats them as searchable text rather than opaque attachments.
That changes what you can ask. "What did the inspection say about the electrical panel?" The agent pulls the relevant section with a citation back to the page in the PDF. "Compare the lender estimates on the closing costs side by side." It reads across the three PDFs and assembles a comparison.
For the inspection report specifically, this is genuinely useful. Inspection reports are long, dense, and full of small things that all matter at different intensities. Asking the agent for "the top five things flagged that the inspector recommends addressing within a year" gives you a tractable list to take into the negotiation. The same workflow shows up in legal matters — see Notes for Legal Documentation.
Negotiation notes you'll thank yourself for
Whether you're negotiating rent on an apartment or repair credits on a house, you want a record of what was said, when, and by whom. A Negotiation page with a chronological log is enough.
Voice notes work well for this too — after a phone call with the agent or landlord, narrate what was discussed for thirty seconds. "Talked to Jen at 2pm. They're willing to drop the rent fifty dollars if we sign for two years. Heat is definitely included. They want a deposit equal to first month and a half." Transcribed, dated, in the page.
When you're ready to write the offer or counter, ask the agent: "Based on the negotiation notes for the Pine Street place, summarize what the landlord has offered and what we've asked for." You get a clean summary you can actually act on.
For house buying, this same shape covers the back-and-forth on the offer, the inspection contingency, the appraisal, and the closing. Each communication lands in the page; the agent can pull the timeline when you need it.
Neighbourhood research, without leaving the page
A property is also the neighbourhood it sits in, and a lot of neighbourhood research happens at random — a friend mentions the area is great, you read a Reddit thread about the local crime rate, you check the walk score, you look up which school district it falls under.
The agent's web_search tool can pull current information into the page. "Find what's been written recently about the [neighbourhood name] area — restaurants, safety, transit." Comes back with sources you can read or skip. "Search for any news in the last six months about the school district that covers this address." Same deal.
For a house, this also covers research like checking the property tax history, looking up zoning, finding out what's been built or proposed nearby. Each search lands in the page as a record, so when you later need to remember what you found, it's there with sources.
A decision page that lets you actually choose
When you've been through this for weeks, decision fatigue is real. The way to fight it is a single Decision page that holds your honest take on each finalist.
The shape that works: for each candidate, write a paragraph or two on what you genuinely think — what you liked, what worried you, what you're afraid you'll regret. Then a section called If I had to choose right now, I'd pick… with the reasoning. You can come back the next day and edit it; the page tracks your thinking over time.
When you're ready, ask the agent: "Read the decision page and the comparison table. Summarize the case for and against each finalist as if you were explaining to a friend." You get a clean version of your own thinking, reflected back. Sometimes that's all you need to commit.
For couples or partners going through this together, the page can hold both perspectives. Speaker labels in the audio recordings distinguish who said what during tours; the decision page can be split into "what each of us thinks" sections. Docapybara is single-user, so this is one shared workspace per person — but you can export pages or summaries to talk through with the other person. (For a take on how Docapybara compares with Notion or Obsidian for this kind of long research, see Looking for an Obsidian alternative?.)
A starter shape that works on day one
If you're starting today and you've got three or four properties to track, here's what we'd suggest:
- Properties — one parent page. One child per address.
- For each property, a quick Listing note plus an Tour notes page (voice when you go).
- Comparison — one page with an inline database, fed as you visit places.
- Inspection / docs — for finalists only, one page per property with the PDFs dropped in.
- Negotiation — one page per finalist, chronological.
- Decision — one page total, your honest take on each finalist.
That's enough structure to keep the search organized without turning it into a project. The vault grows as the search gets serious; the early scouting stays light.
The point isn't to build an apartment-hunting database. It's that when the right place comes up — and it always comes up faster than you expect — you have what you need to act with confidence instead of trying to remember which one had the closet.
Try Docapybara free. Start with the comparison page and a voice note from your next tour, and see how much clearer the next decision feels.