Commissioning punch list closure referral brief: a fill-in handoff with a completed example

Short answer

A company introduction about commissioning punch list closure is a short brief the commissioning director can read, correct and forward to the CEO unchanged. It holds metadata only: company size and country, the technologies commissioned, the systems that hold test attempts, issue logs, retests and acceptances, years and rough volumes, any documented archive date, the open question, and who can authorize a licensing discussion. It contains no test sheet, site name, owner name or login. The blank form comes first, then one completed Illustrative example.

Visual briefFull-size diagram
A two-column brief card for a fictional utility-scale EPC contractor whose fields, from headcount to sponsor, fill in one at a time with Illustrative values, while a strip below lists what is never attached.
Illustrative: a completed commissioning punch list closure brief. Each entry describes records; none contains them.

This template belongs to the commissioning punch list closure guide. Fill it in after a first conversation with the commissioning director, using only facts someone at the contractor will stand behind.

Blank brief: ten fields to copy

Copy the left two columns and answer each field in a line or two. "Unknown" is an acceptable answer.

FieldWhat to writeWho usually knows
CompanySector, country, full-time headcount at peakOwner or CFO
Work commissionedTechnologies and scale, for example utility-scale generation, battery storage, substationsCommissioning director
Record classesEvery test run with its result, issue log entries, field changes, re-runs after repair, owner sign-offsCommissioning director
SystemsCommissioning platform, document control, project management tool, shared drivesCommissioning director with IT
CoverageProjects and years each system holds, plus any gap from an earlier platformIT or document controller
VolumeProjects a year, tests per project, issues per project, as estimates with their sourceCommissioning director
Access eventAny documented date: project archive rule, platform contract end, site office closureOperations or procurement
Open questionThe one thing nobody yet knows about how complete the test history isCommissioning director
Owner and sponsorWho owns the records day to day; who will sponsor the discussion internallyCommissioning director
Authorized contactThe CEO, who can approve a licensing discussionCEO's office

Write the answers in the company's words. If the director says "we kept every unsuccessful run from about year three", the brief says exactly that.

Writing each field so it survives review

The brief will be read by someone at SourceX who has never seen the contractor's projects. Each line should let them picture the records without seeing any.

  • Every run, not just the outcome. Say whether an unsuccessful test is kept as its own record or overwritten by the successful one. Testing is repeated until a system passes, so a contractor that keeps every run holds a different record from one that keeps only the final sheet.
  • The log in one line. Note whether the issues log records status and responsible party for each item, and whether closed items keep their history. The owner usually receives the closed log; the working history behind it is what the brief should locate. For solar projects, IEC 62446-1 describes the test and documentation package handed to the customer, which is a useful reference point for what the owner holds.
  • Handover versus working files. Write which records go to project owners at handover and which stay with the contractor. That one line saves counsel a week later.
  • Owner frameworks. Note whose commissioning rules a project followed. Some owners publish their own requirements; GSA’s P100 Facilities Standards, for example, require commissioning on GSA construction projects and describe documented checks from design into the first year after construction. A contractor that worked to several owner frameworks may hold differently shaped records for each, and the brief should say so in one line.
  • Volumes as ranges. "Roughly 25 to 35 sites over eight years" is honest and useful.
  • Dates only when documented. A project archive rule or platform renewal date is a real access event. Do not invent one.

Completed example (Illustrative)

A fictional contractor, invented for this page. Every figure is a placeholder, not a real company's.

FieldIllustrative entry
CompanyU.S. utility-scale EPC contractor, about 340 full-time staff at peak
Work commissionedUtility-scale generation, battery storage and project substations
Record classesEquipment functional tests with every run, site-level tests, issues log, field change notices, re-runs, owner sign-offs
SystemsCommissioning platform since year three, document control system, project management tool, shared drives for earlier projects
CoverageAbout 30 projects over eight years; unsuccessful runs kept on the platform only from year three
VolumeSeveral thousand test records a year; 150 to 400 logged issues per project, estimates from the director
Access eventProject files archived 12 months after final completion under current settings
Open questionWhen a component test that succeeded missed a site-level problem, does the issue record link the problem, the fix and the re-run?
Owner and sponsorCommissioning director owns the records day to day and will sponsor
Authorized contactCEO, with general counsel
Not sharedNo test forms, site names, owner names, grid design files, exports or logins

That brief is enough for a first review. It tells SourceX the company likely meets the size threshold, where the test history lives, how far back it goes, the one completeness question worth testing and who signs. The exception examples page shows the kind of case the open question refers to.

Three mistakes that stall a brief

  1. Attaching a sample. Even one redacted test form turns a metadata note into a disclosure. Describe; do not attach.
  2. Naming the wrong decider. A lead engineer who can open every project is not the authorized contact. The who-can-say-yes tree shows who else to involve alongside the CEO.
  3. Skipping the owner question. If large-project owners received full handover packages, say so. Leaving it out does not make it go away; it only delays the rights review.

How the brief travels

Send the brief to the commissioning director first and ask them to correct anything wrong. Then let them forward it to the officer with a short covering note; the warm introduction brief helps with that note, and the client opportunity brief generator produces a similar format for other workflows. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout.

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; the first valid introduction within the 90-day window is credited when the company submits a verified application. Buyer interest, the rights result, de-identification and any offer remain unknown until SourceX reviews the opportunity. Related sectors: energy and utilities and HVAC contractors.

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.

When the commissioning director has corrected the brief and confirmed that the CEO, who can approve it, will take the brief, register as a partner, check the contractor on who qualifies and read the program terms before sending it.

  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

Can I attach one test form so the reader understands the records?

No. A test form names a site, equipment and results, so it is the record itself. Describe its format instead, for example equipment functional test forms with a result field and a re-run count, and leave samples for SourceX's review with the company.

What if the commissioning director cannot give project counts?

Write a range they are comfortable with, or unknown, and note who gave the figure. A traceable estimate is more useful than a precise number no one will stand behind.

Sources

  1. refer.sourcex.si/terms
  2. webstore.iec.ch/en/publication/63726
  3. gsa.gov/system/files/P100 2024 Final (1).pdf

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