Project closeout introduction email: an annotated draft for construction technology advisors

Short answer

Email the contractor's president or CEO once closeout notes show whether approved design changes can still be traced from the RFI to the executed change order and final cost. Keep it to a subject naming the closeout, one paragraph on what the project team said, one on SourceX with your reward interest stated, and one offering an introduction that asks for a description only. No logs, no project names, no attachments. Below is the draft and a sticky note for each line.

Visual briefFull-size diagram
An email to a contractor's president builds up in three stacked blocks, subject, findings, SourceX and disclosure, and the ask, with a sticky note appearing beside each block saying what it does, and a footer listing what never goes in.
The draft in blocks with sticky notes. Braced placeholders come from your closeout notes.

This email is part of the project closeout guide for construction technology advisors, home of the continuity ledger. Most advisors send it after the project closeout meeting agenda ends in an opt-in.

The email, with placeholders

Contractors read email on site, often on a phone. Three short paragraphs and a one-word reply are what get answered.

Subject: Design-change records before {project_type} closeout files are archived

Hi {first_name},

Thanks for letting me sit in with {pe_name} during closeout. One question came up: of the approved design changes, how many still connect to their commercial outcome? {pe_name} said most RFIs on projects since {first_year} carry through to a change event and an executed change order, with bundled items and closeout settlements as the exceptions.

SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. Nothing is shared unless {company} agrees terms, and owner and design-team contracts are part of that review. So you know where I stand: I am a SourceX referral partner and may receive a reward from SourceX if a qualifying license completes. SourceX pays it separately, it never comes out of what {company} would receive, and it has nothing to do with my closeout work.

Happy to introduce you. SourceX would start with a description: number of closed projects and years, whether change orders cite RFI numbers, where records go after closeout and who can approve a talk. No logs or drawings. Reply "yes" or "not now".

{your_name}

Sticky notes, line by line

LineWhy it earns its placeNever put in it
Subject naming closeout and archiveTies the email to a dated, real event in the project life cycle"Data deal", "cash in", any figure
"Sit in with {pe_name}"Shows the facts came from the project executive, not from you browsing logsNames of subcontractors or building owners
The outcome questionRepeats the question as the team heard itAn opinion on what the records are worth
RFI to change event to executed change orderNames the chain at metadata levelRFI numbers, change order amounts, contract sums
"Bundled items and closeout settlements as the exceptions"Reports the two usual breaks honestlyDetails of any dispute or settlement
The SourceX sentenceStates accurately what SourceX doesNamed AI labs, claims about buyers
"Owner and design-team contracts are part of that review"Answers the contractor's first concernLegal opinions about who owns what
DisclosurePuts your interest in writing firstVague wording that hides who pays you
"Nothing to do with my closeout work"Keeps your advisory fee separate from the referralOffers to discount services
Description-only askDraws the metadata lineRequests for exports, drawings or a sample log
"Yes or not now"A one-word exitFollow-up pressure

Why the chain wording matters

AIA's G716 instructions say an RFI does not authorize changes in cost or time, and the G701 instructions say an executed change order records agreement on contract sum and contract time. The design question and the money therefore sit in separate documents by design. The email names both ends so the president recognizes what is being described. Procore's documentation describes creating a change event directly from an RFI when both tools are on the project; if the company works that way, write "change events created from RFIs" instead. For what leaves Procore in an export, see exporting Procore project data.

Why the disclosure is spelled out

The FTC's Endorsement Guides call for clear and conspicuous disclosure of an unexpected connection that could affect how a recommendation is weighed, including the chance of payment. Whether they govern a private business email is a question for your own advisers; the plain sentence costs nothing.

When the closeout facts differ

What you foundEdit to the draft
Change orders rarely cite RFI numbersReplace the second sentence of paragraph one with: "{pe_name} said the RFI and change order logs are kept separately, so links depend on memory."
The company archives to a file server at warranty startAdd: "Files move to {archive_location} when warranty begins."
Records sit with a project-level license that endsReplace the subject with "Project records before {tool} access ends on {date}" using only a confirmed date
The president wants the CFO involvedAddress both and name the CFO as the working contact
The company is a specialty subcontractorReplace "design changes" with "scope changes" and keep the rest

The introduction email builder helps with placeholders. Advisors who also support site IT can compare the MSP guide for construction companies, and the punch list process page covers another closeout record.

Facts to confirm before sending

  • Records: closed projects and years with a consistent RFI and change order practice, and the systems that hold them.
  • Ownership: which prime contracts or design agreements carry confidentiality terms. "To confirm" is acceptable.
  • Authority: the recipient can approve a licensing discussion.
  • Fit: 50+ full-time employees at peak (contractors excluded, full-time field staff on payroll counted), 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.

Unknown until SourceX reviews it: demand for design-change records, the project-by-project rights result, any offer and any reward. If the archive context checklist shows the logs will be split at archive, mention it.

After the president answers

"Yes": submit the introduction through your partner account with the president's details and step back. "Not now": note the date and do not chase. Sign the Channel Partner Agreement before submitting. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, one partner per company. Illustrative only: a company paid USD 400,000 on its first qualifying completed handoff would mean a reward of USD 70,000 (the USD 50,000 floor plus 5% of the payout, which beats 15%), and the floor applies once per company; this is not a promise of earnings. See the rewards page for each condition.

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.

Before the draft goes to the contractor's president, register as a partner, confirm the company against who qualifies and read the program terms behind your disclosure line.

  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

Should the email mention the project where we found the links?

Only in general terms, such as a recent healthcare project, and only if the owner is comfortable. Project names can identify the building owner and design team, whose contracts may carry confidentiality terms.

What if the president asks for a ballpark reward figure?

Point to the rewards page. The default reward on a company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, and it depends on a qualifying paid transaction of at least USD 100,000. A number in the email reads as a promise.

Can the project executive send the email instead of me?

The introduction has to come from you as the partner, but it can go to the president with the project executive copied, so the person who knows the records is in the thread.

Sources

  1. help.aiacontracts.com/hc/en-us/articles/1500009325281-Instructions…
  2. help.aiacontracts.com/hc/en-us/articles/1500009322061-Instructions…
  3. support.procore.com/products/online/user-guide/project-level/rfi…
  4. ecfr.gov/current/title-16/chapter-I/subchapter-B/part…
  5. refer.sourcex.si/terms
  6. refer.sourcex.si/rewards

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