Action Focus
The Focus indicates where an Action Plan action acts: on the product, on the process, on the cause or on another target defined by your organization. Some customers also call it the action's Object or Target.
Besides classifying actions, the focus lets the manager of a form require that each anomaly registered during data collection has actions with certain focuses. For example: every anomaly needs at least one action on the process and one action on the cause, while an action on the product is optional.
The feature has three parts:
- Focus registration, done once in the module settings and shared by all forms.
- Per-form configuration: which focuses are displayed and which are required.
- Validation during collection: the form is only sent when each anomaly has actions with every required focus.
What the Focus is for
The focus answers the question "What does this action act on?". It is different from the Action Type, which answers "What is the nature of this action?" (immediate, corrective, preventive...). The same action can be, for example, of type Corrective action with focus Action on the process.
The focuses suggested by the system are:
| Focus | When to use | Example |
|---|---|---|
| Action on the product | Handle the product or batch affected by the deviation | Segregate and re-inspect the batch produced with out-of-standard temperature |
| Action on the process | Fix or adjust the process so the deviation stops happening | Adjust the oven setpoint and review the work instruction |
| Action on the cause | Eliminate the root cause identified in the analysis | Replace the faulty temperature sensor |
You can use these three, rename them or register others that make sense for your organization, such as Action on the supplier or Action on the equipment.
Requiring an action on the cause and another on the process prevents an anomaly from being "solved" only with a containment on the product, without treating the origin of the problem.
Registering focuses
Focuses are managed in the module settings area. To access it, the Manage settings profile is required.
Accessing the settings:
- In the side menu, go to Action Plan Settings.
- Click the Focus tab.
Adding the suggested focuses:
While the list is empty, clicking the New focus button shows the No focus registered dialog with the suggested focuses (Action on the product, Action on the process and Action on the cause).
- Add suggestions registers all three at once.
- Add manually opens the registration of a focus with the name you choose.
Creating a new focus:
- Click the New focus button.
- Fill in the Name field. E.g.:
Action on the supplier. - Click Create.
Editing an existing focus:
- Find the focus in the list and click it (or open the More options menu and choose Edit).
- Change the Name field.
- Click Edit.
Removing a focus:
- Find the focus in the list.
- Open the More options menu and choose Remove.
- Confirm the removal.
As in the other sections, two focuses cannot have the same name (see Unique names).
When you remove a focus:
- It can no longer be chosen in new actions.
- Actions that already used it keep the saved value.
- It stops being required in every form that required it, without any warning. If you only want to change the name, edit the focus instead of removing it and creating another one.
Configuring the focus in a form
Registering focuses does not change any form. Each form decides whether to show the Focus field, which options appear and which are required.
To configure it, you need permission to manage forms, and there must be at least one focus registered in the module settings. Without registered focuses, the section does not appear.
- Open the form and go to the General settings.
- Find the Focus of the action plan actions section (right after Audio recording during data collection).
- Select Display. A table with all registered focuses is shown.
- For each focus, check:
- Display: the focus appears as an option in the Focus field when creating an action.
- Required: every anomaly of the action plan needs at least one action with that focus.
Changes are saved automatically.
| Display | Required | Result during collection |
|---|---|---|
| ☐ | ☐ | The focus does not appear as an option |
| ☑ | ☐ | The focus can be chosen, but is not required |
| ☑ | ☑ | The focus can be chosen and each anomaly needs at least one action with it |
Rules applied automatically by the screen:
- Only displayed focuses can be required. Unchecking Display also unchecks Required for that focus.
- With the field displayed, at least one focus must be checked in Display.
- When you select Display in a form that has no visible focus yet, all registered focuses are checked. Uncheck those that do not make sense for that form.
- When you switch back to Do not display, the selection is kept and comes back if the field is displayed again.
- Focuses registered later do not appear automatically in forms already configured. Check them in each form where they should appear.
A form set to Do not display still allows creating action plans normally; only the Focus field does not appear in actions created during collection.
How the focus appears when filling in
| Where | How it works |
|---|---|
| Form collection (portal or mobile app) | When creating an action, the Focus field appears only if the form is configured to display it, listing only the focuses checked in Display. Below the field, a notice shows the required focuses still missing in that anomaly |
| Action Plans screen (portal) | The Focus field appears in the 5W2H Action sidebar whenever focuses are registered, with all active focuses. Here it is always optional |
| AI assistants | The assistant reads the focuses along with the other module settings and can set the focus when creating or editing an action |
A focus removed from the settings is no longer offered as an option, but actions that already used it keep the saved value. During collection, it is still shown as the current value of those actions.
In the mobile app, the focus list is updated in the sync following the settings change.
Validation of required focuses
When the form has required focuses, the rule is: each anomaly registered during collection needs at least one action with each required focus. The actions may have been created from different questions, on any page of the form: what counts is the set of actions of the anomaly.
The rule applies only to the anomalies that are created. It does not force anyone to create an action plan; for that, use the question's mandatory action plan option.
While creating actions: below the Focus field, the notice "This anomaly still needs actions for the focuses: ..." shows what is missing. It disappears when every required focus is met.
When finishing the collection: before the review screen, the system checks every anomaly. If any of them does not meet the rule, the collection does not proceed and the message Required focus missing appears, with the name of the anomaly and of the missing focuses. The form is taken to the question where the anomaly was created, so you can add the missing action.
When sending: the server repeats the same check. This covers, for example, collections made offline in the app before a change in the form configuration. If the submission is rejected:
- Portal: the message Required focus missing appears with the Revalidate answers button, which reloads the form with the current configuration so you can complete the actions and send it again.
- Mobile app: the collection stays on the Responses for submission screen with the Required focus missing error. Tap it to edit, complete the actions and send it again.
The mobile app must be on version 3.17.0 or later to send the action focus. On earlier versions, a collection in which an anomaly does not meet the required focuses is rejected with a request to update the app.
In the mobile app, responses with audio recording cannot be edited on the Responses for submission screen. If one of these collections is rejected for a missing required focus, the collector cannot fix it and it fails on every sync, until an administrator stops requiring those focuses in the form (or switches the field back to Do not display). Avoid combining required focuses with audio recording in forms answered offline.
Plans and actions created or edited directly on the Action Plans screen are not subject to this validation: the requirement is a rule of the form collection.
Use cases
Food industry — treat the cause, not just the batch
In a temperature control checklist, every non-conformity must have an action on the process and an action on the cause; segregating the batch is optional.
- Display: Action on the product, Action on the process, Action on the cause.
- Required: Action on the process, Action on the cause.
The inspector who registers "Oven temperature 10 °C above standard" can only finish the collection after planning, for example, "Adjust the oven setpoint" (process) and "Replace the temperature sensor" (cause).
Internal audit — classify without requiring
In the audit, the team wants to classify actions for follow-up, without blocking the auditor.
- Display: all focuses.
- Required: none.
Different forms, different rules
Since configuration is per form, each area can have its own rule using the same focus registry:
| Form | Displayed focuses | Required focuses |
|---|---|---|
| Finished product quality inspection | Product, Process, Cause | Product, Cause |
| Occupational safety checklist | Process, Cause | Cause |
| Maintenance round | Process, Cause, Equipment | Equipment |
Tips
- Start with the suggestions. The three default focuses cover most anomaly analysis cases; adjust the names later if needed.
- Require little. Each required focus is one more action per anomaly. Require only what your standard or procedure actually asks for.
- Communicate before requiring. Warn data collectors before making a focus required, especially those using the app offline: collections made before the change may be rejected when sent.
- Update the app. Make sure devices are on version 3.17.0 or later before configuring required focuses.
- Watch out for audio recording. In the app, collections with audio recording rejected for a missing focus cannot be edited (see Validation of required focuses).
- Rename instead of removing. Removing a focus drops its requirement from every form.
- Review forms when creating new focuses. A new focus does not appear in forms already configured until it is checked in Display.
Frequently asked questions
The "Focus of the action plan actions" section does not appear in the form settings. Register at least one focus in Action Plan Settings → Focus and make sure you have permission to manage forms.
I created a focus, but it does not appear during collection. Check it in Display in the settings of each form where it should appear.
The Focus field does not appear when creating an action during collection. Check that the form has Display selected in the Focus of the action plan actions section.
Does an anomaly with several actions need the focus in all of them? No. Among the actions of the anomaly, there just needs to be at least one for each required focus. The other actions can have any focus or none.
Can I require the focus when creating plans on the Action Plans screen? No. On that screen the field is always optional; the requirement applies to the form collection.