Open-source project
potatoqualitee/eol-dr avatar
potatoqualitee/eol-dr

EOL DR Is a Checklist Written on the Assumption That Someone Else Places the Call

🕊️ A crowd-sourced guide to help techs help their non-tech spouses / partners / parents / kids when we are at the end-of-life

5,303 stars237 forksUnknownLicense varies

At a glance

What is it?
A crowd-sourced document for technical people leaving non-technical relatives a working setup after a sudden death. It exists in two formats, one of them generated, and the design goal is that the person who needs help never has to ask for it.
Who is it for?
This checklist fits a technical person whose household depends on infrastructure they alone understand, and who knows the hardest part is not the passwords but identifying who owns which account and which device. It does not fit as a substitute for estate planning, a will, or a power of attorney, none of which it claims to be, and it does not help if the relative is unwilling or unable to use the contacts listed.
Can I use it commercially?
Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
Is it still maintained?
Yes. The repository last received commits 15 days ago.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • potatoqualitee/eol-dr5,303 ★ · +545
Star history
Repository2026-09-232026-11-15
potatoqualitee/eol-dr4.8k5.3k

545 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The Word file is generated, so only the markdown is edited

The checklist is published twice, and the README is explicit about which one is the source:

text
In markdown format: [checklist.md](/checklist.md)
In docx format, generated by the GitHub Action: [checklist.docx](/checklist.docx)

So the markdown file is hand-maintained and the Word file is produced by an automated action, and the note about contributions adds that upon approval of a pull request the Word document will be regenerated for others. That division is the practical thing to understand before you touch either file. Editing the docx locally gets your changes overwritten by the next regeneration, and submitting a diff against a binary document is not reviewable. The reason for having a Word version at all is stated in the story rather than in a feature list, because the author's first move was to create a Word document, print it out, fill in a couple of passwords by hand and store it in a fireproof bag. The docx exists so that other people can do the same thing without installing a markdown toolchain, and the GitHub Action exists so that they never have to convert it themselves.

The failure mode it designs around is a phone call, not a password

The origin story is the design document here, and its sharpest detail is not technical. A colleague died unexpectedly, and six months later his widow was avoiding his office entirely. She worried about what would happen when the television stopped working and when the wifi stopped working, and the README says she knew people would help but that the idea of calling them was torturous. The author's response was to ask for her email address and phone number so that she would not have to dread making the call, and someone else would place it. Former colleagues who lived near her offered to drop by and help work out both short-term and long-term plans. Every design decision follows from that. A checklist that lives in a repository is useless to someone who cannot reach a terminal, so the artefact has to be printable. A list of credentials that assumes the reader knows who to ask is useless to someone who does not, so the list has to name people. The document is an attempt to move the burden of the first call away from the grieving person.

The questions are about account ownership and bills, not about servers

Read the questions the author and his friends asked and notice what is in them. What would Andy have wanted for his homelab? What would our own spouses do if we suddenly were not there? Who would close our Azure accounts? Who should get the PureStorage array? And, for those of us who are the bill payers, how would our spouses know which bill is paid by what bank account? Only one of those is about hardware, and the specific worry that started it was whether the wifi devices would even get an IP address if the DHCP server went down. That symptom is the visible one, but the durable problems are the ones underneath it: cloud accounts that get closed or billed forever, storage arrays whose ownership is unclear, and a household's recurring payments that nobody can map to an account.

It was nearly a gist, and the repository exists for the pull requests

The reason this is a repository rather than a text file is stated in one sentence. The author wrote an initial draft for his own wife and then crowdsourced the rest, with tech friends contributing things he had not thought of and, as he puts it, probably more still. He was going to make it a gist, and a friend suggested putting it on GitHub because that would make pull requests possible. That is the entire design rationale for the tooling, and it explains the shape of the repository, which is small:

bash
checklist.md
checklist.docx
CONTRIBUTING.md

There is no code to run and nothing to install. Contributions arrive as pull requests against a markdown file, following the guidance in the contribution document, and the person who started it is explicit that this is a sanitized list meant for other people's own purposes rather than his filled-in copy. The sanitization is the point. The passwords that matter most never enter the repository at all, they are the ones you write on the printed copy by hand, and a document that can be read by anyone browsing a public page cannot hold them.

The author's own copy went to paper within hours

