Skip to content

Scenario · Projects · Site scheduleScenario · Rain delays

After a week of rain, which delays were really ours?

Last monsoon, an Alpha1 site lost days to the rain and days to its own late materials. By the time the client asked why the slab was late, every delay had become “the rain”, and nobody could say how many days were which.

TaskMIS task 1019-0029, Velachery: second-floor slab pour (concrete from our plant): Velachery School, Structure, raised by Meera Nair on 19 Oct; due in 2 days, deadline changed 2 times; assigned to Arjun Das, Not Started, High priority, due 07 Nov, was 31 Oct, moved 2 times, Dependency on others, 7 days later; not waiting; request HOD, Meera Nair, 19 Oct; Very High business impact; Vikram Iyer copied; what done looks like: about 52 m³ of M25 from our plant, done = slab poured and cubes cast. The record: raised 19 Oct at 10:05 with target date 31 Oct; date moved 31 Oct → 04 Nov by Arjun Das on 26 Oct, Rain / weather: follows the shuttering, four rain days; date moved 04 Nov → 07 Nov on 2 Nov, Dependency on others: follows the steel, three more days. Shown on Thursday 5 Nov at 10 AM
Task 1019-0029 on Thursday 5 Nov, 10 AM · Alpha1 demo workspace, sample data
See the same fortnight in TaskMIS

Illustrative scenario. Alpha1 is a fictional company. Not a customer story.

Meet Alpha1 — a fictional construction contractor in Chennai, with its own ready-mix plant and quarry.

  • Rohan PillaiRohan · MD · Admin
  • Arjun DasArjun · Site engineer
  • Leo ThomasLeo · Purchase
  • Meera NairMeera · Projects

What went wrong

“Everything moves by a week” is not a reason.

  1. MondayHeavy rain. The site is waterlogged.
  2. Group chat“All dates move by a week.”
  3. SupplierThe steel is late too. Nobody writes it down.
  4. Client“Why is the slab a week late?”

One excuse. Three costs.

  • The client hears an excuse, not an accountWithout dates and reasons, the conversation is about trust, not facts.
  • Your own delays stay hiddenLate steel filed under rain is never taken up with the supplier.
  • Work that could go on stops tooWhen every date moves together, indoor work the rain never touched slips with the rest.

The same fortnight in TaskMIS

Same rain. Every date that moved says why.

  1. 01 ReasonMon 26 Oct
  2. 02 Move26 – 29 Oct
  3. 03 ReportMon 2 Nov
  4. 04 ExplainThu 5 Nov

Mon 26 Oct · ReasonMon 26 Oct, 8:40 AM · Rain becomes a reason of its own

Before anyone moves a date, Rohan adds “Rain / weather” to the reasons.

The reasons a date can move are a list the admin controls. On the first morning of the rain, Rohan Pillai, the MD, adds Rain / weather to Alpha1’s list, beside Dependency on others, Client delay and the rest, so a rain day is never recorded as anything else.

Reasons: Workload · Dependency on others · Client delay · Scope change · Priority shifted · Other · Rain / weather

Masters, revision reasons, Monday 26 Oct at 8:45 AM: Workload, Dependency on others, Client delay, Scope change, Priority shifted, Other, Rain / weather, and a box to add more
Masters → the date-change reasons, with Rain / weather added

26 – 29 Oct · MoveMon 26 Oct, 9:10 – 9:25 AM · Four dates move, each by its own days

Only the work the rain stops moves, each by the days it loses.

Arjun Das, the site engineer at Velachery School, moves four tasks with Rain / weather and a note: the second-floor shuttering and the pour by four days, the east-wing brickwork by three, the north-face plastering by five. The ground-floor conduits are indoors; they keep their date and finish on 28 October. On Thursday evening the site’s list shows four open tasks, each moved once.

4 moved for rain · the indoor conduits done on their date

Tasks filtered to the Velachery School department, Thursday 29 Oct at 5:10 PM: 4 of 14 active tasks, each marked R1, all Arjun Das. 1019-0032 Velachery: external plastering, north face, Finishing, Medium, In Progress, due 04 Nov; 1019-0030 Velachery: ground-floor brickwork, east wing, Structure, Medium, In Progress, due 31 Oct; 1019-0029 Velachery: second-floor slab pour (concrete from our plant), Structure, High, Not Started, due 04 Nov; 1019-0028 Velachery: second-floor slab, shuttering and steel, Structure, High, In Progress, due 02 Nov
Tasks → Department: Velachery School, Thursday 29 Oct

Mon 2 Nov · ReportMon 2 Nov, 10:00 AM · October’s date changes, each with its reason

The Due-date revision report keeps the rain apart from everything else.

Rohan opens October’s Due-date revision report: eleven tasks moved across Alpha1, each with its latest reason. Four Velachery tasks moved for Rain / weather. The steel for the slab moved six days for the supplier, Dependency on others. Below it, a table only admins see shows who changed the dates and their top reasons.

11 tasks moved in October · 4 for Rain / weather

