How to identify overdue tasks with an explicit reference date
An overdue report answers a precise question: which incomplete tasks have a stated due date before the chosen reference date? Making that rule explicit keeps the result reproducible.
Start with the right material.
- What you provide
- a task table plus the user's reference date and timezone.
- The intended result
- Export incomplete tasks whose explicit due dates precede the reference date.
How the workflow works.
Provide the reference date, relevant timezone and completion rules. Compare dates only for tasks that have a readable deadline, and keep undated tasks in a separate group if you want them reviewed.
What to check in the result.
Check boundary dates and completed items before acting. A task due today may not be overdue under your chosen rule, and a missing date should not be treated as an expired deadline.
Import the CSV with a consistent delimiter and inspect text identifiers, dates and amounts before using spreadsheet totals. Keep the original file available while checking any automatic type conversion.
Learn from the worked example.
The downloadable CSV example uses these columns: Task, Due date, Reference date, Timezone, Days overdue. Compare a complete record with the source before sorting, combining or importing your own output.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.