Skip to main content

Documentation Index

Fetch the complete documentation index at: https://support.cim.build/llms.txt

Use this file to discover all available pages before exploring further.

When you click Process new revision set or Process upload, CIM Build queues your files for analysis. The platform runs them through a sequence of automated processing stages — from splitting raw PDFs into individual drawing sheets all the way through to generating structured audit checks and detecting clashes between disciplines. You can monitor every stage of this pipeline in real time from the Status page.
Processing runs entirely in the background. You don’t need to stay on the Status page — navigate anywhere in the platform and come back any time to check progress.

Pipeline stages

1

Drawing Processing

CIM Build splits uploaded drawing PDFs into individual sheets and analyses each one. It extracts drawing metadata such as sheet numbers, titles, revision marks, and discipline assignments. This stage is the foundation for all drawing-based analysis — clash detection, change register comparisons, and the drawings viewer all depend on it completing successfully.The status page shows progress as “Processing pages 234/450” so you can see exactly how far along your upload is.
2

Specification Processing

For uploaded specification documents, CIM Build reads through each PDF and extracts individual requirements. It identifies discrete clauses, provisions, and obligations from the raw document text, structuring them into a form that downstream analysis tools can work with.
3

Specification Check Generation

Using the requirements extracted in the previous stage, CIM Build generates a set of audit checks — structured questions and criteria that can be run against your drawings. These checks populate the Audit Checklist tool and provide the basis for specification compliance reviews.
4

Clash Analysis

CIM Build cross-references drawings from different disciplines to detect potential conflicts — for example, where a structural element intersects with an MEP service route. Clash analysis requires the contract baseline to be set and drawing processing to be complete before it can run.

The Status page

Click Status in the left sidebar to open the Status page at any time. It shows you the current state of all processing activity for your project.

System status

At the top of the page, the System Status section gives you an at-a-glance summary. It shows an overall progress bar and a status line such as “2 analysis systems running · ETA ~23m”, so you know roughly how long to wait before results are ready.

Processing tools

Below the system status, individual processing tools are listed in two groups: Inputs & Preparation
  • Drawing Processing — splits and analyses uploaded drawing PDFs
  • Specification Processing — extracts requirements from specification documents
  • Specification Check Generation — creates audit checks from extracted specifications
Active Analysis
  • Clash Analysis — detects conflicts between disciplines
Each tool displays:
  • A Running or Complete status badge
  • A description of what it is currently doing (e.g. “Processing pages 234/450”)
  • A progress bar showing how far through the workload it is

Pipeline Detail panel

The Pipeline Detail panel lists every individual file and its current processing step. Each file shows whether it is queued, processing, or done. This is useful when you want to check whether a specific drawing has finished processing before using it in analysis.

Workflow Runs

The Workflow Runs section shows the individual workflow executions that make up the pipeline. Each run displays its status (Queued, Running, Completed, or Failed), duration, and an expandable detail view. If a workflow shows as Failed, expand it to see the error details. Org-wide Workflow Runs shows organisation-level workflows that may affect your project, such as background indexing tasks.
Use the Refresh button on the Status page to pull the latest status if the page does not update automatically.
If a workflow shows as Failed, expand it to read the error details before re-uploading or re-processing files. Some failures are transient and resolve on retry; others may indicate a problem with the source file.