Archive a former household member without erasing task history
Export shared records, reassign open work, then deactivate access while preserving names on completed tasks and decisions.
Archive a former household member without erasing task history
Export shared records, reassign open work, then deactivate access while preserving names on completed tasks and decisions. The workable rule names a physical or digital state, the person responsible for changing it, and the point at which the handoff is closed.
Separate access removal from record deletion
Before removing anyone, export the household data the group is entitled to keep and give the departing member a reasonable chance to export their own records. Identify open chores, recurring assignments, grocery requests, approvals, and files owned only by that account.
Choose an effective date and preserve attribution on completed work and decisions. Renaming old actions as “deleted user” can destroy context. If the platform cannot retain attribution, create a dated export and a concise transition note before deactivation.
Reassign first, deactivate second
The fastest reliable method is a closed loop with a visible finish. Use these steps in order:
1. List every open or recurring item assigned to the departing member and pause time-sensitive automation if needed.
2. Transfer ownership of shared lists, integrations, files, and device connections to consenting current members.
3. Export the agreed record and verify that it opens before changing access.
4. At the effective time, remove the member, revoke invitations and sessions where supported, and rotate shared credentials that were actually known.
5. Review orphaned tasks, notification routes, and linked household devices, then record completion without retaining private data unnecessarily.
Do not use deletion to rewrite a dispute
Preserve records subject to an active expense, property, or household dispute according to applicable obligations, but do not keep unrelated personal material “just in case.” Access removal is not permission to inspect a former member’s private account or device.
CISA advises using strong, unique passwords. Rotate a credential only if it was shared or exposed, and replace the shared-login pattern with individual access where the service supports it.
A good handoff also passes the Island Test: a housemate returning after several quiet days can understand the current state without reconstructing a chat thread. Put the state beside the thing itself when possible, and keep the digital record focused on ownership, timing, and exceptions. If the physical signal and the app disagree, pause, inspect the real-world situation, and correct both records. Do not choose whichever version is more convenient.
Keep the trial small. Run the rule for two normal household cycles, then ask three concrete questions: Was the next action obvious? Did anyone duplicate work? Could a person who missed the original discussion continue the process? Change one weak point at a time. A process that needs repeated verbal explanation is not yet a shared process.
Agree on a fallback before it is needed. The fallback should protect the household outcome without making one person the permanent rescuer. It might be a temporary reassignment, a substitute item, a manual check, or a decision to wait. Record who chose the fallback and when normal operation should resume. This keeps an exception from quietly becoming the new rule.
How HomeCo helps
Create one clearly named item in HomeCo, assign the current owner, and put the exception in the same shared thread so context does not scatter across texts. Use the roommate app data export checklist for the related household process. HomeCo can coordinate the handoff, but it should not become a vault for secrets or replace professional records.
FAQ
How much detail should the record contain?
Include only what the next person needs: current state, next action, owner, and timing. Add evidence only when it answers a specific dispute or service question.
What if the assigned person cannot finish?
They should reassign before the trigger passes and write the obstacle in one sentence. The new owner should explicitly accept rather than being silently tagged.
When should we revise the rule?
Review it after two exceptions of the same kind or whenever the household, product, or schedule changes. Keep the parts that worked and change the failed trigger.