Checkpoints

Found in: Data > Checkpoint List

Checkpoints are a crucial part of the platform’s quality assurance functionality. They guide technicians on what to inspect for each product, which tests to perform, and what criteria to evaluate.

The Checkpoint Library

Every checkpoint begins its lifecycle in the checkpoint library. Each checkpoint includes several mandatory attributes that ensure clarity and consistency during inspections.

High-Level Attribute Overview

  • Name – Unique identifier of the checkpoint
  • Category – Groups checkpoints by inspection type (e.g., Product & Unit, Packing, Process Overview)
  • Motive – Groups checkpoints by inspection purpose (e.g., Safety & Regulatory, Function & Usability)
  • Description – Detailed explanation of what needs to be inspected
  • Photos – Reference images showing correct and incorrect examples
  • Required Result – Expected outcome and instructions for recording it
  • Important Flag – Marks the checkpoint as critical
  • Ordinal Position – Defines order within a category (0–100)
  • Required Photos – Minimum number of photos required
  • Coefficient – Weight of the checkpoint in the overall evaluation (0–100%)
  • Default Quantity to Inspect – Default number of samples to check
  • Service Type – Restricts checkpoint to certain service types
  • Tools – Equipment required for inspection
  • Inputs – Additional fields to be filled during inspection
  • Application Criteria – Conditions for which the checkpoint applies
  • Properties to Check – Specific product properties to validate during inspection

Configuring Inputs

Custom inputs can be added for technicians to capture detailed measurements or observations. By default, technicians record a general result per checkpoint. When specific measurements are needed—such as dimensions for a textile product—custom inputs allow for precise data collection.

Configuring Properties to Check

In addition to custom inputs, you can define dynamic product properties for verification.

For example, if a checkpoint is titled “Check Frequency”, you can associate it with a “Frequency” property. During inspection, the technician will compare the expected value with the measured one.

Applying Checkpoints to Products and Bookings

By default, new checkpoints apply to all products and bookings. However, to optimize quality control, it’s recommended to define strict application rules.

Filtering by Service Type

Checkpoints with a specific Service Type only apply to bookings with that same service type. For instance, a “Voltage Test” checkpoint would be relevant for “Product Inspections” but not for “Factory Inspections”.

📘 Booking Service Types can be configured in Vocabularies

Filtering by Product Properties (Application Criteria)

Not all checkpoints are relevant to every product. You can refine applicability by configuring Meta Properties like “Product Group”.

For example, a soft toy and an electrical product will have different sets of applicable checkpoints. A “Country” property can also be applied at the booking level to account for region-specific inspection requirements (e.g., US vs EU regulations).

Mark these meta properties as “Used for Checkpoint or Technical Folder Criteria” to enable automatic filtering.

Ensuring Correct Application

Once your Meta Properties and checkpoints are set up, attach a product to a booking. The platform will automatically assign relevant checkpoints.

If you make changes to a booking or product and expect a different set of checkpoints, click the “Refresh” button next to the product to update the checkpoint list.

Refresh Screenshot

Filtering in the Technician App

Technicians may use inspection templates to filter visible checkpoints. These templates can limit checkpoints by Category or Motive, especially useful when inspections are conducted over multiple days or by different personnel.

Sorting Checkpoints

Checkpoints are displayed in the following order:

  1. Grouped by Category
  2. Then grouped by Motive within each category
  3. Sorted by Ordinal Position

📘 Categories and Motives can be configured in Vocabularies

Booking-Level Configuration

Once checkpoints are assigned to a booking, some attributes can be overridden directly from the booking page. You can adjust:

  • Quantity to inspect
  • Required result
  • Importance flag
  • Inputs

This flexibility allows for more precise customization per inspection scenario.