How I Use Deadline Guard to Stop Forgetting Everyday Tasks
How I use Deadline Guard to stop forgetting home checks, offsite NAS backups, tax dates, subscription windows, pet vaccinations, and links saved at work.
Last Tuesday I left the office with one thought in my head: I needed to check why the dehumidifier in the basement had been running non-stop. By the time I reached the train, the thought was gone. I remembered it again on Thursday, in bed, at the exact moment when getting up was the only useful response.
That is the kind of task I built Deadline Guard for. Not projects. Not meetings. The small, dated obligations that sit between work and home, where neither a calendar nor an issue tracker is really looking.
I wrote about the implementation in an earlier post. That article was about architecture, AI assistance, and the decisions behind the app. This one is about the less glamorous side: what I actually put into the list, what I deliberately keep out, and how a couple of dozen dates changed the way I handle the things I used to carry in my head.
I’m the developer, so this isn’t a neutral review. Still, it’s an honest account of my own usage. The app isn’t the reason the system works. The rules around it are. What changed is not the number of tasks I finish. It is the amount of attention I spend holding them.
The Rule: If a Date Can Cost Me Something, It Goes In
After a few months, the rule condensed into one sentence: if a date can cost me money, health, or a second trip, it goes into the app. Everything else stays where it already lives.
Cost is the filter. A concert ticket belongs in my calendar. A project with fifteen open tasks belongs in my issue tracker. Return windows, cancellation periods, vaccination dates, and warranties that end in three weeks all have the same shape: one date, one decision, and a price for missing it.
The second rule is about timing. I capture the date when I notice it, not when I get around to organizing it. This is why the share sheet matters more than any other feature. When I find a subscription page while paying a bill, I share it to Deadline Guard, pick a date, and I’m done in under thirty seconds. If capture takes longer than that, I won’t do it. I’ve proven this to myself with every note-taking app I’ve abandoned.
The workflow is deliberately short. If it had more steps, I’d skip it. Conceptually, it looks like this.
flowchart TD
A[Date with a consequence] --> B[Capture immediately]
B --> C{When can I act?}
C -->|Small home task| D[Reminder at a useful time]
C -->|Cancellation window| E[Reminders weeks and days before]
C -->|Recurring check| F[Repeat on my schedule]
D --> G[Act]
E --> G
F --> G
G --> H[Confirm]
H --> I[Archive with a timestamp]
A deadline entry is not a task list. If an item needs five steps, it belongs in my issue tracker. The deadline marks the date by which the last step has to be finished.
The Small Things After Work
When I leave the office, I don’t need a project plan. I need a nudge at 18:15 that says “check the boiler pressure”. The task takes two minutes. Remembering it for the whole train ride takes considerably longer.
These entries usually have a due time instead of just a due date: check the parcel room, water the plants before a trip, look at the dehumidifier, confirm that the window in the home office is closed when rain is forecast. None of them deserve a calendar slot, and all of them are easy to lose between the last meeting and dinner.
I used to send myself messages on my phone. They disappeared into the same chat as everything else, somewhere between a delivery notification and a calendar reminder. A notification at the time I can act is a different thing. It does not ask me to remember. It asks me to do.
One entry, one action. If I notice a second thing while I’m at it, it gets its own entry. That sounds bureaucratic for a two-minute task, but the alternative is a mental list that runs in the background all day and drains attention in small, invisible amounts.
The first week I used the app, I missed a reminder because I’d set it for 20:00 and was already in the basement at 18:30. The fix was not a better app. It was a better reminder time. Now I set the notification for the moment I’m likely to be near the thing, not the moment the deadline expires.
Weekly: The Offsite Backup Starts With a USB Cable
The offsite backup is not a job that runs by itself. Once a week I take the USB drive out of secure storage, plug it into the NAS, and start the backup. If I don’t put that on a deadline, it doesn’t happen. The NAS keeps running, the local backups look fine, and the copy that is supposed to survive a fire or a theft stays in storage for another week.
I keep a recurring deadline for Sunday morning. It repeats weekly. The title is deliberately physical: “Plug in the offsite USB drive and start the backup.” The description holds the steps I need, because the version of me that gets the notification will otherwise plug the drive into the wrong port and wonder why the job is writing to the internal disk.
1
2
3
4
5
6
1. Take the USB drive out of secure storage.
2. Plug it into the NAS and confirm it is mounted.
3. Start the offsite backup job.
4. Wait for it to finish without errors.
5. Check that the new copy is on the USB drive, not the internal disk, and that its timestamp is newer than the last one.
6. Unmount the drive and return it to secure storage.
The list has six steps because stopping at “start the backup” is not enough. A job can finish successfully and still write to the wrong target. A drive can sit on my desk for a week because I never added “return it” to the list. The last step is not optional. An offsite drive that stays in the house is just another local copy with extra steps.
After the copy finishes, I open the target and look at the actual state. The check itself takes five minutes. The copy takes as long as it takes. If something is wrong, I create a separate deadline for the repair. A failing check should not disappear into a recurring entry that I confirm out of habit.
The verification depends on the tool. For a snapshot-based repository such as Restic, it means looking at the last snapshot and the free space on the target. For a file-level copy it means comparing timestamps and file counts. The principle is the same: open the target, not the job history. A green checkmark in a scheduler only proves that the scheduler ran.
A recurring reminder is easy to confirm on autopilot. If the backup has real consequences, open the target before you tap confirm, and check that the drive is back in storage. The notification is not the verification.
That distinction matters more than it sounds. The archive shows when I last confirmed the offsite backup, not when the backup last succeeded. If I confirm without looking, I’m generating a comfortable fiction with timestamps.
Quarterly: Taxes Have a Due Date and an Action Date
The tax office gives me a date when the money has to arrive. That is not the date I need in my calendar. I need the Saturday morning three weeks earlier when I’ve got the numbers, the paperwork, and enough coffee to file the advance payment without guessing.
I keep a recurring entry for the advance payments. Each occurrence carries two reminders: two weeks before, when I should have the numbers ready, and three days before, when it’s time to actually pay. The description holds the details I won’t remember in three months: which form, which account, the amount from the last payment, and a link to FinanzOnline.
I used to treat tax dates as a single annual event. They are not. The quarterly advance payments are the part that bites, because they arrive four times a year and each one is small enough to postpone. A recurring deadline makes them visible before they become urgent.
Tax dates and amounts depend on your situation. I use the dates from my tax office and verify them on the official portal. This is my workflow, not tax advice.
Confirming the entry is also useful. The archive becomes a record of when I paid and how much. In January, when I can’t remember whether the last payment went out, I check the archive instead of searching bank statements. That is a small thing, but it’s the difference between a reminder app and a record I can trust.
Subscriptions: The Cancellation Window Is the Real Deadline
The renewal date is the date the money leaves. The deadline is the last day I can stop it. For annual contracts those two dates can be months apart, and the reminder email from the provider usually arrives after the window has closed or so close to it that support is the only option left.
For every subscription I add two reminders: one a month before the cancellation deadline, when I can still compare alternatives, and one a week before, when I need to send the cancellation. For a free trial, the first reminder is two days before the charge. Reminders are part of the one-time PRO upgrade. There is no subscription in the app, which would be a strange thing to sell inside a subscription tracker.
The title starts with a verb: “Cancel the streaming subscription”, not “Streaming subscription”. On the lock screen, the title is the instruction. The description holds the account email and a link to the cancellation page, because the version of me that gets the notification won’t remember which address I used.
1
2
3
4
5
6
7
Title: Cancel the streaming subscription
Due: last day to cancel
Reminders: 30 days before, 7 days before
Tags: Money
Description: Account: personal@example.com
Cancel at: https://example.com/account
Price: 17.99 EUR per month
When I cancel, I confirm the entry. It moves to the archive with a timestamp. Six months later, when I wonder whether I still pay for something, I filter the archive instead of reading bank statements. That archive has become the part of the app I use more than I expected.
A notification on the renewal date is a receipt, not a warning. Set the reminder for the last moment you can still act.
Pet Vaccinations: Book Early, Not on the Due Date
The vet tells me when the next vaccination is due. I write that date down before I leave the practice, with a reminder six weeks before. The reminder is not for the vaccination itself. It is for booking the appointment, because the good slots are gone by the time the date is close.
I keep a photo of the vaccination record as an attachment and put the vaccine name and the vet’s phone number in the description. For dogs, the booster interval depends on the vaccine and the manufacturer’s label, so I don’t calculate it myself. I ask, and I write down what I was told. The same applies to cats and any other animal with a vaccination schedule.
This is the example I use when someone asks why a deadline app is not just for work. The cost of missing it is not money. It is a lapsed vaccination and a stressful phone call.
The Work Link That Never Gets Read
I find something at work that I want to try at home: a CLI tool, an article about ZFS, a repository with a clever approach. I used to email it to myself. My personal inbox is where links go to be archived unread.
Now I share the link from the browser to Deadline Guard, set the due date to the next Saturday morning, and add a reminder for the same time. The due date is artificial. The link is not a contract and nobody charges me for ignoring it. But the entry gives the link a place and an expiry. On Saturday I either read it or confirm that I won’t. Both outcomes are better than forty open tabs.
One boundary: public links only. No internal wiki pages, no customer documents, no ticket URLs. The app stores data locally, but the phone is still a personal device, and a URL is still a pointer to work content. The share sheet makes it easy to cross that line, so I decided where the line is before it became convenient to cross it.
Other Entries That Earn Their Place
Not everything in my list is a recurring ritual. Some entries exist once a year and still pay for themselves.
- Return windows. An online order has a date by which the parcel must be back at the shop, not the date I put it in the mail. I set the deadline two days before the official end and add a reminder for the evening before. The EU withdrawal right gives me fourteen days in most cases, but the shop’s own policy can be longer, so I use the date in the order confirmation.
- Warranty. When a device starts making a noise, the last thing I need is to discover that the warranty ended last week. A reminder three weeks before the end of the warranty period is enough time to test the device and open a claim.
- Passport and ID. Some countries want six months of validity left when you arrive. I renew nine months before expiry, which sounds excessive until you are booking a flight in a hurry.
- Domains and certificates. Renewal failures are silent. A recurring deadline thirty days before expiry gives me time to fix a payment method or a DNS challenge without an outage.
- Contract notice periods. The gym, the insurance, the phone contract. The date that matters is the last day to give notice, not the renewal date. I put the notice date in the title so I can’t confuse the two.
Each of these has the same property: the date is fixed, the consequence is personal, and nobody will remind me if I forget. That is exactly the gap the app fills.
How I Keep the List From Becoming Noise
A deadline list can turn into another inbox. I have five habits that keep mine small.
#1 Tags mirror my life, not the app’s defaults: Home, Homelab, Money, Pets, Read later. On Sunday I filter by one tag at a time. The filter is less about finding things and more about seeing a category as a whole. When I look at the Homelab tag, I can tell whether I’ve taken on too many maintenance promises.
#2 In the app, titles start with a verb and contain the action. “Plug in the offsite USB drive and start the backup” instead of “NAS”. “Cancel the streaming subscription” instead of the provider’s name. The notification is the instruction, and I don’t want to decode it at 18:15.
#3 Descriptions hold the context. A deadline without context is a phone call I have to make twice: once to find out what it was about, and once to do it. Account numbers, contract IDs, links, and the name of the person I spoke to all go into the description, even when the entry looks trivial.
#4 Reminder timing follows the action, not the deadline. A reminder to call the tax office at 23:59 is useless. A reminder at 09:00 on a weekday, when the office is open and I have the documents in front of me, is useful. For home tasks, the useful time is the evening. For subscriptions, it’s a quiet Sunday morning when I can compare prices without a meeting starting in five minutes.
#5 And once a week, I spend ten minutes on the list. I scan the upcoming entries, reschedule what slipped, confirm what is done, and delete what I’ve decided not to do. The review is the price of trusting the list. Without it, the app is just another place where things go to be forgotten.
What Deadline Guard Does Not Do
Deadline Guard doesn’t pull the USB drive out of storage, plug it into the NAS, or start the backup. It doesn’t file the tax return, cancel the subscription, or book the vet. It makes the date visible. The action is still mine.
It doesn’t replace my calendar. A dentist appointment at 14:00 is a calendar event because it occupies a slot and involves another person. A cancellation window is a deadline because it is a date by which I must act. Putting both in the same tool makes the calendar noisy and the deadlines easy to miss.
It doesn’t sync. Local-only storage is the reason I trust it with subscription and tax entries in the first place, but it has a cost: the data lives on one phone. I export a backup before I switch devices, and I accept that there is no web interface. For a list of thirty dates, that is a trade I am happy to make.
It also doesn’t know whether I actually did the thing. A confirmed deadline is my statement, not evidence. The weekly offsite backup is only as good as the drive I actually plug in and the target I actually inspect. The app can remind me to be honest. It can’t be honest for me.
If everything is a deadline, nothing is. I keep the upcoming list under thirty entries. When it grows, I prune. A reminder I ignore is worse than no reminder, because it teaches me to ignore the next one.
Final Thoughts
None of these examples are dramatic. A dehumidifier, an offsite backup, a tax payment, a vaccination. That is the point. The tasks that cause the most low-level stress are rarely the big ones. They are the small, dated obligations that live in the gap between work and home, where no tool is really looking.
Deadline Guard did not give me more hours. It gave me a place to put the thought until the moment I can act on it. The list is boring, and I mean that as a compliment. A good system should become invisible: I capture the date, I get the reminder, I do the thing, I confirm it, and I stop carrying it.
I still forget things. The difference is that forgetting is now visible in the overdue tab instead of silent. That is a much better failure mode.
