Office Hours

Customer Success Live Q&A

Office Hours Q&A

These questions come from our Customer Success Office Hours with Thane Vajda, CSM. Some were submitted when attendees registered, and the rest were asked live. Each one has Thane’s answer below.

Submitted Questions

How can I set up a workflow that assigns someone to a checklist after it’s been completed?

Start with why. Usually the goal is to make sure the right person knows a checklist is ready for their review.

The simplest option is the Watch button on a checklist. Anyone watching a checklist gets a notification every time its status changes. That works for a handful of checklists, but it gets tedious as your project grows, and so does bulk reassigning checklists to each reviewer.

Thane’s recommendation is to build the workflow into your checklist statuses.

  1. Add a status for each review stage. In your project settings, add statuses like “Complete and Ready for Mechanical Review” and “Complete and Ready for Engineering Review”, each with its own color.
  2. Restrict who can set each status. In the status permissions, choose who can use each status. Permissions are now multiselect, so you can select owners, co-owners, and managers along with specific people, companies, or roles. For example, only the mechanical contractor and the commissioning provider can set “Complete and Ready for Engineering Review”. You can also restrict who can unset a status, so a finished checklist stays finished.
  3. Give each reviewer their queue. Reviewers open the dashboard, or filter the checklist list by status, to see everything waiting on them. When they finish a review, they move the checklist to the next status. If something isn’t ready, they send it back with a status like “Contractor Review Required”.

Nobody has to remember to reassign anything, and you can see at a glance how many checklists are waiting on each team.

How can I best show weekly progress on checklists?

For a snapshot of where things stand today, use the checklist section of the dashboard. Break checklists down by status, add a second breakdown such as checklist type or discipline, then open the table view. You’ll see exactly where your L1, L2, and L3 checklists stand.

To show what changed from one week to the next, use a progress report. Progress reports draw on the project’s activity log, which records every change, including checklist status changes.

  1. Go to Reports, open Progress Reports, and add a new report. Give it a name and a report date.
  2. Choose a reporting period. The presets include previous week, month to date, and previous month, or you can set a custom range.
  3. Open Details to see new items and completed items for that period.
  4. Select PDF, choose what to include, and save those options as your default so the next report is ready to go.

An item counts as completed when it reaches the last status in its workflow. That applies to checklists and issues alike. Statuses that sit outside a workflow, such as Failed, Complete with Open Issues, or Seasonal Testing Required on a test, are also counted as completed, so a failed test still shows up in your report.

For completion trends over time, add milestones. Milestones let you set rules, such as equipment status changes, checklist line item completion, or issues closed, and plot them over time. Both have dedicated videos in our Customer Success Series, Milestones and Progress Reports.

Is there a way to build a milestone template and save it to my account?

Yes. Milestone templates are built at the account level as Milestone Presets. A milestone you’ve already set up in a project doesn’t save back up to the account, so build your presets at the account level first, then use them in every new project.

  1. In your account, open Milestone Presets and create a preset. For example, checklist completion over time, with rules at 20%, 40%, 60%, and 80% complete.
  2. In a project, go to Milestones, add a new milestone collection, and select your preset. The rules come in preconfigured.

Presets use your account-level settings. If your project statuses don’t match your account statuses, the preset can’t pull the right data, so keep the two aligned.

Milestones and Training

Do you offer specific training for milestones? We’re having trouble tying milestones to construction dates for equipment and checklists.

Yes. If you work with a Customer Success Manager, reach out to schedule time. Milestones are one of the topics we’re asked about most, and your CSM can work through your setup with you.

If you want something to share with your team right away, watch the Milestones video from our Customer Success Series.

Drawings, RFIs, and Integrations

Can we bring approved drawings into CxAlloy for review and reference during QA/QC inspections, including as-builts?

Yes. In CxAlloy, there are two places to keep drawings.

For reference, upload them to the Files section of your project. Files supports your common file types and keeps revisions, so it works well for drawing sets, commissioning plans, and other project documents.

For review, create a design review for each drawing set, such as 50% DD, 50% CD, or issued for construction. Each design review has its own file section where you can mark up and redline drawings, then download them at the end of the project as a record.

If you use Built Insights, you can also upload drawings in Smart Markups under Documents and associate each one with a project. Markups on the drawing link directly to your CxAlloy data, including equipment, issues, checklists, and tests. Click a markup and it opens that record in your CxAlloy project, so the drawing becomes a living view of progress across the project.

The right approach depends on what you want the drawings to do. Your CSM can help you decide whether a file upload or Smart Markups fits your team best.

Our projects have multiple stakeholders and no single construction management platform, so we track RFIs in Field Observations. Will RFIs have their own section in CxAlloy?

Thane’s recommendation today is to track RFIs with issue attributes. In your project settings, add an issue attribute called RFI Required. Set the validation type to single select, with Yes and No as the options.

When you log an issue, set RFI Required to Yes if it needs a request for information. You can then search by that issue attribute to pull up every issue that needs an RFI. You can also combine it with issue types to narrow the list further.

From there, your team can write and respond to RFIs in whichever platform the project uses.

Can information from a sequence of operations be turned into test lines?

Yes, through Built Insights. AI integrations run through Built Insights rather than directly in CxAlloy, connecting your CxAlloy data with the AI tool of your choice or other tools in your stack.

For example, your team uploads a sequence of operations to the AI tool or file repository you already use. Built Insights reads the data from there and pushes it into CxAlloy as a new checklist or test template, with each step as a line item. The same approach works for pushing changes to existing templates.

Importing and Exporting Data

What are the best practices for importing from Excel, and what can and can’t be imported?

CxAlloy imports CSV, XLS, and XLSX files. You can export an existing list, make your changes, and import that same file, or use any spreadsheet that follows the supported formats.

Two things to watch for.

  • Macros. Macros don’t carry over into CxAlloy.
  • Formulas. Formulas import as the formula itself, not the result. A VLOOKUP comes in as “=VLOOKUP” rather than the value you see in Excel.

Before importing a spreadsheet that uses formulas or macros, save a copy, select all the data, and paste it back as values or plain text. The results of your formulas stay, and the file imports cleanly.

When you build your import file, keep each type of data in its own column. All equipment names in one column, all disciplines in another, and so on. Beyond that, the file can include as many columns as you need.

What are the options for exporting data out of CxAlloy?

Most areas of CxAlloy include an export, and you now have a Custom option alongside the full export. Custom lets you choose exactly which columns to export. For example, you can export just the equipment name, zone, manufacturer, model, and serial number. Extended status information adds the date and time each status was set.

Exports open in Excel by default, and Excel sometimes reformats values. A serial number with leading zeros may lose them, or a value may pick up commas or decimals.

There are two ways to keep your data exactly as entered.

  • Export a CSV from the account level. From there, you can export data from any project, with attributes and extended status information, and the CSV keeps leading zeros intact.
  • Include a dash or underscore in the value. If your naming convention allows it, Excel treats the value as text and leaves it alone. Commas and decimals don’t have the same effect.

How do I update data through an import without creating duplicates or overwriting records?

During the import, select the option to update existing equipment. CxAlloy then updates matching records and adds anything new, instead of creating a second copy of each piece of equipment.

Changing equipment names takes one extra step, because the name is usually what the import matches on. Thane’s recommendation is to add an attribute called Old Name.

  1. Export your equipment list and copy the current names into the Old Name column.
  2. Import the file with the update option, matching on name. Every piece of equipment now carries its original name as an attribute.
  3. From then on, match imports on Old Name instead of the name. You can then rename equipment freely without creating duplicates.

This process is covered in detail in the Progress Reports video from our Customer Success Series.