The checklist was closed as «No completada» (not completed)
Why an expired checklist no longer accepts submission, what margin you had, and how to prevent it from happening again.
Updated on
If a list closes as “Not completed,” it means the time to sign it has run out. It’s not an error: it’s the record that it wasn’t sent on time. Here’s what happened and how to avoid it.
What happened
Each list has a time slot and a delay margin. When the slot ends and the margin runs out, the list closes automatically with the status “Not completed.” From that moment on, it no longer accepts submissions, even if the work was already done.
The record reflects what was signed on time, not what was done without signing. If an employee completed the tasks but didn’t tap “Submit list,” the system can’t know that: for Timlup, that list was left unsigned.
The automatic closure runs every hour on the server. The status updates on that pass, not at the exact minute the deadline passes.
Why you can’t sign late
Because the record is already closed. If we allowed late signatures, the compliance data would no longer be reliable: we wouldn’t know if the task was actually done on time or signed afterward.
The status “Not completed” doesn’t mean the work was done poorly: it means there’s no signed record within the deadline. It’s different from “Late,” which isn’t a failure — a list signed within the margin counts as resolved, with half the value in the monthly score.
How to avoid it next time
You can make three adjustments:
- Increase the list’s delay margin. The default is 45 minutes, but you can extend it from Lists to give employees more leeway.
- Turn on “Complete tasks early” if the shift starts before the time slot. This way employees can sign in advance and work doesn’t pile up at the end.
- Set up the “Expiring unsigned” alert in Notifications. You’ll get an email when a list is about to expire without a signature, so you can react the same day.
With these three adjustments, most unexpected closures can be avoided. The key is making sure the team knows the list needs to be submitted before the margin runs out, even if the work is already done.
Frequently asked questions
Can I sign an already expired list?
No. Once the list closes as “Not completed,” it no longer accepts submissions. The record is closed and can’t be modified.
Why did it close on its own?
Because the time slot and the delay margin ran out. The automatic closure runs every hour on the server, so the status updates on that pass.
How do I keep this from happening again?
Adjust the list’s delay margin, turn on “Complete tasks early” if the shift starts earlier, and set up the “Expiring unsigned” alert in Notifications. That way you’ll have time to react before the list closes.