# Multimodal workflow context: worked example | SourceX

Canonical: https://refer.sourcex.si/guides/multimodal-workflow-context-workflow-example
Last updated: 2026-11-04

Multimodal workflow context means the photos, notes, forms and readings a job produces stay attached to that job, in order, with its outcome. In an ordinary field-service call, a technician photographs a fault, writes what it means, gets a repair approved, photographs the fix and closes the job; a month later the system shows whether it held. Each step leaves a record. Together they show how what someone saw led to what they did.

This walkthrough is part of [how to assess multimodal workflow records without uploading raw assets](/guides/how-to-assess-multimodal-workflow-records-without-uploading-raw-assets). Where the main guide uses a short rooftop-unit case, this page follows a different job through every step, including the decision points, and marks which records carry the signal an AI-data review looks for.

## The job: a walk-in freezer that will not hold temperature

Illustrative and fictional. A 380-person commercial refrigeration service company has a maintenance contract with a restaurant group. At 06:50 one restaurant's kitchen manager reports that the walk-in freezer reads above its set point and ice is building on the evaporator. Stock is at risk, so the job is urgent.

The company runs a field service app on technicians' phones. Like many such apps, it lets technicians attach images and text notes to the booking and take pictures inside inspection forms with a caption; Microsoft documents both features for its Dynamics 365 Field Service mobile app. The company's own app may differ, which is a question for the owner, not an assumption.

## Step by step: decisions and the records each one leaves

| Step | Time | Decision made | Record left behind | Mode |
|---|---|---|---|---|
| 1. Intake | 06:52 | Classify as urgent under the contract | Work order with asset ID, problem code and priority | Structured text |
| 2. Dispatch | 07:05 | Send the nearest certified technician | Assignment with technician ID and travel start | Structured, time |
| 3. Arrival | 07:48 | What to inspect first | Photo of the iced evaporator coil, taken in the app | Image, capture time |
| 4. Diagnosis | 08:10 | Defrost timer failed; heater intact | Technician note and inspection form answers | Text, form |
| 5. Approval | 08:25 | Repair now versus quote a full controller upgrade | Quote line and the kitchen manager's signature | Structured, signature |
| 6. Repair | 09:30 | Replace timer, run a manual defrost | Photo of the cleared coil, parts used, closing reading | Image, structured |
| 7. Check | Day 30 | Did the fix hold? | No repeat call for the asset; next routine reading in range | System status |

Seven steps, records in several forms (structured fields, photos, notes, a form and a signature), one job number joining them. Remove the job number and the arrival photo is an anonymous picture of ice.

## Which records carry the signal

Not every record is equally useful. An AI-data review looks for the moments where an observation turns into a judgment, and for proof of what happened next.

**High signal.**
- *Step 3 photo with step 4 note.* The photo shows what the technician saw; the note says what it meant. Neither explains itself alone. The pairing is the core of multimodal workflow context.
- *Step 5 approval.* The technician offered two options and the customer chose one. That is a recorded decision with a reason (cost, downtime) attached.
- *Step 7 outcome.* No repeat call within 30 days labels the diagnosis as probably right.

**Supporting.**
- *Step 6 after-photo and reading.* Confirms the end state matches the note.
- *Step 1 problem code.* Lets many similar jobs be grouped and compared.

**Low signal on its own.**
- *Step 2 dispatch.* Useful for scheduling studies, but it says nothing about the fault.

Timing holds the pairing together. Camera files can carry an Exif DateTimeOriginal tag, the time the image data was generated, defined separately from the time it was digitized. If the app keeps that capture time, the review can confirm the arrival photo came before the diagnosis note and the after-photo came after the repair. If only the upload time survives, the order can blur.

## What this job looks like when a step is missing

Three common breaks, each removing a different piece of the chain:

| Missing step | What the company still holds | What the case loses |
|---|---|---|
| Arrival photo taken on a personal phone | Note, approval, outcome | The observation the note interprets |
| Approval given verbally | Photo, note, repair, outcome | The decision between two options |
| No asset link on repeat calls | Everything up to closure | Whether the repair held |

A complete version of this job across thousands of calls is the strong case. A company where step 5 is usually verbal still holds useful observation-to-action pairs, and should be described that way. The [field-level review packet](/resources/multimodal-workflow-context-review-packet) lists the documents that describe these records before anyone looks at a file.

## Recognizing the same workflow at a client

The refrigeration call is one instance of a common shape: someone inspects a physical thing, records what they saw in a picture and words, a decision follows, and a later event confirms the result. The same shape appears in property maintenance, elevator service, fleet repair, roofing and insurance inspection. Ask the operations director, at metadata level:

1. Where do job photos live, and are they attached to the job inside the app?
2. Is the note written by the technician on site, in the same job?
3. Are repair options and customer approvals recorded?
4. Does a repeat visit link back to the asset or the original job?
5. How many years of jobs does the system hold, and who owns it?

If the answers are mostly yes, the [multimodal workflow context scorecard](/questions/does-multimodal-workflow-context-data-qualify) helps decide whether to introduce. The broader record type is described under [multimodal operating records](/data-types/multimodal-operating-records), and why a linked chain beats a pile of files is explained in the guide to [useful workflow context instead of isolated files](/guides/how-to-identify-useful-workflow-context-instead-of-isolated-files). A non-field example of the same idea is in the [logistics workflow example pack](/resources/logistics-workflow-example-pack).

## Who owns these records, and what stays unknown

The service manager knows how technicians use the app. The owner, CEO or COO usually decides whether to discuss licensing. Client contracts matter: photos taken on a customer's premises may be restricted, and images can show people, vehicles or addresses that need removal. Some data marketplaces make this an entry condition; Defined.ai's partnership page, checked on October 18, 2026, requires partners to hold rights to commercialize image, text or multimodal data for AI training.

A partner never asks to see photos or notes. What stays unknown until SourceX reviews it: rights to client-site imagery, image quality after any compression by the app, how many jobs have all seven steps, and whether a buyer wants this record type. The company also needs 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. Other record families are under [data types](/data-types).

## 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 a client's jobs leave a photo, a note and an outcome under one job number, [register as a partner](/register), confirm the company against [who qualifies](/who-qualifies) and read the [terms](/terms) before you introduce its owner.

## Sources

- https://learn.microsoft.com/en-us/dynamics365/field-service/mobile/get-work-done-mobile-app
- https://learn.microsoft.com/en-us/dynamics365/field-service/inspections
- https://www.cipa.jp/std/documents/e/DC-008-2012_E.pdf
- https://defined.ai/partnership-programs
- https://refer.sourcex.si/terms