Reports, Due-Date Revision Report, October 2026, every count comes from the permanent history and cannot be edited, Monday 2 Nov at 10 AM. 11 tasks, each revised once, with total slip and latest reason: 0928-0003 Measurement sheet for the monthly bill: Velachery School, Arjun Das, +2, Client delay; 1001-0007 Cube results: Velachery 1st-floor slab, 28-day, Vikram Iyer, +2, Dependency on others; 1005-0009 Release the hired excavator at Velachery, Arjun Das, +3, Scope change; 1012-0012 Start up the new M-sand unit, Vikram Iyer, +4, Dependency on others; 1012-0014 Supplier’s service engineer, Leo Thomas, +5, Dependency on others; 1017-0024 Block B snags: replace 6 chipped floor tiles, Leo Thomas, +2, Dependency on others; 1019-0028 Velachery: second-floor slab, shuttering and steel, Arjun Das, +4, Rain / weather; 1019-0029 Velachery: second-floor slab pour, Arjun Das, +4, Rain / weather; 1019-0030 Velachery: ground-floor brickwork, east wing, Arjun Das, +3, Rain / weather; 1019-0032 Velachery: external plastering, north face, Arjun Das, +5, Rain / weather; 1020-0033 Steel for the second-floor slab: last lot of 12 mm, Leo Thomas, +6, Dependency on others. Who changed the dates (admins only): Arjun Das, 6 tasks, 6 revisions, average slip 3.5 days, top reasons Rain / weather, Client delay; Leo Thomas, 3 tasks, 3 revisions, 4.3 days, Dependency on others; Vikram Iyer, 2 tasks, 2 revisions, 3.0 days, Dependency on others
Reports → Due-date revision, October 2026

Thu 5 Nov · ExplainThu 5 Nov, 10:00 AM · The pour’s two moves, in the client meeting

Four days for the rain, three for the steel, each on record.

At the client meeting Rohan opens the slab pour. It was due on 31 October. The rain moved it to 4 November; on 2 November the late steel moved it again, to the 7th. Alpha1 owns the three steel days and says so. The slab is poured on 7 November, with 52 m³ of M25 from its own plant.

The record of task 1019-0029, 3 entries: Meera Nair raised this task on 19 Oct at 10:05, assigned to Arjun Das, target date 31 Oct, High priority, Very High impact; Date moved 31 Oct → 04 Nov by Arjun Das on 26 Oct: Rain / weather — Follows the shuttering: four rain days; Date moved 04 Nov → 07 Nov by Arjun Das on 2 Nov: Dependency on others — Follows the steel: three more days
The pour’s record · append-only, no user can edit

Try it before the next rain.

Free for up to 6 members. No credit card required.

Join TaskMIS Today

The difference

Same rain. A different conversation with the client.

DateIn the chatIn TaskMIS
26 OctMonChat“All dates move by a week.”In TaskMISRain / weather added; four tasks moved, each by its own days
28 OctWedChatIndoor work waits with the rest.In TaskMISConduits done on their date
2 NovMonChatThe steel is late; nobody writes it down.In TaskMISOctober’s report: four for rain, the steel for the supplier
5 NovThuChat“It was the rain.”In TaskMISFour days rain, three days steel, on the recordOn record

It rained for four days either way. The difference is that every date that moved said why, so Alpha1 could own its three days and stand by the rest.

What could change

Three outcomes for Alpha1

The reasons fit the work.

The admin adds a reason like Rain / weather, and every date change can use it.

FeatureMasters you control

Each delay keeps its own cause.

Every move asks for a reason and a note, so rain days and late steel stay apart.

FeatureA reason for every date change · A record no user can edit

The client meeting starts from the report.

The Due-date revision report lists every task that moved in the month, with its reason.

FeatureDue-date revision report · Export to Excel

Possible outcomes in a fictional scenario, not measured customer results.

Used in this scenario

  • Masters you control
  • Team roles
  • A reason for every date change
  • Every change counted
  • A record no user can edit
  • Search and filters
  • Due-date revision report
  • Export to Excel
See every feature on the Product page →

For the owner

Four answers when the client asks about the delay

  • Which dates moved this month, and why?

    Answered in: Reports · Due-date revision
  • How many days did the rain cost this slab?

    Answered in: The task’s record
  • Which delays were our own?

    Answered in: Due-date revision · Latest reason
  • Who moved the dates?

    Answered in: Due-date revision · admins only

Start this week

Start before the next rain

  1. Add the reasons your sites really have, such as Rain / weather, to the date-change list in Masters.
  2. When work stops, move only the tasks it stops, each with a reason and a note.
  3. At month end, open the Due-date revision report before the client meeting.

Questions

Quick answers

Who can add a date-change reason?

The admin, in Masters. The lists there feed every dropdown in the task window.

Does TaskMIS know the weather?

No. It has no weather data. The person who moves the date records the reason.

Can the client see the report?

No. Only your team works in TaskMIS. Export Excel on the report gives you a file to share.

Bring clarity and accountability to your team.

Join TaskMIS Today

Free for up to 6 members. No credit card required.