Compressed Air Submittal Registers: Tracking Drawings Data and Open Questions After Award

After award, keep compressed air equipment submittals in a register that tracks each required document, its current revision, review status, responsible party, and next action. Link unresolved questions to the affected equipment and documents. A folder of PDFs alone won’t tell a project manager whether a package is ready for purchasing or still waiting on a decision.

The register should answer three practical questions: What has been submitted? What remains unresolved? What does that unresolved item affect? At Process & Power, we recommend keeping document review status separate from purchasing and fabrication release status. A reviewed drawing doesn’t necessarily mean every technical question or commercial release requirement has been satisfied.

Build the Register Around the Awarded Scope

Start with the purchase order, accepted equipment proposal, current drawings, specifications, and applicable addenda. Record their revision dates so the team knows which requirements formed the basis of the award. Don’t quietly replace that baseline when a later drawing arrives; log the change and identify what needs review.

Organize entries by equipment tag or package designation. Depending on the project, the compressor, dryer, receiver, filtration, condensate equipment, and package controls may need separate entries within one coordinated submittal package.

Identify required documents from the contract requirements rather than requesting every document available. Typical entries may include:

  • Equipment data identifying the selected configuration and rating conditions.

  • General arrangement drawings showing dimensions, connection locations, weights, and service clearances.

  • Electrical data and equipment wiring diagrams.

  • Controls interface information, including required signals and communication details.

  • Air treatment, receiver, and condensate accessory information.

  • A clearly identified list of deviations or proposed substitutions.

If preliminary budget selections remain in the project files, label them accordingly. They shouldn’t be mistaken for the awarded configuration or a firm equipment proposal.

Give Each Entry an Owner and a Next Action

A useful register can be a spreadsheet or part of the contractor’s project management system. The platform matters less than consistent fields and someone assigned to maintain them.

For each document or coordinated package, record:

  • Identification: Register ID, equipment tag, document title, and specification reference.

  • Document control: Supplier document number, revision, issue date, and controlled file location.

  • Submission history: Transmittal number, date submitted, date returned, and reviewer disposition.

  • Responsibility: Document preparer, designated reviewer, and person responsible for the next action.

  • Timing: Required return date and the procurement or coordination milestone it supports.

  • Open items: Linked question IDs, affected scope, and any release restrictions.

  • Closure: Response reference, revised document reference, and confirmation that comments were incorporated.

Keep the reviewer’s actual disposition wording. “Approved as noted,” “revise and resubmit,” and similar terms must be interpreted under the project’s procedures—not replaced with an informal “looks good.” If your team also uses an internal status, keep it in a separate field.

Preserve earlier revisions and review comments in the history, but clearly mark superseded files. Installation teams need an obvious current document, not several nearly identical PDFs with ambiguous filenames.

Track Open Questions Separately, Then Link Them Back

Document status and question status aren’t the same thing. A compressor drawing may be under review while a controls interface question awaits the owner’s automation team. Putting both into one “pending” cell hides who needs to act.

Use a linked question log with one issue per entry. Each issue should state the question, its source, the affected equipment or drawing, the decision owner, the required response date, and the consequence of leaving it open.

For compressed air equipment submittals, useful questions are specific:

  • Does the submitted capacity correspond to the specified operating pressure and stated rating conditions?

  • Are dryer performance assumptions consistent with the specified inlet and ambient conditions?

  • Does the arrangement provide the manufacturer’s required service access and ventilation provisions?

  • Who supplies and connects condensate piping beyond the package connection?

  • Which remote signals are required, and who provides field wiring and controls programming?

Route formal clarification requests through the project’s required process. An email can support the record, but it shouldn’t bypass an RFI or substitution procedure when one is required. A supplier’s proposed alternate remains a proposal until accepted through the engineer of record and project approval process.

Separate Technical Review From Release Authorization

Avoid using “approved” as shorthand for “everything can proceed.” Record technical review status, unresolved conditions, and purchasing or fabrication authorization separately.

A package might have reviewed dimensional drawings while electrical requirements remain unresolved. Another might be technically accepted but awaiting an authorized purchase order amendment. If the project permits a limited release, document who authorized it, exactly what may proceed, and what remains on hold.

Scope boundaries belong in this record too. Equipment supply doesn’t automatically include installation, electrical work, controls integration, testing, or startup. Assign those responsibilities from the actual contract and proposal. We can discuss equipment and installation needs, but our responsibility on a specific project must be confirmed in the agreed scope.

Review dates should connect to actual decisions. Work backward from the required-on-site date using supplier-confirmed production and shipping information, project review durations, and any resubmittal allowance. Don’t treat an earlier quotation’s schedule as current without confirmation.

Example: A Controls Question on a Tennessee Expansion

Consider a hypothetical facility expansion in West Tennessee. The compressor package submittal shows available remote signals, but the project documents don’t clearly identify which signals the facility requires or who will integrate them.

The register lists the controls document revision and review status. A linked question identifies the missing interface requirements, names the designated project contact responsible for coordinating an answer, and asks the supplier whether the decision affects factory configuration.

The contractor doesn’t close the issue merely because someone replies, “Coordinate in field.” Closure requires documented interface requirements, assigned wiring and programming responsibilities, and updated documents where needed. Any effect on equipment release remains visible until the authorized project team resolves it.

Use This Checklist Before Closing a Submittal Cycle

  • Does the register identify the current awarded scope and document revisions?

  • Have returned comments been assigned to specific people?

  • Are unresolved questions linked to the affected drawings and equipment?

  • Are deviations and substitution decisions explicitly documented?

  • Have revised utility and controls details reached the affected trades?

  • Are release restrictions and authorization records clear?

  • Does each closed issue point to a response and, where needed, a corrected document?

  • Can the field team identify the current reviewed package without searching email?

Bring the Document Requirements Into the Equipment Conversation

For an upcoming Tennessee compressed air package, send us the project scope, specifications, location, bid deadline, required-on-site date, and estimator or project manager contact through our Contractor Bids page. Include required submittal documents and known open questions so we can discuss equipment pricing and coordination needs. You can also contact us about including Process & Power on relevant equipment bid lists.

Process & Power, Inc.

901-362-5500

1721 Corporate Avenue, Memphis, TN 38132

Brian Williamson

Creative and strategic Website & Graphic Designer with 15+ years of experience in design,
branding, and marketing leadership. Proven track record in team management, visual
storytelling, and building cohesive brand identities across print and digital platforms. Adept at
developing innovative solutions that enhance efficiency, drive sales, and elevate user
experiences.

https://www.limegroupllc.com/
Next
Next

Centrifugal Separator Purge Settings: Making Sure Collected Solids Leave the System