3D Checklists

Use this guide to author and run 3D Checklists in WorkLink Create and WorkLink. A 3D Checklist turns parts of your 3D model into an interactive, object-by-object checklist in AR—ideal for inspections, assembly verification, and sensor-driven procedures like bolt torque.

What is a 3D Checklist?

A 3D Checklist is attached to a single step in your work instruction. Instead of having to create a new step to capture data for every object, you can use 3D Checklists to work through and capture data for a sequence of 3D objects on a single step.

For each object, the checklist tracks a state:

While working, the Viewer sees:

• A highlight or reticle on the active object in AR
• An optional callout with instructions or live readings
• A slide-in panel with Current and All tabs showing progress

You can run checklists in two modes:

• Manual — the Viewer taps Pass or Fail on each object
• Connected — live sensor/IoT data automatically marks objects Pass or Fail and can advance to the next object

When to Use a 3D Checklist

3D Checklists work well when:

• The task is tied to specific physical parts in the 3D model
• Objects must be completed in a defined order
• You want to capture readings or photos per object
• A connected device (torque wrench, sensor, PLC tag) should drive Pass/Fail automatically

Examples: torquing bolts in sequence, inspecting multiple components, verifying sensor readings at each connection point.

Prerequisites

Feature availability: 3D Checklists require the 3D Checklists feature to be enabled for your organization. Contact your WorkLink administrator if you do not see this option.

Connected data: To use live sensor values, your organization must have Connected Services (IoT data sources) configured. Your administrator sets these up outside of Create. Once configured, you reference those values inside your checklist.

 

Creating a 3D Checklist

Step 1: Select your step

In WorkLink Create, select the step where the checklist should appear.

Step 2: Open the Form Editor

Go to Window → Form Editor.

Step 3: Set the form type

At the top of the Form Editor:

1. Set Type to 3D Checklist
2. Choose Priority:
   • Passive — panel stays closed until the Viewer opens it
   • Auto Open — panel opens automatically when the step starts (common for checklists)
   • Force View — Viewer must complete the checklist before advancing

Step 4: Configure the checklist sections

The Form Editor shows these sections (in order):

 

Configuring Checklist Objects

In the Objects section:

1. Click Add Object for each part in your checklist. You can also multi select objects in the Step Hierarchy and drag them into the Form Editor.
2. For each row, set:
   • Label — the name shown to the Viewer (e.g., "Bolt 1")
   • Object — the 3D object used in the checklist
3. Enable Order Specific if objects must be completed in a fixed sequence

Tip: When Order Specific is on, use Order Selection Mode (shown below) to define the order directly in the 3D scene. Drag rows to reorder, or click objects in the scene to set sequence.

Configuring States

In the States section, control how Pass and Fail work:

Default error message (if you leave the field blank):
"This object failed. Check with your team lead for next steps."

Custom states can also be added by changing the dropdown from Pass/Fail to custom. This allows you to add additional states and custom images to each state.

Manual Selection Mode

By default, manual selection mode is enabled whenever Connected Data is not enabled. In manual mode, the Viewer can tap the object to see all the states available to them. If Order Specific is enabled, they can only select the next object in the sequence, or previously completed ones.

Connected Data

The Connected Data section links your checklist to live sensor or device readings. This is where automatic Pass/Fail and live readings are configured.

Use Connected Services

Turn Use Connected Services on to:

• Read live values from connected devices
• Automatically set object states when conditions are met
• Auto-advance to the next object when configured

Turn it off for a fully manual checklist where the Viewer taps Pass/Fail themselves.

Note: If you open an older project that does not have this setting, it behaves as if Connected Services is on until you change it.

Conditionals

Conditionals are rules that run when a check passes. Each condition watches a value and, when its rule is satisfied, performs actions such as marking an object Pass or moving to the next object.

Helper text in the editor:
"Each condition watches for its check to pass and then runs its actions, such as setting an object's state or moving to the next one."

Building a condition

Available actions

Click Add Condition to add more rules (e.g., one for Pass, one for Fail).

Example: auto-Pass when torque is in spec

