Multimodal workflow context review packet: eight documents to assemble, in order

Short answer

A multimodal workflow context review packet holds eight short, metadata-only documents, assembled in this order: a scope note, a system inventory, a job field map, an image metadata summary, a description of note practice, the outcome rule, an acceptance check, and a rights note. Together they let SourceX judge whether photos, notes and outcomes can be rebuilt into complete job records, before anyone opens a file. The operations director usually coordinates; the app administrator supplies three of the eight, and counsel or the CFO writes the rights note.

Visual briefFull-size diagram
Eight labelled documents drop one after another into an open folder: scope note, system inventory, job field map, image metadata summary, note practice, outcome rule, acceptance check and rights note; the folder front reads review packet.
Illustrative packet order. Every document describes records; none contains a photo or a note.

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

OrderDocumentWhat it showsWho prepares it
1Scope noteWhich job types, years and regions are proposedOperations director
2System inventoryEvery system holding photos, notes, jobs and outcomesApp or IT administrator
3Job field mapThe fields that tie a photo and a note to a jobApp administrator
4Image metadata summaryCapture time, size, linkage rates, storage pathApp administrator
5Note practiceWho writes notes, when, and in what languageService manager
6Outcome ruleHow the company decides a job's result heldService manager with operations
7Acceptance checkThe conditions a complete record must meetOperations director
8Rights noteOwnership, client contract limits, people in imagesCounsel 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:

FieldEntry
ScopeRepair and maintenance jobs, five years, U.S. only
SystemsField service app since 2020; earlier photos on a shared drive
Joining fieldsJob number and asset ID on photos, notes and parts
Capture timeKept for in-app photos; not for shared-drive images
Outcome ruleNo repeat visit for the asset within 30 days
RightsContracts with two restaurant groups under review
AuthorizerCEO, 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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Does the partner prepare the packet?

No. The company prepares it with SourceX after it applies. The partner's job ends at a well-described introduction; knowing what the packet contains helps the partner ask the right questions earlier.

How long does the packet take to assemble?

It depends on the company. Most documents are short descriptions that the operations director and app administrator can write from what they already know. The rights note can take longest if contracts need review.

Can the packet include a few sample photos to show quality?

Not at this stage. The packet describes images by their metadata. Samples, if any, are exchanged later under an agreement and SourceX's preparation process.

Sources

  1. learn.microsoft.com/en-us/dynamics365/field-service/inspections
  2. learn.microsoft.com/en-us/dynamics365/field-service/mobile/get-w…
  3. cipa.jp/std/documents/e/DC-008-2012_E.pdf
  4. defined.ai/partnership-programs
  5. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment