Shutdown and Turnaround Manager Software for a Fixed Window
Kissflow runs the scope, permit and readiness checks, job-by-job execution tracking, and punch-list closure for a defined shutdown or turnaround, so contractors, operations, and maintenance work off one live schedule and the fixed startup date doesn't slip on a preventable delay.
Trusted by energy operators worldwide
A turnaround has one fixed date and a thousand tasks that all claim to be on the critical path.
Months of deferred maintenance, inspection, and modification work get compressed into the fixed window of a shutdown or turnaround, where every extra day of downtime costs production and every contractor crew on site adds coordination overhead. A spreadsheet can hold a worklist. It can't show which permits are still open the morning of day one, which punch-list items are blocking startup, whether this turnaround is tracking to its original scope or creeping past it, or give contractors, operations, and maintenance a single shared view of where the event stands right now.
Kissflow runs the shutdown or turnaround as a governed app rather than a spreadsheet someone updates between meetings: scope and worklist planning with jobs sequenced and assigned ahead of the window, a permit and readiness gate that blocks execution until materials and crew readiness are confirmed, execution tracking job by job against the schedule, punch-list closure tracked to the startup date instead of discovered one item at a time, cross-crew coordination so every team works off the same live schedule, and reporting that covers the whole event for the post-turnaround review.
Where a turnaround loses its fixed window to preventable delay
Scope creeps unmanaged
Additional work gets added mid-turnaround with no visibility into how it affects the schedule or the budget.
Readiness isn't verified
Execution starts on day one without a clear picture of which permits, materials, and crews are actually ready.
The punch list blocks startup blind
Outstanding items surface one at a time instead of as a managed list against a startup date.
Reporting happens after the fact
Progress against schedule and budget gets reconstructed at the post-turnaround review instead of tracked as the event runs.
Six modules. Built around a fixed window, not a generic project template.
Every module ships with default forms, routing, and dashboards. Configure each one to your turnaround's scope and readiness criteria.
Scope and worklist planning
Every job in the turnaround is scoped, sequenced, and assigned to a crew and a window before execution starts, avoiding mid-event surprises.
Permit and readiness gate
Execution can't start on a job until its permits, materials, and crew readiness are confirmed and logged against that worklist item.
Execution tracking
Progress against the schedule is tracked job by job, so a slipping item is visible the day it slips, not at the post-mortem.
Punch-list closure
Outstanding items are tracked to closure against the startup date, not discovered one at a time on the day itself.
Cross-crew coordination
Contractors, operations, and maintenance work off the same live schedule instead of separate spreadsheets.
Turnaround reporting
A live dashboard tracks schedule adherence, open permits, and punch-list status across the whole event, not just at the closeout meeting.
From request to system of record in four steps
Plan
The worklist is built, sequenced, and assigned to crews and time windows well ahead of the shutdown.
Assign
Permits, materials, and crews are checked against readiness criteria before execution starts.
Execute
Job-by-job progress is tracked against the schedule for the duration of the turnaround.
Close-out
Outstanding items are tracked and closed on the punch list before startup, with a full report behind the event.
What changes when turnaround management runs on Kissflow
| Process | Before Kissflow | On Kissflow |
|---|---|---|
| Scope management | Tracked in a spreadsheet that's out of date within days | A live worklist with sequencing and assignment |
| Readiness checks | Assumed, not verified, before execution starts | Confirmed against permits, materials, and crew before go |
| Execution tracking | Status collected verbally at the daily meeting | Tracked job by job in real time |
| Punch list | Surfaces item by item on the day of startup | Managed as a list against the startup date throughout |
| Cross-crew coordination | Contractors and operations work off separate spreadsheets | Everyone works off the same live schedule |
| Post-turnaround reporting | Reconstructed from memory at the review meeting | Available as a live report throughout and after the event |
Connects to your CMMS/EAM and permit to work systems; those stay the systems of record for work orders and permits
Kissflow doesn't replace your CMMS or permit to work system. It runs the scope, readiness, and punch-list coordination layer that ties them together for the duration of the event.


Built for a fixed-window event
Built for a fixed-window event
Scope, readiness, execution, and punch-list closure, structured around a turnaround's actual shape, not a generic project template.
Readiness confirmed before go
Execution can't start on a job whose permits or materials aren't ready, closing a common cause of turnaround delay.
Live status, not a daily meeting reconstruction
Schedule adherence and open items are visible in real time, not collected verbally each morning.
Live in weeks
Configure the worklist and readiness criteria in the visual builder, or describe the use case to the AI Builder.
One schedule for every crew
Contractors, operations, and maintenance work off the same live plan.
Governed from day one
Role-based access and a complete audit log are built into every job and every punch-list item.
Related apps
Asset Reliability & Turnaround Orchestration Workflow
Plan the reliability program that decides when and why a turnaround happens.
Site Onboarding and Commissioning Management System
Coordinate the stage-gate tasks that bring a site back online after a turnaround.
Job Safety Analysis (JSA) Management System
Break down each turnaround job's hazards and get sign-off before the crew starts.
We help turnaround teams close the punch list before startup, not after

“If a company cannot enable everybody to use AI, they will never get the true benefit of AI. Platforms like Kissflow allow us to put that capability in the hands of our users in a safe way.”
Vagesh Dave
GVP & CIO at McDermott International, Ltd
See The Full Story

“Advanced automation of all processes is easy to set up. I cannot imagine how to manage workflows without this software.”
Tanay Tiwary
Global Head - Digitalization & Business Improvement
See the Full Story

“Kissflow supports rapid application development by building a working application prototype in the shortest amount of time.”
Maria Theresa Cabigon
CIO, SN Aboitiz Power Group
See The Full StorySee what Kissflow can do for you
Talk to usGot questions? We're here to help.
Get SupportAsset Reliability & Turnaround Orchestration Workflow is the longer-horizon reliability program that decides when a turnaround is needed and why, drawing on asset condition data. Shutdown and Turnaround Manager is the execution app for a specific, dated turnaround: scope, readiness, execution tracking, and punch-list closure for that one window.
No. Your CMMS or EAM stays the system of record for work orders and asset history. This app runs the scope, readiness, and punch-list coordination layer for the turnaround event.
Yes, added or changed jobs go through the same scoping and readiness process as the original worklist, so schedule impact is visible.
A job can't move from planned to in-progress until its permit, materials, and crew readiness are confirmed in the app.
Whoever you assign, typically a turnaround coordinator, with items visible to every crew until closed.
Yes, within the scope and permissions you configure for their role.
Configuration and AI-assisted app generation move delivery from a multi-month program to a matter of weeks, though most teams stand this up well ahead of a planned turnaround date.
Kissflow is certified to SOC 1, SOC 2, SOC 3, and ISO/IEC 27001, with role-based access and a full audit log on every job and change.