This page belongs to how to assess multimodal workflow records without uploading raw assets. The main guide explains what the photo-and-note pairing is; this page measures a real archive against what a review would want, piece by piece.
The eight pieces a review expects
Expected evidence on the left, typical reality on the right. The patterns come from how field apps and shared drives are usually used; ask the company for its own answers.
| Expected evidence | What field companies typically keep | What is usually missing |
|---|---|---|
| Job link on each photo | Photos attached in the app for most jobs | Photos uploaded later to a shared drive without job numbers |
| Original capture time | A timestamp of some kind | The time the image was taken, as distinct from upload time |
| Image fidelity | Images good enough to view on a phone | Full-resolution originals after app compression |
| On-site note | A note in the job record | Who wrote it and when; office summaries look the same |
| Decision record | The work done | The options offered and who approved the choice |
| Outcome link | Job closed | A link from a later visit or warranty claim back to this job |
| Site permission | Customer contracts on file | Whether they allow photos to be reused |
| People and plates | Nothing specific | A count or estimate of images showing faces, vehicles or addresses |
Each missing piece has a different effect. A missing job link makes the photo an orphan. A missing capture time blurs the order of fault and fix. A missing outcome link leaves the case without a label. A missing permission may exclude the images entirely.
Worked gap profile: a roofing contractor's inspection archive
Illustrative and fictional. A 260-person commercial roofing contractor inspects flat roofs for property managers, photographs defects, writes findings and quotes repairs. It has used a field app for six years.
| Evidence | Status, as the operations director describes it |
|---|---|
| Job link | Mostly available: crews attach photos in the app; drone images go to a shared drive by property name |
| Capture time | Partial: app photos keep it; drone images show upload date only |
| Image fidelity | Partial: the app resizes images on upload, per its settings |
| On-site note | Available: inspectors write findings on the roof |
| Decision record | Partial: quotes recorded; client approvals often by email |
| Outcome link | Missing for most jobs: leak call-backs are logged by property, not by job |
| Site permission | Unknown: property management contracts not reviewed |
| People and plates | Low: roofs rarely show people; parking areas sometimes visible |
The honest summary: six years of on-site findings with attached photos, a partial decision trail, and weak outcome linkage. That is a real archive with a specific weakness, and it should be described that way.
Why these gaps appear
Capture time versus upload time. Camera files can carry an Exif DateTimeOriginal tag, defined in the Exif standard as the date and time the original image data was generated, separately from other timestamps. Whether that value survives depends on the app or upload path. Images copied through messaging apps or re-saved by editing tools may keep only a later date.
Compression by design. Some field apps reduce image size to save storage. Microsoft states that images added to notes in its Dynamics 365 Field Service mobile app are compressed to save storage. That is a reasonable product choice, and it means fine detail may no longer be visible. Other apps behave differently, which is why the owner should check.
Outcomes tracked by place, not by job. Many companies log a return visit against a site or customer. Joining it back to a specific earlier job then needs a date window and a judgment call, which weakens the label.
Rights and personal data. Images taken on a client's property can be restricted by contract. Faces and vehicle plates can identify people, and under the GDPR personal data covers information relating to an identified or identifiable person. Some data 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.
Video archives raise the same questions; the page on exporting all Loom videos shows how a single system can hold years of recorded work.
Describing the gap honestly in an introduction
Name the strongest piece and the weakest piece in one or two sentences. Patterns that work:
- "Six years of inspection findings with photos attached in the app; return visits are logged by property, so outcomes need matching."
- "Photos and notes share job numbers; capture times were lost for images uploaded from a shared drive."
- "Rich photo archive; client contracts have not been reviewed for image reuse."
Avoid "complete", "fully linked" or "high resolution" unless the owner has confirmed it. If the company is still deciding whether to proceed, the multimodal workflow context scorecard turns these gaps into a fit reading, and the review packet contents list shows how the company would document them for SourceX. Why linked records beat file collections is explained in the guide to useful workflow context instead of isolated files.
Who can close a gap, and what stays open until review
Some gaps can be closed by the company before a review, and some cannot.
| Gap | Can the company close it? | Who would |
|---|---|---|
| Job link | Sometimes, by matching folder names to jobs | Operations or app administrator |
| Capture time | Rarely, once lost | App administrator can confirm what was kept |
| Outcome link | Partly, by agreeing a matching rule | Service manager |
| Site permission | Yes, by reviewing contracts | Counsel or CFO |
| People and plates | Handled during preparation | SourceX with the company |
A partner closes none of them and never asks to see images. Partners record metadata and introduce the executive who can authorize a licensing discussion. What stays unknown until SourceX reviews it: actual image quality, which years and job types are in scope, rights outcomes, and whether any buyer wants the record type. The record family is described under multimodal operating records.
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.
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 archive's strongest pieces are job links and on-site notes and you can state its gaps in a sentence, register as a partner, check who qualifies and read the terms before introducing the owner.