Audit intermediate Works with: Any AI

Asana Deadline Reliability Audit Across Projects

Table output Has example

• ✅ Asana

Measure how often deadlines are met and why not.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Analyse deadline reliability using this data: [COMPLETED_TASKS_WITH_DUE_AND_COMPLETION_DATES]. Period: [PERIOD]. Major events such as holidays or reorganisations: [CONTEXT].

Calculate the on-time rate (tasks completed on or before the due date divided by tasks completed), average days late for late tasks, the median days late, the share of tasks whose due date was changed at least once if the data shows it, and rates by project and task size. Report separately for tasks with a due date set at creation and those given one later, if the data allows. Show arithmetic and sample sizes, and warn about any group with fewer than ten tasks.

Offer three hypotheses for any weak result with a cheap test for each, separating planning problems (dates set unrealistically) from execution problems (work started late). Do not use the numbers to rank individuals. Finish with two changes to try next month and the measure that will show whether they worked.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Invented data: 80 tasks completed. 56 on time = 70 percent. 24 late with total 96 days late; average = 96 / 24 = 4 days; median 2 days.
By size: small tasks 30 of 36 on time (83.3 percent); large tasks 8 of 18 on time (44.4 percent).
Hypothesis: large tasks are planned optimistically. Test: split the next three large tasks and compare. Reading: the median lateness of 2 days is lower than the average of 4 days, so a few very late tasks pull the average up. Sample sizes: 36 small and 18 large tasks, so the contrast between 83.3 and 44.4 percent is probably real, but 18 is not a large sample. Next step: record the reason when a due date is moved, so the next audit can separate planning from execution.

• asana