This list belongs to how to assess multimodal workflow records without uploading raw assets. The order matters: each document narrows the next, so a company stops early if a basic condition fails.
The packet at a glance
| Order | Document | What it shows | Who prepares it |
|---|---|---|---|
| 1 | Scope note | Which job types, years and regions are proposed | Operations director |
| 2 | System inventory | Every system holding photos, notes, jobs and outcomes | App or IT administrator |
| 3 | Job field map | The fields that tie a photo and a note to a job | App administrator |
| 4 | Image metadata summary | Capture time, size, linkage rates, storage path | App administrator |
| 5 | Note practice | Who writes notes, when, and in what language | Service manager |
| 6 | Outcome rule | How the company decides a job's result held | Service manager with operations |
| 7 | Acceptance check | The conditions a complete record must meet | Operations director |
| 8 | Rights note | Ownership, client contract limits, people in images | Counsel or CFO |
The packet is short on purpose. Most documents run to a page. None contains a photo, a note or a customer name.
Documents 1 to 3: scope, systems and the joining fields
1. Scope note. One paragraph naming the job types proposed (for example, refrigeration repairs and planned maintenance), the years, the countries and an order-of-magnitude job count. It also names the executive who can authorize a licensing discussion. A narrow, well-documented scope reviews faster than "everything we have".
2. System inventory. A list of each system and what it holds: the field service app, any shared drive with job photos, the ERP that holds parts and invoices, and the phone or CRM system that logs repeat calls. For each, the years covered and whether the system has been replaced. A replaced app often means photos before a certain date sit somewhere else.
3. Job field map. The fields that make a record joinable: job or work order number, asset ID, technician ID, and the timestamps on each. Field apps commonly attach images and notes to the booking, and inspection forms can take pictures with a caption comment, as Microsoft documents for Dynamics 365 Field Service. The map says which of these the company's app actually records.
Documents 4 and 5: the images and the words
4. Image metadata summary. No images, only facts about them:
- Share of photos attached to a job inside the app versus stored elsewhere.
- Whether the original capture time is kept. The Exif standard defines DateTimeOriginal, the time the image data was generated, separately from later timestamps; the summary says whether the app preserves it or only records upload time.
- Whether the app changes images on upload. Microsoft notes that its field service mobile app compresses images added to notes to save storage. The summary records what the company's app does, as checked by the administrator.
- Typical file formats and storage location.
5. Note practice. Who writes the note (technician on site, or office staff later), whether it is required before a job can close, its typical length, and the language. For companies outside the U.S., Canada and the EU, the language share matters for eligibility.
Documents 6 and 7: outcome and acceptance
6. Outcome rule. How the company decides that a repair held. Usually: no repeat visit for the same asset within a set number of days, which the company chooses. The rule names the field that links a later visit to the earlier job. If return visits are logged only by site, say so; matching by date window is weaker.
7. Acceptance check. Written before anyone examines outcomes, so nobody fits the rule to the result. Illustrative, for a refrigeration repair:
- ☐The arrival photo and the technician note carry the same job number.
- ☐The photo's capture time is after arrival and before the repair note.
- ☐The parts recorded match the repair the note describes.
- ☐An after-repair photo or closing reading exists.
- ☐No repeat visit for the same asset within the company's chosen window.
A record that meets every condition is a complete case. One that fails the second condition still holds a photo and a note, but not a provable order. The worked freezer service call shows a job that passes all five.
Document 8: rights, and an illustrative cover sheet
8. Rights note. Who owns the job records; client contracts that restrict photos taken on their premises; whether images show people, vehicles or addresses and roughly how often; and any subcontractor whose technicians took photos. Some marketplaces make rights an entry condition; Defined.ai's partnership page, checked on October 18, 2026, requires partner data to be sourced with consent and rights to commercialize it for AI training.
Illustrative and fictional cover sheet, for a 380-person refrigeration service company:
| Field | Entry |
|---|---|
| Scope | Repair and maintenance jobs, five years, U.S. only |
| Systems | Field service app since 2020; earlier photos on a shared drive |
| Joining fields | Job number and asset ID on photos, notes and parts |
| Capture time | Kept for in-app photos; not for shared-drive images |
| Outcome rule | No repeat visit for the asset within 30 days |
| Rights | Contracts with two restaurant groups under review |
| Authorizer | CEO, with the operations director coordinating |
Where gaps show up in documents 4 to 8, the evidence gaps analysis suggests how to describe them. Related record types are under multimodal operating records and field service histories; a packet from a different workflow is in the finance workflow example pack, and why joined records matter is in the guide to useful workflow context instead of isolated files.
Eligibility still applies: 50+ full-time employees at peak (contractors excluded), 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.
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 operations director could write the scope note and job field map from what is already in place, register as a partner, confirm the company against who qualifies and read the terms, then introduce the executive and let the company build the packet with SourceX.