Asana tracks your office tasks but can't run a plant shutdown with permits, contractors and a hard window
Custom project management software for a Bunbury industrial operator typically costs $45k to $110k over 3 to 7 months. Asana, Monday, Jira and ClickUp run office task lists well, but they can't coordinate a plant shutdown with permits to work, contractor inductions, isolation steps and a hard restart window. Custom software encodes the safety-critical sequencing those generic tools leave to a spreadsheet.
Asana and Monday are fine for marketing tasks and product roadmaps. They fall apart when the project is a shutdown at your alumina or mineral-sands plant: dozens of contractors needing valid inductions, permits to work that must be issued and closed in order, isolations and lock-outs that gate downstream tasks, and a hard window because the plant can't stay offline a day longer than planned. A generic task tool has no permit, no induction status and no isolation dependency.
So the real shutdown plan lives in a spreadsheet and a stack of paper permits, the scheduler reconciles by hand, and a missed isolation or an expired induction becomes a safety incident or a blown restart window. For a South West processing operation, the project tool that should be enforcing the safety-critical sequence is instead a place you log generic tasks while the dangerous part runs on paper.
What breaks first in Bunbury
- Asana and Monday have no concept of a permit to work, an induction status or an isolation that gates downstream tasks
- Plant shutdowns run on a spreadsheet and paper permits reconciled by hand, so a missed isolation becomes a safety risk
- Contractor inductions and competencies aren't tracked, so an unqualified worker can be assigned a task
- A hard restart window has no enforcement in the tool, so slippage surfaces too late to recover
The fix: project management built for Bunbury, not rented
Custom project software encodes the safety-critical sequence: permits issued and closed in order, isolations gating the tasks they protect, contractor inductions checked before assignment, and the hard restart window tracked against real progress. The dangerous part of a shutdown comes off paper and into a system that won't let a task start until its permit and isolation are valid.
What project management costs in Bunbury
| Project scope | Typical cost | Timeline |
|---|---|---|
| Shutdown coordination with permits and isolations | $45k to $75k | 3 to 5 months |
| Full system: permits, inductions, hard-window, audit | $80k to $110k | 5 to 7 months |
| Permit and induction layer over existing scheduling | $40k to $65k | 3 to 4 months |
The capability list that earns its budget
What we build under project management in Bunbury
The engagements Bunbury teams bring us most often: team collaboration software, workflow management, custom project management software, task management, Gantt charts and resource scheduling.
Exactly what you get
A system that runs a plant shutdown the way it has to be run: permits issued and closed in order, isolations gating the tasks they protect, contractor inductions checked before anyone is assigned, and the hard restart window tracked against real progress. The dangerous part comes off paper and into software that won't let a task start until its permit and isolation are valid, with a full audit trail for the safety review afterwards.
How to choose a developer in Bunbury
Choose a developer with experience in safety-critical or industrial software, not just office productivity apps, and ask how they validate permit and isolation sequencing. South West operators value honesty, so trust the developer who says Asana is fine for your office work and a custom build is only for the shutdown. This software connects to HR (Human Resources) software for inductions, field service management software and business intelligence dashboards, so confirm those links are scoped.
- !Vendor treats a shutdown as a task list; ask how permits and isolations gate tasks
- !No induction tracking; ask how an unqualified contractor is blocked from a task
- !No audit trail; ask how a safety review reconstructs what happened
- !Light on testing; ask how safety-critical sequencing is validated
- !Ignores mobile; ask how a crew accesses a permit on the plant
If project management is on the roadmap, field service management, booking & scheduling, mobile app usually follow within the year. Budget them as one conversation.
Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.
Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
Why can't Asana run our shutdown?
Asana and Monday are task lists with no concept of a permit to work, an induction status or an isolation that gates downstream tasks. The safety-critical sequencing that makes a shutdown safe ends up on a spreadsheet and paper, which is exactly the risk a custom system removes.
How does it enforce isolations?
An isolation or lock-out gates the tasks it protects, so a downstream task can't start until the isolation is verified valid in the system. That turns a paper dependency into an enforced one.
Can it check contractor inductions?
Yes. Inductions and competencies are validated before anyone is assigned a task, so an unqualified or expired-induction contractor is blocked rather than discovered after the fact.
What about the hard restart window?
The system tracks progress against the hard window, surfacing slippage early enough to recover or re-sequence, instead of finding out you'll overrun when it's too late.
How long does a shutdown system take?
About 3 to 5 months for permit and isolation coordination, or 5 to 7 for a full system with inductions, hard-window tracking and audit. The safety-critical testing is a significant part of the timeline.