Back to all posts
Projects & Retrofits7 min read·October 26, 2026

What Files and Access Should a Controls Handover Include?

TB
ThynkBlox Automation Team
Automation Engineering

A PLC or SCADA project handover should include editable source files, current device configurations, as-built drawings, software rights, asset records and documented access. Require a witnessed check that your nominated maintenance team can open the supplied files using the agreed software and licences. Record any missing items and their operational consequences before accepting the handover.

What should the handover package contain?

Set the required deliverables before commissioning, with a named person responsible for each item. Use the table below as a starting point, then remove items outside the agreed scope and add equipment specific to your plant. Files are only part of handover; see the operator training needed before handover.

DeliverableWhat to requestWhat to check
PLC projectsEditable projects, comments, symbols and required librariesThe supplied project opens with its dependencies available
SCADA and operator-screen projectsEditable applications, graphics, scripts and alarm definitionsThe editor opens the project without unexplained missing components
Device configurationsCurrent settings for drives, instruments, gateways and network equipmentEach configuration identifies its device and installed revision
As-built drawingsElectrical drawings, panel layouts, network diagrams and I/O schedulesChanges made during installation and commissioning are included
Software and rightsRequired versions, licence records and agreed permissionsThe plant knows what it may use, modify and share with a maintenance provider
Access recordsAccount ownership, roles, recovery arrangements and remote-access detailsAuthorised plant staff can use the agreed access routes
Asset registerEquipment identifiers, models, locations and support detailsRecords match the installed equipment
Test and recovery recordsAccepted test results, unresolved items and recovery instructionsResponsibilities and remaining restrictions are clear

Treat this as an acceptance list. A folder containing many files is not evidence that every deliverable is complete or usable.

Which editable source files should you require?

Ask for the native, editable engineering projects used for the installed system. Agree separate deliverables for PLC logic, operator screens, SCADA applications and any custom integration software.

For each project, request the comments, tag descriptions, libraries, scripts, graphics and other dependencies needed to maintain it. Record the engineering software version and any required add-ons. Identify protected components explicitly and agree how future maintenance will work where their source will not be supplied.

Keep the editable project, deployment files and recovery backups clearly identified. Do not accept a file labelled “backup” without establishing what it contains and what work it supports.

Ask the supplier to state which delivered revision represents the accepted installation. If commissioning changes were made after an earlier backup, require an updated package and a record of those changes.

The expected behaviour should already be defined in the functional design specification. Use that specification to check that the handover covers the functions and interfaces actually delivered.

How should current configurations and drawings be recorded?

Require a configuration record for each device included in the project scope. Depending on the installation, this could include drives, remote I/O, instruments, communication gateways, switches and supervisory computers.

Identify each configuration by equipment tag, device model and relevant software or firmware version. Ask the supplier to explain how it was captured and whether any settings must be recorded separately.

For drawings, require an as-built issue that incorporates accepted site changes. Include terminal details, cable references, I/O assignments, network connections and panel layouts where relevant. Provide readable copies for maintenance use and editable originals where agreed.

Keep discrepancies visible. If a field connection differs from the drawing, assign responsibility for resolving it rather than leaving a handwritten note as the final record.

For a retrofit, include a clear boundary between retained equipment and new work. Our guide to planning a PLC retrofit around a shutdown window explains why that boundary belongs in the project plan.

What software rights and licences should be agreed?

Ask for a written record of what your plant is entitled to receive and use. Do not leave this to assumptions about who paid for the project.

Agree whether the plant may:

  • Open and edit the delivered projects.
  • Maintain them through another service provider.
  • Copy them for backup and recovery.
  • Install the required engineering software on nominated equipment.
  • Transfer relevant licences when equipment or maintenance responsibility changes.

Identify third-party libraries, protected code and separately licensed tools. For each restriction, document the maintenance route and who must provide support.

Keep licence evidence and activation or recovery instructions under plant control. Record whose account holds each entitlement, any renewal requirement and what happens when the original supplier's involvement ends.

