Live data from Hacker News

Writing documentation for your house

luke.hsiao.dev

31–40 of 326 posts

Re: Writing documentation for your house

#31
I just have a Google Doc with all of the stuff in there:

- utilities and where they're paid and expected cost

- issues if any with common appliances, e.g.

  - dishwasher occasionally needs to be manually spun with size 7 hex key (placed under)
- who I've given keys to

- where I pay rent to and when and how much

- how to request access to the home lights and voice system

I just call it a House Manual and since it's easy to put pictures and stuff into a Google Doc and you can put videos somewhere else. The primary consumer of this is me. My wife just remembers everything.

Re: Writing documentation for your house

#32
Airbnb hosts do this.

An engineering friend of mine has documented and labeled every aspect of his vacation rental in Hawaii.

The only thing is, it's styled the same as the 1980s terminal systems he worked on down to the embossed black tape labels that gets attached to every switch, knob, and dial.

Treat your house like a black box.

Re: Writing documentation for your house

#33
The concept is spot on but the implementation seems awfully complex.

My strategy that has scaled well over several homes: write install date/vendor/serial on the front of appliance manuals and keep them in a folder. Yes, you can scan them but it’s often easier to look at a paper manual while troubleshooting an appliance.

For notes, punchlists, “how I did it” reminders and details, a shared Apple note or Notion page or Google doc is great. Spouse acceptance factor high and participation factor higher.

Re: Writing documentation for your house

#34
Awesome advice and a great way to prepare for unexpected death or incapacitation (if you are the one in your family who usually handles all this stuff). I only would add that if you do go ahead with this, use tools or a medium that mere mortals are familiar with. Assume the person who needs to read it only knows git as a Larry the Cable Guy reference ("git 'er done!").

Re: Writing documentation for your house

#35
post #17

For my last house, I had spent years on smart home automation, I had a binder that contained clear instructions I wrote for everything, and receipts for every upgrade I ever made on the home, warranty docs, QR codes to download smart home apps to control the devices, plot maps, floor plans, a 1-page list of repairmen for everything- you name it. I made short YouTube videos for everything like turning the water on/off…

I have a home-built system for monitoring the levels in our water tanks (we live on rain water).

Of course some people get by with a simple float indicator, but why would I do that when I could be using high accuracy hydrostatic sensors, esp32, influxdb, grafana, spring, keycloak and mysql running in AWS?

I certainly wouldn't want to be getting support calls if we were to ever sell, so I would probably remove it myself if that happened.

Re: Writing documentation for your house

#36
post #2

The idea of writing technical documentation for your home seems like excellent advise. I think many people do this in an informal manner. I'm not sure a full blown mkdoc setup is necessary -- of having your "home repair/maintenance" notes in their own subfolder of an Obsidian vault or git repository might be sufficient. In my own experience, having quick access to this info has made troubleshooting easier a number of…

I keep it in a Google Doc that I print out and have visible on the kitchen counter when I go to sell.

Even putting aside the practical value it could provide to the new homeowner, it shows the house has been well-maintained to the potential buyer. It also conveys that there are likely fewer "unknowns" about the house because it implies nothing is being hidden.

Re: Writing documentation for your house

#37

Another good trick is to label each outlet and light switch with the number of the circuit breaker its connected to. Things such as a big label on the valve: "MAIN WATER CUTOFF" are also a good idea. Centralized documentation is great , but who reads manuals?

Locality of the information is important.

People will see comments in the code. They may even bother to read a README.md dropped in the same folder as the files they’re looking at. They probably won’t look in a docs/ folder in the root and they’re almost definitely not going to go search Confluence.

Centralized documentation is great for high level information. “Here’s an overview of the water treatment system.” You know where I wanna see instructions for resetting the alarm after cleaning the filter? Beside the filter.

Most of my “home documentation” is sharpied pieces of masking tape stuck around the place.

Re: Writing documentation for your house

#38
post #17

For my last house, I had spent years on smart home automation, I had a binder that contained clear instructions I wrote for everything, and receipts for every upgrade I ever made on the home, warranty docs, QR codes to download smart home apps to control the devices, plot maps, floor plans, a 1-page list of repairmen for everything- you name it. I made short YouTube videos for everything like turning the water on/off…

The last time I bought a house I paid about $600 for a pre-purchase inspection and the inspector basically prepared such a binder for me. A few hundred pages of photos and suggested fixes for not only all the defects she found, but also suggested ongoing maintenance schedules and routines for all the systems of the house, photos of the water shutoff, etc. and even a thumb drive with a few videos she shot and a sewer scope. I was updating the binder as I added/changed stuff but ultimately figured it's probably easier to just a hire another inspection when it's time to sell. There were no smart devices, though, that may have added a premium.

Re: Writing documentation for your house

#39

So, i sold a house i had in north Seattle after a divorce in 2018. We had bought it in 04, i was working at Microsoft at the time. We raised our son there. I even built a 8’x8’x8’ brick oven for baking pizza and bread (plans from Ovencrafters). I rented an excavator for a week and dug around the entire house and put in 12’ deep footing drains, with clean-out pipes every 20’ down the 100’ to the road. A new 2” pex wat…

Yeah sounds like the people who bought it suck. Why would you destroy a pizza oven? It would add a ton of value to the house for the right buyer. If you had sold it to me I would have absolutely kept the oven :) Also inspires me to follow a similar path for my house. I think the key is to price the house so only someone who values the work you've done would bother buying it, if you have the time to wait around. And I guess that doesn't guarantee anything.

Re: Writing documentation for your house

#40
Wow! I love this. I’m going to copy the hell out of this.

I’m a proud “organized person” and have documentation for family and relatives. I’ve got the “Inventory” for most major appliances and long-term items in the house. On my wife’s side, they are a massive Indian family with 20+ cousins across each generation living in large mansions spanning a tiny community. Most of the time, the wife or I would call from across the country to ask where “that was kept,” which services go where, and which cable (I labeled most of them) to look for when the Internet goes down. The in-laws would keep a list of what to set up, fix, and organize when I visit next.

I’m not in favor of using any software or tools for these. I want to stay with OpenFormats, plain-text, PDFs, etc, organized in files. Since the pandemic, I have been slowly documenting and collecting the medical records of my immediate family. This has helped a lot when the father-in-law had to go through an extensive heart-related treatment last year.

Thanks for doing this. This is a big inspiration, though a tad more micro and technical than I wanted. I suggest others who haven’t started something — stay simple and keep it to files — something that would have worked 20 years ago and will likely work in the next 50 years. If you use a tool, it should be like a varnish on top; the contents should work on its own.

Post reply on HN