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.
- 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.
- 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.
- 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.
- 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.
- 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 class | Who can describe it | Who decides about licensing it |
|---|---|---|
| Component and system test attempts, including failures | Lead commissioning engineer | The contractor, after counsel checks owner contracts |
| Issues and resolution log, working history | Commissioning director | The contractor, subject to owner contract terms |
| Final log and handover package | Document controller | Often shared with or controlled by the project owner |
| Field changes and corrective work orders | Project manager or document controller | The contractor |
| Protection settings, one-line diagrams, interconnection studies | Electrical engineering lead | Counsel first; may be restricted for security reasons |
| Manufacturer test reports and equipment data | Commissioning engineer | The contractor, subject to manufacturer terms |
| Owner acceptance and sign-off records | Document controller | The 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.
| Step | 340-person utility-scale EPC contractor | 160-person independent commissioning agent |
|---|---|---|
| Who describes the records? | Platform administrator and document controller | Lead commissioning engineer |
| Who sponsors? | Commissioning director | Founder and principal engineer |
| Owner contract terms | Handover required on large projects; working files retained | Reports owned by clients; methods and templates retained |
| Side branch | Interconnection files flagged for counsel | Client-owned reports flagged |
| Who approves? | CEO, with general counsel | CEO, 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.