Crisphive

SATURDAY · 5:30 AM · TURNAROUND DAY 3

Industrial turnaround & contractor scheduling

One slipped inspection is blocking four crews.

Day 3 of the turnaround, and one vessel re-inspection is holding a weld crew, a scaffold modification, and the NDT signoff behind it. The schedule didn’t slip because planners got it wrong — it slipped because a turnaround is one giant dependency graph: inspect before weld, permit before entry, scaffold before either, and a critical path where every idle hour is invoiced. Software that ignores the graph hands it to a coordinator at 5:30 a.m. Crisphive carries the graph so your people don’t have to.

Who it's forTurnaround and maintenance managers coordinating contractor crews — from a single unit outage to a full-plant shutdownWhat it protectsPermit windows, job dependencies, the critical path, and every idle crew-hour the plant is paying for

Reshuffling this by hand: about 30 minutes of calls, texts and spreadsheet edits.

Get started freeThe job is waiting on the board

This demo replays a real kind of morning: one emergency lands, and every job finds a new slot without breaking a promise. See how it works ↓

Incoming — not on the board yetE-104 re-inspectWaiting 1:32

Tasks moved: 0Dependencies violated: 0Idle crew-hours: 0Notified: 0

Every field operations day is a dependency graph. Most software pretends it isn't — and hands the graph to a dispatcher to solve in their head, under pressure, forty times a day. We think the schedule should carry that weight, not your people. That's the whole company.

— Why Crisphive exists

How it fits your day — Copy link to this sectionLink copied

When the day changes, the schedule keeps up.

Crisphive is the layer that carries your day’s dependencies — every job, permit, crew rule, and promised date. So when something slips, the plan repairs itself instead of landing on a coordinator at the permit desk. Your day still keeps its promises, and nobody has to hold the whole graph in their head.

The day changes

The slip arrives however it comes — an inspector flags a re-inspect, a permit desk holds an entry, a crane no-shows, a weld fails visual. However it reaches you, Crisphive sees it as a break in the day’s dependency chain.

The schedule recomputes

The schedule recomputes the crews against every hard rule — job dependencies, permits, shift and fatigue limits, mob/demob — and hands back a new plan plus a backup.

Your team is notified

You confirm once. Your crews get resequenced and your contractors get notified — nothing else needed. The moment anything shifts again, you’ll know.

You never rebuild the day by hand. The schedule recomputes around the disruption, keeps every promise it can, and shows you exactly what moved before anything goes out. Confirming the new plan takes one click.

The rules of your day — Copy link to this sectionLink copied

Hard rules, not suggestions.

A schedule that ignores dependencies isn’t scheduling — it’s guessing, and an idle crew pays for the guess. Every plan Crisphive gives you respects every rule below. If the plan comes back, it satisfies all of them — no exceptions, no “hope the crew makes it.”

dependency

Dependencies drive the schedule

Inspect before weld, scaffold before either, test after all of it. That chain of dependencies is the schedule — built into every plan and never quietly broken.

critical-path

Critical-path protection

The schedule knows which chain is critical and absorbs slips into slack first. Watch the demo: six tasks move and the critical path slips zero minutes.

compliance

Permit-to-work windows

No entry without a live permit. Permit validity is a hard rule, and re-issues are planned like any other dependency with real turnaround time — shown on the plan, never billed.

coordination

Multi-crew coordination

Four crews, one vessel. When the plan shifts, every affected crew resequences together, so weld doesn’t show up to a deck scaffold hasn’t modified yet.

logistics

Mob & demob of heavy equipment

Cranes and vac trucks don’t teleport. Mobilization and demobilization carry real durations per asset, so the plan reflects the yard, not the whiteboard.

fatigue

Shift & fatigue rules

Turnaround shifts run hard. Fatigue and shift-length limits are hard rules — the compliant plan is the only plan Crisphive will return.

1

Add your crews and their certifications

Sign up and add your crews with their skills, certifications, and heavy equipment — API-510, CWB, scaffold access, the cranes and vac trucks — everything the schedule has to respect.

2

Bring in your jobs and customers

Bring in the turnaround’s scope and contractors — by import or right alongside the tools you already use — and the confirmed permits and promised dates come with them.

3

Let the day run itself

From then on the schedule keeps itself. Emergencies slot in, affected jobs move, and your team and customers hear about it automatically — you just confirm.

