Skip to content

Scenario · Ready-mix plant · Cube testsScenario · Cube tests

The 28-day cube result: who is waiting for it?

At Alpha1, cube results come back weeks after the pour, by mail to the plant’s lab technician. In September a 28-day report sat unread until the consultant asked for it before approving the next slab. Nobody had owned the wait.

TaskMIS task 1001-0007, Cube results: Velachery 1st-floor slab (poured 1 Oct), 28-day: Ready-mix plant, Quality, raised by Meera Nair on 1 Oct; due in 2 days, deadline changed once; assigned to Vikram Iyer, In Progress, High priority, due 31 Oct, was 29 Oct, moved once, Dependency on others, 2 days later; waiting for Testing lab — 28-day report since 29 Oct; request HOD, Meera Nair, 01 Oct; Very High business impact; Arjun Das copied; what done looks like: same cubes, 28-day test, done = results checked against M25 and sent to the site and the consultant before the next slab is approved. The record: raised 1 Oct at 18:12 with target date 29 Oct; In Progress on 27 Oct; cubes sent to the lab for the 28-day test on 29 Oct; now waiting for the testing lab, 29 Oct 11:00; date moved 29 Oct → 31 Oct, Dependency on others: the lab’s testing machine is down; they test our cubes on Saturday morning. Shown on Thursday 29 Oct at 11:10 AM
Task 1001-0007 on Thursday 29 Oct, 11:10 AM · Alpha1 demo workspace, sample data
See the same pour 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.

  • Vikram IyerVikram · Plant & quarry
  • Meera NairMeera · Projects
  • Arjun DasArjun · Site engineer

What went wrong

The result had a date. Nobody was waiting for it.

  1. PourConcrete placed, cubes cast, everyone goes home.
  2. LabTests at 7 and 28 days.
  3. Lab technicianThe report lands in one inbox.
  4. Consultant“Where is the 28-day result?”

One report. Three costs.

  • The next slab waitsThe consultant holds the next approval until the earlier results are in front of him.
  • The site hears it lastThe engineer who needs the result is not the person it is mailed to.
  • A problem found late is biggerIf a result is ever low, every week of not knowing means more work built on top.

The same pour with TaskMIS

Same cubes. Each result has an owner from the day of the pour.

  1. 01 PourThu 1 Oct
  2. 02 7-dayThu 8 Oct
  3. 03 28-dayThu 29 Oct
  4. 04 CloseSat 31 Oct

Thu 1 Oct · PourThu 1 Oct, 6:10 PM · Two tasks the evening of the pour

Both results are tasks before the cubes leave the site.

The first-floor slab at Velachery School takes 46 m³ of M25 from Alpha1’s own plant. That evening Meera Nair, who heads projects, raises two tasks for Vikram Iyer, who runs the plant: the 7-day result by 8 October and the 28-day result by 29 October. Arjun Das, the site engineer, is copied on both.

2 tasks · due 8 Oct and 29 Oct · Arjun copied

Tasks searched for Cube, Thursday 1 Oct at 6:20 PM: 2 of 5 active tasks. 1001-0007 Cube results: Velachery 1st-floor slab (poured 1 Oct), 28-day, Ready-mix plant, Quality, Vikram Iyer, High, Not Started, due 29 Oct; 1001-0006 Cube results: Velachery 1st-floor slab (poured 1 Oct), 7-day, Ready-mix plant, Quality, Vikram Iyer, High, Not Started, due 08 Oct
Tasks → search “Cube”, Thursday 6:20 PM

Thu 8 Oct · 7-dayThu 8 Oct, 4:20 PM · The first result, on its date

Meera hears that the 7-day result is in without asking.

Vikram gets a reminder the day before and the result on the 8th. He sends it to the site and the consultant and marks the task complete. Meera’s completion mail shows it closed on its date, with no date change.

Completion mail to Meera Nair: Vikram Iyer completed your task, Cube results: Velachery 1st-floor slab (poured 1 Oct), 7-day. Completed on Thu 8 Oct 2026; target date Thu 8 Oct 2026 — on time; date moved never; reminders sent 2; done by Vikram Iyer; task #1001-0006
Completion mail to Meera, Thursday 8 Oct

Completion mail to Meera

Thu 29 Oct · 28-dayThu 29 Oct, 7:00 – 11:05 AM · Four weeks later, still on someone’s list

Four weeks on, the result is the first line of Vikram’s morning mail.

At 7 AM the Breakfast report lists the 28-day result as due today. The lab’s testing machine is down, so at 11 AM Vikram marks the task as waiting for the lab and moves the date to Saturday 31 October, with the reason. Meera, who raised it, gets the date-moved mail; Arjun sees the new date on the task.

