Skip to content

Scenario · Manufacturing · Drawing changesScenario · Drawing changes

The drawing changed after work started. Who moved the date?

Beta1 was machining 40 globe valves for order 2588 when the customer sent revision C of the drawing: the flanges now drilled to a different standard. The mail was forwarded to the group. The night shift kept drilling to revision B, and the plan still said Friday.

TaskMIS task 0925-0013, Machine 40 globe valves, order 2588: Production, Machining, raised by Aarav Shah on 25 Sept, due in 3 days; assigned to Ishaan Verma, status On Hold, High priority, due 02 Oct, waiting for Aarav — released drawing rev C since 29 Sept, request HOD, Very High business impact, Kiara Rao copied; what done looks like: order 2588, 40 globe valves DN80, drawing GV-80 rev B, dispatch promised to the customer for Mon 5 Oct. Shown on Tuesday 29 Sep at 4 PM
Task 0925-0013 on Tuesday 29 Sep, 4 PM · Beta1 demo workspace, sample data
See the same week in TaskMIS

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

Meet Beta1 — a fictional valve manufacturer in Coimbatore.

  • Aarav ShahAarav · Sales · Admin
  • Ishaan VermaIshaan · Production
  • Kiara RaoKiara · Quality

What went wrong

The drawing changed. The job, the date and the inspection did not.

  1. Customer · Tue 3 PMSends drawing rev C: new flange drilling.
  2. SalesForwards it to the group.
  3. Night shiftDrills flanges to rev B.
  4. Fri 2 OctThe old date passes. The customer hears on Friday.

One revision. Three costs.

  • Parts made to the old drawingWork done after the change has to be redone, or scrapped.
  • Inspection to the wrong revisionQuality checks against the drawing it has, not the one the customer signed.
  • A late date with no reasonAt month end the delay looks like production’s, not the customer’s change.

The same week with TaskMIS

Same revision. It lands on the job, the same afternoon.

  1. 01 RecordTue 3:10 PM
  2. 02 HoldTue 3:30 PM
  3. 03 Re-dateWed 11:10 AM
  4. 04 DeliverWed 7 Oct

Tue 29 Sep, 3:10 PM · RecordTue 29 Sep, 3:10 PM · The change goes on the job

The change is written on the job, and quality is copied.

Aarav writes the revision on the machining task itself: flanges to Class 150, bodies unchanged, stop drilling until rev C is released. He copies Kiara, so inspection works to the new drawing. Kiara gets a mail for her information.

Mail to Kiara Rao, for your information: Aarav Shah copied you on a task, Machine 40 globe valves, order 2588; there is nothing you need to do; assigned to Ishaan Verma; due Fri 2 Oct 2026; raised by Aarav Shah; task 0925-0013
Kiara’s copy mail, 3:12 PM

Copy mail to Kiara

Tue 29 Sep, 3:30 PM · HoldTue 29 Sep, 3:30 – 3:36 PM · Stop, and say what it is waiting for

Ishaan stops the drilling and names what he needs.

Ishaan puts the job on hold after 8 flanges and keeps the bodies running. The task now waits for Aarav: the released rev C drawing. Anyone who opens it sees why the job stopped and what it needs to restart.

The record of task 0925-0013, 6 entries: Aarav Shah raised this task on 25 Sept at 11:00, target date 02 Oct; Status: Not Started → In Progress, Ishaan Verma, 28 Sept, 08:30; Aarav Shah on 29 Sept at 15:10: Customer sent drawing rev C today: flanges drilled to ASME Class 150, not PN16. Bodies unchanged. Stop flange drilling until rev C is released; Status: In Progress → On Hold, Ishaan Verma, 15:30; Ishaan Verma at 15:35: Flange drilling stopped after 8 valves; body machining continues. Need the released rev C drawing; Now waiting for: Aarav — released drawing rev C, 15:36
The job’s record, Tuesday 4 PM · append-only, no user can edit

Wed 30 Sep, 11:10 AM · Re-date

