Key takeaways

A maintenance contractor has finished repairing a pump during a plant turnaround. The work order is marked complete. But when the operations team asks for the inspection results, the supervisor has to search through emails. The latest drawing is in a shared folder, the contractor’s report is in a separate system, and approval to close the job is still pending.

The repair may be complete. The documentation trail is not.

This is a common problem during complex shutdowns and turnarounds. Multiple teams work to a fixed schedule. Contractors handle different work packages. Inspections uncover additional work, and engineering decisions may change after equipment is opened and examined. Each stage produces records, sometimes across separate systems.

When records are incomplete or disconnected, teams may struggle to confirm what was approved, which procedure was followed, what work was completed and whether the equipment is ready for handover.

Shutdown and turnaround documentation must connect the original work requirement to the approved scope, current technical instructions, execution evidence, inspection results and final equipment status.

Good documentation starts before the shutdown and continues through execution, verification and close-out.

Why shutdown and turnaround documentation becomes difficult to manage

A shutdown or turnaround brings together maintenance, engineering, operations, inspection, safety, procurement and contractor teams. Each group produces information that another group may need before work can proceed.

An inspection team may identify corrosion in a section of piping. Engineering must assess the finding. The maintenance planner may need to create an additional work order. Procurement may need to source materials, while the shutdown coordinator checks the effect on the schedule.

The information passes between several people before the job is complete.

Problems arise when these records are not connected.

Common documentation problems include:

• Incomplete work packs: Technicians receive job instructions without the latest drawings, inspection findings, material details, or acceptance criteria.
• Uncontrolled document revisions: Contractors or internal teams use outdated procedures or engineering drawings.
• Disconnected inspection reports: Inspection findings are stored separately from the work orders created to address them.
• Unrecorded scope changes: Additional work is agreed through conversations or emails without a complete approval and revision trail.
• Missing execution evidence: Work is marked complete without the required readings, photographs, test results, or inspection records.
• Late contractor submissions: Reports and completion documents arrive after the work has been carried out.
• Incomplete handover packages: The operations team receives equipment without a complete record of outstanding defects, inspection results, or approvals.

These problems can affect decisions during the shutdown.

A work order cannot be planned properly if the inspection finding behind it is missing. A contractor may carry out work using an outdated drawing. An operations team cannot assess equipment readiness from a completion status that has no supporting evidence.

The aim is to keep a traceable record of each job, from its identification to handover.

1. Establish what needs to be documented before the shutdown

Documentation preparation should begin during shutdown planning, before contractors arrive at the plant.

The first task is to establish the work scope and identify the information required for each job.

A shutdown scope may include preventive maintenance, statutory inspections, equipment repairs, modifications, equipment replacements, and corrective work carried forward from earlier operating periods.

Each proposed job needs a clear reason for inclusion.

A maintenance team may include a heat exchanger inspection because it is due. Another job may come from a recurring equipment defect, while a third may be required to address a finding from an earlier inspection.

These jobs should not enter the shutdown work list as unexplained task descriptions. The team should be able to trace each job to its source.

A shutdown scope register can include:

Information	What it records
Job or work-order ID	A unique reference for the proposed work
Asset ID and location	The equipment and exact area involved
Work description	What needs to be inspected, repaired or replaced
Reason for work	Inspection finding, maintenance backlog, reliability concern or planned activity
Technical reference	Relevant drawing, inspection report or engineering document
Priority and criticality	The importance of completing the job
Responsible team	The person or group accountable for the work
Approval status	Whether the job is proposed, reviewed or approved
Planning status	Whether the job is ready for detailed preparation

This register becomes the basis for developing work packs and coordinating the shutdown scope.

For organisations reviewing how maintenance information, work orders and asset history are managed outside the shutdown period, maintenance management software can help organise these records. Read our guide to industrial maintenance software to learn how digital tools can support maintenance planning and asset-related work.

Keep scope changes traceable

