Skip to content

Scenario · Manufacturing · Date changesScenario · Date changes

The deadline moved three times. Do you know why?

A drilling-jig change for the 6-inch valve body was due on 9 October. It finished on the 23rd, after three moves. Each move had a reason, and together they pointed somewhere nobody expected.

TaskMIS task 1001-0001, Modify the drilling jig for the 6-inch valve body: raised by Aarav Shah on 1 Oct, assigned to Ishaan Verma, In Progress, High priority, Deadline changed 3 times, due 23 Oct, was 09 Oct, moved 3 times, latest reason Client delay, 14 days later. Shown on Monday 19 Oct at 6:15 PM
Task 1001-0001 on Monday 19 Oct, 6:15 PM · Beta1 demo workspace, sample data
See the same month in TaskMIS

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

Meet Beta1 — a fictional valve manufacturer in Coimbatore.

  • Ishaan VermaIshaan · Production
  • Aarav ShahAarav · Sales · Admin

What went wrong

Three new dates. No reasons kept.

  1. Production · 8 Oct“Jig needs a few more days.”
  2. Production · 13 Oct“Next week, sure.”
  3. Month endThe review sees a two-week slip.
  4. Management“Production is slow.” The real hold-up stays.

Three moves. Three problems.

  • The wrong person blamedThe delay lands on whoever owns the task, not on what held it up.
  • The same delay next monthThe cause isn’t fixed, so the next job slips the same way.
  • No pattern to seeOne slip looks like bad luck. Three, without reasons, still do.

The same month with TaskMIS

Same jig. Every move carries its reason.

  1. 01 First moveThu 8 Oct
  2. 02 Two more13 and 19 Oct
  3. 03 Month endMon 2 Nov
  4. 04 Fix the causeMon 2 Nov

Thu 8 Oct, 5:20 PM · First move

The first move needs a reason, and Aarav sees it.

The jig plate is out, but the revised drawing hasn’t come. Ishaan moves the date from 9 to 14 October. TaskMIS asks for the reason: Dependency on others, revised drawing awaited from Sales. Aarav, who raised the task, gets the mail.

Date-moved mail to Aarav Shah: Ishaan Verma moved the date of Modify the drilling jig for the 6-inch valve body; new date Wed 14 Oct 2026; was Fri 9 Oct 2026; reason Dependency on others; note: Revised drawing awaited from Sales; assigned to Ishaan Verma; task 1001-0001
Aarav’s date-moved mail, 8 Oct

Date-moved mail to Aarav

13 and 19 Oct · Two more movesTue 13 and Mon 19 Oct · Two more moves, two more reasons

Each move goes on the record with its reason.

On the 13th the customer changes the hole pattern: Scope change, rev C drawing awaited. On the 19th rev C still isn’t approved: Client delay. The task shows Deadline changed 3 times, and the record keeps all three.

Record entries on task 1001-0001: Date moved 09 Oct to 14 Oct by Ishaan Verma, 8 Oct, Dependency on others: Revised drawing awaited from Sales; Date moved 14 Oct to 20 Oct by Ishaan Verma, 13 Oct, Scope change: Customer changed the hole pattern; drawing rev C awaited; Date moved 20 Oct to 23 Oct by Ishaan Verma, 19 Oct, Client delay: Rev C drawing not yet approved by the customer
The record, 19 Oct · three moves, three reasons

Mon 2 Nov, 9:30 AM · Month endMon 2 Nov, 9:30 AM · Read October’s moves together

The revision report puts the moves side by side.

Reports → Due-Date Revision for October puts the jig at the top: 3 revisions, 14 days. Ishaan changed the most dates, and the reasons column says why: Dependency on others and Scope change, all of it about the customer’s drawing. The jig finished on 23 October, proved on five trial bodies.

1001-0001 · 3 revisions · +14 days

