Record type alone settles nothing. Two firms can each hold fifteen years of inspection notes, one owning most of what its inspectors wrote and the other holding mostly client material. The checklist below tells them apart without anyone opening a file.
What sits inside one field inspection note
In plain terms, a field inspection note is the record an inspector makes at a site or an asset: what was looked at, what was found, how it was rated and what should happen next. Inside one note, the parts often come from different hands.
| Part of the note | Typical author | Why it matters for original work |
|---|---|---|
| Header: site, asset, date | Often copied from the client's work request or asset list | Identifiers may be the client's, and they point to the client |
| Observations in free text | The inspector | Usually the richest original material, if the inspector is the company's own |
| Ratings and condition codes | The inspector, using someone's scale | The judgment is the inspector's; the scale may belong to a client, a standard or the company |
| Stock sentences | A comment list, written by staff or supplied with software | Company-written lists are company work; supplied text is someone else's |
| Pasted references | Codes, standards, manufacturer manuals | Third-party text, whatever the inspector intended |
| Photos and measurements | The inspector, on someone else's property | Company work that may show client sites, client staff or the public |
| Attachments | Client drawings, earlier reports by others | Third-party material by default |
| Recommendation and sign-off | The inspector, sometimes under a client-mandated format | The words may be original while the format is not |
The operating partner pages on testing, inspection and certification and industrial services draw the line at the report a client receives. This page goes one level down, inside the note itself, because that is where "original work" is won or lost.
The original-work authority checklist
Ten questions, asked of a company's notes as a whole, never of a single file the partner has seen. Each answer points toward the company's own work, toward someone else's, or toward a hold for SourceX's review.
| # | Question | Points to the company's own work | Points elsewhere | Hold for review when |
|---|---|---|---|---|
| 1 | Who typed the observations? | Employee inspectors | The client's staff | Contract inspectors, or a mix nobody has counted |
| 2 | Whose words fill the note? | Inspectors' own text, or a comment list written by staff | Text pasted from codes, standards or manuals | A library that came with the software, of unknown authorship |
| 3 | Whose form is it? | A checklist the company designed | A form the client requires | A format a regulator or program prescribes |
| 4 | What is attached? | The company's photos and measurements | Client drawings, earlier reports by other firms | Photos that show people or client property |
| 5 | Under whose contract was the inspection done? | The company's own program, or terms that leave working notes with it | Terms that make the work product the client's | Terms nobody has read with this question in mind |
| 6 | Where do the notes live? | The company's own system | The client's portal | Copies in both places |
| 7 | Did an AI tool touch the text? | No | Notes created or rewritten for the sale | Drafting or summary features used during ordinary work |
| 8 | Have the notes been licensed before? | Never licensed for AI training | Licensed for AI training before, which makes them ineligible | Any earlier data deal nobody can describe |
| 9 | Does personal data appear? | Little or none | Notes that profile identifiable people | Names, faces or addresses in photos and comments |
| 10 | Who can authorize a licensing discussion? | The CEO, who knows and wants the conversation | A field supervisor acting alone | A CEO who has not heard about it yet |
Questions 1 to 6 cover authorship and custody. Questions 7 and 8 come from what SourceX asks every supplier to confirm: rights to license, lawfully collected personal data, no earlier AI-training license, and records not created or altered with AI for the sale. Question 10 is authority, not authorship: the inspectors wrote the notes, but the CEO decides whether the company discusses licensing them.
Method note. The checklist applies SourceX's published screening guidance and the confirmations its process asks of suppliers, both checked 2026-10-27. Its "points elsewhere" column flags material that is usually not a fit, such as material belonging to clients; it does not decide rights, which SourceX's review and the company's own counsel do. It measures no demand and no volume.
One note, line by line (Illustrative)
Illustrative. The note and its line counts are invented to show the subtraction, not drawn from any company's records.
| Source of the lines | Lines | Verdict |
|---|---|---|
| The inspector's own observations and recommendation | 9 | Company original |
| Sentences from a comment list the company's quality team wrote | 4 | Company original |
| Text pasted from a published code | 3 | Someone else's words |
| Stock sentences supplied with the inspection software | 2 | Someone else's words |
| References to the client's drawings and asset list | 2 | Client material |
| Total | 20 | 13 company original, 7 elsewhere |
Thirteen of twenty lines survive. The other 7 are not a problem in themselves; they are why the company describes its notes and SourceX's review decides the scope.
Three companies, three verdicts (Illustrative)
Illustrative. Generic companies with invented facts; no outcome is implied for any of them.
Original work: a 280-person commercial roofing contractor. Its employee estimators inspect roofs before bidding and its service crews inspect them on maintenance plans, writing in their own words on checklists the company designed, in the company's own field app. The comment list was written by the operations team. Answers to questions 1 to 6 all point to the company. What stays open: photos that show building occupants, and whether any maintenance contract says otherwise. The partner's next move is the CEO.
Mixed third-party content: a 520-person engineering consultancy that inspects bridges for public agencies. Its inspectors write observations in their own words, but much of each file follows the agency's requirements. The federal National Bridge Inspection Standards define an inspection report as "The document which summarizes the bridge inspection findings, recommendations, and identifies the team leader responsible for the inspection and report", and section 650.307 makes the agency's bridge inspection organization responsible for managing inspection reports and files. The reports themselves, in other words, are managed in the agency's files. Whether the consultancy's own field notes, review comments and method documents are separable is a question for its contracts and SourceX's rights review, not for the partner.
Uncertain ownership: a 190-person property inspection firm working for insurers. Most notes are typed by contract inspectors directly into insurers' portals, and the firm switched on a drafting feature last year that rewrites rough notes into finished text. Questions 1 and 7 land in the hold column, question 6 points to the insurers, and the firm's full-time headcount must reach 50 at its peak without counting the contract inspectors. The honest outcome here may be no introduction yet: describe the facts to the CEO and let the company decide whether to ask SourceX.
Who inside the company knows where each line came from
Nobody holds the whole picture, and none of these people decides on their own.
- The quality or operations lead knows which templates and comment lists exist and who wrote them.
- Field supervisors know who writes notes: employees, contract inspectors or a mix, and whether that changed over the years.
- The contracts lead or counsel knows whether client agreements say anything about work product and confidentiality.
- The system administrator knows where the notes live, how far back they go and whether copies sit in client portals.
- The CEO authorizes a licensing discussion, and is the person the partner introduces.
Developers have their own reason to want this sorting done. NIST's AI Risk Management Framework includes, among its Map outcomes, that "Risks and benefits are mapped for all components of the AI system including third-party software and data." A developer working to that outcome would want mixed authorship in a dataset mapped, and a company that has already sorted its notes can describe them far more precisely.
Questions to ask without asking for a single note
Asked of the CEO or someone the CEO names, and answered from memory, system settings and contracts, never from files:
- Roughly how many inspections a year, and since which year in the current system?
- Do employees or contract inspectors write most of the notes, and has that changed?
- Are observations typed freely, chosen from a comment list, or both? Who wrote the list?
- Which forms are the company's own, and which do clients or programs prescribe?
- Where do notes live: the company's own system, client portals, or both?
- Do client agreements say anything about who owns reports, working notes or photos?
- Has any drafting or summarizing tool been used on the notes, and since when?
- Has the company licensed any of these records to anyone before?
Answers mostly in the hold column are a finding, not a failure. The field service work order checklist covers a neighboring record, and after-call work notes shows the same authorship question in a contact center.
Fit facts, and what stays unknown until review
The company still has to pass the published fit facts: 50 or more full-time employees at its peak, with contract inspectors excluded; years of documented operating records; rights to license them; and a CEO who knows about and wants the conversation. 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.
Three things stay unknown until SourceX reviews them: what the company's client agreements allow, how much personal data in photos and comments limits the scope, and whether its notes match current data needs. Material belonging to clients is usually not a fit, and notes already licensed for AI training are not eligible at all.
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 most of a company's checklist answers point to its own work and its CEO wants the conversation, register as a partner, confirm the fit facts on who qualifies and read the program terms before you introduce anyone.