Skip to main content
AI file ingestion reads gig paperwork and proposes structured records: a timeline, a crew list with fees, ledger items, and leads. You review the proposals and select what to apply. Extracted records are applied only when you commit; uploaded files are attached to the gig immediately. It produces the same Universal Event Format (UEF) as the spreadsheet importer and partner feeds, so a file dropped on a gig and a row imported from a spreadsheet end up in the same normalized tables.
CheckAI AI file ingestion is in Private Preview, available only to the existing beta tester group. Signing up, choosing a paid plan, upgrading, contacting support, or viewing a public demo does not grant access. Ordinary gig attachments are a separate workflow and do not require AI ingestion.

​
The flow

1

Open the gig's Files tab

Existing testers with an Owner, Admin, or Gig Coordinator role can open the enabled Files preview. Files are grouped into an ingestion batch for that gig; uploading creates a batch when needed.
2

Add files

Drop files or choose Choose files. Supported inputs include PDFs, DOCX documents, images, text files, spreadsheets, and saved emails. Uploading attaches the source files to the gig before you review extracted records.
3

Per-file analysis

CheckAI reads each file and extracts a set of proposals: schedule items, crew members, ledger items, leads, and event details. A file moves from analyzing to ready for review.
4

Review proposals

For each file you see exactly what was found, with a dry-run preview: which rows are new versus which already exist (a crew member already on your roster, a venue already in your CRM). Check the proposed values and select only the records you want to apply. Leave incorrect or uncertain rows unselected.
5

Review combined files

A batch can combine proposals across files. Check overlapping or conflicting details, such as two different load-in times, against the original documents. Refresh a review if files or combined proposals change.
6

Commit what you chose

Commit the proposals you selected, by file or from the combined batch review. Commit selected applies those choices to the gig. Review them before selecting it; an AI client uses the separate confirmation step described below.

​
What gets extracted

A single file can propose any of: Crew rows without a contact channel can’t become an invitation and are skipped at write time. The same rule the importer follows.

​
New vs. duplicate

Before you commit, the review summarizes new and matching records against data you already have. Matching records can reuse an existing crew member, venue, or customer. Review the matches carefully when re-ingesting an updated document, especially if names, contact details, or external identifiers have changed. Identity follows the same external-ID and natural-key rules described in Identity and idempotence.

​
Review before applying extracted records

In the web review, Commit selected is your approval to write the selected records and event fields. A combined review that has changed must be refreshed before it can be committed. Check the result afterward: a partial failure can leave some selected records applied and others still needing attention. When using CheckAI or an external AI client, the MCP commit tools require an explicit confirmation of the proposed changes. If the selected data or merge changes, review the updated proposal and confirm it again. See the MCP security model.

​
From an AI client

The ingestion pipeline also has MCP tools for authorized external clients. This integration has its own authentication and available tools; connecting an MCP client does not grant CheckAI Private Preview access. The ingest_gig_files prompt walks the whole batch, review, confirm, and commit loop. See the available tools on the MCP server page.

CheckAI overview

The assistant behind ingestion.

Spreadsheet imports

The other way data gets into Soundcheck.

Universal Event Format

The shape every ingestion produces.