Who can say yes to licensing commissioning punch list closure records? A decision tree for energy project advisors

Short answer

Introduce the contractor's CEO, with general counsel, and bring in the commissioning director as sponsor. The commissioning director knows which projects kept every test attempt and which were closed in a hurry, so they are the right first contact. They rarely hold authority to license company records alone. Platform administrators can open and export projects; that is access, not authority. Owner turnover terms and grid security details need counsel, and what can be licensed stays unknown until SourceX's rights review.

Visual briefFull-size diagram
A left-to-right approval tree: platform administrators and the document controller lead to the commissioning director as sponsor, two side branches flag owner handover terms and grid security details for counsel, and the lit path ends at the CEO with general counsel.
The lit path is the introduction. Amber branches mark records that need counsel, the project owner or SourceX's rights review.

This tree is part of the commissioning punch list closure guide, which covers what to inventory before closeout. Here the job is narrower: working out, for an energy project systems advisor, which person inside a commissioning contractor can say yes to a conversation about its closure history.

Access versus authority on a commissioning project

An advisor who has helped configure a commissioning platform often knows the people who run it best: the platform administrator, a lead commissioning engineer, the document controller. Each can describe records in detail. None of them decides what the company does with those records.

The distinction matters more in commissioning than in most workflows because the records sit between two parties. Commissioning practice, such as ASHRAE Standard 202, expects a final issues log that the owner accepts for the final commissioning report, so part of the record set reaches the owner by design, while the contractor's own working history, such as diagnosis notes and rejected test runs, usually stays behind. Who may license which part is a contract question, not a login question.

The decision tree, step by step

Work through the steps in order. Each answer points to the next person. The graphic draws the same path from the people who hold records to the person who signs.

  1. Who do you know today? If your contact is a platform administrator, field engineer or document controller, ask one question: who is accountable for how commissioning issues are closed across projects? The answer is usually the commissioning director or a VP of field operations.
  2. Will the commissioning director sponsor? Ask whether they would raise a discussion about the company's commissioning history with leadership. A yes makes them your working contact. A no ends the path for now; nobody else will carry it.
  3. Which projects are in question? For each group of projects, ask who the owner was and whether the contract required handover of commissioning records, restricted reuse or marked anything confidential. You need only the answer "yes, no or unsure", never the contract.
  4. Does any record describe grid or substation design? Protection settings, one-line diagrams and interconnection details can be security sensitive. If yes, counsel must be involved before scope is discussed.
  5. Who approves? The CEO, with general counsel advising. If a private equity sponsor or parent holds approval rights over company information, add them.

Stop when you have a sponsor and a named approver. That pair is the introduction.

Records, holders and deciders

The table separates the person who can describe a record class from the party who can decide about licensing it. Every entry is a role, not a document.

Record classWho can describe itWho decides about licensing it
Component and system test attempts, including failuresLead commissioning engineerThe contractor, after counsel checks owner contracts
Issues and resolution log, working historyCommissioning directorThe contractor, subject to owner contract terms
Final log and handover packageDocument controllerOften shared with or controlled by the project owner
Field changes and corrective work ordersProject manager or document controllerThe contractor
Protection settings, one-line diagrams, interconnection studiesElectrical engineering leadCounsel first; may be restricted for security reasons
Manufacturer test reports and equipment dataCommissioning engineerThe contractor, subject to manufacturer terms
Owner acceptance and sign-off recordsDocument controllerThe contractor and owner, per contract

In the United States, FERC treats specific engineering, vulnerability or detailed design information about critical electric infrastructure, beyond its general location, as Critical Energy/Electric Infrastructure Information with restricted access. The handling rules sit in federal regulation, 18 CFR 388.113, which governs how such information is designated, shared and disseminated. A contractor's interconnection files may or may not meet that definition. The point for a partner is only that such records exist and belong on counsel's list, not in a first conversation.

Branches that need counsel or the owner

Three side branches change scope without ending the discussion:

  • Owner handover and reuse clauses. If a contract hands commissioning records to the owner or limits reuse, those projects may be excluded or need the owner's consent.
  • Grid and substation detail. Security-sensitive design information is often excluded outright or heavily reduced. Many discussions can focus on the issue log and retest history instead.
  • Records under dispute. Projects with open warranty claims, liquidated damages or litigation stay out of scope.

Report these early in the referral brief template so the review starts in the right place. The system map for commissioning records helps the sponsor describe where each class lives without opening a project.

Two Illustrative paths

Two fictional companies, invented for this page.

Step340-person utility-scale EPC contractor160-person independent commissioning agent
Who describes the records?Platform administrator and document controllerLead commissioning engineer
Who sponsors?Commissioning directorFounder and principal engineer
Owner contract termsHandover required on large projects; working files retainedReports owned by clients; methods and templates retained
Side branchInterconnection files flagged for counselClient-owned reports flagged
Who approves?CEO, with general counselCEO, with outside counsel

The EPC path is short: one sponsor, one approver, one counsel question about interconnection files. The commissioning agent's path is narrower, because many reports may belong to its clients, though its own issue-tracking methods and retest histories may still be worth discussing. Both companies clear the 50-employee threshold; a much smaller specialist firm would not.

What only SourceX's rights review can settle

When the CEO agrees to talk, these stay open:

  • Rights: which projects, years and record classes the contractor may license after owner contracts and security limits are checked.
  • Scope and form: whether test histories, issue logs and field changes are all in, and how site and owner identities are removed.
  • Demand: whether any buyer wants commissioning closure histories when SourceX reviews them.
  • Terms: whether an offer follows, and on what payout and schedule.

The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Partners sign the Channel Partner Agreement before submitting introductions; the first valid introduction within the 90-day window is credited when the company submits a verified application, with one partner credited per company. Why data rights matter explains why the review comes first. For a first pass on fit, use the screening worksheet for construction and field services businesses; the construction punch list process page and the data center electrical contractor page cover neighboring record types, and preparing for a joint call with a company sponsor helps once the director agrees.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

Once the commissioning director has agreed to sponsor and to bring in the CEO, who can say yes, register as a partner, confirm the contractor on who qualifies and read the program terms before making the introduction.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

I administer the contractor's commissioning platform. Can I approve the discussion?

No. Platform administration lets you open projects and run reports; it does not give you authority to license company records. Describe which systems and years exist, then hand over to the commissioning director, who can bring in the CEO.

Does the project owner have to agree before a contractor discusses its commissioning history?

Sometimes. It depends on what each owner contract says about turnover, reuse and confidentiality. Counsel reads those contracts, and SourceX's rights review decides which projects and record classes are in scope.

What if the commissioning work was done by a subcontracted commissioning agent?

Then two companies hold parts of the record. The agent's own working files may belong to the agent, subject to its contract. Introduce whichever company actually holds and owns the records you are discussing, and note the split in the brief.

Sources

  1. refer.sourcex.si/terms
  2. govinfo.gov/content/pkg/CFR-2018-title18-vol1/pdf/CFR-20…
  3. ferc.gov/enforcement-legal/ceii/overview
  4. ashrae.org/file library/technical resources/standards a…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment