# Project closeout introduction email, annotated | SourceX

Canonical: https://refer.sourcex.si/resources/project-closeout-introduction-email
Last updated: 2026-11-05

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.

This email is part of the [project closeout guide for construction technology advisors](/guides/moment-project-closeout-construction-technology-advisors), home of the continuity ledger. Most advisors send it after the [project closeout meeting agenda](/resources/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

| Line | Why it earns its place | Never put in it |
|---|---|---|
| Subject naming closeout and archive | Ties 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 logs | Names of subcontractors or building owners |
| The outcome question | Repeats the question as the team heard it | An opinion on what the records are worth |
| RFI to change event to executed change order | Names the chain at metadata level | RFI numbers, change order amounts, contract sums |
| "Bundled items and closeout settlements as the exceptions" | Reports the two usual breaks honestly | Details of any dispute or settlement |
| The SourceX sentence | States accurately what SourceX does | Named AI labs, claims about buyers |
| "Owner and design-team contracts are part of that review" | Answers the contractor's first concern | Legal opinions about who owns what |
| Disclosure | Puts your interest in writing first | Vague wording that hides who pays you |
| "Nothing to do with my closeout work" | Keeps your advisory fee separate from the referral | Offers to discount services |
| Description-only ask | Draws the metadata line | Requests for exports, drawings or a sample log |
| "Yes or not now" | A one-word exit | Follow-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](/systems/procore-export-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 found | Edit to the draft |
|---|---|
| Change orders rarely cite RFI numbers | Replace 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 start | Add: "Files move to {archive_location} when warranty begins." |
| Records sit with a project-level license that ends | Replace the subject with "Project records before {tool} access ends on {date}" using only a confirmed date |
| The president wants the CFO involved | Address both and name the CFO as the working contact |
| The company is a specialty subcontractor | Replace "design changes" with "scope changes" and keep the rest |

The [introduction email builder](/tools/introduction-email-builder) helps with placeholders. Advisors who also support site IT can compare the [MSP guide for construction companies](/guides/msp-for-construction-companies), and the [punch list process page](/data-types/construction-punch-list-process) 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](/resources/project-closeout-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](/rewards) 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](/register), confirm the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) behind your disclosure line.

## Sources

- https://help.aiacontracts.com/hc/en-us/articles/1500009325281-Instructions-G716-2004-Request-for-Information-RFI
- https://help.aiacontracts.com/hc/en-us/articles/1500009322061-Instructions-G701-2017-Change-Order
- https://support.procore.com/products/online/user-guide/project-level/rfi/tutorials/create-a-change-event-from-an-rfi
- https://www.ecfr.gov/current/title-16/chapter-I/subchapter-B/part-255/section-255.5
- https://refer.sourcex.si/terms
- https://refer.sourcex.si/rewards
