# Multimodal workflow context fit scorecard | SourceX

Canonical: https://refer.sourcex.si/questions/does-multimodal-workflow-context-data-qualify
Last updated: 2026-11-04

Score the client on seven criteria: company size, operating history, rights to license, record depth, linkage between photo and note, outcome tracking, and English share where the company sits outside the U.S., Canada and the EU. Give each 0, 1 or 2 points. Ten or more out of 14, with no zero on size, rights or linkage, is a strong fit worth introducing. Six to nine is borderline. Below six, or any zero on size, rights or linkage, wait.

This scorecard belongs to [how to assess multimodal workflow records without uploading raw assets](/guides/how-to-assess-multimodal-workflow-records-without-uploading-raw-assets). It turns the introducer's questions into a decision: introduce now, introduce with caveats, or not yet.

## The seven criteria and how to score them

Each row is answered from a conversation with the operations director or owner. None needs a photo.

| Criterion | 2 points: strong | 1 point: borderline | 0 points: weak |
|---|---|---|---|
| Company size | 50+ full-time at peak, clearly | Near 50; peak figure needs checking | Under 50 full-time, or mostly contractors |
| Operating history | Five or more years of jobs in a system | Two to four years | Under two years, or paper records |
| Rights to license | Company owns its job records; client contracts known | Contracts not yet reviewed | Client contracts forbid reuse of site imagery |
| Record depth | Photos and notes on most jobs, tens of thousands of jobs | Photos on some job types only | Photos rare or kept outside any system |
| Photo-to-note linkage | Photos attached to the job in the app, capture time kept | Photos in folders named by job number | Photos on personal phones or unnamed drives |
| Outcome tracking | Repeat visits link to the asset or job | Repeat visits logged but not linked | No record of whether the fix held |
| English share | U.S., Canada or EU, or 70%+ English elsewhere | Mostly English, share unconfirmed | Outside the listed regions, or under 70% English |

Size, rights and linkage are gates: a zero on any of them stops the introduction regardless of the total. Size is a program rule. Rights decide whether anything can be licensed at all; Defined.ai's partnership page, checked on October 18, 2026, for example requires partners to hold rights to commercialize image, text or multimodal data for AI training. Linkage decides whether the photos are workflow context or a picture library.

## The eligibility facts behind the scorecard

The first, third and last rows restate program requirements. Introduced companies need 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.

For multimodal records the English share applies to the text: technician notes, form answers, captions and closing comments. A photo has no language, but the note that interprets it does. The [company fit checker](/tools/company-fit-checker) runs the general baseline quickly, and the full rules are on [who qualifies](/who-qualifies).

## What strong, borderline and weak fits look like

Three Illustrative and fictional companies, scored on the same card.

| Criterion | Elevator service, 450 staff | Property maintenance, 210 staff | Landscaping, about 50 staff |
|---|---|---|---|
| Company size | 2 | 2 | 1 |
| Operating history | 2 | 1 | 1 |
| Rights to license | 1 | 1 | 1 |
| Record depth | 2 | 1 | 0 |
| Photo-to-note linkage | 2 | 1 | 0 |
| Outcome tracking | 1 | 1 | 0 |
| English share | 1 | 2 | 2 |
| Total out of 14 | 11 | 9 | 5 |
| Reading | Strong: introduce | Borderline: introduce with caveats | Weak: linkage zero, wait |

**The elevator service company** attaches inspection photos and technician notes to each job in its app and has done so for seven years. Repeat call-outs are logged but not always linked to the original job, so outcome tracking scores 1. It operates in the UK and the text share in English has not been confirmed, so that row scores 1 until it is. Contracts with building owners have not been reviewed. Strong fit; say what is unconfirmed.

**The property maintenance company** stores photos in a shared drive with job numbers in folder names. Notes are typed later by an office team. Borderline: worth introducing with the linkage described accurately.

**The landscaping company** has before-and-after photos on crew leaders' phones. Linkage scores zero, which stops the introduction regardless of total. Revisit if it adopts a job app.

## Tie-breakers for borderline scores

When a company lands between six and nine, three details separate the useful from the hopeful.

1. **Capture time.** Ask whether photos keep the time they were taken. The Exif standard defines DateTimeOriginal, the time the image data was generated, separately from later timestamps. If the app keeps it, the order of observation and action can be checked; if only upload time is kept, it often cannot.
2. **Image handling.** Ask whether the app changes images on upload. Microsoft documents that its field service mobile app compresses images added to notes to save storage. Other apps behave differently, so the owner should check rather than the partner guessing.
3. **Note authorship.** A note written by the technician on site carries the interpretation. A note typed later by the office is a summary, which is weaker.

A borderline company that scores well on all three tie-breakers usually reads closer to strong. The [multimodal workflow context evidence gaps analysis](/questions/multimodal-workflow-context-evidence-gaps) explains each weakness in more depth, and the [worked freezer service call](/guides/multimodal-workflow-context-workflow-example) shows a complete job for comparison.

## Recording the result and what stays unknown

Write down the score, the gate results, the tools named, the years covered and the executive who can authorize a licensing discussion. Do not ask for photos, notes or exports. Partners never handle raw client records.

What stays unknown until SourceX reviews it: rights to client-site imagery, removal of faces, plates and addresses, which years are in scope, actual image quality, and whether any buyer wants the record type. The record family is described under [multimodal operating records](/data-types/multimodal-operating-records), resolution-note practice is covered in the [field service records guide](/guides/how-to-assess-field-service-records-and-resolution-notes), and the wider licensing picture for introducers is in [a business introducer's guide to operational data licensing](/guides/a-business-introducer-guide-to-operational-data-licensing).

## 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 scores ten or more with no zero on size, rights or linkage, [register](/register), confirm the details against [who qualifies](/who-qualifies) and read the [terms](/terms), then introduce the owner with the unconfirmed rows stated plainly.

## Sources

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