The approved scope may change after planning is complete.

A vessel inspection, for example, may reveal corrosion that requires further assessment and repair. The team may need to revise the work scope, obtain engineering approval, arrange materials and adjust the schedule.

The original scope should remain available after a change.

The organisation should retain:

• The original work requirement.
• The new finding or reason for change.
• The technical assessment.
• The decision and approval.
• The revised scope and affected documents.
• The schedule or resource changes.
• The final work and verification records.

This creates a record of how the job changed. It also helps shutdown managers tell the difference between work included in the original plan and additional work found during execution.

2. Build complete, asset-linked shutdown work packs

A shutdown work pack brings together the information required to complete a specific job.

It is more than a work order or a collection of attachments. It connects the asset, work scope, technical instructions, resources, safety requirements, and completion criteria.

A work pack for a pump overhaul, for example, may include the equipment identification, maintenance history, approved scope, relevant drawings, dismantling instructions, inspection requirements, replacement component specifications and testing requirements.

The exact contents depend on the job and the organisation’s engineering and safety procedures.

A practical work-pack structure may include:

Work-pack section	Information to include
Job identification	Work-order number, asset ID, equipment location and job description
Work justification	Maintenance history, inspection findings or engineering recommendation
Technical information	Approved drawings, specifications, equipment manuals and relevant procedures
Job instructions	Work sequence, task steps and technical requirements
Resources	Required skills, labour, tools, equipment and materials
Safety preparation	Risk assessment, permits, isolation requirements and applicable precautions
Inspection and testing	Inspection stages, test requirements and acceptance criteria
Completion requirements	Required evidence, inspection reports, approvals and sign-offs

Link the work pack to the correct asset

Asset identification needs careful attention.

A report may refer to a pump by its equipment tag, while a contractor refers to it by its location or a local job number. If these references cannot be matched, it becomes difficult to confirm which equipment the report covers.

Use a consistent asset identifier across work orders, inspection reports, drawings, photographs and completion records.

Where a job involves several components, the documentation should identify the relevant component or equipment location. A broad plant-area reference may not be enough.

Include acceptance criteria before work begins

Teams should know what counts as an acceptable result before carrying out an inspection, repair or test.

A pump overhaul may involve dimensional checks, component inspections, alignment requirements and a functional test. The applicable limits and test methods must come from the relevant engineering specifications, manufacturer requirements and approved procedures.

A test result without its acceptance criteria does not establish whether the equipment passed.

The work pack should identify the applicable requirements and the records needed to show that they were met.

For procedures that technicians need at the point of work, digital work instructions software can help make approved task guidance available in a structured format.

Maintenance workflow software can also help teams manage the steps connected to each job, from work preparation and assignment to execution updates and approval. During a shutdown, this can help track work-pack status and show which jobs are waiting for information or review.

3. Control document revisions throughout the turnaround

A shutdown may involve several versions of engineering drawings, maintenance procedures and inspection documents.

A drawing may be revised after an engineering review. A work instruction may change after a safety assessment. An inspection report may introduce additional requirements.

If teams continue using an earlier version, they may carry out work using information that is no longer approved.

This risk can increase when contractors and internal teams access documents through different channels.

A controlled document process should establish:

• Document ownership: Identify who is responsible for creating, reviewing and approving each document.
• Revision identification: Each controlled document should display its revision number, issue date and approval status.
• Current-version access: Workers should have access to the approved version that applies to their job.
• Superseded-document control: Earlier versions should be marked so they cannot be mistaken for current instructions.
• Change history: Record what changed, who approved the revision and when it became effective.
• Contractor communication: Ensure relevant contractors receive updated information and know which version applies.

Consider a contractor preparing to replace a section of piping. The work pack contains an earlier drawing, but engineering has since revised the routing.

If the revision is not shared, the contractor may prepare materials or perform work using the old design.

