This template belongs to the defect closeout verification guide, which covers what to inventory before handover. Here you get the form itself: copy it, fill it in on a call with the quality manager, then check each line against the filter below before anyone forwards it.
The blank brief: eight fields to copy
Paste this block into an email. Replace every bracket with a short answer, or with the word "unknown".
- Contractor: [trade or sector, region, full-time staff at peak]
- Workflow: verifying that defects stay fixed, from punch item to owner acceptance, including items that reopen in a linked area
- Systems: [inspection or punch list platform; project management system; closeout folders or document control]
- History: [number of closed projects, first and last year, any gap or platform switch]
- Volume: [approximate punch items in total or per project, and how the figure was counted]
- Record owner: [quality manager, project controls lead, document controller]
- Authorized contact: [executive name and role, with counsel if known]
- Access event: [archive renewal, license change, sale or wind-down, with its documented date]
Two optional lines help when the answers are known: Open question (one sentence on what nobody can confirm yet) and Sponsor (the person who will forward the brief, usually the quality manager).
Filling each field without touching a record
Every answer below comes from memory, a report total or a contract, never from opening an item.
Contractor. Headcount is full-time staff at peak, excluding subcontractors, because that is the measure SourceX qualifies on. Trade matters too: a mechanical contractor's punch items look different from a finishes contractor's.
Systems. Name the type and, if the quality manager volunteers it, the product as plain text. Many platforms log each verification step with a role attached. Procore, for one, separates the people who mark work ready for review from the final approver who closes an item or marks it not accepted. If the quality manager confirms that kind of sign-off chain, write it down in three words, such as "approver sign-off logged": it tells SourceX every check carries a name and a date.
History. Count closed projects, not open ones, and note the year the current platform started. Projects from before a platform switch often sit in folders as PDFs, which is worth one phrase.
Volume. Project-level totals are enough. If the platform reports items per project, multiply a typical figure by the project count and say that is how the estimate was made.
Record owner. The person who administers the platform and the person who keeps closeout folders are often different. List both.
Authorized contact. A platform admin can describe exports but cannot license anything. The who-can-say-yes tree helps pick the executive.
Access event. Only a date with a source: an archive renewal in the platform contract, a planned migration, a sale. If there is none, write "none known".
The open question this workflow always raises
The note should name one unresolved issue, and for defect closeout verification it is nearly always the same: when a repaired defect reappeared nearby, were the two items linked to one root cause and accepted together, or does the record show two unrelated closures?
Why it matters to the reader of the brief: under the standard federal construction warranty clause, repaired or replaced work carries its own one-year warranty running from the date of the repair, so a defect that comes back has a second, dated clock attached. A trail that links the original item, the failed repair and the second acceptance shows how a defect was actually resolved. A trail that closes each item separately shows less. The brief does not need to answer the question; it needs to ask it plainly so SourceX can scope the review. The records across systems map shows which identifiers would answer it. This is general information, not legal advice.
The include-or-omit filter
Run each line of the finished brief through this table.
| Fine to include | Keep out of the brief |
|---|---|
| Trade, region and full-time headcount | Project names, addresses, unit or room numbers |
| Platform types and product names as plain text | Logins, exports, screenshots or report files |
| Counts of closed projects and punch items | Before and after photos, or descriptions of them |
| Year ranges and platform switch dates | Building owner or resident names |
| Whether reopened items were linked | Back-charge amounts or subcontractor names |
| Roles of record owners and the executive | Any estimate of what the records are worth |
| A documented access date and its source | Timing pressure the contract does not support |
Photos need the firmest line. Repair photos taken in occupied buildings can show people and belongings, so the brief may say "before and after photos attached to most items" and nothing more.
One completed brief (Illustrative)
Written for this page about a fictional 380-person mechanical contractor. Every value is invented.
| Field | Illustrative entry |
|---|---|
| Contractor | Mechanical and plumbing contractor, U.S. Midwest, 380 full-time staff at peak |
| Workflow | Verifying that defects stay fixed through owner acceptance, including reopened items |
| Systems | Inspection platform since year three; project management system; closeout folders for earlier jobs |
| History | 41 closed projects over eight years; first two years in PDF closeout binders only |
| Volume | About 9,600 punch items, from project-level totals in the platform |
| Record owner | Quality manager for the platform; document controller for closeout folders |
| Authorized contact | VP of operations, with outside counsel; quality manager as sponsor |
| Access event | Closed-project archive renewal, March 31, per the current platform agreement |
| Open question | Whether reopened items were linked to the original before the linking feature was used in year five |
The VP reading this knows what exists, how far back it runs, who keeps it and what is unresolved, and nothing in it identifies a building, a resident or a subcontractor.
After the brief is sent
If the VP agrees, the contractor applies and SourceX reviews record classes, rights and qualification. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. Whether owner contracts give building owners rights in some records, how photos would be handled, whether there is SourceX's current data needs and whether any offer follows all stay unknown until that review.
The contractor 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.
For the covering message, use the warm introduction brief. The construction punch list page explains the records to an owner who asks, the Procore export page covers one common platform, and construction company insolvency describes the case where the access event is a wind-down.
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 every line of the brief passes the filter and the quality manager is ready to forward it, register as a partner, confirm the contractor on who qualifies and read the program terms.