A practical home for the digital systems that keep a household moving.
The Digital Care Manual is a publication about the part of technology that rarely gets a product launch: the ordinary, recurring work of keeping digital life usable. We write for people who manage school notices, family calendars, passwords, photos, subscriptions, shared documents, devices, and a dozen small accounts that nobody remembers creating. Our goal is not to make your household more “optimized.” It is to make the important things easier to find, safer to maintain, and less dependent on one exhausted person remembering everything.
The guiding question behind the site is simple: Can this digital system still work six months from now? A setup that looks impressive on day one may be a poor household system if no one knows how to review it, recover it, or hand it to another person. We care about the quiet parts: naming conventions, backup checks, recovery information, permission boundaries, recurring reviews, paper fallbacks, and instructions that a tired family member can actually follow.
What we mean by a digital care manual
A household does not need a giant command center. It needs a small set of understandable routines. A digital care manual might be a family account list, a photo backup plan, a weekly review, a subscription audit, a shared folder map, a recovery note, or a checklist for setting up a child’s device. These are not glamorous projects, but they become valuable when a phone is lost, a payment card expires, a parent needs help, or the person who normally handles the admin is unavailable.
We write about setup, but we also write about the life after setup. Who checks the backup? What happens when a child changes schools? Which subscriptions renew? Where is the emergency information stored? What should stay offline? What can be automated safely, and what should remain a simple human reminder?
Meet Mei Harwood
The site is written by Mei Harwood, a 39-year-old independent digital life systems consultant in St. Paul, Minnesota. Mei previously worked in technology product operations and process improvement, where she learned to turn complicated workflows into clear, repeatable instructions. Her work now focuses on individuals and families rather than large internal systems.
Mei lives with her spouse and two children, ages 9 and 12. Her expertise comes from both professional workflow design and the unglamorous reality of running a household: school messages that arrive at the wrong moment, duplicated photos, an expired card attached to a forgotten subscription, and a family member who needs an account recovered without a technical lecture.
She uses tools such as ChatGPT, Claude, Apple Shortcuts, Google Workspace, Microsoft 365, and lightweight automation platforms. She does not assume that every reader needs those tools. Sometimes the best answer is a labeled folder, a paper binder, a recurring calendar reminder, or one shared spreadsheet with clear ownership.
What readers can expect
The next useful action appears before the theory.
Instructions explain both setup and recurring maintenance.
Low-cost, manual, and repairable options are considered alongside paid tools.
Privacy is treated as a design decision, not a reason to panic.
AI is presented as an assistant that needs boundaries, review, and a clear purpose.
Articles distinguish tested experience, sourced facts, and editorial judgment.
We explain what can fail and how to recover without starting over.
What we do not promise
The Digital Care Manual does not promise perfect organization, absolute privacy, or a household that never becomes messy again. It does not suggest that one app can solve family communication, recordkeeping, security, and memory all at once. It does not shame readers for having scattered files or neglected accounts. A messy digital life is often the result of too many demands and too little time, not a character flaw.
We also do not treat AI output as a final legal, medical, financial, or safety decision. If a workflow touches sensitive family information, the article should explain what to leave out, what to review, and when not to automate.
Our operating principle: the best system is one another person can understand, maintain, and use when you are busy.
Why the site exists
Digital administration has become a form of household labor. It takes time, attention, and memory, yet it is often invisible until something breaks. The Digital Care Manual gives that work a place to be named and improved. We believe a calmer digital life is not built by collecting more tools. It is built by making fewer important things depend on luck.
Mei’s signature phrase is also the site’s promise: Make your digital life easier to keep.
The household handoff test
Mei often imagines a simple handoff test while reviewing a system: if the person who normally manages it were away for a week, could another adult understand what matters, where to look, and what not to touch? This does not mean every family needs a formal operations manual. It means important information should not be trapped inside one person’s memory, one phone, or one app that nobody else can open.
That test changes how we evaluate convenience. A clever shortcut may save thirty seconds today but create confusion next month. A shared folder may be less elegant than an integrated platform but easier for a spouse, babysitter, or older relative to understand. A paper note may look old-fashioned but remain available during a device failure. We consider the whole life of the system, including the moments when the original setup person is tired, traveling, or unavailable.
Our approach to AI
AI can help sort a long email thread, draft a grocery list, summarize a meeting, name a group of photos, or suggest a first version of a household plan. It can also misunderstand context, invent details, expose sensitive information, or make a confident suggestion that does not fit a family’s actual needs. We therefore treat AI as a bounded assistant. Give it a defined task, provide only the information it needs, check the result, and decide whether the convenience is worth the ongoing risk and maintenance.
We will not describe a workflow as “automatic” merely because a model produced the first draft. A person still needs to approve the message, verify the calendar, check the allergy information, review the privacy setting, or confirm that a file was backed up. Good automation reduces repetitive work; it does not remove responsibility.
How we keep the advice grounded
When we test a tool, we try to record the version, the device or platform, the required account level, the setup time, the cost, and the point where a human must review the output. When we cannot test something directly, we say so. When a recommendation depends on a vendor’s current feature set, we link to the relevant documentation and encourage readers to check it before relying on the guide.
We also look for the failure path. Can the system be undone? Can a family member find the data? What happens if the internet is down? What happens when a subscription ends? Does an automation create duplicates? Can the account be recovered without the original phone? These questions are not intended to make technology frightening. They are how a useful system becomes a durable one.
A note to the person doing most of the digital work
If you are the person who knows the passwords, maintains the family calendar, finds the school forms, pays the subscriptions, and rescues everyone’s devices, the site is partly for you. You should not have to become the permanent help desk for a household. A good system distributes knowledge, makes routine tasks visible, and gives other people a chance to participate without needing to learn every technical detail.
Progress can be small. Label one folder. Write down one recovery path. Turn off one unnecessary notification. Review one subscription. Make one backup and try restoring one file. The goal is not a perfect digital home. It is a home that is a little easier to keep.
Small improvements count
The work described here is intentionally modest. A household does not have to migrate every file, replace every app, or build a perfect taxonomy to become easier to manage. One clear shared location, one backup that has been tested, one recovery note, and one recurring review can reduce a surprising amount of stress. We would rather help a reader finish a small durable improvement than leave them with an ambitious system they never return to.