Storing the latest drawing on a shared drive does not solve the full problem. The team needs a reliable way to identify the approved version and make it available to the people doing the work.

For engineering drawings and controlled technical documents, the organisation should also define whether its official document management system remains the source of truth. A frontline workflow platform can provide access to approved documents without replacing the engineering document management system.

4. Connect inspection findings to scope changes and work orders

Inspection findings can determine what additional work must be completed during a shutdown.

An inspection may identify corrosion, cracks, leaks, excessive wear, damaged components, or other conditions that need further assessment.

The finding must pass through a defined process before it becomes completed maintenance work.

Consider a refinery piping inspection.

An inspector identifies an area of wall-thickness loss. The inspection report records the equipment reference, location, measurement and observation. Engineering reviews the result against the applicable assessment criteria and decides what action is required.

Depending on the finding, the action may involve:

• Further inspection or measurement.
• Engineering assessment.
• Repair or component replacement.
• Additional monitoring.
• A change to the maintenance or inspection plan.

The documentation trail should connect each step:

Inspection finding → Technical assessment → Approved scope change → Revised work pack → Execution → Verification → Updated asset history

This connection matters because an inspection report alone does not show that the required corrective action was completed.

The team must be able to trace the finding to the decision, approved job, work performed, and final verification.

It is also important to retain findings where no corrective work is required. A decision to continue monitoring an asset should have a documented technical basis and suitable follow-up requirements.

Maintenance inspection software can help teams record inspection findings against the relevant asset and keep supporting information with the inspection record. When a finding requires corrective work, teams can link it to the technical assessment and resulting work order, depending on the systems in use.

5. Capture execution evidence at the point of work

Once the shutdown begins, documentation moves from preparation to execution.

Paper forms, spreadsheets, emails, and separate contractor systems can create extra work. Information may be recorded in one place and transferred to another later. During a busy turnaround, delayed data entry can leave managers with an incomplete view of job progress.

A better approach is to record the required information close to the activity.

For each job, the execution record should capture the details relevant to that task.

These may include:

• Asset and component identification.
• Work-order reference.
• Date and time of execution.
• Person or team performing the work.
• Work performed and observations.
• Inspection readings and measurements.
• Photographs or videos where they provide useful evidence.
• Deviations from the approved work instructions.
• Materials or components replaced, where required.
• Test results and verification records.
• Required approvals and sign-offs.

Why asset identification and inspection results matter

Certain regulations specify the inspection records that covered employers must keep.

The US Occupational Safety and Health Administration’s Process Safety Management standard, 29 CFR 1910.119(j)(4)(iv), requires covered employers to document inspections and tests of specified process equipment.

The records must identify the date, the person who performed the inspection or test, the equipment serial number or another identifier, a description of the inspection or test, and its results. Covered equipment includes pressure vessels, storage tanks, piping systems, relief and vent systems, emergency shutdown systems, controls and pumps.

OSHA has also clarified that both positive and negative inspection findings matter to ongoing mechanical integrity. A record showing that no defect was found can still help when setting future inspection requirements. OSHA also recognises electronic records when the information remains easy to retrieve and access.

This is useful for shutdown documentation beyond the specific US regulatory setting: an inspection record should preserve the result, not just confirm that an inspection took place.

Avoid turning every task into a paperwork exercise

More fields do not automatically produce better records.

The UK Health and Safety Executive advises that inspection checklists should match the equipment and safety requirements. It warns that too much detail can make inspections burdensome and lead to superficial tick-box entries.

Documentation requirements should match the job.

A routine visual check does not need the same evidence package as a pressure test or a major equipment repair. The organisation should define what must be recorded for each type of work.

The aim is to capture enough information to show what happened, who was responsible, what was found and whether the required result was achieved.

6. Maintain traceability across contractors and internal teams

Contractors may perform a large share of the work during a shutdown. Specialist inspection agencies, maintenance contractors, engineering consultants and equipment vendors may all produce documents that the plant needs to retain.