One sentence in the README carries more weight than the rest of the file. Within hours of the conversation described above, the author created a Word document, printed it out, filled in a couple of passwords manually, and then stored it in a fireproof bag. Physical custody, not a password manager, is the mechanism the author chose, and the surrounding story explains why. A digital safe that depends on a device, an account and a working network is exactly the kind of thing that fails in the situation the document is for. A printed sheet in a fireproof bag has no dependency beyond finding the bag. This also sets the bar for anyone using the checklist. Printing it, filling it in by hand and telling someone where it is, is the intended completion state, and any version of this plan that leaves the only copy on a machine inside the homelab has reintroduced the problem it was meant to solve.

Four related resources are named, and none of them is a checklist

The README ends with a table of things the author considers adjacent, and it is worth reading as a map of the same problem approached from four directions rather than as recommendations. One is a guide book about organising personal and business information for loved ones in case of emergency or death. One is a physical emergency information storage product, a fireproof box with a checklist for critical documents, which is the commercial version of the author's fireproof bag. One is a digital safe designed for non-technical people where important information can be split among several trusted contacts and recovered after a tragic event, which is the multi-key version of the same idea. The fourth is a curated collection of personal blogs with timeless content, aimed at preserving digital legacies rather than credentials. Read together they mark out the different failure modes people have tried to solve: paper custody, physical storage, distributed keys, and content that outlives the person who wrote it.

A document repository with one automated step and no releases

There is not much machinery here, and the smallness is deliberate. The top level holds the GitHub configuration directory, a contribution document, a licence file, the README, and the two checklist files. The only automation named anywhere is the action that regenerates the Word document from the markdown after a pull request is approved. There are no releases published, and the last recorded push to the repository is 2026-11-01, so the document is still being revised without any version history in the release sense. For a reader deciding how much to trust it, the honest framing is that this is a maintained document rather than a maintained product, and the maintenance consists of accepting sensible additions from other people in the same position. Its value is that other people have already thought about the questions you have not asked yet, which is precisely the thing a solo checklist cannot give you and the reason this one was written in public rather than kept on a disk.

Editorial conclusion

This checklist fits a technical person whose household depends on infrastructure they alone understand, and who knows the hardest part is not the passwords but identifying who owns which account and which device. It does not fit as a substitute for estate planning, a will, or a power of attorney, none of which it claims to be, and it does not help if the relative is unwilling or unable to use the contacts listed. Before you use it, verify three things: which of your accounts are in your name alone rather than a shared or corporate one, because the checklist exists precisely to make that list, and who would be willing to show up, since the document's own origin story is about colleagues dropping by. Then print the filled-in copy, because the author's version was filled in by hand and put in a fireproof bag, and the file in the repository deliberately contains no secrets.

Frequently asked questions

What is EOL DR?

A crowd-sourced guide to help technical people help their non-technical spouses, partners, parents or kids when they are at the end of their life. It started as a personal draft written for the author's own wife after a colleague died unexpectedly, and the questions that prompted it were about a homelab, cloud accounts, a storage array and recurring bills.

Which file should I edit in the EOL DR repository?

The markdown one. checklist.md is the hand-maintained source, and checklist.docx is generated from it by a GitHub Action, which regenerates the Word document once a pull request is approved. Editing the docx directly means your changes are overwritten, and the contribution document is the guidance to follow when submitting a pull request.

Does the EOL DR checklist contain anyone's passwords?

No. The file in the repository is described as a sanitized list meant for your own purposes, and the author filled in a couple of passwords by hand on a printed copy which he stored in a fireproof bag. The published document is a set of prompts and contact details to fill in yourself, and the secrets stay on the paper copy you print.

What should I do first with the EOL DR checklist?

Work through the ownership questions it raises rather than the passwords first. The questions the author and his friends asked were who would close the cloud accounts, who should get the storage array, and for bill payers which bill is paid by which bank account. Print the filled-in copy afterwards, since the author's own version was printed within hours and put in a fireproof bag, and tell someone where it is.

Official sources

  1. Issues
  2. potatoqualitee/eol-dr on GitHub
  3. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/potatoqualitee-eol-dr.svg)](https://hysenlabs.com/projects/potatoqualitee-eol-dr)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/potatoqualitee-eol-dr.svg)](https://hysenlabs.com/projects/potatoqualitee-eol-dr)

Was this useful?