At Balay ni Bruno & Co. our founder's task list is built from the "still open" notes our team writes in each project's work log. Once an hour, an AI tidies and sorts those notes so the list reads clearly.
That tidying is useful, but it caused a quiet problem. The list was set up to treat "this line is gone" as "this task is finished". When the AI reworded a note, the old line disappeared, so the list marked it done, even though nobody had touched the work.
What Went Wrong
False Done rows started showing up within minutes. One task appeared as both open and done at the same time. Another was closed only because the rewording dropped a person's name from the line, so the list no longer recognised it as theirs.
How the list worked before
- The task was the exact text of the note
- If the text changed, the old task looked gone
- Gone was read as finished
- A missing name was enough to close a task
- Wrong closes were hard to spot
How it works now
- Each task keeps a fixed label, the wording can change
- Reworded lines are matched back to the same task
- A task closes only when nothing open still resembles it
- No closing across a new week
- Every close shows who did it, with a Bring back button
The Five Rules That Fixed It
Each task gets its own label that never changes. The words describing it are allowed to change as often as they like.
Two lines count as the same task if they start the same way, share most of their words, or score as very similar.
A task closes only if no open line in that project resembles it. Not finding a person's name is not enough.
The weekly sort starts empty, so a task missing at the start of a week proves nothing. The list waits instead of closing it.
Every closed task shows who closed it, "You marked it" or "The work log closed it", and can be brought back with one tap.
The simple idea behind all five: a line going missing is not proof that the work is done. Only treat a task as finished when you have a real reason to, and make every close easy to see and easy to undo.
Two More Things We Learned Along the Way
Alerts hide in lists nobody reads
While fixing this, we found that a separate list of messages our system "could not read" was holding an important alert that sat unseen for two days. A feed nobody looks at is exactly where missed items hide. Now we filter out confirmations of things the person already did and bring only the real alerts to the front.
Test copy first: We build changes to the dashboard as a separate test copy, so the owner can look at it and approve it before the live version changes.
Slow parts should never hold up the page
Sources that are slow to answer now load on their own, so the rest of the page shows straight away instead of waiting. Link checks run side by side rather than one after another.
Common Questions
Why did my task list close a job nobody finished?
If your list is built from notes that get reworded, it may be treating a line that disappeared as a job that was finished. When the wording changes, the old line looks gone, so the list closes it. The fix is to give each task its own fixed label and treat the wording as something that can change.
How can a list tell that a reworded line is still the same task?
We count two lines as the same task if they start the same way, share most of their words, or score as very similar to each other. A task is only closed when no open line in that project still looks like it.
What if the list still closes something by mistake?
Every closed task should have a Bring back button and a note saying who closed it, for example "You marked it" or "The work log closed it". That way a wrong close takes one tap to undo, and you can always see why it happened.
Key Takeaways
- If an AI rewords your notes, "the line is gone" does not mean "the task is done".
- Give each task a fixed label and let the wording change freely.
- Match reworded lines back to the same task before closing anything.
- Do not close tasks at the start of a new week, when the list is still empty.
- Show who closed each task and keep a Bring back button on every one.