Each organisation may have its own reporting formats, file naming rules and submission process.

The task is to make those records usable within the plant’s own maintenance and asset history.

A contractor’s job completion report should not remain an isolated attachment. It should be linked to the relevant work order and equipment.

Before work begins, agree on:

• The documents contractors must receive.
• The approved drawing and procedure versions.
• The information they must record.
• The inspection and test reports they must submit.
• The required completion evidence.
• The person responsible for reviewing and accepting submissions.
• The process for recording deviations and additional findings.

A contractor may complete a valve replacement and submit a job report. The plant team may still need material certification, inspection results, test documentation and confirmation that the valve was installed according to approved requirements.

The work should not be treated as fully documented until the required records have been reviewed and accepted.

A clear submission and review process can also reduce the time spent chasing documents from contractors during the final days of the shutdown.

7. Prepare mechanical completion and handover documentation

Completing the physical work does not by itself establish that equipment is ready for the next stage.

A job may be finished but still require inspection, testing, quality verification or engineering approval. Some items may remain open as punch-list actions.

The organisation needs clear completion and handover requirements.

For applicable projects, mechanical completion records may include:

• Completed work orders and work packs.
• Inspection and test reports.
• Relevant material and component records.
• Approved deviations and change records.
• Equipment checks and test results.
• Required inspection and quality sign-offs.
• Outstanding punch-list items.
• Records of defects or deferred work.
• Required release and handover approvals.

Distinguish completion from operational release

A mechanical completion sign-off confirms that defined construction, maintenance or installation activities have been completed against the applicable requirements.

It does not automatically confirm that the equipment or system is ready for operation.

Depending on the facility and project, further activities may be required. These could include commissioning checks, functional testing, pre-startup safety reviews, operational readiness checks, and formal release.

OSHA’s Process Safety Management standard requires a pre-startup safety review for new facilities and certain modified facilities before highly hazardous chemicals are introduced into the process. The review must confirm that construction and equipment match design specifications, suitable procedures are in place, relevant process hazard analysis recommendations have been addressed and employee training has been completed.

This requirement applies to covered US processes. Other jurisdictions and industries have their own requirements.

The handover package must show the equipment’s actual status and identify outstanding work. A completed work order should not count as automatic approval to return equipment to service.

Keep open items visible

A handover record should distinguish between:

• Work completed and verified.
• Work completed but awaiting documentation.
• Work requiring additional inspection or testing.
• Outstanding defects.
• Approved deferred work.
• Items that must be resolved before operation.

Each outstanding item should have an owner, status and agreed next action.

This helps prevent unresolved work from being missed in a general close-out report.

8. Use digital workflows to improve shutdown documentation

Digital tools can help connect information that may otherwise be spread across paper forms, spreadsheets, email and separate reporting systems.

Organisations should understand the role of each system.

A CMMS or enterprise asset management system may manage asset records, work orders, maintenance history and planning. An engineering document management system may control drawings, specifications and technical revisions. A frontline workflow platform can help workers access task information, complete checklists, capture evidence and submit work for review.

These systems can work together, but they do not necessarily replace one another.

For shutdown and turnaround documentation, useful digital capabilities include:

Capability	How it helps
Mobile forms and checklists	Gives workers a structured way to record task information at the point of work
Asset-linked records	Connects observations, photos and work updates to the relevant equipment
Photo and video capture	Provides supporting evidence of equipment condition and completed activities
Digital approvals	Records review and approval steps
Timestamped entries	Helps establish when work and observations were recorded
Offline access and synchronisation	Supports field teams working in areas with limited connectivity
Central reporting	Helps supervisors review submitted records and outstanding work
System integration	Connects frontline records with existing maintenance and enterprise systems, where supported

A digital maintenance workflow can connect records created during work preparation, execution and review. For shutdown teams, this may include work orders, inspection results, photographs, approvals and completion records. Digital inspection workflows can also help standardise how field teams record observations, measurements and supporting evidence across jobs.

