Commissioning work lives and dies by two things: how quickly teams can turn field observations into actionable issues, and how easily leadership can see progress without chasing updates.
Our latest release tackles both.
We’ve shipped a set of upgrades that make reporting easier to automate and visualize datasets, and support documentation of standard procedures, checklists, and forms. This release focuses on two big areas:
- Reports: dynamic content inside your report narrative, a new section type for work templates by equipment type, and automated PDF delivery.
- Issues: configurable categories, priorities, and custom properties—designed to standardize across projects while staying flexible.
Here’s what’s new and how teams are using these new features.
1) Custom Report Shortcodes: Dynamic content inside your report text
If you’ve ever wanted your report narrative to include live project visuals—without rebuilding charts by hand—Custom Report Shortcodes are for you.
Shortcodes let you insert charts, tables, equipment lists, and other dynamic project data directly into a text editor section of your report. When you save the document and preview or export the report, those shortcodes automatically render into the final text, charts, and tables.
What you can insert today
The available custom report shortcode library now includes:
- Issue Bar Chart
- Issue Category Bar Chart
- Issue Category Line Chart
- Issue Line Chart
- Issue Responsibility Table
- Issue Top Line
- Project Member List
- Work Bar Chart
- Work Line Chart
- Work Progress Table
- Work Top Line
- Equipment List
How it works
- Pick a shortcode type from the list of available options
- Configure filters (so the output matches your audience and reporting scope)
- Then either:
- Type the shortcode into your report text, or
- Copy/paste the shortcode into your report text
Why it matters: You can write a true narrative report (“Here’s what changed this week…”) and drop in the supporting visuals right where they belong, with the confidence that the output stays current.
2) Report Delivery Schedules: Automated PDF reports, delivered on time
Manually generating PDFs and emailing them out is one of those recurring tasks that never gets easier. Report Delivery Scheduling removes that step entirely.
With scheduling enabled, Bluerithm will generate a PDF using current project data and email it to selected recipients automatically—daily, weekly, or monthly.
Key capabilities
- Schedule any custom report built with the Report Builder
- Choose daily, weekly, or monthly frequency
- Select specific days and times
- Send to multiple project members
- Delivery includes the report as a PDF email attachment
- Reports are stored securely and remain accessible via the email download link and in the project’s Files > Reports folder
Setup in minutes
You can schedule reports from either:
- Project → Reports tab → click the Schedule button in the Delivery column, or
- Open a report → click the Schedule Delivery button
Then:
- Check Enable Scheduled Delivery
- Choose Daily, Weekly, or Monthly
- Pick a time (project timezone; 30-minute increments)
- Configure frequency options:
- Weekly: choose one or more weekdays
- Monthly: choose day 1–31 (if a day doesn’t exist, it sends on the last day of that month)
- Select one or more recipients (project members)
- Click the Save Schedule button
Managing schedules is straightforward
- Active schedules show a green calendar icon (hover for a summary and recipient count)
- Disabled schedules show a gray calendar icon
- You can modify, pause (disable without deleting), or delete schedules at any time
Who can schedule? Users with the roles User or Account Admin (Privileged Guests can’t access scheduling).
3) New Report Section Type: Work Templates from Equipment Types
We’ve also added a new report section type: Work Templates from Equipment Types.
This section is designed for projects that need to document standard procedures, checklists, and forms as defined at the equipment type level—before they’re applied to individual equipment, or later as “blank templates” for systems manuals.
What it displays
- Equipment types listed alphabetically (A–Z, 0–9)
- Work items grouped by work category, then sorted by position
- Work item descriptions, tables/checklists, notes, images, and attachments
Filters & options
Filters:
- Equipment Type
- Work Category
Options:
- Include/exclude notes, images, attachments
- Page break after each work item
- Page break after each equipment type
- Skip section when empty
Why it matters: You can produce cleaner closeout documentation and systems manuals without hand-compiling templates from multiple places.
4) Issue Categories, Priorities, and Custom Issue Properties: Configure issues your way
Different projects track issues differently. Some care about safety vs. quality; others need cost impact, ECM identifiers, or compliance tags. This update makes issue tracking more configurable—while still supporting standardization.
Standardize via templates, customize per project
Your defined lists of categories, priorities, and properties can be saved on template projects and copied into new projects during setup. From there, each project can still adjust what it needs.
That means:
- Faster setup
- Consistent reporting across projects
- Flexibility where it counts
Issue Categories
Categories help classify issues by type (e.g., Safety, Quality, Design, RFI) so you can filter and report more effectively.
Add categories
- While creating/editing an issue: choose from Categories, or click Add New Category
- Or from Project → Settings → Issue Categories → Add Category
Delete categories
- Project → Settings → Issue Categories → Delete
- Existing issues keep the old value, but the category won’t be available for new issues.
ACC-connected projects (Autodesk Construction Cloud)
- Categories are read-only in Bluerithm and sync from ACC Issue Types.
Issue Priorities
Priorities let teams communicate urgency and focus (e.g., Critical/High/Medium/Low or 1–5).
Add priorities
- While creating/editing an issue: Priorities dropdown → Add New Priority
- Or from Project → Settings → Issue Priorities → Add Priority
Delete priorities
- Deleting doesn’t change existing issues (they keep the value), but it removes the option from new/edit dropdowns.
Procore-connected projects
- Priorities are read-only in Bluerithm and sync from Procore Observation Priorities.
Custom Issue Properties
Properties are custom fields that apply to all issues on the project—perfect for anything beyond the standard issue schema (e.g., Cost Impact, Expected Savings, ECM Identifier).
Add properties
- Project → Settings → Issue Properties → Add Property
- The field is immediately available on all issues.
Edit properties
- Click the Edit button in the Issue Properties section
- Rename, set defaults, define units for numeric values, and set display order.
Delete properties (important warning)
- Go to Project > Settings, scroll to Issue Properties, click Delete next to the property, and confirm
- Deleting a property removes it from all issues and permanently deletes the data stored in that field.
Locking properties
- You can lock a property so Guest users can’t edit it per-issue. When locked, edits happen from the Issue Properties Edit page and apply consistently.
Sync + reorder
- Sync can be needed if changes were made while users created issues offline.
- Reorder is drag-and-drop for controlling how properties appear.
Best practices (quick wins)
Categories
- Start with 5–10 broad categories
- Use consistent naming conventions
- Remove unused categories over time
Priorities
- Keep it to 3–5 levels
- Choose one format (numbers or labels) and stick to it
- Document what each level means
Properties
- Add only what you truly need (they apply to every issue)
- Use clear names, set defaults when helpful
- Lock sparingly
- Clean up properties you no longer use
Wrap-up: Reports that run themselves, issues that match your reality
With report shortcodes, scheduling, and the new work template report section, it’s now much easier to generate polished reporting that stays current—and to distribute it automatically. And with configurable issue categories, priorities, and properties, your issue data becomes more consistent, more reportable, and more useful across teams and projects.
