> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adam.new/llms.txt
> Use this file to discover all available pages before exploring further.

# Apply an operation across files

> Run a reviewed export, drawing, or inspection procedure over an explicit set of models.

Batch work is useful for repeated exports, drawing updates, metadata checks, and design reviews. Start with a defined file list and an operation you have checked on a representative input.

## Define the batch

Specify the files or document links, configurations, source revisions, operation, destination, and naming convention. Decide how to handle existing outputs and which failures should stop the batch.

A folder name alone may be ambiguous. Ask Adam to enumerate the inputs before it starts, especially when subfolders or multiple configurations are involved.

```text title="Plan a STEP export batch" wrap theme={null}
List the native parts in [folder or document list] that you can access. Prepare a STEP export plan for configuration [name] of each part, using millimeters and [output folder]. Name outputs with part number and revision. Report missing references, unsaved documents, and destination collisions. Show the manifest before exporting.
```

## Check one result first

Run the operation on a representative file, then open its output. For geometry exports, verify scale, bodies, and configuration. For drawings, inspect all sheets and confirm the PDF reflects the intended source revision.

```text title="Run the checked export procedure" wrap theme={null}
Apply the export procedure we verified to the remaining files in the manifest. Preserve the source files and skip conflicting destination names. Return a per-file table with source revision, configuration, output path, verification performed, and success or failure. Keep failed items separate so we can retry only those after inspection.
```

## Handle interruptions

A timeout can occur after an application has already changed a file. Inspect the document and destination before retrying. Ask Adam to distinguish completed work, confirmed failures, and items whose state is uncertain.

Desktop batches require the paired computer and application to remain available. Solver or CAD session limits may mean work runs sequentially.

## Keep a reusable record

Retain the manifest, procedure, outputs, and exception report. Use [Repeat engineering work](https://docs.adam.new/guides/repeatable-work.md) to preserve the brief and [Scheduled tasks](https://docs.adam.new/guides/automations.md) when the work needs a recurring trigger.

For drawing batches, see [Engineering drawings](https://docs.adam.new/cad/drawings.md). For a final handoff, see [Documentation and release](https://docs.adam.new/cad/documentation-and-release.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.