Digital workflows can reduce the need to transfer information by hand between forms and spreadsheets. They can also make records easier to retrieve during execution and after the shutdown.

Digitising a poor process does not make it reliable. Organisations need to define which information is required, who is responsible for it, and how each record is reviewed.

How Telepresenz SmartOPS™ supports frontline documentation

Telepresenz SmartOPS™ is an AI-powered field operations platform with CMMS capabilities. It supports digital workflows, mobile checklists, asset tracking, approvals, photo and video evidence capture, reporting, remote assistance and offline work with synchronisation.

These capabilities can support parts of the shutdown documentation process where frontline teams need to record activities and share information with supervisors.

A worker carrying out a maintenance inspection can use a digital checklist to record observations and capture supporting photographs. A supervisor can review the submitted information and follow the defined approval process. The records can provide a more structured view of frontline activities than disconnected paper forms and informal updates.

These features can support maintenance workflow software requirements at the frontline, especially where teams need mobile task updates, asset-linked records and supervisor review.

SmartOPS can also integrate with wider operational systems, including ERP, MES, SCADA and IoT platforms, depending on the deployment and integration requirements.

Learn more about Telepresenz SmartOPS™ and its digital maintenance and field execution capabilities.

For approved work procedures and technical instructions, Telepresenz SmartITM™ can support access to digital work instructions and operational knowledge.

SmartOPS supports frontline work execution and documentation. Organisations may continue to use their existing engineering document management, planning and specialist turnaround systems for functions outside the platform’s scope.

Glencore reduced remote mine repair time by 85%

At Telepresenz, we deployed SmartOPS™ for Glencore Nickel Operations in New Caledonia to connect local field workers with engineering experts based in Perth, Australia.

The mining sites were spread across remote areas with limited connectivity. When equipment faults occurred, local workers could wait days or even weeks for an expert to reach the site. Travel also involved long flights and complex logistics.

Through SmartOPS™, field technicians used RealWear HMT-1 wearable devices to share live, hands-free video with remote engineers. Experts could view equipment, add visual annotations, share technical drawings and guide workers through maintenance and troubleshooting steps.

SmartOPS™ also adjusted video quality for low-bandwidth conditions. Support sessions were recorded and archived for audit and training.

The deployment delivered the following results:

The deployment also gave local technicians access to live guidance from experienced engineers, supporting skill development during maintenance work.

Read the Glencore New Caledonia case study.

9. Audit shutdown documentation before closing the project

The final documentation review should not be left until the last day of the shutdown.

Teams should check records as work packages are completed. This gives them time to request missing inspection reports, approvals or test results while the relevant people are still available.

A close-out audit can cover:

Audit question	What to verify
Is every completed job linked to an asset?	Work order and equipment references are consistent.
Is the approved scope traceable?	Original scope, revisions and additional work are recorded.
Are current document revisions identifiable?	Superseded drawings and procedures are not mistaken for approved versions.
Are inspection results available?	Reports include the required observations, measurements and results.
Is execution evidence complete?	Work performed, deviations, photographs and other required records are attached.
Are contractor submissions accepted?	Required reports and supporting documents have been reviewed.
Are completion requirements met?	Applicable inspection, test and approval records are available.
Are outstanding items assigned?	Punch-list actions and deferred work have owners and follow-up dates.
Is equipment status clear?	Handover and release requirements have been addressed.
Has asset history been updated?	Relevant maintenance and inspection records are retained for future use.

The audit should also identify recurring documentation problems.

If several contractors submit incomplete inspection reports, the organisation may need to revise its submission requirements. If work packs repeatedly contain outdated drawings, document distribution and revision control may need attention.

The close-out review can help improve documentation for the next shutdown.

Telepresenz SmartOPS™ supports digital frontline workflows, mobile checklists, evidence capture and operational reporting.

FAQs

---