> For the complete documentation index, see [llms.txt](https://docs.unitlab.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unitlab.ai/documentation/multimodal-annotations/media-and-document-layouts.md).

# Media and document layouts

A media-and-document task should preserve one business or research case even when its evidence uses different file types. Unitlab Data Groups bring native viewers into one custom layout so an annotator can create a label in the active tile while consulting the remaining evidence.

![Video, PDF, and audio evidence in one multimodal workspace](/files/JQmJNJVVmr06fbCAGqin)

*The group—not an individual file—defines the reviewable case.*

## Choose the evidence model

Use this pattern for examples such as:

* manufacturing video + inspection report + vibration audio;
* image + OCR text + supporting PDF;
* customer recording + transcript + case document;
* field image + sensor export + technician note;
* clinical image + report or study documentation.

Keep each source as its native file whenever possible. Flattening a PDF, waveform, or video into screenshots removes page, time, and content behavior that reviewers need.

## Build the layout

{% stepper %}
{% step %}

#### 1. Define one case

Choose the stable grouping key shared by every file in the work unit—for example inspection ID, encounter ID, capture session, or case number.
{% endstep %}

{% step %}

#### 2. Create or auto-generate the Data Group

Map filename patterns or metadata to tile roles. Add exclusions for files that must not join a group and preview the matches before creation.
{% endstep %}

{% step %}

#### 3. Design the presentation

Choose grid, list, or custom layout; set tile order; enlarge the primary evidence; and keep reference panels large enough to read without distortion.
{% endstep %}

{% step %}

#### 4. Attach the group to a project

Use an ontology whose classes, properties, Item Properties, and relations describe the decisions that span the evidence.
{% endstep %}

{% step %}

#### 5. Annotate from the active tile

Activate the correct native editor, create the label, and use passive tiles for context. Switch active tiles intentionally when another file requires its own annotation.
{% endstep %}

{% step %}

#### 6. Review and deliver the case

Check file membership, tile roles, cross-modal relations, required values, and workflow outcome before publishing the group through a dataset version or release.
{% endstep %}
{% endstepper %}

![Grid, list, and custom multimodal layouts](/files/Z7AMj4XHa9FhoCcw3Vxi)

*Custom layouts control how a repeated case is presented to every annotator and reviewer.*

## Auto-Grouping

![Related MP4, CSV, PDF, and MP3 files auto-grouped into one case](/files/PMDdjgvDNjBkvSihEseF)

Use Auto-Grouping when filenames or metadata consistently encode case membership. Configure the source folder, grouping keys, name pattern, tile rules, exclusions, and layout. Review unmatched and duplicate files before creating groups; an incorrect grouping rule creates a data-quality problem upstream of annotation.

## Cross-modal relations

![A package defect linked to thermal, audio, and document evidence](/files/sH8vZbEefsHes7gwM1p2)

Relations can connect labels across the ontology when the downstream dataset needs explicit evidence structure. Define direction and meaning before production—for example finding-supported-by-report or defect-correlates-with-audio-event. Do not assume proximity in a layout is an implicit relation.

## Production checks

* Every group has the expected files and no unintended duplicates.
* Tile roles and order are stable.
* The active editor is visually unambiguous.
* Page, frame, time, and source-file identity remain separate.
* Reviewers can reconstruct why a label was created from the visible evidence.
* Dataset and release outputs preserve group membership and relation semantics.