SafetyCulture
  1. Inicio
  2. Usar SafetyCulture
  3. IA en SafetyCulture
  4. Configure your lines and products

IA en SafetyCulture

Última actualización: 5 de junio de 2026

Configure your lines and products

Learn how to set up Production so your team can start running quality checks on the floor.

Before operators can run checks, you need to tell Production what you're making, where you're making it, and what good looks like. That means configuring three things: lines with their areas, check items, and products with their specifications.

Most admins are moving from a paper or spreadsheet-based process, so the easiest place to start is your lines, then build out the areas and check items within them. Once your check items exist, you can set up your products and link specifications back to the right checks. A typical order is:

  1. Set up production lines and areas: create a line under your site and add the areas where checking happens.

  2. Set up check items for an area: add the check groups and the individual checks operators complete.

  3. Set up products and specifications: add your products and link specifications to the matching check items.

  4. Set up alerts and critical alerts: decide how deviations are raised and who gets notified.

You don't have to build all of this by hand. You can configure everything manually using the articles above, generate a starting configuration with the AI setup assistant and refine it, or contact our team for a guided demo. Once your lines, areas, products, and alerts are in place, you're ready to start a production run.

What is the AI setup assistant?

The AI setup assistant helps you build out your Production configuration from a description of how your facility operates. Instead of creating each line, area, check group, and check item one by one, you describe what you make and how you check it, and the assistant generates a starting configuration for you to review and refine. This gets new sites running faster and gives you a structured first draft you can adjust manually at any time.

Set up with the AI setup assistant

Web app

  1. Log in to the web app.

  2. Select Production in the upper navigation.

  3. Click Configure.

  4. Click Quick Setup in the top right corner.

  5. Describe your operation: the lines you run, the areas on each line, the products you make, and the checks you perform, including how often. Upload any docs that support this detail.

  6. Review the lines, areas, check groups, check items, and products the assistant generates.

  7. Adjust anything that isn't quite right, then save.

Please note that the assistant creates a starting point, not a finished configuration. Review the generated check items and specifications against your real tolerances before you run a product, and fine-tune them using Set up check items for an area and Set up products and specifications.

What are lines and areas?

A line represents a complete production flow, raw materials in, finished or in-process product out. If a product is stored and then processed again later, that's generally a separate line. Areas are the specific zones or stations within a line where work, and checking, actually happens, and where most of your configuration effort goes. Each area contains check groups: sets of check forms that operators complete during a production run.

Add a line and its areas

Web app

  1. Log in to the web app.

  2. Select Production in the upper navigation, then select Sites and your site.

  3. Select Add line, enter a name that reflects the flow (such as "Filling Line 3" or "Blending to Packaging"), and select Save.

  4. Select the line, then select Add area and give it a name.

  5. Select Add check group, give the group a name, and choose a trigger type: Manual or Time interval. If you chose Time interval, set how frequently the check should run, such as every 30 minutes. You can change this later.

  6. Select Add check item, then pick an existing check item or create a new one.

  7. Repeat for as many check groups as the area needs, then select Save.

Please note that both trigger types only activate once a product run is underway in that area. A manually triggered group is a batch check, prompted by the operator at a moment such as a batch change. A time-interval group is a production check that the system prompts automatically.

What are check items?

A check item is a single thing an operator records during a run, such as label position, fill weight, or appearance. Check items live inside check groups within an area, and each one has a response type that controls how the operator answers and how the result is validated. Clear check items mean operators capture consistent data, and the right results can be measured against your product specifications.

Add a check item to a check group

Web app

  1. Log in to the web app.

  2. Go to Production > Configure, select your site, then select your line and area.

  3. Open the check group you want to add to, then select Add check item.

  4. Pick an existing check item, or select to create a new one.

  5. When creating a new check item, give it a name and set its response type:

    • Number: validates against a product specification limit pulled in at run time.

    • Choice: a list of selectable options.

    • Text: a free-text response.

    • Calculation: a computed value based on other inputs.

  6. Select Save.

Tip: Number check items don't have fixed limits. They reference your product specifications. This means the same area can run different products with different tolerances without any reconfiguration. The right limits load automatically when a product run starts.

What are products and specifications?

A product represents a finished or in-process item your facility manufactures. Each product carries specifications, the measurable quality attributes that define what good looks like, such as fill weight, dimensions, percentage values, packaging codes, and barcode numbers. Production matches specifications to the check items in your areas, so the right limits flow through automatically at run time and every result is read against the correct standard.

Please note that before you can add a specification to a product, the corresponding check item needs to exist in your areas. If you haven't set up your areas yet, do that first and come back here.

Create a product

Web app

  1. Log in to the web app.

  2. Go to Production> Configure > Products, then select Add product.

  3. Enter the SKU Number (your product identifier) and the SKU Name (a human-readable name).

  4. Select the Sites this product applies to. You can assign it to multiple sites.

  5. Add your Specifications, select from existing check items, then set the acceptable values and any out-of-spec or critical limits. Each specification is either a number range (minimum and maximum) or a multiple choice list.

  6. Select Save.

How do alerts work?

Production alerts are driven by issues. When a check result breaches an out-of-spec or critical limit, Production automatically creates an issue and fires an alert in the background. As an admin, you configure which issue category is raised for each alert type, and that category controls the severity, who gets notified, and how. Because issue categories can be used across your whole organization, alerts stay consistent at scale, and assignment is scoped to site members within a group so only the right people are notified for each site. Both standard and critical alerts require setup. The difference is only in how you configure each.

Set up alerts

Web app

  1. Log in to the web app.

  2. Go to Issues and create a new category for your alert type, then set the notifications, who gets alerted, at what severity, and how. If you manage multiple sites, use the Sites × Groups function to apply one category across sites while notifying only the right people at each location. Repeat for each alert type you need.

  3. In Production, Configure.

  4. Select which issue category to use for out-of-spec alerts, and, separately, which to use for critical alerts.

Please note that you can configure notifications for out-of-spec deviations, critical limit breaches, or both. We recommend reserving critical notifications for critical limits only, so urgent alerts stay meaningful.

¿Fue útil esta página?

SafetyCulture
App Store
Google Play