Your weekly documents, generated

Use it when you write the client’s requirements, or to check a tender BEP against them.

Write the client’s exchange information requirements as a register and check the BEP answers each one.

Use it when you need to write or update the BIM execution plan.

Assemble a BIM execution plan from editable sections, with your tool outputs as appendices.

Use it to agree who does what for information management.

Who is responsible, accountable, consulted and informed for each information management task.

Use it to plan which documents and models each team delivers, and when.

Plan every information deliverable per task team, with document numbers and milestones, and roll up the MIDP.

Use it to agree coordinates and check the model sits in the right place.

Coordinate system, base points and survey control, with a best-fit check and IfcMapConversion values.

Use it when survey, GIS and model coordinates are in different systems, or you need true north for the model.

Convert points between coordinate reference systems by EPSG code, with convergence and scale factor.

Use it when you agree room, sheet or asset numbering, or need to renumber consistently.

Define how rooms, sheets or assets are numbered and preview every new number.

Use it to agree how developed each element must be at each stage.

Set the level of development per element and stage, with responsibilities and information requirements.

Use it to turn information requirements into a file software can check.

Write information requirements as a machine-checkable IDS file — or generate them from your LOD/LOIN matrix.

Use it when you set up the project’s Revit parameters so they match the information requirements.

Build and check a Revit shared parameter file, and the matching IFC property set mapping.

Use it at the start of coordination to decide which clash tests to run.

Define which disciplines are tested against each other, with tolerances, priorities and owners.

Use it every week: agenda, attendance, issue log, actions and minutes.

Agenda, attendance, issue log, actions and minutes. Roll open issues into the next meeting.

Use it every week to report delivery progress to the project team and the client.

A one-page weekly delivery report from your MIDP, issues, RFIs and model QA, with a trend.

Use it after a clash run to turn thousands of clashes into a few issues.

Turn a Navisworks clash report into a short list of grouped issues, then send them to the Meeting Pack.

Use it to read issues from BIM tools, or send your issues back to them.

Open a .bcfzip to review topics and snapshots, import them as issues, or export your issue log as BCF.

Use it to track questions sent to the design team until they are answered.

Numbered requests for information with due dates, responses, impacts and an overdue watch.

Use it whenever drawings are issued, so everyone knows which revision went to whom.

Keep the drawing list with revisions and status, check numbers, and issue transmittals.

Use it when a model arrives and you need to know if it meets the agreed information requirements.

Check an IFC model against an IDS file and see which elements fail, and why.

Use it when you receive an IFC file, before you federate or share it.

Open an IFC file in the browser: structure, elements, properties and required-property checks.

Use it when a new model version arrives and you need to know what changed since last week.

See what changed between two versions of an IFC model.

Use it to look at a model without installing software, or to show where requirements fail.

View an IFC model in 3D and colour it by class, property or IDS results.

Use it when you need quantities, a door or equipment schedule, or a property review from an IFC model in Excel.

Export element properties from an IFC model to a formatted Excel schedule.

Use it each cycle to record whether each team’s model passes the agreed checks.

Pass/fail checks per discipline before models are shared — a record for every coordination cycle.

Use it to check file names before they go into the CDE.

Check file and container names against your project's naming convention, field by field.

Use it to tidy family and type names before a model is shared or a library is published.

Check family and type names against your naming rule and build a rename table.

Use it before handover to check the asset data spreadsheet.

Check a COBie workbook for missing sheets, blank values, duplicates and broken references.

Use it during inspections and before handover to record and close out defects.

Record site defects by location and trade, with photos, and track them to closed.