Overdue vs. Missed: Explained

1. What Triggers Each Status

Both statuses are triggered when a task's due time passes without a submission being recorded. The difference is one project setting:

Mark as Missed after due time passes — this toggle in the project settings is what separates Overdue from Missed.

Toggle OFF → Overdue: The task stays in the active queue. The employee can still open it and submit. The submission will be recorded as "Completed Late." Overdue notifications fire at the due time.

Toggle ON → Missed: The task locks the moment the due time hits. The employee sees the task but cannot submit it. The button is gone or grayed out. It counts as Incomplete in reporting. 

2. The Full Status Comparison

3. Why Mark as Missed Matters for Operations

Without Mark as Missed: a location that never completes their daily checklist accumulates one Overdue task per day — forever. After 90 days of non-compliance, the task board has 90 open overdue tasks. The workspace becomes unnavigable.

With Mark as Missed: tasks lock at the due time and clear from the active queue. The workspace stays clean. Non-completion is recorded as Incomplete in reporting, which is equally visible but doesn't create an ever-growing backlog.

For daily operational checklists with hard deadlines: Mark as Missed ON. A closing checklist submitted at 2pm the next day is worthless — locking it is the correct behavior.

For compliance forms or audits where late submission is better than none: Mark as Missed OFF. A monthly audit submitted 2 days late is still a valuable record.   

4. The Edge Case: Started Before Due, Submitted After