⏱ Most teams are live within a week — no technical setup

Outcomes — Copy link to this sectionLink copied

What changes for you. What your customers feel.

You — running the business

Protect the critical path without running the day by hand.

  • Reclaim your coordinator’s morning. The 5:30 wall-chart scramble becomes one confirmation click.
  • Keep the promised end date without heroics. The critical path is defended by the schedule, not by whoever shouts loudest in the meeting.
  • Stop paying crews to stand around. Resequencing fills slack instead of burning invoiced hours.
  • Have a defensible answer every time. The daily report shows exactly why the path held and what moved.

Your site & contractors

One slipped inspection stops idling four crews.

  • No crew stands around on the clock. When the plan shifts, resequencing fills their slack instead of leaving them idle.
  • Every contractor knows where to be next. A change in one scope gives everyone affected a clear next move, not a radio guessing game.
  • The critical path is defended by the schedule, not by whoever shouts loudest in the morning meeting.
  • The turnaround still ends on the day it was promised — and the daily report shows exactly why.

Running more than one branch?

Set the rules once. They hold across every crew and every site. The dependency, permit, and shift logic you set up for one turnaround carries to the next outage and the next site — so as you take on more work and more crews, growth stops multiplying the dispatcher chaos. One coordinator can run a bigger day, and every site plays by the same rules.

Never billed

Re-planning is free

Re-planning is free and unlimited. Turnarounds are volatile by the hour — recompute on every disruption without ever watching a bill climb.

Consistent

Dependable by design

Schedules come from a deterministic engine, not guesswork — the same situation always produces the same plan. AI helps explain the plan in plain language; it never decides who goes where.

Backup included

Always a plan B

Every urgent booking comes back with a recommended plan and a backup. If the customer declines the first window, the next-best option is already on the table.

Illustrative scenarios written in an operator's voice — composite examples of how Crisphive works, not verified customer quotes.

1,200 workers · TA season
A day-three slip on a vessel re-inspection used to mean rebuilding the wall chart overnight. Now the graph resequences around it, the critical path holds, and the crews behind it get real work instead of standing around at contractor rates. We closed our last outage almost two days early.

Ray Delgado

Turnaround Manager · Gulfline Refining Services

3 units · Annual TA
Permit-before-entry and inspect-before-weld are physics on our site, and this is the first scheduler that treats them that way. When a permit window moves, everything downstream moves with it — correctly. My 5:30 a.m. scramble is gone.

Ingrid Bauer

Maintenance Planning Lead · Northport Chemical

Contractor crews · Multi-site
On the contractor side, idle hours are how you lose a client's trust. Since the plant put Crisphive on the outage, my crews stopped getting parked behind holds nobody flagged. The daily report shows exactly what moved and why — that ends most arguments before they start.

Curtis Boone

Site Coordinator · Ridgeline Industrial Contractors

What happens when an inspection slips during a turnaround?
Every downstream job recomputes immediately — the critical path stays protected and idle crew time gets squeezed out, instead of one slip leaving four crews standing around on the clock.
Are permit-to-work windows respected?
Yes. Permits and job dependencies are hard rules, not preferences. Work is never scheduled outside its permit window, and dependent jobs always move together.
Can it coordinate multiple contractor crews?
Yes. Cross-crew dependencies are built in, so a change in one contractor’s scope resequences everyone affected — with the full move list in front of you before you confirm.
Does it plan mobilization and demobilization?
Mob and demob are scheduled work with their own duration and travel, not guesswork padding. The plan accounts for them the way your crews actually experience them on site.
How large a turnaround can it handle?
A full turnaround’s scope — thousands of dependent jobs across every crew. Crisphive is built for dependency graphs this size, not simple to-do lists, so you can plan the whole outage, not just one shift.
How does per-job billing work when the plan changes hourly?
You only pay for jobs you actually dispatch. Recomputes and cascades are free — which matters in a turnaround where the plan changes by the hour — and soft caps with usage alerts warn you long before any overage is billed.

Your schedule should survive a bad morning.

Start free and drop your worst turnaround morning into Crisphive — watch the day resequence itself around every permit, crew, and dependency before you confirm a thing.

Get started today

Questions? support@crisphive.com · Free to start — no credit card required

See how the scheduling engine worksPricing — pay per job scheduled