October 19, 2026

The Question I Get Asked All the Time About Quality Control

By JonCarlo Oren

Close-up of a man typing on a keyboard, ideal for business themes.
Photo by Jakub Zerdzicki on Pexels

"What Do You Actually Do All Day?"

I get this question a lot, usually from someone who just found out my title is Quality Control Manager. They picture me walking around with a clipboard, checking boxes, and pointing out things that need to be fixed.

There is some walking and plenty of checking. But the role involves much more than inspecting finished work. It takes preparation, technical review, coordination, documentation, and follow-through from the beginning of a project through closeout.

My experience includes supporting construction quality requirements on projects involving the U.S. Army Corps of Engineers (USACE) and the Naval Facilities Engineering Systems Command (NAVFAC). In that environment, you need to understand what the contract requires, how the work will be verified, and what documentation must support it.

So here is the longer answer I give when someone actually wants to know.

It Starts Before Anyone Picks up a Tool

A substantial part of quality control happens before installation begins. That is when the project team has an opportunity to identify questions, coordinate requirements, and prevent avoidable rework.

I review drawings, specifications, approved submittals, and other applicable contract documents. I look at how those documents fit together. Does the equipment being furnished match the design requirements? Do the mechanical and electrical drawings agree? Are the installation details clear? Have required inspections and tests been identified?

For example, an equipment schedule might identify one voltage while an electrical connection schedule shows another. Both documents may look reasonable when reviewed separately. Comparing them can reveal a question that needs to be resolved before the equipment is connected.

When I find a discrepancy, I discuss it with the superintendent and the appropriate subcontractor, then help bring the question forward through the project’s clarification or Request for Information process. Design questions need an authorized response from the appropriate design professional or reviewing authority.

Catching an issue early gives the team more options. Once equipment is installed, piping is concealed, or concrete is placed, the same issue can become much more difficult and expensive to address.

Inspections Are the Visible Part, Not the Whole Job

Once work begins, field inspections become a regular part of my day. I compare the installation with the applicable drawings, specifications, approved submittals, and manufacturer’s instructions.

Depending on the activity, that may include checking material identification, equipment ratings, installation methods, supports, connections, access, or required inspection and testing records. I also look ahead to work that will soon be covered or become difficult to reach.

On projects using the three-phase control process, that work follows a deliberate sequence. The preparatory phase addresses requirements, readiness, responsibilities, and inspection or testing needs before a defined feature of work begins. The initial phase checks the first representative portion of the installation and establishes the expected level of workmanship. The follow-up phase checks that the work continues to meet those requirements as it progresses.

The records behind those inspections matter. A useful report explains what was inspected, where the work occurred, what was observed, and what remains outstanding.

I use tools such as Excel, RMS, ECMS, and CMIS, depending on the project, to organize information and support inspection reporting, submittal tracking, deficiency logs, and corrective-action follow-up. Keeping those records current helps the team understand the actual status of the work.

Closing an item takes more than changing its status in a system. It requires verifying the correction and retaining the supporting documentation, including any required reinspection or test results.

The Part People Do Not Expect: Translation

One of the most important parts of my job is helping people reach a shared understanding of the requirements.

An engineer may describe a requirement through technical language and drawing details. A foreman approaches it through installation methods, access, sequencing, and the crew’s work plan. Both perspectives matter, and questions often become clearer when we review them together.

That might mean walking through a detail with a subcontractor, explaining a review comment, or showing how a proposed installation relates to an approved submittal. It also means listening. The people installing the work may identify a field condition that needs further review.

My responsibility is to help make the concern clear and get it to the right person for resolution. Where an interpretation or design change is needed, the team needs the appropriate written direction.

Good communication makes corrective work easier to understand and helps prevent the same issue from recurring. People should know what needs attention, which requirement applies, and what must happen next.

Why the Discrepancies Matter More Than People Think

A quality discrepancy can appear minor when it is first identified. Its significance depends on what it affects and how far the work has progressed.

An equipment rating that does not match the intended connection can affect installation and startup. A support detail that has not been resolved can hold up equipment placement. Missing test documentation can leave the team unable to demonstrate that a requirement was satisfied.

These are practical concerns. They can affect coordination between trades, system performance, maintenance access, acceptance, and the project schedule.

I try to identify those questions while the team still has time to address them in an orderly way. That involves explaining the concern clearly, identifying the applicable requirement, and tracking the response through completion.

It also requires judgment. Some issues can be corrected directly within the approved requirements. Others need formal clarification, additional review, or a decision from someone with the authority to make it. Knowing when to raise the question is an important part of the role.

What a Normal Day Looks Like

An average day usually includes a combination of document review, field observation, conversations, and follow-up.

I may start by reviewing planned activities, outstanding submittals, open deficiencies, and any inspections or tests that need coordination. Before a crew begins a new activity, I want to understand whether the required information, materials, and approvals are available.

During the site walk, I check ongoing installations and previously identified concerns. I speak with the superintendent and subcontractors about progress, upcoming work, and anything that could affect quality. If a condition needs clarification, I document it and help coordinate the next step.

Back at my desk, I update reports and tracking records, review responses, and follow up on outstanding items. When meetings involve USACE, NAVFAC, or other government representatives, clear records help support a productive discussion about completed work, open concerns, and upcoming requirements.

As closeout approaches, the focus also includes outstanding deficiencies, required test reports, record drawings, operation and maintenance information, warranties, and other contract deliverables. Preparing those records throughout the project makes final turnover more manageable.

The schedule changes from day to day, but the need for consistency remains. An issue identified on Monday still needs attention on Friday if it has not been resolved. Following it through is part of the job.

The Real Answer

When someone asks what I actually do, my answer is that I work with the project team to verify that construction meets the contract requirements and that the records support what was inspected, tested, and completed.

That takes time in the field and time reviewing documents. It takes clear conversations, careful questions, and the patience to follow an issue through to resolution.

The clipboard may still be part of the job. So are the drawings, the digital systems, and the daily coordination. What gives all of them value is the care behind the work and a record that accurately reflects what was built.

← All posts