Skip to content
Explore the preview
Browse workflow ideas

Find possible project-standard gaps before an engineer signs off.

Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.

For supported building project files you are authorized to inspect, compare extracted data with approved spreadsheet rules and prepare an error summary and quantity tables. Automated checks can miss design intent or flag acceptable exceptions, so keep the rule version and source file visible, protect project data, and treat findings as review prompts. An engineer or project owner must resolve exceptions and approve any changes before the model is revised or delivered.

Explore the simulation Explore the idea

Actual availability depends on published steps, supported connections, permissions, and provider approval.

Illustrative workflow and outcome
A building project file is submitted for standards reviewA supported project file and a current, owner-approved standards sheet
“Identify possible naming, structure, attribute, or completeness issues without changing the project file.”
Work through the request.

Clear tasks, with review where it matters.

  1. Confirm the project file and review scope
  2. Select the current approved standards
  3. Prepare a findings and quantity report
See all 5 tasks
A findings report and quantity tables linked to source and rule versions.

What this workflow could do

Helps project teams compare building model data with documented standards and review possible issues.

Review points proposed in this idea

Automated checks are not an engineering certification. Validate rules, units, and exceptions, keep the original unchanged, and require a qualified reviewer to approve any correction or compliance decision.

How the idea could work

Select an illustrative task to explore its proposed role. No workflow runs here.

Explore the sequenceStep 1 of 5

  1. Check file ownership, supported format, and which project standards apply.

Step 1 of 5

Confirm the project file and review scope

Check file ownership, supported format, and which project standards apply.

Proposed setup considerations

These are planning notes for the concept, not instructions for a currently available template.

  1. 01

    Maintain versioned project standards

    Document rule owners, scope, field definitions, and review dates.

  2. 02

    Define supported file and output handling

    Preserve source files and keep reports in approved project storage.

  3. 03

    Set exception and escalation guidance

    Route uncertain or safety-relevant findings to qualified staff.

  4. 04

    Assign an engineering approver

    Name who signs off on corrections and any compliance statements.

Read the prelaunch status

Published templates and verified customer availability remain pending.

A little help with the whole task

A little less busywork.
A little more room for you.

Explore the sample experience while launch details are being finalized.

View pricing status Explore the simulation