Deviations, improvement suggestions and actions

When a problem recurs, you need to see what happened and what you did about it. AmpliFlow is software for managing procedures, responsibilities and follow-up. Its deviation tool keeps the report, decision, actions and follow-up together in one case. You can also submit improvement suggestions and flag risks.

"The biggest value of the certification is really the structure for employees and how we can manage our 'internal headache'."
Meysam Saidzadeh
Meysam SaidzadehCEO, LUCO AB

Adapt the form to what you need to follow up

Handle deviations, customer complaints, improvement suggestions, risk observations, near-misses and accidents as structured cases. Create forms with questions that fit each type, from registration through analysis, implementation and verification.

A risk observation need not describe a problem that has already occurred, and an improvement suggestion need not arise from a deviation. You decide what needs investigation and action. For a deviation, record which process it concerns.

Choose forms for complaints, improvement proposals, deviations and other case types in AmpliFlow
Form selection in the Northstar Instruments demo organization. English interface and fictional data.Open the original image to read the detailsThe interface is also available in Swedish.

Investigate near-misses and accidents

Use a deviation form for near-misses and accidents. Describe the event, assess consequences with your chosen grading categories, investigate the cause and assign actions. Check the result at the workplace and record the outcome before closing the case.

Follow a near miss in the AmpliFlow demo through reporting, analysis, actions and follow-up.

1. Report and clear the walkway

Hannah catches her boot on a temporary cable at commissioning bay C2 but regains her balance without falling. Omar stops use of the supply and removes the cable from the walkway. The outcome is People health and safety 1, No harm. A fall and injury are recorded separately as a potential consequence.

Case 211: the report describes the near miss, the immediate response by Omar and the absence of a fall or injury.
REVIEW: The event and immediate response are recorded together.Open the original image to read the details
Show grading, process, date and coordinator
Only People health and safety is selected, at consequence level 1. Other categories are unselected.
The grading records the actual outcome, not the potential injury.Open the original image to read the details
The native No harm tooltip appears above the selected level 1.
No harm means nobody was harmed in the fictional near miss.Open the original image to read the details
Discovered in and Originated in both point to the same facilities, access, safety and environment process.
The same process was selected for where the near miss was discovered and originated.Open the original image to read the details
Report date, Process classification and Priya Shah as coordinator. The step is complete.
Priya coordinates the report.Open the original image to read the details

2. Investigate why the cable was there

Priya and Omar identify two gaps: no planned cable route and no owner for checking the walkway after setup changes. The analysis does not blame the person walking. They set success criteria: a clear walkway, a revised pre-start check and five days of checks with an independent observation.

The barrier analysis records gaps in planning and check ownership, with criteria for follow-up.
ANALYZE: Causes and success criteria are recorded before the actions.Open the original image to read the details
Show analysis method, checks and owner
Barrier analysis is selected, three analysis tasks are complete and Priya Shah is the analysis owner.
Evidence, affected scope and similar records have been reviewed in the example.Open the original image to read the details

3. Assign and carry out the actions

Omar routes the cable outside pedestrian access and demonstrates the check to operators. Priya revises the setup sheet and pre-start check to require a clear walkway and a named person to check it. The target date is 9 October 2026.

The action log describes what Omar and Priya changed and why.
ACT: The actions address the analysis findings, with responsibilities and implementation recorded.Open the original image to read the details
Show completed tasks, target date and owner
Three delivery tasks are complete and Omar Haddad is the action owner.
Implementation is recorded. That is not yet the same as verifying effectiveness.Open the original image to read the details

4. Check the result and close the case

Hannah follows up the result. Checks show clear walkways across the three bays and the case closes as Resolved fully. The pre-start check continues after every setup change.

Verification shows the check log, result and continuing pre-start check.
The result is compared with the analysis criteria.Open the original image to read the details
Show decision, verifier and closure: Resolved fully
Effective, the verification date, Hannah Reed and Resolved fully closure.
All four steps are complete. The native closure decision is visible here.Open the original image to read the details

Report, act and review the result

Make it easy to describe what happened

Use forms with questions that fit the case. A colleague describes the event, idea or observation, and the person investigating can add to the report. For deviations, link the case to the process where the problem was found and where it originated.

Assign the actions

Describe the cause and what you want to change. Assign tasks to the colleagues involved and follow the case status from reporting through analysis, implementation and verification.

Read what you did last time

Record what the follow-up shows and why the case is closed. If the problem recurs, you can return to the cause, actions and result in the earlier case.

Put colleagues' improvement suggestions to use

A colleague describes what could work better, such as waste, waiting times or a cumbersome task. They do not need a ready-made solution to submit a suggestion. Assess the idea and decide what to try.

Record the result and the reason for closing the case. Even when a suggestion is postponed or not implemented, the decision remains available to explain to anyone who asks.

Elena's recorded proposal: create a searchable library of resolved field-service problems
Elena's idea for reusing field-service experience, with its description and reporter. English interface and fictional data.Open the original image to read the details

Assign actions and check the result

Give each task an owner and describe what needs to be done. The assigned colleague marks it complete, and you can see what remains with the background kept in the case. Then record the action's result during verification before closing the case.

Tasks also exist in action plans for goals and measurements and for controls. Projects can bring together tasks with owners and dates.

Task list with assignees, dates and links to deviations, goals, projects, checklists and controls
Assigned tasks with links to their source. The list shows remaining work, not verified effectiveness. English interface and fictional data.Open the original image to read the details

Questions about cases and actions

Can we use different forms for different types of cases?
Yes. Create forms with your own questions for registration, analysis, implementation and verification. Use different forms for deviations, improvement suggestions and risk observations, for example.
Where are actions created in AmpliFlow?
Record actions in cases and assign them as tasks. Action plans for goals, measurements and controls can also contain tasks.
How is a completed action verified?
Completion and effectiveness are different things. The assigned colleague marks the task complete. Then check the result and record your assessment in the case verification step before closing it.

Do you need human expert help?

Use the software to build your management system yourselves, or get help with setup and implementation. We agree the scope of that help before you decide.

  • Software only

    your team sets up and leads the work.

  • Implementation support

    Mini includes Swedish-speaking software support and introductory training. Midi provides project leadership, and with Maxi we build the management system with you. Midi and Maxi include migration of files at no extra migration charge.

Your team still coordinates its part of the work, and management makes the business decisions.

AI help and human expertise

Optional AI help lets you write and edit drafts that you review yourselves. Our human experts can help with assessments, priorities and questions where you need experience.

See what the optional AI can help with

Compare pricing and our Mini/Midi/Maxi support levels.

See prices and support

We'd like to talk to you!

We show how a report or idea becomes a case with tasks and follow-up, and answer questions about your forms. Consulting support is optional.