• Value to watch: your torque sensor tag
• When true: reading is above your minimum (e.g., #MyTorqueWrench_Reading_value > 1000)
• Then:
  • Set Active Object State → Pass
  • Select Next Object

Example: auto-Fail when torque is too low

• Value to watch: same torque sensor tag
• When true: reading is below your fail threshold (e.g., #MyTorqueWrench_Reading_value < 100)
• Then:
  • Set Active Object State → Fail

When Pass state required is enabled and an object fails, the Viewer sees a dialog with:

• Try Again — retry the same object
• Start Over — reset the entire checklist (only if Can be re-started is enabled)
• Bypass — skip the failed object and continue (only if Fail state can be bypassed is enabled)

Live Values

Live Values are variables that update continuously while an object is selected. Use them to show real-time readings in callouts or to store the latest value per object.

Helper text in the editor:
"These variables are updated continuously while an object is selected, unlike the conditions above which only run when their check passes."

Setting up a Live Value

Click Add Variable and configure:

Conditionals vs. Live Values — when to use which

You typically use both together: Live Values display the reading in real time; Conditionals decide when the object passes.

Referencing IoT and UI Variables

• Use the # prefix to insert live data into conditions, Live Values, and callout text.
• IoT / connected device tags follow this pattern:
  • #Topic_Device_Tag_Field
  • Example: #Factory_Turbine1_Vibration_Value
• UI variables you create (such as Live Values):
  • #BoltTorque
• When Per item is enabled, each object gets its own stored value. In callout text, #BoltTorque automatically shows the reading for whichever object is currently active.
• Built-in variables like #StepName and #ProjectName also work in callout text.
• IoT data sources are configured by your administrator. In Create, you use existing tags—you do not create new IoT subscriptions from the Form Editor.

Callouts and Highlights

Callouts

Callouts can be turned on for objects in the 3D checklist. This will override the majority of the object’s callout settings that are usually found in the object properties with the exception of size, offset and origin.

In the Callouts section, configure 3D labels that appear on each checklist object. Use them to show:

• Object name or instructions
• Live readings via variables (e.g., "Target: 1000 N·m — Current: #BoltTorque")

The Default tab is the baseline for all the other states. Changes values on this tab for them to propagate across all the other states. You can set different callout appearances per object state via the other tabs: Waiting, Active, Pass, Fail.

Highlights

Highlights can also be turned on, or off and customized on a per state level. Objects can be highlighted using a reticle or a highlight sphere. 

• Reticles can be customized to use any graphic you like
• Highlight spheres use the same visual as per the Timeline Editor

Checklist Questions

In Checklist Questions, add form fields shown on the Current tab for each object:

• Text fields (e.g., "What torque was achieved?")
• Checkboxes (e.g., "Does the bolt meet QC requirements?")
• Photos, numbers, and other form types

These questions appear per object as the Viewer moves through the checklist. Answers are captured separately for each object.

Click Add Checklist Question to add fields.

Example Use Case: Bolt Torque Procedure

This is a common 3D Checklist scenario: a technician must torque three bolts in order, with a connected torque wrench driving Pass/Fail automatically.

Scenario Overview

1. The Viewer enters the step; Bolt 1 becomes active and is highlighted in AR
2. The torque wrench sends live readings to WorkLink
3. The callout shows the current torque via a Live Value
4. When torque stays in spec, the bolt is marked Pass and the checklist advances to Bolt 2
5. If torque is too low, the bolt is marked Fail and the Viewer sees an error dialog
6. The Viewer confirms a QC checkbox before moving on
7. After all three bolts pass, the Viewer taps Continue to advance to the next step

Authoring Setup: Bolt Torque

1. General settings

• Type: 3D Checklist
• Priority: Auto Open
• Description: "Torque all three bolts to specification before continuing."
• Can be re-started: On (allows Start Over if something goes wrong)

2. Objects

Add three objects:

Enable Order Specific so bolts must be torqued in sequence.

3. States

• Pass state required: On
• Fail state can be bypassed: On (optional—allows supervisor override)
• Error Message: "Torque below spec. See your team lead."

4. Connected Data

• Live Values — add one new variable

Condition 1 — Pass when in spec

Field	Value
Run when value changes	Off
When true	Your pass criteria plus a baseline value e.g. #drill_torque_torque_value > 180 && <= 200 && #baseline == true

The baseline value is required, so the check forces the torque reading to drop to zero or near zero before considering its value for the condition. Without this check it would instantly see the passing torque on all bolts and pass them all immediately.

• Action 1 - Set Active Object State

Field	Value
State	Pass

• Action 2 - Select Next Object
• Action 3 - Set UI Variable

Field	Value
Variable Name	Baseline
Type	Boolean
Value	True

 

Condition 2 — Fail when below spec

Field	Value
Run when value changes	Off
When true	Your fail criteria e.g. #drill_torque_torque_value > 200

• Action 1 

Field	Value
State	Fail

 

5. Callouts

Set callout description text such as:

Bolt: #ObjectName

Current torque: #BoltTorque N·m

Target: 180-200 N·m

The learner sees the live reading update as they torque each bolt.

6. Test and publish

1. Use Simulate in Create to walk through the flow
2. Verify each bolt highlights, live torque appears, and Pass/Fail triggers correctly
3. Publish your project

What the Viewer Experiences

Starting the checklist

When the learner reaches your step, the checklist panel opens (if Auto Open or Force View is set). The Current tab shows the active object; the All tab shows overall progress such as (passed: 0, failed: 0).

Connected mode (Connected Services on)

1. First unresolved object activates automatically
2. Live readings stream into callouts and Live Values
3. When a condition passes, the object is marked Pass (or Fail) and may auto-advance
4. Checklist questions may auto-fill (e.g., measured torque)
5. Learner confirms any required checkbox
6. When all objects are done, taps Continue

Manual mode (Connected Services off)

1. First object becomes Active with a highlight in AR
2. Learner taps Pass or Fail on the object
3. If Fail and Pass state required is on, a dialog appears with Try Again, Start Over, and/or Bypass
4. Learner answers any checklist questions on the Current tab
5. Uses Previous / Next to move between objects (unless Order Specific restricts navigation)
6. When all objects are complete, taps Continue

Restarting

If Can be re-started is enabled, the learner can restart the checklist from the All tab. They will be warned:

"Re-starting will clear all your captured data. Restart?"

Tap Reset to start over.

Tips and Best Practices

1. Start simple — build a manual 2–3 object checklist first, then add Connected Data
2. Use Order Specific for sequential procedures like bolt torque
3. Pair Live Values with Conditionals — Live Values for display, Conditionals for Pass/Fail logic
4. Turn on "Run when value changes" for IoT-driven conditions so readings must actually change (not just be in range on step entry)
5. Write clear Error Messages so viewers know what to do when something fails
6. Test with Simulate before publishing, especially connected flows
7. Use meaningful object labels — "Bolt 1 – Front Left" is clearer than "Object 3"
8. Enable Can be re-started for long or critical checklists where a full reset may be needed

Frequently Asked Questions

Can I use a 3D Checklist on multiple steps?
Each step has its own checklist. Configure a separate 3D Checklist on each step that needs one.

What's the difference between a Form and a 3D Checklist?
A standard Form is a flat list of questions. A 3D Checklist ties questions and states to specific 3D objects in your scene.

Do checklist answers get saved?
Yes. Per-object states and form answers are captured as the viewer completes the checklist.

Can viewers skip objects?
Only if Order Specific is off (free navigation) or Fail state can be bypassed is on after a failure.

I don't see "3D Checklist" as a Type option.
Ask your administrator to enable the 3D Checklists feature for your organization.

I don't see my IoT tags in the variable picker.
Connected Services must be configured for your environment. Contact your administrator to verify IoT data sources are set up and publishing.

Known Limitations

• Step-level, not per-object: Use Connected Services applies to the whole step. You cannot mix IoT-driven and manual objects on the same step.

• Achieved value is session-only: Settled row text is a display cache derived from per-item Live Values; not persisted, cleared on restart.