# CIM Build > Scope risk management for builders. CIM reads every drawing, spec and schedule on every revision, flags what changed and what it exposes you to, and drafts the paperwork that follows. CIM Build is construction intelligence management software for builders, developers and the consultants who work with them. It reads every drawing, specification, consultant report and brief on every revision, audits them against each other and against the building code, and keeps the findings in live registers the team can act on. ## Pages - [Home](https://www.cim.build/au): Product overview for CIM Build. - [Mission](https://www.cim.build/au/purpose): A letter from the cofounders of CIM Build. The awning that cost a builder $50,000, why misses like it are normal, and what we built to read what a human never had time for. - [Customer stories](https://www.cim.build/au/case-studies): How Australian builders use CIM on live jobs: the discrepancies caught before packages were let, and the tenders won without the lowest price. - [Blog](https://www.cim.build/au/blog): Playbooks and ideas on construction document control and project delivery. - [The Construction Executive](https://www.cim.build/au/news): A publication for construction executives. Budgets, policy and industry shifts decoded for Australian design and construct builders, and what they mean for your margin. - [FAQ](https://www.cim.build/au/faq): Answers on what CIM Build checks, how it compares to ChatGPT, integrations, data residency and SOC 2. - [Contact](https://www.cim.build/au/contact): Book a briefing or get in touch. ## Who it's for Builders are served from the home page. Each other segment has its own landing page. - [Developer-builders](https://www.cim.build/au/for/developer-builders): You engage the consultants and you carry the build, so design risk stays with you. CIM reads every revision against the brief and flags the scope the design has picked up and the design issues still open, cited to the page, while the drawing is still cheap to change. - [Developers](https://www.cim.build/au/for/developers): Whatever your tender set leaves open, the builder prices as risk or claims as a variation. CIM reads the set before it goes to market and flags what is missing while it is still yours to fix. - [Data centre operators](https://www.cim.build/au/for/data-centre-operators): Design starts three years before construction, and half of every variation register traces back to a design miss. CIM reads every revision, flags the misses and clashes before they become RFIs, and cites each finding to the sheet. - [Building code consultants](https://www.cim.build/au/for/building-code-consultants): CIM reads the full drawing set against the NCC on every issue - fire, egress, access, energy, structure - and returns each finding cited to the clause and the sheet. More BCA reports out of the same team, with the working attached. - [Architects/Consultants](https://www.cim.build/au/for/consultants): AI-assisted QA on every issue - CIM checks the set against itself, against the specification and against the NCC, and returns each finding cited to the sheet it sits on. Your practice issues more work without adding reviewers, and your seniors spend their hours on the design. ### By role - [Directors](https://www.cim.build/au/for-who/directors): A drawing-review standard on every project, with nothing for your team to learn. CIM gives every team the rigour of a senior reviewer on every revision. - [Estimating teams](https://www.cim.build/au/for-who/estimating-teams): CIM reads the full tender pack in under an hour: drawings against specs, schedules against drawings, prior revisions against the current set. - [Delivery teams](https://www.cim.build/au/for-who/delivery-teams): See exactly what changed between revisions. CIM flags unclouded consultant edits and schedule drift before the trades raise them. - [Design managers](https://www.cim.build/au/for-who/design-managers): CIM keeps a defensible change register current automatically, so nobody runs it by hand. ## Outcomes - [Proactive Project Intelligence](https://www.cim.build/au/outcomes/proactive-project-intelligence): Every project document read as it lands, and the risk raised while there is still time to act. CIM audits each new revision against the drawings, the specification and the brief, and returns what changed, what it conflicts with and what it exposes you to, cited to the sheet. - [Protect your margin from unclouded changes](https://www.cim.build/au/outcomes/protect-your-margin): The changes that cost you are the ones nobody clouded. CIM compares every revision against the last and against the contract baseline, flags what changed within hours, cited to the drawing and page, and gives your team the record to raise it while the notice window is open. - [Tender with confidence](https://www.cim.build/au/outcomes/win-more-tenders): Know what you are pricing before you commit a number. CIM reads the full tender pack in under an hour and returns every scope gap and spec conflict cited to the page, so your team prices the risk it can see and qualifies the rest. - [Protect your feasibility](https://www.cim.build/au/outcomes/protect-your-feasibility): The number was set at feasibility; the design develops for eighteen months after it. CIM flags where the drawings have picked up scope the feasibility never carried, cited to the page, while a correction still costs a redraw. - [Hold consultants to the brief](https://www.cim.build/au/outcomes/hold-consultants-to-the-brief): You engage the consultants, so nobody else is checking their work. CIM reads every issue against your brief and against the other disciplines, and flags what the design has missed - cited to the drawing, while there is still a fee conversation to have. - [Build what you sold](https://www.cim.build/au/outcomes/build-what-you-sold): the schedule of finishes in the contract of sale is a promise to a purchaser. CIM checks it against the drawings and specifications on every revision and flags where the design has moved away from what was sold, cited to the page. - [Shorten your defects tail](https://www.cim.build/au/outcomes/shorten-your-defects-tail): Your exposure runs long past practical completion. CIM builds the dated documentation record as the job runs - what was designed, what changed, what was checked - so the defect claim that lands years later meets evidence. - [Brief a complete tender](https://www.cim.build/au/outcomes/brief-a-complete-tender): Every gap in the set you issue is priced as risk or claimed later as a variation. CIM reads the tender pack before it goes to market and returns what is missing or in conflict, cited to the page. - [Test every claim](https://www.cim.build/au/outcomes/test-every-claim): Know whether the scope actually changed. CIM compares the revision a claim rests on against the contract set and shows what moved, cited to the drawing - so a variation is assessed from the documents rather than from argument. - [Hold the builder to the brief](https://www.cim.build/au/outcomes/hold-the-builder-to-the-brief): On design-and-construct the builder owns the design, and you get what they document. CIM checks their drawings against your Principal Project Requirements and flags where the design falls short of what you are paying for. - [Certify what you pay for](https://www.cim.build/au/outcomes/certify-what-you-pay-for): Progress claims and drawdowns rest on what has actually been documented and built. CIM keeps a dated record of every revision and finding, so your financier's QS and your own team are working from the same evidence. - [Protect the turnover date](https://www.cim.build/au/outcomes/protect-the-turnover-date): Schedule is the KPI everything else serves. CIM reads every revision within hours of it landing and cites each finding to the sheet, so documentation problems are resolved while they are still drawings. - [Reduce RFIs and variations](https://www.cim.build/au/outcomes/reduce-rfis-and-variations): Around half of every variation register traces back to a design miss. CIM finds those misses before the set is issued, cited to the sheet, so the RFI is never raised and the variation never priced. - [Catch design risk in CSA](https://www.cim.build/au/outcomes/catch-design-risk-in-csa): Civil, structural and architectural misses cost more time than services clashes do. CIM reads CSA against the specifications and against the other disciplines, and returns the conflicts cited to the sheet. - [Carry lessons between projects](https://www.cim.build/au/outcomes/carry-lessons-between-projects): What one project learned is written into the next one's checks. CIM turns your past findings and standard details into checks that run automatically on every set. - [Read every sheet against the code](https://www.cim.build/au/outcomes/read-every-sheet-against-the-code): CIM reads the full drawing set against the NCC on every issue - fire, egress, access, energy, structure - and returns each finding cited to the clause and the sheet. The whole set, every applicable clause, in the time it takes to open it. - [Turn reports around faster](https://www.cim.build/au/outcomes/turn-reports-around-faster): The read is where the hours in a BCA report go. CIM runs it in an hour and hands your team the findings, cited to the clause and the sheet, so the assessor writes the report and the client has it before the CC deadline. - [Re-check every revision](https://www.cim.build/au/outcomes/re-check-every-revision): A revision lands mid-assessment and the read starts again. CIM compares each issue against the last, flags what changed - clouded or not - and re-checks the changes against the NCC, so the re-read is only the changes. - [Defend every finding](https://www.cim.build/au/outcomes/defend-every-finding): A BCA report carries your name. CIM returns every finding with the clause and the sheet it came from, and keeps the dated read behind each issue, so what you signed is backed by a review you can produce. - [Issue a coordinated set](https://www.cim.build/au/outcomes/issue-a-coordinated-set): Cross-discipline coordination is checked by eye, under schedule pressure. CIM reads architectural against structural against services, and drawings against specifications, and returns the conflicts cited to the page - before the set is issued. - [Cut your RFI load](https://www.cim.build/au/outcomes/cut-your-rfi-load): Most RFIs trace back to something your own set left ambiguous, and answering them is unpaid. CIM finds those gaps before issue - cited to the page - so the questions never get asked. - [Defend your fee](https://www.cim.build/au/outcomes/defend-your-fee): Redraws driven by someone else's change get absorbed into the fee because nobody recorded that the change happened. CIM compares every revision against the last and dates what moved, so additional services are a documented conversation. - [Stand behind your declarations](https://www.cim.build/au/outcomes/stand-behind-your-declarations): The compliance statements you sign rest on a review you should be able to produce. CIM checks the design against the NCC and the client's brief on every issue, with the source on every finding. ## Features - [AI takeoff](https://www.cim.build/au/features/ai-takeoff): AI takeoff for builders and estimators. CIM measures lengths, areas and counts off your PDF drawings, calibrates each sheet's scale, and marks up every measurement on the sheet so you can check it. - [Bill of quantities](https://www.cim.build/au/features/bill-of-quantities): Build a bill of quantities from your drawings and specification with AI. CIM produces a BoQ for each trade, tied to the scope of works and the sheet behind every line, and exports to Excel. - [Report compliance](https://www.cim.build/au/features/report-compliance): Every consultant report checked against the drawings. CIM audits the geotech, acoustic, ESD and fire reports, and the Principal Project Requirements, against the drawing set and specification, and returns each finding cited to the clause and the sheet. - [PPR vs the drawings](https://www.cim.build/au/features/ppr-vs-drawings): Check the Principal Project Requirements against the drawings, clause by clause. CIM runs the brief as its own audit and flags requirements the design has not picked up, along with design that runs past what the brief asks for, each finding cited to the clause and the sheet. - [BCA assessment](https://www.cim.build/au/features/code-assessment): Designs assessed clause by clause against the BCA/NCC. CIM reads the architectural set against the code provisions that apply to the building's class and construction type, and returns each finding cited to the clause, the sheet and the revision. - [Lessons learnt](https://www.cim.build/au/features/lessons-learnt): Turn what the last job taught into checks that run on the next one. CIM takes your past defects, standard details and tender qualifications and runs them as audits on every new set, alongside the code and coordination checks. - [Revision tracking](https://www.cim.build/au/features/revision-tracking): Compare drawing sets, check sheet matches and review detected changes in context. Prioritise findings that could affect scope, procurement or work on site. - [Bulk compare](https://www.cim.build/au/features/bulk-compare): Compare a whole drawing set in one run. Ask for the comparison in plain English, save it as a template, and keep a history of every run, so the same comparison applies to the next issue the same way. - [Safeguard](https://www.cim.build/au/features/safeguard): Hold a trade package until its scope risk is closed out. Safeguard gates the actions that send project content out - exporting a scope of works, letting a package - while open RFIs, blocking compliance findings, scope discrepancies or untriaged quote exclusions remain against that trade. - [Schedule Creator](https://www.cim.build/au/features/schedule-creator): Build the door, window and wall schedules from the drawings and audit them against the set. CIM locates every door and window on the plans, flags what is missing from the schedule, and checks hardware, FRLs, acoustic ratings and finishes against the spec. - [Scope of works](https://www.cim.build/au/features/scope-of-works): Build a trade-by-trade scope register from the project documents. CIM reads the drawings and specification into a scope of works for each trade, ready to match against subcontractor quotes so the gaps between packages show up before they are let. - [Tender levelling](https://www.cim.build/au/features/bid-leveling): Level subcontractor quotes against the drawings and specs. CIM flags what one quote carries and the others leave out, and exports the comparison to Excel. - [Registers](https://www.cim.build/au/features/registers): Every finding tracked in a live register. CIM keeps findings, changes, schedules and scope in registers that carry the source sheet and revision, re-run as the documents change, and export into the templates your contract admin already uses. - [AI-suggested RFIs](https://www.cim.build/au/features/suggested-rfis): RFIs drafted from the gaps and conflicts found in the documents. CIM turns each finding into a draft RFI with the sheet, the revision and the question already written, for your team to review before anything is sent. - [Viewer](https://www.cim.build/au/features/viewer): A canvas-first viewer for drawings and documents. Zoom, switch revisions, overlay two issues in colour, mark up the sheet and work from the drawing index, all in the browser with markups saved against the sheet. - [Workspace](https://www.cim.build/au/features/workspace): Project spreadsheets and documents that work the way Excel and Word do. Import an .xlsx or a .docx, edit in a grid with a formula bar, formula autocomplete and the fill handle, and export back out in the same formats - all of it alongside the drawing set. - [IFC models](https://www.cim.build/au/features/ifc-models): Upload IFC models through the normal document flow and explore them in a 3D viewer alongside the drawings, so the model and the documented set stay part of the same review. ## Integrations - [Integrations](https://www.cim.build/au/features/integrations): CIM connects to the systems your project documents already live in - Procore, Autodesk Construction Cloud, Aconex, SharePoint, Google Drive and Outlook - so the set your team works from is the set that gets audited. - [Procore integration](https://www.cim.build/au/features/integrations/procore): Connect Procore and bring project drawings and documents into CIM. The drawing set syncs across as it is issued, audits run on the current revision, and findings come back with the sheet and revision attached. - [Autodesk Construction Cloud](https://www.cim.build/au/features/integrations/autodesk-construction-cloud): Bring drawings across from Autodesk Construction Cloud projects. The issued set syncs into CIM, audits run on each new revision, and findings cite the sheet and revision they came from. - [Aconex integration](https://www.cim.build/au/features/integrations/aconex): Connect Aconex to sync project documents into CIM. The transmitted set comes across as it is issued, audits run against the current revision, and every finding carries the document reference behind it. - [SharePoint integration](https://www.cim.build/au/features/integrations/sharepoint): Sync project documents from SharePoint document libraries into CIM. Point at the library, and the reports, specifications and drawings your team already files there come across for audit. - [Google Drive integration](https://www.cim.build/au/features/integrations/google-drive): Connect Google Drive and pull project documents straight into CIM. Shared drives and folders sync across, so the set your team works from is the set that gets audited. - [Outlook integration](https://www.cim.build/au/features/integrations/outlook): Connect Outlook to bring project correspondence into CIM, so instructions and sketches sent by email sit alongside the drawing set they change. ## Case studies - [Catching a $50K+ discrepancy before the package was let](https://www.cim.build/au/case-studies/50k-discrepancy-ten-minutes): A three-document coordination error on a $15M lump-sum job: RW35 required, RW30 scheduled, no seals specified. Caught, cited and confirmed before the package was let. - [Winning a $10M job without the lowest price](https://www.cim.build/au/case-studies/the-10m-win): Full tender set reviewed from day one, the material gaps raised as RFIs, and the saved hours spent on value management and the client. The cheapest bid lost. ## Blog posts - [How do I check a quantity takeoff before pricing?](https://www.cim.build/au/blog/how-to-check-a-quantity-takeoff): 5 checks to run on any takeoff before rates go on it: the revision, the scale on every sheet, the lines that carry the most cost, whether the quantities agree with each other, and whether every scope item got measured. - [What is the difference between a bill of quantities and a schedule of rates?](https://www.cim.build/au/blog/bill-of-quantities-vs-schedule-of-rates): A bill of quantities gives the measured quantity for every item and gets priced to a total. A schedule of rates fixes the rate and leaves the quantity to be measured later. Which one you use decides who carries the quantity risk. - [Can you do a takeoff from PDF drawings with AI?](https://www.cim.build/au/blog/ai-takeoff-from-pdf-drawings): Yes. AI takeoff measures off the PDF set you get at tender. How well it goes depends on whether the PDF is vector or scanned, and whether the scale is checked on every sheet first. - [Best AI drawing review software for Australian builders (2026)](https://www.cim.build/au/blog/best-ai-drawing-review-software-australia): What to look for in AI drawing review software, the 7 questions Australian builders ask in every evaluation, and where CIM Build fits. - [AI takeoff software: 8 things to check before you buy](https://www.cim.build/au/blog/ai-takeoff-software-what-to-check): A buyer's checklist for builders comparing AI takeoff and bill of quantities tools: scale calibration, markups, revisions, scope, exports and data residency. - [How to prepare a bill of quantities from drawings](https://www.cim.build/au/blog/how-to-prepare-a-bill-of-quantities): A step-by-step method for builders: write the scope per trade, measure against it, describe each line so it can be priced, and check the bill against the current revision. - [What is AI takeoff? A guide for builders and estimators](https://www.cim.build/au/blog/what-is-ai-takeoff): AI takeoff measures lengths, areas and counts off construction drawings. How it works, where it is reliable, where it needs a person, and how to check the numbers before they go into a price. - [Estimating-to-delivery handover: carrying the tender assumptions into construction](https://www.cim.build/au/blog/estimating-to-delivery-handover): Keep the tender basis, effective quotes, exclusions, budget allowances and open decisions with the project delivery team. - [How to check a fire engineering report against the drawings](https://www.cim.build/au/blog/check-fire-engineering-report-against-drawings): Pull every requirement out of the fire engineering report into a register, map each one to the sheet or schedule that should show it, and recheck the register on every revision. Here is how to do it, and where it usually goes wrong. - [Establishing a reliable head-contract baseline for drawing comparisons](https://www.cim.build/au/blog/head-contract-baseline-drawing-comparisons): Prepare the agreed reference set before comparing later drawings in CIM Build. Keep document issues, identifier mappings and unresolved pairing exceptions clear throughout the review. - [How to level subcontractor quotes: a worked example](https://www.cim.build/au/blog/how-to-level-subcontractor-quotes): Reconcile original quote totals, compare quantities and scope allowances, and select alternatives without double counting. A synthetic example shows every adjustment. - [Missing information or a design discrepancy? Reading report-to-drawing audits](https://www.cim.build/au/blog/report-audit-missing-information-vs-discrepancy): Use CIM Build’s report-to-drawing findings to separate a missing source, a conflicting requirement and evidence that still needs review before assigning the next action. - [How to compare tender drawings with contract drawings before signing](https://www.cim.build/au/blog/tender-to-contract): Use CIM Build to compare the drawings you priced with the proposed contract drawings, inspect the evidence behind each finding and work through the commercial implications in a change register. - [Twenty builders on where D&C risk is heading](https://www.cim.build/au/blog/construction-executives-dinner-dc-risk): A private dinner for twenty builders with more than $8bn of work a year between them, on the future of design & construct risk. Three themes: builders are getting choosier about clients, ECI is becoming the default, and legal spend on contracts is now a line item. - [Alternatives to LightTable: Construction AI Options](https://www.cim.build/au/blog/alternatives-to-lighttable): LightTable is fast, capable AI peer review for design - and its headline is finding more issues, faster. But more isn't the goal; the right issues for the stage is. Here's how CIM Build differs, and where the other alternatives fit. - [Alternatives to Primepoint AI: Construction AI Options](https://www.cim.build/au/blog/alternatives-to-primepoint-ai): Primepoint reads drawings as connected systems and flags clashes and gaps - genuinely capable. The real question is what you check at each documentation gate. Here's how CIM Build differs, and where the other alternatives fit. - [ChatGPT vs Claude Cowork vs Copilot for Construction: Which Should Builders Use?](https://www.cim.build/au/blog/chatgpt-vs-claude-vs-copilot-for-construction): ChatGPT, Claude Cowork and Microsoft Copilot are capable general tools — but the design & construct document jobs run across the whole set. A table comparing all three with CIM Build on spec-to-drawings, brief-to-drawings, cross-discipline coordination and revision tracking. - [Bluebeam Revu Alternatives: AI Drawing Review for D&C Builders](https://www.cim.build/au/blog/alternatives-to-bluebeam-revu): Bluebeam Revu is built for one person marking up one sheet. D&C builders carry risk across the whole pack, every revision. Here are the alternatives - and why CIM Build is built for the way D&C teams actually work. - [Alternatives to Trunk Tools: Construction AI Options](https://www.cim.build/au/blog/alternatives-to-trunk-tools): Trunk Tools detects real issues on a drawing set - but it runs the same checks every time. D&C builders need to check different things at different documentation gates. Here's how CIM Build is built around that, and where the other alternatives fit. - [A director's guide to ChatGPT and Claude for construction](https://www.cim.build/au/blog/directors-guide-chatgpt-claude-construction): General-purpose AI like ChatGPT and Claude is already on your team's phones. Here's where it earns its keep on a construction business, where it quietly fails, and the line you can't let anyone cross. - [9 questions to ask before you buy an AI drawing review tool](https://www.cim.build/au/blog/9-questions-before-buying-ai-drawing-review-tool): The AI drawing review category got crowded fast, and every demo looks great. These nine questions cut through the pitch so the tool you sign for is the tool you needed. - [AI drawing review and BIM clash detection are not the same thing](https://www.cim.build/au/blog/ai-drawing-review-vs-bim-clash-detection): Treating them as substitutes is how GCs end up paying for both and getting the value of neither. They cover different failure modes - here's how to tell which one you actually need. - [Bluebeam Max vs CIM Build: AI for Drawing Review](https://www.cim.build/au/blog/bluebeam-ai-vs-cim-build): Bluebeam Max is an AI assistant inside a per-user markup tool. CIM Build is a design-management workflow that audits the whole project pack on every revision. Most builders run both - here's why. - [Procore AI vs CIM Build: AI Drawing Review for Builders](https://www.cim.build/au/blog/procore-ai-vs-cim-build): Procore AI is a search and automation layer over your Procore data. CIM Build is a structured audit layer over your drawings, specs, schedules, and consultant reports. Both can live in the same builder. - [What the 2026-27 Federal Budget Means for D&C Builders](https://www.cim.build/au/blog/what-the-budget-means-for-dc-builders): Handed down 12 May 2026, the 2026-27 Budget is a mixed bag for design & construct: a permanent $20,000 instant asset write-off and a new $2bn Local Infrastructure Fund, set against negative gearing and CGT changes Treasury's own papers say will cut new housing supply by ~35,000 homes.