Skip to content

Scenario · Purchase & stores · HireScenario · Hired machines

The excavator’s work is done. Who sends it back?

In September a hired crane stood at Alpha1’s Porur site for six days after its last lift. The site thought purchase would call the hire company; purchase was waiting to hear from the site. The hire bill counted every day.

TaskMIS task 1005-0009, Release the hired excavator at Velachery (on hire from 5 Oct): Purchase & stores, Hire, raised by Leo Thomas on 5 Oct, deadline changed once; assigned to Arjun Das, In Progress, High priority, due 20 Oct in 5 days, was 17 Oct, moved once, Scope change, 3 days later; not waiting; request HOD, Leo Thomas, 05 Oct; High business impact; Divya Menon copied; what done looks like: day rate, work: footing excavation for the second block, done = machine off site and the hire company’s return slip signed, Leo told the same day. The record: raised 5 Oct at 10:00 with target date 17 Oct; In Progress 5 Oct at 11:00; Arjun Das on 15 Oct at 18:00: hard rock at the north-east corner, needs the breaker attachment for two to three days; date moved 17 Oct → 20 Oct, Scope change: hard rock at the north-east corner, three more days with the breaker. Shown on Thursday 15 Oct at 6:10 PM
Task 1005-0009 on Thursday 15 Oct, 6:10 PM · Alpha1 demo workspace, sample data
See October’s hired machines 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.

  • Leo ThomasLeo · Purchase & hire
  • Arjun DasArjun · Site engineer
  • Divya MenonDivya · Accounts

What went wrong

The work ended on site. The hire ran on in purchase.

  1. SiteThe last lift is done on Thursday.
  2. CraneStands at the gate, the operator waiting.
  3. PurchaseHears on Tuesday. Calls the hire company.
  4. AccountsPays six idle days at the day rate.

One phone call. Three costs.

  • Days paid for nothingA day-rate machine costs the same whether it works or waits.
  • Accounts cannot check the billNobody wrote down when the work ended, so the hire company’s count is the only record.
  • Extensions agreed blindWhen the work does run over, purchase extends the hire without knowing why or for how long.

October in TaskMIS

Same machines. Each one has a release date and an owner.

  1. 01 Hire5 – 15 Oct
  2. 02 ExtendThu 15 Oct
  3. 03 ReleaseTue 20 Oct
  4. 04 CheckMon 2 Nov

5 – 15 Oct · HireMon 5 – Thu 15 Oct · A release task for every hired machine

The day a machine arrives, its release is a task for the site.

Leo Thomas, who handles purchase and hire, raises a release task the day each machine comes on hire. Arjun Das, the site engineer, owns it, the target date is the planned end of its work, and Divya Menon in accounts is copied. By 15 October there are three: the excavator at Velachery, the mobile crane at Porur and the scaffolding on Porur Block B.

3 on hire · release dates 16 Oct, 20 Oct, 31 Oct

Tasks filtered to the Purchase & stores department, Thursday 15 Oct at 6:10 PM: 3 tasks, all Purchase & stores, Hire, assigned to Arjun Das. 1012-0011 Return the hired scaffolding at Porur Block B (120 sets), Medium, Not Started, due 31 Oct; 1008-0010 Release the hired mobile crane at Porur (on hire from 8 Oct), High, In Progress, due 16 Oct, tomorrow; 1005-0009 Release the hired excavator at Velachery (on hire from 5 Oct), High, In Progress, due 20 Oct, R1
Tasks → Department: Purchase & stores, Thursday 6:10 PM

Thu 15 Oct · ExtendThu 15 Oct, 6:05 PM · Three more days, with the reason

When the work runs over, purchase hears why the same evening.

The excavation meets hard rock at the north-east corner. Arjun moves the release from 17 to 20 October with the reason, Scope change, and a note. Leo gets the date-moved mail that evening and extends the hire by three days, knowing exactly why.

Date-moved mail to Leo Thomas: Arjun Das moved the date. Release the hired excavator at Velachery (on hire from 5 Oct). New date Tue 20 Oct 2026; was Sat 17 Oct 2026; reason Scope change; note: Hard rock at the north-east corner: three more days with the breaker; assigned to Arjun Das; task #1005-0009
Date-moved mail to Leo, Thursday 15 Oct

Date-moved mail to Leo

Tue 20 Oct · ReleaseTue 20 Oct, 7:00 AM · The release is the first line of the morning

On the release day, it tops Arjun’s morning mail.

At 7 AM Arjun’s Breakfast report lists the excavator’s release as due today, above the Block B snag work due later in the week. The excavation ends that afternoon; the machine leaves the site at 4 PM with the return slip signed, and Arjun closes the task.

