---
title: What to Ask Before Hiring a Controls Integrator
description: Before hiring a controls integrator, ask these questions. They reveal how a firm defines the work, who does the engineering, and how startup is verified.
---

[News](https://www.liberty-automation.com/news)

# [What to Ask Before Hiring a Controls Integrator](https://www.liberty-automation.com/news/what-to-ask-before-hiring-a-controls-integrator)

 Written by [Liberty Automation](https://www.liberty-automation.com/news/author/liberty-automation) | Nov 16, 2026, 5:52:33 PM

**QUICK ANSWER**

The most important questions to ask before hiring a controls integrator are not about price. Ask [how the firm defines the work](https://www.liberty-automation.com/news/how-controls-project-gets-scope) before it quotes, who will actually do the engineering, how it verifies I/O before startup, what documentation you receive at project close, and how it handles field conditions that do not match the plan. Liberty Automation answers those questions the same way on every project: the project manager is the lead engineer, every installation includes 100% I/O verification, and every project closes with a complete documentation package built for the team that has to support the system afterward.

# **What to Ask Before Hiring a Controls Integrator**

Hiring a controls integrator for a [PLC upgrade](https://www.liberty-automation.com/plc-hmi-programming), a panel build, or a line integration project is a different kind of buying decision than ordering components or contracting routine maintenance.

The technical risk is higher. The work is harder to define upfront. The outcome depends on what the integrator finds in the field, how it handles surprises, and whether the deliverables it leaves behind are usable by the people who inherit the system.

A lower bid does not automatically mean a lower-cost project. A firm that prices from assumptions, skips field verification, or delivers thin documentation can create more cost and disruption than a more thorough firm would have, even when its first number was lower.

The questions below surface how a firm actually works, not how it presents itself. Each one includes what a strong answer sounds like and how Liberty Automation answers it, so there is a clear standard to hold every firm on the shortlist against.

## **Before price: how the work gets defined**

**How do you define the work before you quote a job like this?**

This is the most important question on the list, and the answer reveals more than any other.

A strong answer describes a process: reviewing existing documentation, walking the machine or line, identifying I/O, verifying communication dependencies, confirming hardware constraints, and writing down assumptions. The firm should say what it needs from you to price accurately and what stays open until it can see the system.

A weak answer is a number based on your description alone. That number may look competitive. It is also more likely to grow once field conditions do not match what was assumed.

The practical test: ask the integrator to walk through the last project where the work changed after it started. What caused it? How was it handled? What would have prevented it? A specific answer shows a firm that learns from its projects. A vague one is a signal.

**How Liberty answers:** Liberty builds the plan from the machine, not from a description. On retrofits, the process starts with detailed reverse engineering: documenting what exists and mapping undocumented wiring and logic before committing to a number. The effort is sized to the job. On a [Siemens S5 to Rockwell retrofit](https://www.liberty-automation.com/news/case-studies/obsolete-plc-retrofit-siemens-s5-to-rockwell), the existing schematics were known to be accurate, so the plant's own maintenance staff pulled the I/O counts device by device while Liberty did the engineering. The plan was delivered in about a week instead of a month. Discovery is there to remove guesswork, not to add process.

**What information do you need before you can give a dependable estimate?**

A rigorous integrator will name specific items: current drawings and their condition, existing program files and backup status, I/O count and type, communication architecture, panel condition, production window constraints, and any known modifications to the existing system.

An integrator who says it can price the job from a phone call is either pricing with heavy contingency or pricing without accounting for work it will still need to do.

| **What they ask for upfront** | **What it signals** |
| --- | --- |
| Current drawings, program backups, I/O list | Pricing the actual job, not a description of it |
| Machine walkthrough or site visit before quoting | Field-first approach: verify before assuming |
| Communication architecture and device list | Awareness of integration dependencies |
| Production window and access constraints | Startup planning built into the estimate |
| Minimal information, fast turnaround | Heavy contingency or missing work |

**How Liberty answers:** The first conversation with Liberty covers the project's technical requirements, timeline, success criteria and ongoing support needs. Liberty's stated approach is to establish fit, not push a sale. If the project is not a good match, that is better to know before anyone commits.

## **Who does the work, and how it gets verified**

**Who will actually do the engineering on my project?**

Some firms sell a project with a senior engineer in the room and staff it with someone else. Ask who will design the system, who will write the program, who will be on site for startup, and who you will call six months later. Ask for names, not roles.

**How Liberty answers:** At Liberty Automation, the project manager is the lead engineer. Senior staff handle every project from initial assessment through final commissioning, so you speak directly with the person who designed your system, not a sales rep or a middle layer. Nothing gets lost in a handoff, because there is no handoff.

**How do you handle I/O verification before startup?**

I/O verification is one of the clearest differences between a thorough integrator and one that shortcuts commissioning. The answer shows whether the firm treats verification as a standard part of the job or as optional depending on budget.

A rigorous answer describes a point-to-point process: confirming that the field device, wire, terminal, I/O address, PLC tag, and machine function all agree. That is not the same as forcing outputs and watching indicator lights. It confirms that what is labeled matches what is connected, and that what is connected does what the logic expects.

Skipped or compressed I/O verification is one of the most common sources of startup problems that carry into production. If the answer is vague, such as "we do standard commissioning," push for specifics.

**How Liberty answers:** Every Liberty installation includes complete system checkout, 100% I/O verification, IQ, OQ, and PQ when required, and functional testing, followed by operator training. Every point is checked, not a sample.

**What does your startup process look like for a project of this type?**

Startup is where every design assumption gets tested against the real machine. An integrator with a defined startup process will describe what gets checked before production runs, how fault conditions are tested, what the operator walkthrough covers, and how the system is handed to the plant team.

Ask specifically: what happens if something assumed to be working does not work during startup? How is it tracked? Who owns the fix, and how does it affect the schedule?

**How Liberty answers:** On the S5 retrofit, the processor replacement and the network bridging old and new devices were completed during the plant's planned winter shutdown. On the first day running product, the line was making A-grade product before the sister plants/lines were running.

**What programming standards do you follow, and can I see an example of your code structure?**

Clean, modular, commented PLC and HMI code is not universal. It reflects a firm's standards and the discipline it applies when nobody is watching. Ask how routines are organized, how faults are handled and displayed, how logic is documented inside the program, and what the HMI standards are for operator interaction.

Two references are useful here. [IEC 61131-3](https://webstore.iec.ch/en/publication/68533) is the international standard that defines PLC programming languages, including ladder diagram, structured text, and function block diagram. [ISA-18.2](https://www.isa.org/standards-and-publications/isa-standards/isa-18-series-of-standards) is the widely referenced standard for alarm management. A firm does not need to cite either one by name, but it should be able to explain how its code and alarms are organized.

**How Liberty answers:** Liberty's programming follows industry best practices with clean structure, comprehensive documentation, and verified backups, so the system can be supported for the life of the equipment. Liberty works in [PLC and HMI programming](https://www.liberty-automation.com/plc-hmi-programming) on Allen-Bradley/Rockwell and most major platforms, including legacy SLC, PLC-5, Siemens, GE, and Mitsubishi replacements.

## **What you receive at project close**

**What documentation is included in the project deliverables?**

The answer should include updated electrical drawings that reflect the field condition, current PLC and HMI program files with version information, an I/O list that matches the installed hardware, any network or communication configuration documentation, and operator or maintenance reference materials that fit the project.

Ask specifically: are the drawings as-built or as-designed? As-built drawings reflect what was actually installed. As-designed drawings reflect the original design intent, which can drift from the field during installation.

**How Liberty answers:** Every Liberty project concludes with a complete documentation package, including schematics, program backups, operation manuals, and maintenance schedules when specified. The package is built for the maintenance team that inherits the system, not just for the project file. See what goes into Liberty's [control panel](https://www.liberty-automation.com/control-panels) work.

**What access will we have to the PLC and HMI programs after the project?**

Ask this before the project starts, and get the answer in writing. Your team should receive the program files it needs to back up the system, troubleshoot it, and keep the machine running. A program your team can't access when a fault comes up turns routine maintenance into a service call.

It's also worth clarifying what that access covers. Having a copy of the program for your machine is not the same as owning the software. Ask whether the files are provided for the delivered machine only, or whether they can be used on more equipment. If you plan to build more of the same machine, bring that up early so the agreement covers it.

**How Liberty answers:** Every Liberty documentation package includes program backups. Your team has what it needs to back up the system and keep its machine running. The files are provided for use on the machine Liberty delivered. If duplicate machines are part of the plan, Liberty can address that before the project starts.

## **What happens when things change**

**Have you worked on this type of machine or process before?**

Relevant experience reduces startup risk. This is not a knockout question, since good integrators regularly work outside their direct experience. But the answer shows whether the firm's confidence comes from comparable work or from general controls capability.

**How Liberty answers:** Liberty's work covers [obsolete control system retrofits](https://www.liberty-automation.com/news/modernizing-obsolete-control-systems-engineering-guide), [control panel design and build](https://www.liberty-automation.com/control-panels), servo and motion control, HMI and SCADA, vision inspection, equipment integration, and safety system modernization. Published examples include the [S5 retrofit](https://www.liberty-automation.com/news/case-studies/obsolete-plc-retrofit-siemens-s5-to-rockwell) on a line with roughly 1,300 connected devices and a [custom assembly press with press-fit validation](https://www.liberty-automation.com/news/case-studies/custom-assembly-press-press-fit-validation).

**How do you handle changes that come up during the project?**

Every controls project turns up some field discovery: conditions that differ from the documentation, devices added without being recorded, or wiring that does not match the drawings. How an integrator handles those findings says a lot about how the working relationship will go.

A good answer describes a process: documenting the finding, telling the customer before acting on it, agreeing on the path forward, and tracking any cost or schedule impact openly and fairly. A firm that adjusts informally without documentation is a concern. So is one that absorbs every discovery silently.

**How Liberty answers:** On the S5 retrofit, many of the device communication files needed for the new network predated the modern internet. Liberty tracked down about 90% of them, hand-built roughly another 10% from device manuals, and replaced the last few devices with current models, a minor parts change the plant absorbed. It was handled within the original timeline and budget.

**What does your support look like after startup?**

Know what you are buying after the project closes. The more important question: if your maintenance team runs into a problem six months after startup, what is the process for getting help, and does that person know the system?

**How Liberty answers:** When a Liberty project finishes, the relationship does not end. Customers keep a direct number, the documentation, and ongoing support. Liberty also troubleshoots systems it did not build. After one minor post-startup adjustment, the S5 line has run without a single support call, and the plant is now having Liberty quote the same kind of retrofit on its next two lines.

## **How Liberty Automation measures up**

| **Question to ask** | **What a strong answer sounds like** | **Liberty's standard** |
| --- | --- | --- |
| How do you define the work before quoting? | A described process tied to the actual machine | Plan built from the machine, starting with reverse engineering on retrofits |
| Who will do the engineering? | Named people, the same ones from design to startup | The project manager is the lead engineer |
| How do you verify I/O? | Point-to-point, device to machine function | 100% I/O verification on every installation |
| What do you deliver at close? | Drawings, program files, I/O list, network documentation | Schematics, program backups, operation manuals, and maintenance schedules when specified |
| What happens after startup? | A known contact who knows the system | Direct number, documentation, and ongoing support |

Ask every firm on the shortlist the same questions and compare the answers side by side. Liberty Automation is built to hold up to that comparison.

For more on how the work is defined and priced, see [how a controls project is defined before pricing](https://www.liberty-automation.com/news/how-controls-project-gets-scope) and [what changes the number on a controls retrofit](https://www.liberty-automation.com/news/controls-retrofit-cost-what-changes-the-number).

## **Frequently Asked Questions**

**What is the most important question to ask a controls integrator?**

Ask how the firm defines the work before it quotes. The answer shows whether the integrator prices from field-verified information or from assumptions. An integrator that reviews drawings, visits the site, and confirms system details before quoting is more likely to deliver a project that stays on budget.

**Who should I expect to work with during a controls project?**

Ask for the names of the people who will design the system, write the program, and support startup. At Liberty Automation, the project manager is the lead engineer, and senior staff handle every project from initial assessment through final commissioning.

**How do I compare quotes from multiple controls integrators?**

Compare what each quote covers, not just the total. One proposal may include field verification, documentation, I/O checkout, and startup support. Another may assume the existing drawings are accurate and price only hardware and programming. Ask each firm what its estimate includes, what it assumes, and what would change the number.

**What documentation should a controls integrator provide at project close?**

At minimum: updated electrical drawings that reflect the installed condition, current PLC and HMI program files with version information, an I/O list that matches the installed hardware, and any communication or network configuration documentation. Ask whether the drawings are as-built or as-designed.

**Can I use the PLC program from a controls project on other machines?**

Not necessarily. Receiving program backups for your machine gives your team what it needs to support that machine, but it's not the same as owning the software. Before the project starts, confirm what the agreement allows: backup and support of the delivered machine, or use on more equipment. If you plan to build duplicate machines, raise it early.

**What is the difference between a controls integrator and an in-house controls engineer?**

A controls integrator brings outside engineering capability for specific projects without a permanent headcount commitment. Many plants use both: internal engineers for day-to-day work and an outside integrator for capital projects or platform expertise.

## **Talk Through Your Project**

If you are comparing controls firms for a capital project or looking for a controls partner for ongoing machine work, start with a fit call. Liberty Automation will go over the project's technical requirements, timeline and budget expectations, and success criteria, and give a straight answer on whether Liberty is the right fit before you commit.<https://www.liberty-automation.com/fit-call>

[View full post](https://www.liberty-automation.com/news/what-to-ask-before-hiring-a-controls-integrator)

```json
{
  "@context" : "http://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Liberty Automation"
  },
  "dateModified" : "2026-11-16T17:52:58.023Z",
  "datePublished" : "2026-11-16T17:52:33Z",
  "headline" : "What to Ask Before Hiring a Controls Integrator",
  "image" : {
    "@type" : "ImageObject",
    "height" : 459,
    "url" : "https://244365853.fs1.hubspotusercontent-na2.net/hubfs/244365853/What%20to%20Ask%20Before%20Hiring%20a%20Controls%20Integrator.png",
    "width" : 1080
  },
  "mainEntityOfPage" : "https://www.liberty-automation.com/news/what-to-ask-before-hiring-a-controls-integrator",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "height" : 60,
      "url" : "/hs/hsstatic/content_shared_assets/static-1.4092/img/default-amp-logo.png",
      "width" : 60
    },
    "name" : "News"
  }
}
```