Reports, Due-Date Revision Report, October 2026, every count from the permanent history, it cannot be edited. 1001-0001 Modify the drilling jig for the 6-inch valve body, Ishaan Verma, 3 revisions, +14 days, latest reason Client delay; 1022-0016 Send revised quotation to the customer, Aarav Shah, 2 revisions, +7; 1007-0003 Make the drilling fixture for the 4-inch flange, Ishaan Verma, 1 revision, +7, Dependency on others; and three more with one revision each. Who changed the dates: Ishaan Verma, 2 tasks, 4 revisions, average slip 5.3 days, top reasons Dependency on others, Scope change; Aarav Shah 1 task, 2 revisions; Anika Bose, Sam Mathew and Kiara Rao 1 each
Reports → Due-Date Revision, October 2026

Mon 2 Nov, 10:05 AM · Fix the cause

The hold-up gets its own task, and an owner.

The reasons point at Sales: the customer’s drawing approval. So Aarav raises it as a task for himself, due 5 November: signed drawing for rev D before production gets a date for the next jig change.

Task 1102-0041, Get customer approval: 6-inch body drawing rev D: Sales, Orders, raised by Aarav Shah on 2 Nov, assigned to Aarav Shah, not started, High priority, due 05 Nov in 3 days, not waiting, Self request
Aarav’s new task, 10:10 AM

Try it on the next date that moves.

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

Join TaskMIS Today

The difference

Same three moves. Different month end.

DateBy word of mouthIn TaskMIS
8 OctThuWord of mouth“A few more days.”In TaskMISMoved to 14 Oct · Dependency on others: drawing awaited from Sales
13 OctTueWord of mouth“Next week.”In TaskMISMoved to 20 Oct · Scope change: hole pattern changed
19 OctMonWord of mouth“Almost there.”In TaskMISMoved to 23 Oct · Client delay: rev C not approved
2 NovMonWord of mouth“Production slipped two weeks.”In TaskMISReport: 3 revisions, +14 days, every reason on the drawing
2 NovMonWord of mouthNext job: the same delay.In TaskMISDrawing approval is a task, with an owner and a dateCause owned

The jig slipped two weeks either way. The difference is that the reasons were kept, so the month end found the cause instead of a culprit.

What could change

Three outcomes for Beta1

Every move says why.

A date can’t change without a reason, and the person who raised the task hears about it the same minute.

FeatureA reason for every date change · Date-moved mail

The moves can’t be tidied away.

Each move stays on the task’s record, and the report counts from that history. No one can edit it.

FeatureA record no user can edit · Every change counted

Month end finds causes, not culprits.

The revision report lists who moved dates and the reasons they gave, so a blocked person shows up as blocked.

FeatureDue-Date Revision report

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

Used in this scenario

  • A reason for every date change
  • Date-moved mail
  • Task history
  • Due-Date Revision report
  • Export to Excel
See every feature on the Product page →

For management

Four answers at month end

  • Which tasks moved most this month, and by how much?

    Answered in: Reports · Due-Date Revision
  • Who is moving dates, and what reasons do they give?

    Answered in: Due-Date Revision · Who changed the dates
  • What exactly happened on this task, and when?

    Answered in: Task record
  • Is the same reason coming back every month?

    Answered in: Due-Date Revision · month by month

Start this week

Start reading the reasons

  1. Agree as a team to move dates only in TaskMIS, so every move carries a reason.
  2. At month end, open Reports → Due-Date Revision and pick last month.
  3. Read the reasons column before the names, and give the most common hold-up its own task.

Questions

Quick answers

Can someone change a date without giving a reason?

No. Moving a date asks for a reason from the team’s list, with an optional note. The person who raised the task gets a mail.

Can a date move be deleted later?

No. Each move stays on the task’s record, and the revision report counts from that history.

Can we change the list of reasons?

Yes. An admin edits the reasons on Masters. TaskMIS starts with Workload, Dependency on others, Client delay, Scope change, Priority shifted and Other.

Bring clarity and accountability to your team.

Join TaskMIS Today

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