Breakfast report to Vikram Iyer, Thursday 29 Oct, 7 AM: Good morning, Vikram, with a waving-hand emoji. Projects & Plant: 0 overdue · 1 due today. 1001-0007 Cube results: Velachery 1st-floor slab (poured 1 Oct), 28-day — due today; 1012-0012 Start up the new M-sand unit: first trial run — due tomorrow · deadline changed once; 1015-0019 Cube results: Velachery 1st-floor columns (poured 15 Oct), 28-day — no update for 14 days
Breakfast report to Vikram, Thursday 29 Oct, 7 AM

Breakfast report to Vikram

Sat 31 Oct · CloseSat 31 Oct, 11:40 AM · Closed, with the wait on record

The result meets M25, and the record shows the two-day wait and why.

The lab tests the cubes on Saturday morning. At 11:40 Vikram records that the 28-day results meet M25, sends the report to the site and the consultant, and closes the task. When the consultant asks, the answer and its date are on the task.

The record of task 1001-0007, 9 entries: Meera Nair raised this task on 1 Oct at 18:12, assigned to Vikram Iyer, target date 29 Oct, High priority, Very High impact; Status: Not Started → In Progress, Vikram Iyer, 27 Oct, 10:00; Vikram Iyer on 27 Oct at 10:05: Cubes sent to the lab for the 28-day test on 29 Oct; Now waiting for: Testing lab — 28-day report, 29 Oct, 11:00; Date moved 29 Oct → 31 Oct by Vikram Iyer, 29 Oct: Dependency on others — The lab’s testing machine is down; they test our cubes on Saturday morning; No longer waiting — unblocked, 31 Oct, 11:30; Vikram Iyer on 31 Oct at 11:38: 28-day results meet M25. Report sent to the site and the consultant; Status: In Progress → Completed, 11:40; Completed, delivered 31 Oct
The 28-day task’s record · append-only, no user can edit

Try it on the cubes from your next pour.

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

Join TaskMIS Today

The difference

Same cubes. A different answer when the consultant asks.

DateIn one inboxIn TaskMIS
1 OctThuInboxCubes cast. The test dates are in nobody’s diary.In TaskMISTwo tasks: 7-day by 8 Oct, 28-day by 29 Oct
8 OctThuInboxThe 7-day report reaches the lab technician.In TaskMISDone on its date; Meera gets the completion mail
29 OctThuInboxNobody notices the 28-day result is due.In TaskMISFirst line of Vikram’s 7 AM mail; waiting for the lab
31 OctSatInboxThe report sits in one inbox.In TaskMISResults meet M25; sent to the site and the consultantOn record

The lab took four weeks either way. The difference is that someone was waiting for the result on the day it was due.

What could change

Three outcomes for Alpha1

A result due in four weeks has an owner today.

The tasks are raised the evening of the pour, with the test dates as target dates.

FeatureOne owner on every task · A target date is required

The due date comes to the owner.

A reminder the day before and the 7 AM Breakfast report on the day put the result on Vikram’s list.

FeatureReminders before the due date · Breakfast report

The consultant’s question has an answer.

When the results came, where they went and any wait on the lab stay on the task.

FeatureWaiting for · A record no user can edit

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

Used in this scenario

  • One owner on every task
  • A target date is required
  • Copy the people who should know
  • Reminders before the due date
  • Breakfast report
  • Waiting for
  • A reason for every date change
  • The raiser hears about it
  • Completion mail to the raiser
  • A record no user can edit
  • Search and filters
See every feature on the Product page →

For the owner

Four answers before the next slab is approved

  • Which cube results are due this week?

    Answered in: Tasks · search “Cube”
  • Is any result waiting on the lab?

    Answered in: Tasks · Waiting on someone
  • When did the 28-day result for this slab come in?

    Answered in: The task’s record · Archive
  • Are any results late?

    Answered in: Dashboard · Overdue

Start this week

Start with the next pour

  1. After each pour, raise one task per test, with the test date as the target date.
  2. Make the plant’s quality head the owner and copy the site engineer.
  3. Write in what done looks like who gets the results: the site, the consultant, or both.

Questions

Quick answers

Does TaskMIS keep the cube test reports?

No. It does not hold attachments. Keep the reports where you keep them today and note on the task where they are filed.

Does it tell us whether a result passes?

No. Your quality head checks each result against the grade. TaskMIS tracks the follow-up: who has it, by when, and what it is waiting for.

Can the consultant or the lab see the task?

No. Only your team works in TaskMIS. Results go to the consultant the way they do today.

Bring clarity and accountability to your team.

Join TaskMIS Today

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