Breakfast report to Arjun Das, Tuesday 20 Oct, 7 AM: Good morning, Arjun, with a waving-hand emoji. Projects & Plant: 0 overdue · 1 due today. 1005-0009 Release the hired excavator at Velachery (on hire from 5 Oct) — due today · no update for 5 days; 1017-0021 Block B snags: plumbing, 14 points — due in 3 days; 1017-0022 Block B snags: electrical, 9 points — due in 2 days; 0928-0002 Measurement sheet for the monthly bill: Porur Apartments — Monthly: Oct 2026 — no update for 22 days; 0928-0003 Measurement sheet for the monthly bill: Velachery School — Monthly: Oct 2026 — no update for 22 days
Breakfast report to Arjun, Tuesday 20 Oct, 7 AM

Breakfast report to Arjun

Mon 2 Nov · CheckTue 20 Oct – Mon 2 Nov · The hire bills checked against the record

Accounts checks each hire bill against the date on record.

Leo’s completion mail on the 20th shows the excavator released on its new date, after one date change. When October’s hire bills arrive, Divya searches the Archive: the crane was released on 16 October, the excavator on the 20th and the scaffolding on the 31st. Each bill is checked against those dates.

Completion mail to Leo Thomas: Arjun Das completed your task, Release the hired excavator at Velachery (on hire from 5 Oct). Completed on Tue 20 Oct 2026; target date Tue 20 Oct 2026 — on time; date moved 1 time; reminders sent 2; done by Arjun Das; task #1005-0009
Completion mail to Leo, Tuesday 20 Oct

Completion mail to Leo

Archive searched for hired, Monday 2 Nov: 3 completed tasks, all assigned to Arjun Das. 1012-0011 Return the hired scaffolding at Porur Block B (120 sets), Medium, completed 31 Oct; 1005-0009 Release the hired excavator at Velachery (on hire from 5 Oct), High, completed 20 Oct; 1008-0010 Release the hired mobile crane at Porur (on hire from 8 Oct), High, completed 16 Oct
Archive → search “hired”, Monday 2 Nov

Try it on the machines on hire this week.

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

Join TaskMIS Today

The difference

Same machines. A different hire bill.

DateOn the phoneIn TaskMIS
5 OctMonPhoneExcavator arrives. The end date is in Arjun’s head.In TaskMISRelease task for Arjun, due 17 Oct; Divya copied
15 OctThuPhoneHard rock. Purchase hears next week.In TaskMISMoved to 20 Oct with the reason; Leo mailed that evening
16 OctFriPhoneThe crane stands at the gate.In TaskMISCrane released at 1 PM, on its date
20 OctTuePhoneExcavation done; the machine waits for a call.In TaskMISReleased at 4 PM; return slip signed
2 NovMonPhoneAccounts pays the hire company’s count.In TaskMISBills checked against the dates in the ArchiveChecked

The hard rock cost three days either way. The difference is that the hire stopped the day the work did, and accounts could see when that was.

What could change

Three outcomes for Alpha1

A machine’s release is somebody’s job.

Each hired machine gets a release task for the site on the day it arrives.

FeatureOne owner on every task · A target date is required

Purchase hears when the work runs over.

A new date needs a reason, and the person who raised the task gets it by mail.

FeatureA reason for every date change · The raiser hears about it

Hire bills are checked against facts.

The Archive keeps when each machine was released, for accounts to check the bill.

FeatureArchive · Completion mail to the raiser

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
  • Departments and sub-departments
  • A reason for every date change
  • The raiser hears about it
  • Breakfast report
  • Completion mail to the raiser
  • Archive
See every feature on the Product page →

For the owner

Four answers before the hire bill comes

  • Which hired machines are on our sites, and until when?

    Answered in: Tasks · Purchase & stores › Hire
  • Why did the excavator stay three extra days?

    Answered in: The task’s record
  • Which releases are due this week?

    Answered in: Tasks · Deadline view
  • When was each machine actually released?

    Answered in: Archive · search “hired”

Start this week

Start with what is on hire today

  1. List every hired machine on your sites and raise a release task for each, owned by the site.
  2. Make the target date the planned end of its work, and copy accounts.
  3. When a hire bill arrives, check its days against the Archive.

Questions

Quick answers

Can the hire company see the task?

No. Only your team works in TaskMIS. Purchase calls the hire company the way it does today, on the day the task says.

Does TaskMIS track hire rates or bills?

No. It tracks the follow-up: who releases each machine, by when, and why the date moved. Rates and bills stay in your accounts.

Does TaskMIS know where a machine is?

No. There is no GPS or location tracking. The site engineer records when the machine leaves.

Bring clarity and accountability to your team.

Join TaskMIS Today

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