How can we help?
Search for the articles here or browse the categories below.
Browse by topic
Find guides, tutorials, and answers organised by category.
Popular articles
What other people are reading right now.
Quickstart: your first project in 30 minutes
Click here to watch Quick guidde This training will teach you how to upload and manage contract documents within the CIM Build application. 1. Introduction You will learn to navigate the interface, perform reviews, and export selected files efficiently. Introduction 2. Access Documents Section Click the Documents section to view all available files within CIM Build. Access Documents Section 3. Open Upload Interface Click the Upload button to begin adding new documents to the system. Open Upload Interface 4. Select Contract Set Upload Click Contract Set to upload contract set of documents so that you can compare them easily in the future. Or click on any of the other options - Tender, Addendum or Revision when uploading those. Select Contract Set Upload 5. Confirm Upload Files Click Upload files to confirm and start the file upload process. Confirm Upload Files 6. Open Finder To Select Files Click Finder to browse your local system and select files for upload. Open Finder To Select Files 7. Check Upload Status Click Upload status to monitor the progress and status of your file uploads. Check Upload Status 8. Review Uploaded Documents Click Review to run your first review. Reviews are your way to store results in registers. Review Uploaded Documents 9. Access Gates Section Click on Gates to run a few reviews at a time. Gates are a collection of reviews that you run at certain points along your project. We recommend setting up gates at different stages so you can start systemizing your reviews and checks. Access Gates Section 10. Open Your First Gate Click here to run your first gate. If you don't have a Gate, we recommend adding a template one to get started. Open Your First Gate 11. Proceed To Next Step Click here to continue with the next action in the audit process. Proceed To Next Step 12. Run Audit Checks Click Run Checks to initiate the automated audit process for your documents. Run Audit Checks 13. Register Audit Results When your results finish, click Register to view the results of your reviews. Reviews usually take around 20 minutes to finish running but the results are updated live. Register Audit Results 14. Exporting specific findings. Once you see your findings, click on this checkbox to export specific findings. Exporting specific findings. 15. Input Option Information Fill on to input the required information for the activated option. Input Option Information 16. Export Selected Files Click Export Selected to download or save the chosen findings from CIM Build. Export Selected Files After completing this training, you will be able to upload contract documents, perform audits, and export files efficiently within CIM Build. Practice these steps to ensure accurate document management and ensuring your review systems run continuously. Powered by guidde
Get StartedChoosing your first workflow
CIM supports a few broad workflows. Pick the one that matches what you're being measured on this week. 1. Preliminary tender review document health checks. You've received a tender package and need to high-level eyeball what documents you received. Run: Document → Checklist 2. Tender review - you find the main issues that effect pricing before you price it. Run: Checklist → Gates → Run specific gate you select 3. Drawing coordination. You're a design manager during ECI/design development. Run: Cross-reference review (architectural vs services vs structural) → spec/drawing consistency → window/door schedule reconciliation. Rerun on every revision / addendum. 4. Change Tracking: You've received an addendum or revised set mid-project. Run: Click Set-up, In any case, we plan to support being able to run all workflows through our main core Assistant in the near future.
Get StartedConcepts: how CIM is organised
Five concepts unlock everything else. Learn these once. Organisation. Your company. Holds shared templates, members, and integrations (Procore, Google Drive). Project. One job. Holds documents, gates, findings, and members. Most work happens at the project level. Document. A drawing, spec, schedule, BCA report, or any file you've uploaded. CIM auto-tags documents by discipline based on folder path and content. Gate. A bundle of reviews that runs against your project. Review. One question the AI asks. Some checks run at discipline level (civil vs structural). Others run at individual drawing level (RCP vs unit plan for GPO placement). Each template tells you which. Finding. Something the AI flagged. Findings live in the Register, which is your single source of truth — AI findings and anything you add manually live in the same register.
Get StartedGlossary
Glossary Common terms across CIM and how we use them. We've tried to match construction-industry usage, but a few terms are CIM-specific. | Term | Definition | | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | Gate | A bundle of checks that runs together. See Concepts. | | Check | A single question the AI asks of your documents. | | Finding | A flagged item — something the AI thinks is worth your attention. | | Register | The unified list of all findings + any manual items you've added. | | Change | A difference between two revisions of the same drawing. Lives in the Change Register. | | Template | A reusable bundle of checks you can apply across projects. Org-level or project-level. | | Discipline | Architectural, Structural, Hydraulic, Electrical, etc. CIM uses this to filter and group. | | Health check | A gate that validates your document set before you run real reviews. | | Citation | The drawing/page reference the AI used to support a finding. Always click through to verify. | | Hallucination | When the AI flags something incorrectly. Roughly 1 in 4 findings will be a false positive — always verify. | | Bounding box | A drawn region the AI highlights on a drawing. Used in detection and markup tools. | | Archive | Hides a finding from the active register without deleting it. Archived findings can be restored. |
Understanding the AIWhat the AI is good at — and what it isn't
CIM uses AI to read your drawings and specs and surface findings. It's powerful, but it's not magic. Reading this once will save you from the most common trust issues. What it's good at - Reading text on drawings and specs. Title blocks, notes, schedules, callouts. High accuracy. - Comparing two documents for consistency. Architectural vs structural column grids, drawings vs spec, revision A vs revision B. - Finding things that aren't there. Missing notes, absent details, undocumented assumptions. - Volume work. Reading 400 sheets in an hour and surfacing the 30 that need a human. What it's not (yet) good at - Counting. Car spaces, GPOs, doors, fixtures. Don't trust quantities. Use it as a starting point and recount. - Measurements. Corridor widths, room areas, setback distances. Same rule — verify on the drawing. - Implicit cross-document inference. If the answer requires combining info from three documents the AI wasn't told to look at, it'll often miss it. - Knowing what should be on a drawing. It can compare what's there to what you told it to check for, but it doesn't have construction intuition. Expect false positives. Roughly 1 in 4 findings will be wrong. This is normal and we tell every customer upfront. The right mental model: the AI is doing the first pass, you're doing the judgement call. Always click the citation to verify before you action a finding. The single most common failure mode: the AI looked at the wrong drawing.
Get StartedIn-app tours
CIM has built-in guided tours for most major features. They're not video tutorials — they're an overlay on the real app that walks you through each button as you use it. Starting a tour. Look for the koala icon in the bottom-right corner. Click it to see tours available for the page you're on. Tours are context-aware — the ones offered on the Risk Register are different from the ones offered on the Change Register. Restarting a tour. Tours don't replay automatically. If you dismissed one and want it back, click the koala and pick the tour again. Tours triggered by chat. The AI assistant can launch a relevant tour when you ask a "how do I" question. If you ask "how do I assign a finding to a consultant?", expect chat to offer to walk you through it. Suggested first tours: 1. Upload to findings — The full loop from a fresh project to a triaged register. 2. Reviewing in the Risk Register — How to triage, assign, and archive. 3. Comparing drawing revisions — The Change Register flow. 4. Asking chat about a document — Selecting context before you ask.