Back to library
Forms + AssetsWorkflow capture pendingReal TASC screen

Create an Asset Pre-Use Inspection

Build the first connected form template and launch it safely from an asset QR code.

18 minutes7 stepsCoreUAT screen captured · Production cross-check pending

Outcome

A mobile-friendly inspection template is linked to an asset, captures useful evidence and produces a reviewable result when a check fails.

Find it in TASC

Employer PortalSettingsForm TemplatesTASC Assets

Before you begin

  • A test asset and inspection profile
  • The approved inspection questions
  • A named reviewer for failed conditions
  • Synthetic success and failure test cases

Actual TASC screen

Build the Assets form template

Choose the module and template, then structure the worker journey and individual fields.

UAT capture
Annotated TASC Form Templates editor showing the Assets module, selected template, Add Steps and an Asset Name field card.Open full-size
TASC UAT · demo template · 6 Sep 2026. Callouts were added for learning; identifying information is redacted and active training codes are hidden.
1TASC AssetsSelect the module that will own the template.
2Template listOpen an existing template or create a purpose-specific one.
3Add StepsBreak longer forms into clear sections for field users.
4Field cardSet the label, type, requirement and supporting guidance deliberately.

Decisions that matter

Required fields

Require only information needed to make or verify the safety decision.

Conditional follow-up

A failed check should request the evidence and detail needed for action—not every possible field.

Live-template changes

Treat changes to fields, order, logic, permissions or outcomes as controlled workflow changes.

0 of 7 steps complete0%
x

Progress is saved on this device only.

  1. Step 1

    Open Form Templates

    Choose the Assets module and create a clearly named template for the inspection purpose.

  2. Step 2

    Build the core fields

    Add inspection date, asset link, condition checks, comments and evidence fields.

  3. Step 3

    Set requirements deliberately

    Make only necessary fields mandatory and explain why evidence is required.

  4. Step 4

    Add conditional follow-up

    Use conditional logic so a failed check requests the right evidence or follow-up information.

  5. Step 5

    Link the template

    Connect the form to the appropriate asset inspection profile.

  6. Step 6

    Test the complete path

    Scan the asset QR, complete both successful and failed scenarios, and review the resulting record and actions.

  7. Step 7

    Control later changes

    Retest live templates after changes to steps, required fields, logic, permissions or outcomes.

Prove it worked

  • The template appears for the correct asset/profile
  • A pass can be completed efficiently on mobile
  • A failure requests the intended evidence
  • The resulting record and follow-up reach the authorized reviewer

Common problems and safe recovery

The form does not appear after scanning.

Confirm the template module, active status, asset inspection profile and QR scope.

A failed check creates no usable follow-up.

Review conditional logic, evidence requirements and the configured action or reviewer path.

What happens next

Publish only after desktop and mobile tests cover pass, fail, missing evidence, denied access and inactive QR states.