The date moves the day the scope does.

Rev C is released at 10:45. Ishaan restarts the job and moves it from Friday 2 October to Wednesday 7 October, with the reason Scope change: 32 flanges to drill to rev C, 8 to re-drill. Aarav gets the mail and gives the customer the new date the same morning.

Date-moved mail to Aarav Shah: Ishaan Verma moved the date of Machine 40 globe valves, order 2588; new date Wed 7 Oct 2026; was Fri 2 Oct 2026; reason Scope change; note: Drawing rev C: flange drilling to Class 150; 8 flanges to re-drill; assigned to Ishaan Verma; task 0925-0013
Aarav’s date-moved mail, 11:10 AM

Date-moved mail to Aarav

Wed 7 Oct, 3:30 PM · Deliver

Finished to rev C, on the new date.

All 40 valves are machined to rev C and the 8 re-drilled flanges pass inspection. Aarav’s completion mail shows it on time against the new date, with one date move, and the task’s record keeps the reason: the customer’s change.

Completion mail to Aarav Shah: Ishaan Verma completed your task, Machine 40 globe valves, order 2588; completed on Wed 7 Oct 2026; target date Wed 7 Oct 2026, on time; date moved 1 time; reminders sent 2; done by Ishaan Verma; task 0925-0013
Aarav’s completion mail, Wednesday

Completion mail to Aarav

Try it on the next drawing revision.

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

Join TaskMIS Today

The difference

Same revision. Different week.

DateIn the group chatIn TaskMIS
29 SepTueChatRev C forwarded to the group.In TaskMISWritten on the job; Kiara copied
29 SepTueChatThe night shift drills to rev B.In TaskMISOn hold after 8 flanges; waiting for the released drawing
30 SepWedChatThe plan still says Friday.In TaskMISMoved to 7 Oct, Scope change; Aarav gets the mail
2 OctFriChatThe customer hears the date has gone.In TaskMISThe customer has had the new date since Wednesday
7 OctWedChatThe delay is blamed on production.In TaskMISDone on the new date; the reason is on recordOn the new date

The customer changed the drawing either way. The difference is that the job, the inspection and the date changed with it.

What could change

Three outcomes for Beta1

A change reaches the person doing the work.

It is written on the job’s own task, and the people who need it are copied.

FeatureUpdates on the task · Copy the people who should know

A stopped job says why.

On hold, and waiting for a named person and thing, so the restart is not left to chance.

FeatureWaiting for · Updates on the task

The customer’s change is counted as the customer’s.

The date moves with the reason Scope change, so month-end reviews do not blame the shop.

FeatureA reason for every date change · Due-date revision report

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

Used in this scenario

  • Updates on the task
  • Copy the people who should know
  • Waiting for
  • A reason for every date change
  • The raiser hears about it
  • Every change counted
  • Completion mail to the raiser
See every feature on the Product page →

For the production head

Four answers, without asking around

  • Which jobs are on hold, and what are they waiting for?

    Answered in: Tasks · Waiting on someone
  • What changed on this job, and when?

    Answered in: Task record
  • Which dates moved because the customer changed the scope?

    Answered in: Reports · Due-date revision
  • Does quality know about the revision?

    Answered in: Task · CC

Start this week

Start with the jobs on the floor today

  1. Put each running job into TaskMIS with its drawing number and revision in what done looks like.
  2. When a revision arrives, write it on the job’s task and copy quality, the same day.
  3. Move the date with the reason Scope change before the old date passes.

Questions

Quick answers

Can we attach the new drawing to the task?

No. TaskMIS does not hold attachments. Keep drawings where you keep them today, and write the revision and where it is filed on the task.

Who hears when the date moves?

The person who raised the task and the owner, by mail, unless they made the change themselves. People who are copied can follow it on the task.

Does TaskMIS link to our drawings or ERP?

No. It tracks the follow-up: who has the job, by when, and why the date moved.

Bring clarity and accountability to your team.

Join TaskMIS Today

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