Unchecking an accidentally checked task in a shared checklist: moderator mode and history arrive in TAMSIV 1.30
You're at the supermarket, and you think, "I'll check 'bread' before I forget I thought of it." You check it. But your brother sees that bread is checked, so he doesn't go to the bakery. On the morning of the outing, you arrive without bread. No one lied, no one forgot, yet the system failed.
This is the blind spot of collaborative checklists: the premature check. Someone checks an item to remember they thought of it, and that sends a signal to others that it's done. This week, we released TAMSIV version 1.30 with two mechanisms to fix this: moderator mode, which allows unchecking items others have checked, and a complete history for each checklist item.
Key takeaways
- In a shared checklist, checking an item isn't a neutral affirmation; it's a signal sent to others. When it happens too early or by mistake, the whole team silently makes a mistake.
- Moderator mode allows a designated member to uncheck an item validated by someone else, without drama, without messaging, without confrontation.
- A checklist item's history shows who checked, who unchecked, at what time, and from which device. Doubt disappears because you can trace back the actions.
- Calendar events now have the same capabilities as tasks and memos regarding attachments and comments. Total consistency across all three types of shared content.
- Attachments (photos, documents) open in full screen with zoom and swipe-to-close, no more tiny thumbnails you squint to read.
Why does a premature check break a shared checklist?
A private checklist is a memory aid. You check when you want, how you want; it's your problem. A shared checklist is a collective signal. Each check tells others: "you can take this off your mind, it's handled." And we all forget this change in function in our daily lives.
Three typical cases where a check starts to lie:
The "I'll check it to remember I thought of it." You see "fresh bread" on the list and think, "I'm going to the bakery tomorrow morning, I'll make a mental note." To avoid forgetting you thought of it, you check the item. Except you haven't bought the bread yet. Your co-organizers can't distinguish between "I mentally validated it" and "I physically bought it." For them, it's done.
The "oh yes, I'm taking care of it, so I'll check it." Someone asked you in the kitchen, and you replied, "Yeah, don't worry, I'll handle it." You go into the app, you check it to reassure the group. But the physical act of getting the thing, you'll do that in three days. In the meantime, the group is sleeping soundly.
The tap error. A long checklist, a phone, imprecise fingers. You meant to check "bread" but you checked "drinks" right next to it. You don't realize it. Three days later, no one has bought drinks.
In all three cases, the consequence is the same: a false signal circulating in the group that no one can correct without an uncomfortable message like "you did buy the bread, right?"
How does moderator mode work in a TAMSIV checklist?
The principle is simple: on a shared binder, the owner and members in "Total" mode can uncheck an item validated by another member. This action is tracked and appears in the history. No need to ask, no need to discuss; rebalancing happens within the app.
John checks "Fresh bread" → ✅ visible to all Mary (moderator) unchecks → ⬜ visible to all History records: "Checked by John, Monday 3:22 PM" "Unchecked by Mary, Monday 3:47 PM"
The action is socially neutralized because it's part of an intended use of the app, not an interpersonal conflict. Mary doesn't send a message to John saying "you lied"; she unchecks it. John sees that it's back to unchecked, and he understands that he actually needs to go to the bakery. Friction is minimal because the object is the checklist item, not the person.
What exactly does a checklist item's history show?
On each item of a shared checklist, a clock icon opens a window that traces the entire life of that item. Checks, unchecks, text modifications, attachment additions. Each line shows who, when, and from what type of device.
It might seem bureaucratic at first glance, but in practice, it's the opposite. It's what allows you to no longer have to justify yourself. If someone asks "who checked cooler, because we don't have it," you just open the history. The answer is there, dated, sourced. No debate, no accusations, no awkward conversations.
The history also helps understand patterns over time. For an outing that happens regularly (family weekend, sports club, monthly dinner at grandparents'), seeing who naturally takes care of what helps better distribute tasks next time. Not in a reproachful way, but in a "oh okay, I always get the appetizers, we'll rotate" way.
Why does event/task/memo parity matter so much?
From the start, we had three types of objects in TAMSIV: tasks, memos, and calendar events. The first two had full functionality: comments, emoji reactions, attachments, history. Events had a degraded version because they were built later, and we were behind.
With 1.30, it's aligned. You can now attach a photo to an event, comment "I'm 10 min late" under the meeting event, react with a 👍 emoji to confirm your presence, open the history to see who modified the schedule and when. Everything that works on a task works on an event. Everything that works on a memo works on an event.
Why this is important: because users don't think in terms of technical types. They think "I want to say something about this thing in the app." And "this thing," sometimes it's a task, sometimes it's a meeting. Imposing three different grammars depending on the object type creates unnecessary friction.
What else is new in 1.30?
The redesign of attachments. Previously, a photo in a checklist would display as an 80-pixel thumbnail, and you had to open another screen to see it. Now, every image opens full screen with two-finger zoom and a swipe down to close. Just like in any photo app. More natural, less friction, especially for checklists where you share photos of objects ("look at the exact brand," "here's what's left in the cupboard").
On the technical side, we've also unified the checklist progress hooks between tasks, memos, and events. Three files `useChecklistProgress`, `useMemoChecklistProgress`, and `useEventChecklistProgress` now share the same calculation logic, the same disengagement behavior in case of moderation, and the same history format. Fewer potential bugs, easier to extend in future versions.
FAQ
Who can uncheck an item validated by someone else? The binder owner and members in "Total" mode (permissions redesign from April 30). Members in "Write" mode can check and uncheck their own items. Members in "Read" mode see but don't interact with anything.
Does the person whose item was unchecked receive a notification? No push notification saying "Mary unchecked your item." The item simply returns to the unchecked state, and the history records the action. The person sees it when reopening the checklist, without intrusive alerts.
How much storage does the history consume? Each entry weighs less than 200 bytes. A checklist of 50 items with an average of 10 checks/unchecks fits within 100 KB. No noticeable impact on the app.
Does this also work with voice? Yes. You can say "uncheck bread in the fishing trip binder," and the AI processes the request like a manual action, with the history recording "unchecked by voice."
Which version contains these features? Version 1.30 (versionCode 55), available on the Play Store this week.
In summary
A shared checklist is not a collective memory aid; it's a system of signals between people. When a signal becomes false, the whole team silently makes a mistake. Moderator mode and history are the two mechanisms that allow correcting a false signal without social conflict. And event/task/memo parity removes the last remaining friction in the app: you do what you want on the object you want, period.
If you use TAMSIV with family, a team, or a club, open an existing shared checklist and look at the small clock icon to the right of each item. That's the history. It's the end of awkward conversations like "but wait, who checked that?"