The alarm fails silently, so somebody makes it fail loudly
A smoke alarm gives no sign when it stops working. Pressing the test button on a fixed date turns that invisible risk into something you actually know, month after month.

A smoke alarm, seen from underneath, the way you'd actually look at one — a red circle, slotted vents, one button in the middle.
Beside it, a card ruled into twelve short rows. Ten carry a tick in the same firm hand. The last two are still blank.
No numbers on the card. No month names. Just marks, and the two rows still waiting for theirs.
Why press a button on an alarm that hasn't gone off?
Because an alarm that hasn't gone off could mean two completely different things, and there's no way to tell them apart without pressing the button.
It might mean nothing is burning. It might also mean the alarm has stopped working and would say nothing even if something were. A smoke alarm gives no warning when it fails — no light, no sound, no obvious sign, just a device that looks exactly the same whether it's live or dead. Pressing the test button is the way to move from not knowing which one it is to knowing.
Why does the date matter more than remembering to test it?
Because "remember to do it sometime" is exactly the kind of task that quietly stops happening, and tying it to a date that arrives on its own removes the weak link.
An interval you have to count — every so often, roughly monthly — depends on keeping track of when you last did it, one more thing to hold in your head alongside everything else. The first of the month needs no counting at all; it simply arrives, on the calendar, whether or not anyone thought about it in advance. Winding the mantel clock on the same day every week runs on the identical logic — anchor the task to something that shows up regardless, and the task stops depending on memory.
Why keep a card of ticks instead of just doing the test and moving on?
Because a test with nothing to show for it afterwards is indistinguishable, a week later, from a test that never happened — and the value of testing is being able to say, with certainty, when it last passed.
The row of ticks is proof, in the same sense a stamped date on a letter is proof: not decoration, evidence. Shoes polished on the same day every week, whether or not they look like they need it, run on the same logic — the record of doing it regularly is worth more than any single polish, or any single tick. The two blank rows at the end matter as much as the ten filled ones. They're not a gap in the system. They're the part of the card that's plainly still ahead of him, exactly where the year currently stands.
Whose permission do you need to print a habit like this?
Nobody's — testing a smoke alarm on a fixed date isn't a method anyone owns, and no name or face appears anywhere on the design. It's a household routine, not somebody's private property.
What would need clearing is a specific manufacturer's alarm design or a branded logo on the unit itself — this one is drawn as a plain, generic alarm, not a real model, precisely so nothing here needs a licence it wasn't given.
Does this work for a house with more than one alarm, or shared with other people?
Yes, and if anything the logic gets stronger with more than one device, because more alarms means more chances for exactly one of them to be the dead one nobody's noticed.
A single card can stand for the whole house rather than one unit specifically — the print isn't claiming there's only one alarm, it's marking that the check happened, wherever it needed to happen. The shed run as its own small filing system is the same idea scaled to tools instead of alarms: one system, applied everywhere it's needed, rather than one exception per object.
Doesn't a modern alarm already warn you when something's wrong?
Some do chirp when the battery's low, which is a real improvement — but a chirp only fires for one specific failure, and says nothing about whether the alarm as a whole still detects smoke at all.
A low-battery chirp is the unit reporting on itself, a different claim from somebody outside the device confirming it still works end to end. Pressing the test button checks the whole chain — sensor, circuit, sounder — not just the one component that happens to have a warning built in. The built-in chirp is useful. It isn't a substitute for the check.
Does it print well?
Yes — a plain red circle with a single button and a ruled card of ticks are almost entirely flat shapes and hard lines, which is what a screen print reproduces most cleanly.
Two inks cover it: signal red for the alarm, and a darker single colour for the card and its ticks. Keep the ticks visibly hand-drawn rather than uniform — the point of the card is that a person made each mark, on a different day, month after month.
How do I get one made?
Describe the routine at JustOG — what's being checked, how often, and what record proves it happened. Pick a direction, drag the crop frame, see it composited on the real garment, and it's made to order and shipped.
Designs other people have published are in the shop.
Row eleven is still blank, and the first of next month hasn't arrived yet.