An installation date needs more than a task list. Connect approved inputs, parallel preparation and readiness checks so the team can see what must happen first.
Connect approved instructions, site readiness and the installation work before confirming a date.
The installation team is ready to leave, but the customer has not approved the drawing. The workshop can finish the panels, but nobody has confirmed that the room will be clear. Everyone has a task; the tasks simply do not fit together yet.
A useful installation plan shows what must be ready before the next activity starts. That makes the delivery date easier to explain and gives the coordinator specific inputs to check.
This guide uses a hypothetical reading-room shelving job in Dharan. The dates and durations are illustrative planning assumptions, not measured results or a promise of delivery.
Give each task a finished result that the next person can use.
Write tasks around a clear finished result
“Work on shelving” is difficult to hand over. “Confirm site dimensions and record them on the job” gives the next person something usable.
For each task, record its owner, expected duration, required inputs and finish evidence. A drawing task might finish when the customer approves an identified revision. A fabrication task might finish when the required components pass the agreed workshop check.
ERPNext’s Tasks documentation illustrates separate fields for expected dates, expected time, dependencies and task status. The useful lesson is to keep those facts distinct. A planned end date does not show that the work has actually been accepted.
Keep the approved scope and drawing reference with the job. If a customer asks for different shelf dimensions, resolve that change before treating the old instruction as ready for fabrication.
Fabrication and room clearance can overlap; installation requires both to be ready.
Ask what must finish before each task can start
A task dependency describes a relationship between activities. In this example, every dependency is finish to start: the predecessor finishes before its successor begins on the next planned working date.
Microsoft’s task-linking guidance explains that linked predecessors and successors affect the project schedule. A list sorted by date alone does not describe those relationships.
The shelving plan uses five tasks:
| Task |
Duration |
Must finish first |
Planned dates |
| A — Confirm site dimensions |
1 day |
None |
16 November |
| B — Approve the drawing |
1 day |
A |
17 November |
| C — Fabricate and check components |
2 days |
B |
18–19 November |
| D — Clear and confirm the room |
1 day |
B |
18 November |
| E — Deliver, install and check together |
1 day |
C and D |
20 November |
All dates are in 2026. Materials are assumed available, the customer can review on 17 November, and the relevant teams and site are available on the five dates shown. No additional waiting period or buffer is included. Transport and the agreed joint check are included in E, not added again as separate days.
Here, the approved layout identifies the area the customer must clear. Room clearance does not need to wait for fabrication to finish. Installation does need both branches ready.
Separate resources let six days of task durations fit into five working dates.
Use parallel work only when capacity allows it
C and D can run on 18 November because the workshop team and the person coordinating room clearance are separate resources. If the same person must do both, the proposed overlap needs another capacity check.
Adding the task durations gives 1 + 1 + 2 + 1 + 1 = 6 days. The elapsed plan is 1 + 1 + max(2, 1) + 1 = 5 working days, because fabrication and room clearance overlap.
Task durations: 1 + 1 + 2 + 1 + 1 = 6 days
Elapsed plan: 1 + 1 + max(2, 1) + 1 = 5 working days
These are task durations, not six staff-days, payroll hours or a labour-cost estimate. A task may involve several people. The calculation also does not establish how much spare capacity the business has for another job.
ERPNext’s Project Views guide describes a Gantt view using task dates and dependency links. A simple chart is useful here because it shows the overlap and the two prerequisites for installation together.
Do not shorten the plan by overlapping work that needs an approved input. Starting fabrication before the drawing decision would change the assumptions, not merely improve the schedule.
Confirm the correct components and fittings before releasing the installation team.
Check readiness before releasing the installation team
A completed workshop task is one input to dispatch. The coordinator still needs evidence that the correct components, site and people are ready.
| Readiness check |
Useful evidence |
Responsible confirmation |
| Approved instruction |
Drawing revision and approval reference |
Project coordinator |
| Components and fittings |
Checked job list and allocation reference |
Workshop and stores |
| Room and access |
Customer confirmation of usable access |
Site contact |
| Crew and transport |
Confirmed booking and availability |
Installation supervisor |
If an input is missing, record the blocker and the next decision. Avoid marking installation ready simply because the calendar says Friday.
For planned WorkSphere workflows, Project/Task Management could hold the dependency plan, Inventory could provide material-allocation references, and HRM could support the relevant availability check. CRM could retain the agreed customer access and update commitments. Accounting could refer to an approved commercial milestone where the actual contract requires it.
These would be planned connections. A task status should not silently create a stock movement, approve an invoice or confirm that a contractual milestone has been accepted.
A readiness decision needs evidence for every required input.
When a predecessor slips follow its downstream work
If drawing approval is still open at the end of 17 November, check C and D before confirming the 20 November visit. Ask what date the approval can realistically be obtained, then reconsider fabrication capacity, room access, transport and crew bookings.
Do not move only the drawing’s date and leave every dependent activity unchanged. Equally, do not assume every task must move by the same number of calendar days. Working calendars, available capacity and the other branch can change the result.
Keep the original plan and record the revised forecast, reason and person confirming it. Tell the customer what has changed and when the next reliable update will be available. A clear “drawing approval is still needed before fabrication” is more useful than an unsupported assurance that the team will catch up.