About IsoBuilder

We built IsoBuilder to make isolation design faster, simpler, and right the first time.

On a mine site, errors don’t usually come from lack of effort — they come from fragmented information: a redlined PDF, a spreadsheet copied five times, and a P&ID revision that changed after the plan was “final”. IsoBuilder keeps isolation design anchored to the drawing, reviewable by the right people, and traceable from first mark-up to final sign‑off.

What we mean by “Isolation Design”

  • Define intent on the P&ID — what’s being isolated, from where, and why.
  • Capture what matter for execution — isolation points, status, verification, and handover clarity.
  • Generate consistent outputs — isolation lists and packs crews can use without interpretation.
  • Control change — when the drawing or scope changes, you can see what’s affected and who approved it.

If you’ve ever lost half a shift to rework because one valve tag or boundary was wrong, you already understand the value.

Why we exist

Isolation planning is too often treated like paperwork. On site, it’s a control that prevents injuries, equipment damage, and costly downtime. We built IsoBuilder for teams who want isolation design treated with the same discipline as engineering: versioned, reviewable, and auditable.

The goal isn’t to “digitise a PDF”. The goal is to reduce rework, tighten the handover between planning and execution, and make change obvious before it becomes a problem.

Built around the way shutdowns actually run

IsoBuilder is designed for mining and heavy industry realities: remote teams, tight windows, fast scope changes, and multiple disciplines working in parallel.

You don’t need another diagramming tool. You need a controlled path from “this is the scope” to “this is the approved isolation pack” — without chasing version confusion.

  • Planners get structured isolation design they can trust.
  • Permit offices get consistent documentation and traceability.
  • Supervisors and isolators get clear boundaries and fewer surprises in the field.

  1. Start with the drawing
    Keep the isolation design anchored to the P&ID so everyone is working from the same boundary.

  2. Design the isolation
    Record isolation intent and critical details in a structured format — not free-text notes.

  3. Review with the right people
    Engineering, planning, operations and HSE review the same revision without email chains and mismatched copies.

  4. Approve and lock
    Know exactly what was approved, by whom, and when — and keep that history for audits and learning.

  5. Execute with clarity
    Generate consistent isolation outputs that crews can action confidently — then close out cleanly.

What you can expect from IsoBuilder

We keep our focus narrow: isolation design. That’s how we go deeper on the things that matter on site.

One source of truth

Keep the isolation design tied to the P&ID with clear revision history and ownership.

Change control & audit trail

Change is normal in shutdowns. The system should make it obvious, traceable, and reviewable.

Execution-ready by default

Outputs should support execution: clear boundaries, consistent lists, and fewer field surprises.

Built for heavy industry

Designed for high-risk industrial environments where accuracy and speed both matter.

Implementation that respects site reality

  • Start with one area or system. Prove the workflow on real jobs, then scale.
  • Match your standards. Conventions, review gates, and outputs should align to how your site runs.
  • Train the people who do the work. Adoption is won (or lost) with planners, isolators, and supervisors.

Where IsoBuilder fits (and where it doesn’t)

  • Fits: upstream of permits — design and review isolations before execution.
  • Complements: PTW / CMMS / document control — export or integrate as required.
  • Doesn’t replace: your procedures, delegated authorities, or engineering judgement.

Common questions from site

Is this another document repository?

No. IsoBuilder is an isolation design workflow. The point is structured design, review, and traceability tied to the P&ID — not storing PDFs in a nicer folder.

Will we have to change our PTW / isolation process?

You shouldn’t have to. IsoBuilder is built to support your existing governance and review gates. We focus on making the isolation design clean, consistent, and auditable so your process runs with fewer surprises.

Who is it for day-to-day?

The people who carry the isolation plan: maintenance planners, shutdown coordinators, permit offices, supervisors, and isolators. If the tool only works for engineers, it won’t survive a shutdown.

What’s the “win” you’re aiming for?

Fewer reworks and fewer ambiguous handovers. When drawings or scope shift (because they will), it’s obvious what changed and what needs review — before it becomes field confusion.

Trusted by teams who run critical shutdowns

Talk through your next shutdown isolation plan with someone who understands the constraints.