Where proposed terms are unclear, resolve them with the supplier and obtain appropriate legal advice before acceptance.

How should credentials and remote access be handed over?

Require an access register, but keep passwords and other secrets in the plant's approved secure store rather than in general handover documents.

For each system, record the account owner, intended role, approval authority and recovery route. Cover engineering access, operator administration, supervisory computers, network devices and remote-support arrangements within scope.

Have an authorised plant representative demonstrate the access needed for maintenance. Confirm who can approve remote sessions, how access is withdrawn and who handles recovery if the usual administrator is unavailable.

Agree the treatment of temporary commissioning accounts and supplier access. Record any continuing support arrangement, including its owner and permitted use.

Acceptance should not depend on one supplier employee remaining reachable. Establish a plant-controlled route for obtaining authorised access and recovering the relevant accounts.

For ongoing support connections, see how vendors should get remote access to plant controls.

What belongs in the asset and maintenance records?

Create an asset register that helps a maintenance lead identify equipment without reconstructing the project.

For each relevant asset, request its plant tag, description, manufacturer, model, serial number, location and installed software or firmware version. Link it to the applicable drawing, configuration and spare-part record.

Also request support contacts, warranty information, agreed service responsibilities and any known replacement constraints. Mark unavailable information explicitly and assign an owner to close the gap.

Keep operating records separate from credentials. Include accepted operating instructions, alarm responses, maintenance precautions and recovery procedures within scope.

Where safety-related functions are involved, agree the required documentation and validation with a qualified assessor. Keep unresolved safety-related matters subject to that assessment and the plant's acceptance process.

What should the witnessed file-opening check prove?

Schedule the check before final acceptance. Use the actual delivery package and a nominated maintenance computer or other agreed engineering environment.

Ask the plant representative and supplier to work through this checklist together:

  1. Identify the supplied revision and its relationship to the accepted installation.
  2. Open each editable project in the recorded software version.
  3. Confirm that required libraries, graphics, scripts and other dependencies are available.
  4. Navigate representative logic, screens, alarms and interface settings.
  5. Verify that authorised plant staff can retrieve the required licences and access records.
  6. Record missing items, restrictions and the person responsible for resolving them.

Keep this check separate from changes to running equipment. Any connection, download or recovery trial needs its own agreed procedure, operating permission and precautions.

Opening a project satisfies only that acceptance item. Record separately how the supplied project was reconciled with the installed system, and what recovery validation was agreed and completed.

What common mistakes should you avoid?

Accepting readable documents without editable projects. Require both where future maintenance needs them.

Treating an early backup as the final handover. Reconcile the delivery with accepted commissioning changes.

Discovering licence restrictions during a breakdown. Settle permissions, dependencies and account ownership before acceptance.

Putting passwords in a widely shared folder. Use the approved secure store and document who controls access.

Leaving exceptions as verbal promises. Record the missing deliverable, its consequence, the responsible person and the closure condition.

Where full editable source is excluded by agreement, describe that limitation explicitly. Define the support and recovery arrangements the plant will rely on, then make the acceptance decision with that restriction visible.

What questions should be settled before acceptance?

Is a PDF copy of the PLC program enough?

If the agreed maintenance scope requires editing, require the native project and its dependencies as well. Use the PDF as a readable reference.

Must every handover include a live restore?

Specify recovery validation according to the project scope and operational risk. The file-opening check and a restore trial are separate acceptance items; agree suitable conditions for each.

Can the supplier retain remote access?

Agree this as part of the support arrangement. Record the purpose, approval process, responsible plant owner and withdrawal procedure.

What if a required file cannot be opened?

Record the failure and the missing software, dependency, permission or replacement file needed to resolve it. Repeat the affected check after correction before closing that item.


Planning a controls project or retrofit? Discuss the required handover package through our contact page, and include its acceptance conditions in the agreed project scope.

Next step

Want to apply this to your plant?

Every project starts with a fixed-fee assessment, and you can stop after the report.