# Project closeout meeting agenda (15 min) | SourceX

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

Take 15 minutes at the end of a closeout coordination meeting and split them into five three-minute blocks: project count, RFI references, exceptions, archive and ownership, then the decision. The core question, which approved design changes retain their commercial outcome, is answered across blocks two and three by the project executive. The owner closes with one recorded outcome: introduce the company's authorized contact to SourceX now, revisit after archive, or stop. All answers are descriptions; no logs are opened.

This agenda belongs to the [project closeout guide for construction technology advisors](/guides/moment-project-closeout-construction-technology-advisors), which holds the continuity ledger. Use this page to run the conversation.

## Who sits at the table

| Person | What only they can answer | Speaks in blocks |
|---|---|---|
| Project executive or senior project manager | How RFIs, change events and change orders were linked on this and earlier jobs | 1, 2, 3 |
| Project accountant or controller | Where bundled and settled changes were booked | 3 |
| Owner or CEO | Who owns closed-project records and who can authorize a licensing discussion | 4, 5 |

You chair and keep time. A phone timer set to three-minute laps works; when it goes, move on and log anything unfinished as a follow-up.

## The five blocks and what a good answer sounds like

Illustrative. A 210-person design-build firm wrapping up a school district renovation. The advisor runs the agenda straight after the final coordination meeting, while the superintendent is still on site.

| Minutes | Block question | Answered by | Good answer |
|---|---|---|---|
| 0-3 | Roughly how many finished jobs, and since what year, were run with the same paperwork habits? | Project executive | "Around 25 jobs since 2018, all on one platform and one set of templates." |
| 3-6 | When a design question turned into extra cost, does the priced change point back to the question? | Project executive | "On recent jobs, yes: pricing starts from the open question itself, so the number is carried across." |
| 6-9 | Which changes ended up combined or negotiated at the end, and is the result on paper? | Accountant, project executive | "Combined items name their sources in the description line; the final negotiation has a signed summary in the job folder." |
| 9-12 | Where does the job folder go once the building is handed over, and whose is it? | Owner | "It moves to cold storage after the one-year correction period. The district contract limits reuse on this job only." |
| 12-15 | Does the company want to hear how licensing of approved records works, and who would lead? | Owner | "Yes, I can authorize it. Our COO is the working contact." |

### Block two: listen for habit, not software

Under AIA's standard forms, a question to the design team (G716) carries no authority over price or time, while a signed G701 does. So a priced change only "remembers" its question if someone typed the reference in. Procore's help pages describe starting a change event from inside an RFI when both tools are switched on, which makes the habit easier. The project executive's offhand "pricing starts from the open question" is worth more than any feature list.

### Block three: the end-of-job squeeze

The last weeks of a job compress paperwork. Several small items get rolled into one signed change, and disagreements are traded off in a single conversation with the owner's representative. Neither breaks the record if somebody noted what went into the deal. Ask the accountant, who usually filed it.

### Block four: before the files move

Job folders often go to cold storage once the correction period starts, and some lose software access when a per-project license ends. Ask for the documented step, not an estimated date. [Exporting Procore project data](/systems/procore-export-project-data) covers what an export can carry; the [RFI log data type](/data-types/construction-rfi-log) explains why these logs matter.

## Answers that change course mid-meeting

| What you hear | Likely meaning | Adjust |
|---|---|---|
| "Every PM keeps logs differently." | Few consistent years | Ask which PMs or years were consistent; note the range |
| "Changes were priced in email." | Links depend on mailboxes | Note "partial", move on |
| "The building owner owns all project documents." | Rights may not sit with the contractor | Ask which projects; stop for those |
| "Files go to the owner at handover." | The contractor may keep only copies | Record what the contractor retains |
| "We are being acquired." | Authority may be changing | Ask who can authorize today, then pause |

## What to say before the decision block

Before minute 12, cover three points in plain words.

**What SourceX does.** 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 by having this conversation.

**Your interest.** You are a SourceX referral partner. If a qualifying license completes and every payment condition is met, SourceX may pay you a reward under the [terms](/terms). It is funded separately and never deducted from the contractor's payout. Illustrative only: a contractor paid USD 100,000 for a qualifying completed handoff would mean a USD 55,000 reward on that first qualifying transaction.

**Fit.** 50+ full-time employees at peak (contractors excluded; full-time field employees on payroll count, subcontractors do not), 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. Partners never collect RFIs, change orders or drawings.

## The outcome at minute 15

| Outcome | Fits when | Next move |
|---|---|---|
| Introduce now | Blocks two and three are yes or partial, ownership is clear for some projects, the owner opted in | Send the [introduction email](/resources/project-closeout-introduction-email) |
| Revisit after archive | The owner wants the archive step done first | Use the [archive context checklist](/resources/project-closeout-archive-context-checklist) and agree a date tied to the warranty start |
| Stop | The owner declines, or owner contracts restrict every project | Record the reason; closeout continues |

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, one partner per company; see [rewards](/rewards) for payment statuses. The [portfolio review agenda](/resources/portfolio-review-meeting-agenda-private-equity) shows the timed method in an investor setting, and the [fractional CFO guide for engineering firms](/guides/fractional-cfo-for-engineering-firms) is useful when finance prepares the case.

## 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.

If the 15 minutes ended with "introduce now", [register as a partner](/register), confirm the contractor on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you write the introduction.

## 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://refer.sourcex.si/terms
- https://refer.sourcex.si/rewards
