LEED v5 is now available for BD+C, ID+C, and O+M projects, and USGBC says Arc manages LEED v5 registration, documentation, and review. For Tennessee contractors, that makes commissioning documentation less of a sustainability talking point and more of a project-controls issue: who owns the records, where they live, and when the team checks them before testing and turnover pressure collide.

That matters on commercial work across Middle and East Tennessee because project teams are often coordinating multiple trades, startup windows, owner training, and closeout at the same time. If commissioning records stay fragmented until the end, the cleanup lands on the PM, superintendent, and trade partners all at once.

Practical takeaway: treat commissioning documentation as a tracked workflow from preconstruction through turnover, not as a final closeout task.

Key Takeaways

• USGBC says LEED v5 is available for BD+C, ID+C, and O+M projects.
• USGBC support guidance says LEED v5 project registration, documentation, and review are managed in Arc.
• USGBC guidance says teams should submit the documentation specified in the applicable LEED reference guides for each credit or prerequisite pursued.
• For Tennessee contractors, the controllable part is usually not the rating decision itself. It is document ownership, version control, and timing.
• A role-based checklist can help GCs and trades decide what they likely need to collect early and what to confirm with the commissioning authority or LEED submission lead.

A Better Tool: Who Usually Touches What

The exact package depends on the project’s rating system, prerequisite or credit path, and commissioning plan. Still, one recurring problem on commercial jobs is that teams assume someone else is handling a record when no one has actually been assigned ownership.

Use this scoping tool early in preconstruction. It does not replace project-specific LEED requirements; it helps the team decide where to confirm responsibility before records start piling up.

The Three Decisions To Make Before Testing Starts

If a Tennessee GC or trade partner wants a simple way to reduce late-stage confusion, these are the three decisions that matter most:

1. Name one documentation lead on the contractor side. That person does not create every record, but they track what is missing and where the current version lives.
2. Build one shared file structure before collection begins. Waiting until closeout usually means multiple naming systems, duplicates, and unsigned drafts.
3. Set at least one review point before startup or functional testing. Missing forms are easier to fix before crews demobilize or move to the next phase.

This is where the Tennessee angle becomes operational, not decorative. On fast-moving commercial projects in markets like Nashville, Knoxville, and Chattanooga, teams are often balancing schedule pressure, trade coordination, and closeout demands simultaneously. Better commissioning documentation control is one of the few fixes that does not require a redesign or a new procurement decision. It requires earlier discipline.

A Short Contractor Checklist

Preconstruction

• Confirm which systems in your scope are being commissioned.
• Get the current OPR, BOD, and commissioning plan if your work depends on them.
• Assign one contractor-side documentation lead.
• Set one folder structure and naming rule.
• Identify who will ultimately handle Arc uploads or package assembly.

Construction

• Collect approved submittals for commissioned systems in one location.
• Track substitutions or field changes that affect the documented basis of the work.
• Gather startup records and checklists as they are completed, not weeks later.
• Keep issue logs current with owner, status, and next step.
• Run a gap review before functional testing starts.

Closeout and Turnover

• Finalize test records and clearly label unresolved items.
• Collect training agendas, attendance records, and turnover materials.
• Make sure the submission lead can find the current version of each required file.
• Check that turnover records match the latest approved project conditions.

Warning Signs You Need A Documentation Reset

• The PM, superintendent, and trades are working from different versions of the commissioning plan.
• Approved submittals for commissioned systems cannot be found quickly.
• Startup forms are still sitting in inboxes instead of the shared project file.
• Substitutions were accepted in the field, but the related documentation trail is unclear.
• Testing dates are approaching, and forms are still incomplete or unsigned.
• The Arc submission lead is still asking trades which records exist.

What LEED v5 Actually Requires You To Verify

USGBC’s documentation guidance is simple at a high level: the team should submit the documentation specified in the applicable LEED reference guides for each credit or prerequisite pursued. That is why contractors should avoid making assumptions based on an older project or a different rating path.

In other words, good organization helps, but it does not tell you by itself which forms are required on your job. The project team still has to confirm the exact LEED path in use and the commissioning requirements attached to it.

Next Step For Tennessee Contractors

Before the next startup or testing window on a LEED job, hold a 15-minute review with the PM, superintendent, and affected trades. Confirm who owns the log, where files are stored, and which records are still missing. That small check is often more useful than a last-minute closeout scramble.

For teams that want stronger management habits across projects, ABC Greater Tennessee offers education resources for commercial construction professionals in Middle and East Tennessee. For a related operations read, see ABC Greater Tennessee’s article on project technology and management systems.