E-KAKOVOST — news

The Complaints module: none gets lost in e-mail

Tue, 27 Oct 2026 00:00:00 GMT

The auditor says: “Show me your latest customer complaints: when you received them, who handled them and what you told the customer.” If the answer means searching through e-mail, the problem is bigger than the audit. A customer complaint that waits three weeks in the inbox of a colleague who is on holiday is a risk to the business, not just to the audit: the customer does not know whether anyone is listening, and management does not know that the same problem keeps coming back.

In this post we show how the Complaints module of the E-kakovost QMS platform handles complaints: each one gets a number, a due date and a responsible person, its status is visible from receipt to closure, management sees response times and trends, and an action is raised straight from the complaint.

The Complaints module video (37 s), recorded in the E-kakovost QMS platform on sample data. You can see all the modules on the presentation page.

What the standard asks of your complaints

ISO 9001 clause 8.2.1 requires the company to communicate with customers and to obtain their feedback, including complaints. Clause 9.1.2 requires you to monitor how customers perceive the degree to which their needs and expectations have been met, in other words customer satisfaction. Clause 10.2 then requires you to react to a nonconformity, including one that a complaint brings to light, to evaluate whether its cause needs to be eliminated and, where needed, to take corrective action.

The standard prescribes neither a form nor a deadline. It prescribes that you can show the chain: receipt, handling, reply, decision on action. If you want to organise complaint handling in more detail, ISO 10002 offers guidelines written specifically for it. In practice, though, complaints often live in individual inboxes where only the recipient sees them. The Complaints module brings them together in one place.

How a complaint lives in the Complaints module

1. One list instead of many inboxes

The module is the register of every complaint the company receives: from a customer, a supplier, an employee, from inside (internal) or from elsewhere. Above the list are counters for Open, In progress, Closed, Overdue and the average number of days to resolve. The counters always count all of the company’s complaints, so they do not change when you filter the list.

The list of complaints: everyone who needs to know can see who is handling each one, by when and where it stands.

Each row shows the number, the date received, the description, the source with the complainant, the due date, the status and the responsible person. Overdue complaints are marked in red, and for closed ones a green tick shows they were resolved on time. You search by description, number or source and filter by status and source. On a phone each complaint is a card with the same data.

2. A number, a due date and a responsible person from the start

Whoever receives the complaint (sales, the office, the quality manager) records it with + New complaint. The only mandatory field is the description: what the complainant reports, when, how much and what they ask for. The date received is today, and the resolution due date is 14 days ahead by default; you adjust it to the contract or your internal rule. The date received cannot be in the future and the due date cannot be before it.

The complaint gets a number (e.g. PR-2026-004) and a responsible person, who is notified. If you do not yet know who should handle it, the complaint stays unassigned: a colleague can take it on, or the administrator assigns it. You also enter the complainant and their e-mail address, which receives updates on progress and the resolution. If the company has the AI module switched on, the ✨ Improve button rewrites the text into a clear, neutral description that you check before taking it over.

3. A status everyone can see, from receipt to closure

A complaint moves through Open → In progress → Closed, followed by Notification of the complainant. The flow is drawn in the details, so you can see at a glance where a complaint is stuck. The responsible person finds it among their tasks and in the Planner of deadlines. If the complaint is not theirs, they return it with a reason and the administrators assign it to someone else.

Complaint details: status flow, due date, responsible person and source in one place, with actions taken, attachments and conversation below.

While handling the complaint, the responsible person records the actions taken, attaches evidence (photos, the delivery note, the reply to the customer) and discusses the case with colleagues right on the complaint. During handling they can send the complainant an interim message confirming the complaint has been received and is being dealt with; every notification is recorded. The responsible person cannot move the due date or change who is responsible: the complaints manager does that, and every change of the due date stays in the history. When a complaint is overdue, a reminder is sent.

4. Closing with a reply to the complainant

A complaint is closed with ✓ Complete. It cannot be closed without a responsible person, the actions taken and a decision on corrective action: either an action is linked, or you write down why none is needed. That is exactly the decision clause 10.2 asks for. On closure the responsible person and the administrators are notified, and the complainant gets an e-mail with the resolution: what you found, what you did and how you are preventing a recurrence.

All of this is kept in the decision trail: who created, took over, assigned or returned the complaint, changed its status or due date, closed or reopened it. Complaints cannot be deleted because they are evidence; the administrator archives a wrong entry. A closed complaint cannot be edited. If the customer comes back with the same problem, you reopen it and the earlier closure stays visible. A recurrence is a warning that the cause was not removed.

5. Response times and trends for management

The Analytics tab shows performance by person (complaints assigned and resolved, average days, share resolved on time and overdue) and a 12-month trend: complaints received and closed by month. Management can see where complaints keep recurring before they become a systemic problem, and whether response times are getting shorter or longer.

Analytics: who resolves how many complaints, how quickly and what share on time, plus the trend by month.

The same data feeds the KPI overview (share of complaints resolved on time) and the inputs of the management review. From the management review, a link opens exactly the complaints behind the number in the review, so management looks at the records during the meeting, not just the figures. Complaints are thus one of the sources you use to monitor customer satisfaction under clause 9.1.2. You can also export the complaints of a chosen period to Excel.

6. From complaint to action

A justified complaint is the most common source of corrective actions. When a complaint calls for an action, you open it from the complaint details with + Action. A new corrective action opens with the source “Complaint”, the complaint number and the description already filled in. The action is then listed on the complaint with its number, status, due date and responsible person, and a click on the number opens it. The rest of the work (cause analysis, implementation, effectiveness review) takes place in the Actions module.

A corrective action opened from a complaint: the source shows the complaint number, so the loop from complaint to action is visible both ways.

If the complaint concerns a product that does not meet requirements, + Nonconforming output opens a record in the nonconforming outputs register that is already linked to the complaint (clause 8.7). A supplier complaint can also be run as a claim in the Suppliers module. An administrator can define your own handling process (e.g. Receipt → Handling → Resolution), where some steps require a comment on transition and the system warns you when a case stalls. The loop closes, and you can prove it.

What the quality manager gains

	Without a system	Complaints module
Receipt	In the inbox of whoever got it	One register with number, due date and responsible person
Due date	Nobody tracks it	14 days by default, overdue in red with a reminder
Status	You have to ask	A status flow visible to everyone who needs to know
Reply to the customer	A separate e-mail with no trail	A notification to the complainant, recorded in the flow
Action	The decision is written down nowhere	No closure without a decision on action
Recurrence	Nobody notices	A 12-month trend and performance by person
Audit preparation	Searching through e-mail	Decision trail, analytics and Excel export

Who uses the module

The quality manager, who sees every complaint, due date and delay, and shows management the response times and trends for the management review.
Sales and the office, who record a complaint the moment it arrives instead of forwarding it by e-mail.
Responsible people, who get a clear task with a due date, a reminder and all the information in one place.
Management, who can see where complaints keep recurring and whether the response is improving.
The auditor, who gets the chain from receipt through the reply to the customer to the decision on action in one record.

Book a free demo. In 30 minutes we show you how your complaints would live in the Complaints module: from receipt to the reply to the customer and the action, on an example from your industry. Choose a time →

A complaint only makes sense if there is an action behind it that removes the cause. In an earlier post we showed how the Actions module takes corrective actions through to a verified effect, and in the last one how the Risks module keeps the risk register, where the risk of losing a customer belongs too. If you are only introducing ISO 9001, a complaints register with due dates and replies is one of the first proofs that the management system really listens to customers.

The Risks module: a live 5×5 matrix

Tue, 20 Oct 2026 00:00:00 GMT

The auditor asks: “When did you last review the risk register, and what has changed since?” If the answer is “before the audit”, the register is a document, not a tool. Risks change: a new supplier arrives, a key colleague leaves, a law changes. A risk register that is opened once a year is not risk management. It is audit preparation.

In this post we show how the Risks module of the E-kakovost QMS platform manages the risk register: from a 5×5 matrix that shows where it is hottest, to an owner with reminders, a rating history and an action that is raised straight from the risk.

The Risks module video (42 s), recorded in the E-kakovost QMS platform on sample data. You can see all the modules on the presentation page.

What the standard asks of your risks

ISO 9001 clause 4.1 requires the company to understand its context, and clause 4.2 its interested parties and their expectations. Clause 6.1 then requires you to determine the risks and opportunities that follow from them and to plan actions to address them. Those actions should be proportionate to the potential impact on the conformity of products and services.

The standard does not prescribe a register or a form. It prescribes that you can show the chain: context, risk, action. That is exactly the chain the auditor looks at. In practice risks often live in a spreadsheet nobody opens, and actions in e-mail. The Risks module ties the chain together in one place.

How a risk lives in the Risks module

1. A 5×5 matrix that shows where it is hottest

Risks sit in a likelihood × consequence matrix: likelihood vertically, consequence horizontally. The number in a cell says how many open risks have exactly that combination of ratings, and the colour shows the action class: green, orange or red. Red is therefore straight at the top, in the right-hand corner. A click on a cell shows which risks are in it, and a second click removes the filter.

The risk register: matrix on the left, list on the right. The number in a cell is the count of open risks with that score.

The matrix and the list count the same risks, so the number in a cell always equals the number of rows after you click it. Each row of the list shows the score, category, responsible function, review date and status (Open, In progress, Accepted, Closed). The list is sorted from the highest score down, so the quality manager sees what matters most first.

2. A score that is repeatable

You rate likelihood and consequence on a scale from 1 to 5. Every level is described in words, so two people rating the same risk pick the same level and the score is not a matter of gut feeling. For a new risk no rating is pre-selected: a person has to choose it, which makes it a conscious decision rather than a default.

The overall score (likelihood × consequence) is calculated and coloured on the spot, before you save the risk.

From the overall score (1 to 25) the module itself works out the action class. By default: up to 8 no action is needed, from 9 to 16 action is desirable and from 17 up it is required as a priority. The limits are your company’s methodology, since ISO 9001 requires the organisation to define how it rates risks. An administrator changes them in the settings, and the change is written to the audit trail.

3. Owner, actions and review date

Every risk has an owner (a person), a responsible function (e.g. “Head of Purchasing”), control measures and a next review date. The difference matters: a person receives the reminders, while a function survives staff changes. The owner gets a reminder 7 days before the deadline and on the day itself, and the date also shows in the Planner alongside the company’s other deadlines. The register stays alive without the quality manager having to chase it.

Control measures, indicator and next review date: below the date it says the owner gets a reminder 7 days earlier.

The module does not reject an incomplete record. It flags it with a ⚠️ warning instead: a priority risk without actions, without a review date, without a description of consequences or without a responsible person. That way the auditor does not find the gap before you do.

4. Re-rating and rating history

A risk is not a one-off entry. At a review you click Re-rate, change the score and write down the reason (e.g. “after a second supplier was introduced”). Every change of score is one line of history: date, score, reason, who made it and a trend arrow. For a risk, a green arrow down is an improvement and a red arrow up is a deterioration.

For an auditor this is the strongest proof that the register is alive: they see not only today’s score but the story of what you did and how the score changed as a result. The details of a risk have a row of sections at the top (Rating, Actions, Rating history, Links) that jumps you where you want in one click. Risks are never deleted, only closed, so the history stays.

5. From risk to action, process and context

When a risk needs an action with a responsible person, a deadline and an effectiveness check, you create it on the risk’s card with + New action. The problem description and the proposed action are pre-filled from the risk, and the action stays permanently linked to it. The rest of the work (cause analysis, implementation, verification) takes place in the Actions module.

A risk is also linked to where it comes from. You can link a step of a process to a risk, so it is visible where in the process the risk arises. An environmental aspect is linked to a risk in the ISO 14001 view, and workplace risks are kept with an ISO 45001 assessment (hazard, people exposed, hierarchy of controls). On the Context page you keep context issues (clause 4.1) and interested parties (clause 4.2): an important issue with no linked risk, action or objective is flagged with a warning. Besides risks you also record opportunities, either against a risk or on their own (for example a new customer).

6. Suggested risks and a printout for the audit

An empty register is hard to start. If the company has the AI module switched on, AI suggestion proposes 5–8 risks that are not yet in the register, based on your line of business and past actions. Nothing is saved automatically: you take over only the ones that apply and complete them, because a suggestion is a starting point, not the truth.

The “AI suggestion” button above the matrix: you take over suggested risks by hand, and nothing is saved automatically.

For the audit, one click prepares a register printout as a PDF: the 5×5 matrix, a table of risks with score, actions, owner and review date, a separate table of opportunities and a signature block. You can also export the register to Excel.

The register printout for the audit: matrix and table of risks, prepared in one click.

What the quality manager gains

	Without a system	Risks module
Register	A spreadsheet opened once a year	A live 5×5 matrix, a click on a cell shows the risks
Rating	By gut feeling	A 1–5 scale with described levels, class calculated automatically
Owner	A name in a column	An owner with a reminder 7 days before the deadline and on the day
Change of score	An overwritten number	Rating history with reason, author and trend
Actions	In e-mail or a separate document	An action raised from the risk, permanently linked
Context	A separate document	An important issue with no linked risk is flagged
Audit preparation	Assembling the printout by hand	A PDF printout of the register in one click

Who uses the module

The quality manager, who has an overview of the matrix and the review dates and shows management the state of risks, which is an input to management review.
Risk owners, who get a clear review date and a reminder instead of a question at the audit.
People responsible for processes, environment and safety, who link risks to a process, an environmental aspect or a workplace.
Management, who instead of a long spreadsheet sees which risks are in the red and what is being done about them.
The auditor, who gets the chain from context through the rating to the action and the review history in one record.

Book a free demo. In 30 minutes we show you how your risks and opportunities would live in the Risks module: from the first rating to an action, on an example from your industry. Choose a time →

A risk only makes sense if there is an action behind it. In the previous post we showed how the Actions module manages corrective and preventive actions through to a verified effect. If you are only introducing ISO 9001, a risk register with clear owners and review dates is one of the first proofs that the management system really works.

The Actions module (CA/PA): from a failure to its root cause

Tue, 13 Oct 2026 00:00:00 GMT

The auditor asks: “This nonconformity was already recorded last year. What did you do, and how do you know it was enough?” If the answer is “we fixed the pallet”, that was a correction, not a corrective action. A correction removes the consequence. A corrective action removes the cause and proves the failure does not come back.

In this post we show how the Actions module (CA/PA) of the E-kakovost QMS platform manages corrective and preventive actions: from the finding and the search for the root cause to a verified effect, and analytics that show where problems really start.

The Actions module video (46 s), recorded in the application on sample data. You can see all the modules on the presentation page.

What the standard asks of your actions

ISO 9001 clause 10.2 (nonconformity and corrective action) requires that when a nonconformity occurs, including a complaint, you react at once and deal with the consequences, then evaluate whether the cause needs to be eliminated, implement the action needed, review its effectiveness and update risks and the management system where necessary. You must retain documented information on all of it.

The standard does not prescribe a form. It prescribes that you can show the chain: what happened, why, who did what by when, and whether it worked. In practice actions often live in Excel, in e-mail and in the quality manager’s head, and the last step, checking effectiveness, is the one that most often gets lost. The Actions module adds order and a trail to that chain.

How an action lives in the Actions module

1. A list that shows what is late

Every action gets a number (KU-2026-019 for corrective, PU-2026-002 for preventive), a description, a source, a deadline, a responsible person and a state: Open, In progress, Effectiveness check or Closed. Counters above the list show how many actions are in each state, how many are late and how many wait for your check.

The action list: state counters at the top, below them CA and PA with the problem source, deadline and responsible person.

A new action needs only a few fields: type, description, responsible person and deadline (30 days by default). The quality manager is notified of every new action, and the responsible person gets reminders before the deadline and when it is missed. An action cannot be deleted; an administrator can only archive it, so the trail stays.

2. An action starts where the problem happens

You do not need to retype actions from reports. One can arise from an audit (the “Request action” button on a nonconformity), a complaint, an internal finding, an external factor, a risk or a supplier. The source and text carry over and the action stays linked to the originating record. An employee can also report a problem or suggestion through the “Report a problem / suggestion” button, and the quality manager converts it into an action with one click.

3. Root cause analysis: 5 Whys, Ishikawa, 8D

This is where the difference between a correction and an action shows. In the analysis you choose a method: 5 Whys (a chain of answers down to the cause), Ishikawa (six directions of possible causes) or 8D as the report framework for a customer. Before the cause is known you also record the containment action that stopped the damage; its time is stamped on first save and never changes later.

Cause analysis: a containment action, a chain of “whys” and a marked root cause, the one that can be eliminated.

You then define the problem with Is / Is not differences (what is happening and what could be but is not), place the cause in a category that feeds the Pareto, and rate severity: RPN = severity × occurrence × detection (from 1 to 125, 60 and above is high priority).

4. An effectiveness criterion and repeat detection

An action without a criterion cannot be closed with proof. So you enter a criterion (what must hold for the action to be effective) and an observation window in days. The window starts when the implementation is submitted for checking, because the effect of an action that has not been carried out yet cannot be observed; an action cannot be submitted for checking without a criterion. When the window ends, the module reminds the verifier and administrators to confirm the outcome.

A severity rating (RPN 36), Is / Is not, a criterion with a 60-day window and a suggestion of a similar older action.

The module also detects recurrence: if a similar problem has already been closed, it suggests it and you confirm the link. A closed action then shows that its effectiveness is at risk, since a recurrence means the action did not remove the cause.

5. Evidence and independent verification

You document the state with attachments before, during and after the implementation (photos, documents), so you do not explain to the auditor, you show. When the responsible person submits the implementation, the action moves to the effectiveness check. Only someone other than the person responsible for implementation can verify it: they record their findings and the outcome. If the action is effective it closes; if not, it returns to implementation.

Closing an action: notify the internal owners and, if you wish, an interested party, such as the customer who raised the complaint.

On closure the module notifies the responsible person and administrators and, if you wish, sends an e-mail to an external interested party. The whole flow can be printed as a PDF that also serves as an 8D report, or exported to Excel.

6. Analytics: where problems really start

Individual actions fix individual problems. Looked at together, they tell the quality manager far more. The Analytics tab shows effectiveness by person (assigned, closed, average days, share within the deadline), a 12-month trend of open and closed actions and a Pareto of root causes with the “vital” categories marked, the ones that together cause 80 % of problems.

Action analytics: effectiveness by person, a trend and a Pareto that shows where systemic solutions are worth looking for.

This is the input for management review (clause 9.3) and improvement (clause 10.3): you do not look for who made the mistake, but for which category of causes creates the most actions.

What the quality manager gains

	Without a system	Actions module
Action records	Excel and e-mail	One list with live states and counters
Problem source	Retyped from a report	An action arises from an audit, complaint, risk or report
Cause	“Worker error”	5 Whys, Ishikawa or 8D with a marked root cause
Effectiveness	Nobody checks it	Criterion, observation window, independent verifier
Recurrences	Found by chance	A suggestion of similar actions, link confirmed by a person
Evidence	Photos on phones	Attachments before, during and after
Management review	Gathering data by hand	Analytics, trend and Pareto in one click

Who uses the module

The quality manager, who sees which actions are late and which wait for a check, and shows management a Pareto instead of impressions.
People responsible for actions, who get a deadline, a reminder and a clear goal instead of a vague task.
Verifiers, who have everything in one place, from analysis to evidence, and record an independent outcome.
Employees, who report a problem or suggestion without an Excel form.
The auditor, who gets the chain from nonconformity to verified effect in one record.

Book a free consultation. In 30 minutes we show you how your nonconformities, complaints and audit findings would live in the Actions module: from the report to a verified effect, on an example from your industry. Choose a time →

If you are only introducing ISO 9001, a well-kept record of corrective actions is one of the first proofs that the system really works. Slovenian companies can obtain a subsidy of up to 60 % for implementing ISO standards.

The Equipment module: calibration cycle, maintenance and breakdowns in one place

Mon, 05 Oct 2026 00:00:00 GMT

The auditor picks up the calliper from the inspection bench and asks: “When was this calibrated, and where is the certificate?” If the answer is “somewhere in Ana’s folder”, it is not just that calliper that is in question. Every measurement you made with it since the last calibration is, and so is every product you released on the strength of those measurements.

In this post we show how the Equipment module of the E-kakovost platform manages measuring and work equipment: from the register with a traffic light and calibrations with impact assessment to the maintenance plan, breakdowns that employees report from a phone, and the audit printout.

The Equipment module video (35 s), recorded in the application on sample data. You can see all the modules on the presentation page.

What the standard asks of your equipment

Clause 7.1.5 of ISO 9001 (monitoring and measuring resources) requires measuring equipment to be calibrated or verified at specified intervals, its status to be identifiable, the equipment to be protected from adjustment and damage, and, when an instrument is found unfit, the validity of previous results to be assessed and acted upon. Clause 7.1.3 (infrastructure) adds machines, lifting equipment and vehicles: maintenance has to be planned and provable.

The standard prescribes neither the interval nor the tool. It prescribes that you know which item is fine, which is not, and that you can prove it. In practice this often ends in a spreadsheet someone refreshes two weeks before the audit, and certificates in three different folders. The Equipment module turns those requirements into things that happen by themselves.

How equipment lives in the Equipment module

1. A register with a traffic light: what is valid, what is expiring, what slipped

You enter each item once: identifier (e.g. MO-002), name, classification (measuring equipment, work equipment, lifting equipment, vehicles or your own), location, custodian and check interval. For instruments you add the range and accuracy, for vehicles the registration plate and the registration and insurance expiry dates.

From then on every item has a colour: green is valid, amber expires within 30 days, red is overdue or failed its last check, grey is withdrawn. New equipment is red until you enter its first check: no evidence, no validity. The counters above the list tell you how many items are overdue, how many are expiring and how many are valid.

The equipment register: every item has a colour and a due date; forklift OP-001 also carries badges for overdue maintenance and an open breakdown.

The custodian gets a reminder 30 and 7 days before the due date, and daily once it is overdue, until the check is entered. If there is no custodian, the organisation’s administrators get it. The due date also appears in the Planner.

2. Calibration with evidence, and impact assessment when an instrument fails

You record a check with the date, the provider (optionally from the Suppliers register), the certificate number, the measurement uncertainty and the attached certificate. The system calculates the next due date, updates the traffic light and clears the reminders. Records are never deleted or edited: the check history is the evidence.

When an instrument does not conform, the module does not let it stay in use. You must choose the status Use prohibited or Withdrawn, and you must write the impact assessment: which measurements and batches may be affected, what you checked and what you did (re-measurement, holding the batch). That is exactly what clause 7.1.5.2 requires and the first thing an auditor asks. From the record you open a corrective action with the description already filled in, in one click.

If you have an inspection report from an authorised body covering 40 items of work equipment, you do not retype it. Import from document uses AI to read the PDF or scan, recognises items by serial number, proposes the date, result and deficiencies for each, and you check and confirm the rows. For a non-conforming item the impact assessment is mandatory here too.

3. A maintenance plan: several tasks, each with its own interval

Calibration confirms the equipment conforms. Maintenance keeps it that way. On every item you can run several maintenance tasks: the daily forklift check before use, chain lubrication every 30 days, a hydraulic oil change once a year. Each has an interval, a responsible person and a due date; completions are recorded with a click and stay as evidence (clause 7.1.3).

The forklift’s maintenance plan: three tasks, each with its own interval and responsible person; chain lubrication is overdue.

A task has its own colour (on schedule, due within 7 days, overdue), and in the register an item with an overdue task gets the badge 🔧 maintenance overdue. The responsible person gets a reminder on the due date, for longer intervals a week ahead as well, and daily once overdue together with the organisation’s administrators.

4. Breakdowns: reported from a phone, taken over, escalated, with repair evidence

When a machine stops, what matters most is that the right person knows immediately. Anyone can report a breakdown: describe what happened, mark that the equipment is down, and attach photos, video or documents straight from the phone. The equipment gets the status Under repair, downtime hours start running, and the custodian, the people responsible for maintenance and, on a stoppage, the quality manager get an e-mail with the attachments at once.

An open breakdown: downtime is running, it records who reported it and who is handling it; a corrective action opens from it in one click.

Whoever takes over the breakdown is recorded with name and time, so it cannot happen that everyone assumes someone else is on it. If a breakdown with a stoppage is not taken over within two hours, the system escalates to the quality manager and the administrators. On closing you enter the cause, the repair, the provider, the cost and repair evidence (a photo, a service sheet); the equipment returns to use, and the downtime and cost feed the indicators.

5. A QR label on the machine: breakdown reported in three taps

An employee on the shop floor is not going to open a computer to find the right item in the register. So every item has a QR code: the employee scans it with a phone, logs in and gets the breakdown form already opened for that machine, with the camera a thumb away.

You print labels for one item or the whole register: an A4 poster, or Avery sheets of 4, 21 or 65 labels, always with the logo.

Labels print on standard Avery sheets (A6 for machines and vehicles, 63 × 38 mm for instruments and work equipment, mini 38 × 21 mm for hand tools) or as an A4 poster. If a label goes missing or the machine is sold, you renew the token and the old codes stop working.

6. An overview for the manager and a printout for the auditor

The Maintenance button above the register opens an overview of all equipment: active tasks (overdue first), open breakdowns and the indicators for the last 12 months, from the number of breakdowns and downtime hours to costs. Every item has buttons for a new task and a breakdown report.

The maintenance overview: indicators on top, below them all equipment with its status and the quick buttons Task and Breakdown.

For the audit you click PDF: the equipment register with the organisation’s header, by classification, with the last check, the next due date and the status for every item, and optionally the maintenance plan and open breakdowns. Withdrawn equipment is in a separate section. The KPI dashboard shows the share of valid checks and the number of items expiring within 30 days.

What the quality manager gains

	Without a system	Equipment module
Equipment status	A spreadsheet refreshed before the audit	A traffic light on every item, live counters
Calibration due date	Whoever remembers	Calculated from the last check, reminders 30 and 7 days ahead, Planner
Certificates	In three folders	On the check record, history never deleted
Failed instrument	Removed, nothing written down	Mandatory impact assessment, status, corrective action
Maintenance	Service booklet in a drawer	A plan with tasks, completions as evidence
Breakdown	A phone call that gets lost	Reported via QR code with attachments, take-over, escalation, cost
Audit	Searching folders	Equipment register as a PDF

Who uses the module

The quality manager, who always knows what is valid and what is overdue, and shows the auditor one printout.
Equipment custodians and maintenance staff, who get a reminder before a date passes and a breakdown the moment it happens.
Production employees, who report a breakdown from a phone via the QR code, with a photo and no computer.
The auditor, who gets the register, the check history with certificates and the impact assessments in one place.

Book a free consultation. In 30 minutes we show you how your instruments, machines and vehicles would live in the Equipment module: from the register to the audit printout, on an example from your industry. Choose a time →

If you do not have the standard yet, a tidy register of measuring equipment is one of the first things an auditor checks on the shop floor. Slovenian companies can obtain a subsidy of up to 60 % for implementing ISO standards.

The Documents module: one valid version

Tue, 29 Sep 2026 00:00:00 GMT

How many times have you looked for the latest version of an instruction and found three different ones: one on the server, one in an e-mail, one printed on the wall? The certification auditor will take the one on the wall. If it does not match the one on the server, you have a nonconformity, even if the only change was the maintenance phone number.

In this post we show how the Documents module of the E-kakovost platform manages documents: from upload to a history you export as a PDF in seconds at audit time.

The Documents module video (59 s), recorded in the application on sample data. You can see all the modules on the presentation page.

What the standard asks of your documents

Clause 7.5 of ISO 9001 does not ask for a thick quality manual. It asks for documented information to be identified, reviewed and approved, available where people need it and protected from unintended change. When something changes, it has to be clear which version applies and who approved it.

On paper that is simple. In practice documents multiply in three places at once, approvals travel by e-mail, and acknowledgement is proven by a signature sheet that is always in a different folder. The Documents module turns those four requirements into four things that happen by themselves.

How a document lives in the Documents module

1. One valid version, a clear status

You upload the document (PDF, Word, Excel, image) and give it a category, a unit, an identifier (e.g. WI-CNC-07), an owner and the date of the next review. From then on it has one status: draft, under review, approved, rejected or withdrawn. The list shows everything at a glance, and the Waiting for you card shows exactly what needs your signature or acknowledgement, and nothing else.

The document list: every document has one status; the Waiting for you card counts only what is waiting for you.

While the author prepares a new version, employees keep seeing the valid one with the badge 🔄 Under revision. Nobody sees the draft except the author, the approver and the administrator. So nobody can work from a document that has not been approved yet.

2. Approval follows the organisational structure, not a list of e-mail addresses

You do not pick an approver for every document. By default it is the head of the unit the document belongs to, or the head of the parent unit. For two-stage routes (e.g. the quality manager, then management) you draw an approval process; a step can be bound to the head of a unit without a name, so when the head changes, the approver changes too and the process needs no editing.

Approval is a deliberate act: the approver has to open the version before approving it, can add a comment, and on rejection enters a reason the author receives. An approved document states who, when and how approved it: as the designated approver, with administrator rights in place of an absent approver, or automatically on the last acknowledgement, if you chose that activation mode.

Every approved document records who approved it and in what way.

If your organisation requires an electronic signature, the approval is bound to the approver’s password (and MFA code) and to exactly that version of the file.

3. Acknowledgement with evidence instead of a signature sheet

For instructions and procedures the administrator requests acknowledgement, optionally with a deadline. The employee opens the document with Read and confirm, reads it and confirms Acknowledged in the preview. Acknowledgement is not possible without opening the document; the system records when it was opened and when it was confirmed.

In the acknowledgement report the administrator sees who confirmed and when, who has not yet, and who is late. Late employees get a reminder, and the deadline also appears in the Planner. For key documents you can switch on a comprehension quiz: AI prepares three questions from the content and the employee has to answer at least two correctly.

The acknowledgement report replaces the signature sheet: name, time opened, time confirmed.

4. A new version: minor or substantive

An approved document cannot be edited; you upload the change as a new version and describe what changed. A minor change (corrections, typos) goes 1.0 → 1.1, a substantive one (procedures, responsibilities) 1.1 → 2.0. A substantive change goes for re-approval and requires everyone to re-acknowledge; with a minor one the acknowledgements remain. If the organisation has AI switched on, it compares the new file with the current one and suggests the type of change; the decision is yours.

Anyone who may not edit the document can propose a new version with text or a photo from a phone; the manager accepts the proposal as a new version or rejects it with a reason.

History: every version with its change description and every approval with a name and time. Any older version can be downloaded.

5. Review, reminders and a trail for the auditor

The next review date reminds the document owner 14 and 7 days ahead. When validity expires, it reminds whoever you specify. For the auditor the most important button is Document history (PDF): one printout with all versions, the approval log and the acknowledgement record, with version labels that match in every section. Instead of browsing folders, you show one document.

The Valid on date view answers the question auditors like to ask: which documents were valid on the day a nonconforming product was made.

What the quality manager gains

	Without a system	Documents module
Valid version	Three copies in three places	One, with the status Approved; the previous one applies during revision
Approval	By e-mail, no trail	By organisational structure, with name, time and way of approval
Acknowledgement	Signature sheet	Read and confirm, with deadline, report and optional quiz
Change	New file, old name	New version with description, re-approval and re-acknowledgement when needed
Review	Whoever remembers	Owner and date, reminders, Planner
Audit	Searching folders	Document history as a PDF

Who uses the module

The quality manager, who makes sure one version applies and every approval can be proven.
Heads of units as approvers of their unit’s documents, with no extra roles or settings.
Employees, who see only valid documents on a phone or computer and acknowledge in two clicks.
The auditor, who gets the document history in one PDF.

Book a free consultation. In 30 minutes we show you how your procedures and instructions would live in the Documents module: from upload to the history for an audit, on an example from your industry. Choose a time →

If you do not have the standard yet, a tidy document system is the first thing an auditor checks. Slovenian companies can obtain a subsidy of up to 60 % for implementing ISO standards.

The Audits module: an internal audit without days of typing up the report

Mon, 21 Sep 2026 00:00:00 GMT

An internal audit of a department takes a few hours. Then come the days: copying findings out of a notebook, sorting photos from your phone and working out which clause of the standard each one belongs to. If you have ever led an internal audit, you know that the time does not go into the review but into the report.

In this article we show how an audit runs in the Audits module of the E-kakovost platform: from the plan to a report that is done when you leave the last department.

The Audits module video (59 s, narrated in Slovenian), recorded in the application on sample data. You can see all the modules on the presentation page.

Why the internal audit exists at all

ISO 9001, ISO 14001 and ISO 45001 require an organisation to check for itself, at planned intervals, whether its system works as documented (clause 9.2). The certification auditor comes once a year; the internal audit is your look in between.

A good internal audit answers three questions:

Are we doing what we wrote down? Instructions, procedures and records against the actual work in the department.
Does what we do meet the requirements of the standard? Clause by clause, with evidence.
Where is the risk hiding? Findings that are not yet non-conformities but will be if we overlook them.

The problem is not the questions. The problem is that the answers end up in a notebook, the photos on a phone, the report in Word and the actions in Excel. The Audits module puts all of this in one place.

How an audit runs in the Audits module

1. The audit plan: standards, team, areas, dates

You plan the audit in the application. You choose the type (internal, supplier, certification), the standards you are auditing and the company’s activity profile. You assign auditors, auditees and dates by department. The plan doubles as an invitation: everyone involved sees when their turn comes.

The audit plan: the standards and the activity profile determine which questions the questionnaire will contain.

2. A questionnaire with more than 900 questions

The questionnaire is compiled from the plan. The base set has more than 900 questions by clause of the standards, filtered by the selected standards and your organisation’s profile. Every question states which evidence is expected (a register of gauges, a calibration plan, work instructions), so the auditor knows what to ask for.

The answer is simple: conforming, conforming with a recommendation, non-conforming or not applicable. If you are auditing an integrated system, questions common to several standards are merged so you do not ask them twice.

3. Findings on the spot, with a photo as evidence

You record a finding immediately, on site, next to the question it relates to. You attach a photo or a short video. The finding is thereby already filed under the clause of the standard and the process you were auditing; there is nothing to tidy up later.

Findings: every answer has its place, a button for dictation and one for rewording in the language of the standard.

If you would rather talk than type, you dictate the finding. The AI assistant writes it down, rewords it in the language of the standard on request and suggests where it belongs. The proposal sits next to your original and goes into the report only once you confirm it. It invents nothing; the auditor decides.

4. The report in one click

When you answer the last question, the report is done. It contains the audit details, the auditors and auditees, the conformity percentage, the number of questions by rating, conformity by chapter of the standard and a list of conforming clauses, recommendations and non-conformities with evidence. You export it to PDF with a signature block.

The report is produced from the questionnaire. Nothing is copied, nothing gets lost between the notebook and Word.

5. From finding to corrective action

Every non-conformity has a “Request action” button. The action opens in the Actions (CA/PA) module with the same number, source and text of the finding, the owner receives a reminder before the deadline, and the audit stays linked to the action until the effect is verified. The loop closes without re-entering anything.

What the quality manager gains

	Without a system	The Audits module
Audit plan	Excel and e-mail	In the application, everyone sees the dates
Questionnaire	Home-made, several years old	900+ questions, filtered by standard
Findings	Notebook, photos on the phone	On the spot, with a photo, under the clause of the standard
Report	Days of typing	Done at the last answer
Actions	Copied manually into a spreadsheet	One click from the finding, with a trail
Next audit	You start from scratch	You see what was non-conforming last year

For the certification auditor this means you do not search folders: you show the report, the findings with evidence and the actions that follow from them.

Who uses the module

The quality manager, who plans and leads audits and wants a report without copying.
Internal auditors from other departments, who need guidance through the questionnaire and a clear instruction on which evidence to ask for.
An external auditor or consultant, whom you invite into the system with a limited role and who enters findings directly into the questionnaire.
Management, which receives the audit results in the management review automatically, without gathering.

Book a free consultation. In 30 minutes we show you how your next internal audit would run in E-kakovost: from the plan to the report, on an example from your industry. Choose a time →

If you do not have the standard yet, an internal audit is also a good first step: it shows where you stand before you decide on implementation. Slovenian companies can obtain a subsidy of up to 60 % for implementing ISO standards.

What is a QMS and what does a quality management system make easier for a company?

Mon, 14 Sep 2026 00:00:00 GMT

Which version of the instruction is valid? When does our calibration expire? Who is responsible for the complaint that has been waiting three weeks in the inbox of a colleague on holiday? If these questions sound familiar, you already know what a quality management system solves. Not a certificate on the wall, but everyday work.

In this article we explain what a QMS is, what exactly it makes easier for a company and how a digital QMS differs from folders, Excel and e-mail. The principles of ISO 9001, the building blocks of the system and all related articles are collected in our guide to the quality management system.

What is a QMS (quality management system)?

QMS stands for Quality Management System. It is an organised way for a company to plan, carry out, check and improve its work so that products and services are consistently what the customer expects.

A QMS is not a program, a folder or a person. It is a set of agreements:

who is responsible for what (organisational structure, authorisations),
how we work (processes, instructions, forms),
how we know we are doing it right (indicators, audits, reviews),
what we do when something goes wrong (non-conformities, complaints, corrective actions),
how we learn from it (risks, management review, improvements).

The most widespread framework for a QMS is the ISO 9001 standard. The same logic applies to ISO 14001 (environment) and ISO 45001 (occupational health and safety), which is why companies often run all three in a single, integrated system. If you want to know what the standards require, read our guide to ISO standards.

What a QMS makes easier for a company: seven things from practice

From seventeen years of implementing systems in Slovenian companies we know that the benefit of a QMS is not visible in the quality manual but in everyday situations. Here are the seven we hear most often.

1. One valid version of a document

Without a system there is Instruction_v3_FINAL_really.docx and five people working from different versions. A QMS defines which version is valid, who approved it and who has been made aware of it. When a document changes, colleagues find out — not just at the audit.

The Documents module: every document has a status, a version and an owner; whatever is waiting for your signature is at the top.

2. Deadlines that speak up by themselves

Calibration of measuring equipment, validity of training, document reviews, action deadlines, risk reviews. Each of these deadlines lives in its own calendar or in one person’s head. An organised QMS gathers them in one place and reminds the responsible person before it is too late.

3. An audit without a week of typing

An internal audit means a few hours in the department and days of writing the report. With a system that has a questionnaire by clause of the standard, findings with a photo and a report in one click, the report is done when you leave the last department.

4. Mistakes that do not repeat

A complaint, a non-conforming product or an audit finding must get a number, an owner, a deadline and a verified effect. That is the essence of corrective actions (CAPA). A spreadsheet of actions that nobody opens does not guarantee this; a system with reminders and a trail does.

5. Risks you see before they become a problem

A risk register that only comes alive before the audit is not a register. A live risk matrix with owners and review dates shows management where the exposures are today, not last year.

6. Data for management without gathering

The management review under ISO 9001 requires inputs: the status of audits, actions, complaints, risks, indicators, suppliers. If you gather this data department by department, the review is a project. If it lives in one system, the inputs compile themselves and management decides on the basis of numbers.

7. Knowledge stays in the company

Where processes are not documented, knowledge leaves with the colleague. A documented process with inputs, outputs and responsibilities is something you can hand to a new colleague on day one and improve month after month. More on this in the article Business process optimisation.

Paper, Excel or a digital QMS?

Any quality management system can be run on paper and in Excel. The question is the price. Not the licence price, but the price of searching, double entry, missed deadlines and stress before the audit.

	Folders and Excel	Digital QMS
Valid version of a document	Depends on discipline	One, with approval and a trail
Deadlines	In several calendars	In one place, with reminders
Audit report	Manual, days	Automatic, minutes
Trail of changes	None or manual	Every change recorded
Preparing for the audit	Weeks	The evidence is already in the system
Management review	Gathering data	Inputs compile themselves

A digital QMS does not change what the standard requires. It changes how much time you spend proving it.

The platform’s home screen: what is waiting for you is at the top; the modules are tiles between which data flows.

The advantages of the E-kakovost QMS platform

We built the E-kakovost platform on our consulting experience. Every module solves a situation we saw at clients often enough for it to require a system rather than goodwill.

Eighteen modules, one system. Documents, audits, actions, complaints, risks, KPIs, training, measuring equipment, suppliers, non-conforming outputs, management review, legislation, environment, business processes, planner, info screen, standard implementation and standard transition. Data from one module is available to another: from a complaint you open an action, from an audit a finding, from a risk an objective.
It stands on your organisational structure. Approvals follow the org chart, acknowledgement is tracked per person, access is organised by role. There is nothing to adapt to the program; the program adapts to you.
An AI assistant that helps write. A person decides. You write in plain language, the assistant proposes wording in the language of the standard, the proposal sits next to your original and goes into the document only once you confirm it. It invents nothing; if the input is insufficient, it says so. During an audit you dictate findings and the system files them under the clause of the standard.
Deadlines speak up by themselves. The Planner gathers all the organisation’s deadlines on one page: documents, audits, actions, risks, training, calibrations. Overdue items are at the top and a click leads into the module.
Every step leaves a trail. The document’s audit trail, the disposition of a non-conforming output with a name and date, a management-review decision with a deadline. You do not search folders for the auditor; you show the screen or a PDF printout.
Legislation monitored by the system. Your register of regulations is compared automatically with the official national register. When an amendment is published that affects a regulation on your list, the system notifies you, and the impact assessment, action and evidence stay attached to the change.
Implementation without a project. If you do not have the standard yet, the Standard implementation module guides you step by step with the requirements explained in plain language and shows your certification readiness in percent. When a new edition of the standard is published, the Transition module maps the old system onto the new one.
Hosted in the EU, export always available. Data is kept in data centres inside the EU, encrypted in transit and at rest. Your data stays yours and you can export it at any time.
Built in practice, in Slovenia. The platform is available in Slovene and English, with questionnaires by clause of ISO 9001, 14001 and 45001 and with support from people who implement management systems rather than just program them.

You do not have to take our word for it. Every module has a short video recorded in the application (narrated in Slovenian). See the platform module by module.

How to get started

Take stock of what you already have. Documents, records, deadlines, owners. You will be surprised how much of a system already exists — it is just scattered.
Pick one pain point. Documents nobody can find, deadlines that slip or complaints without a trail. Start where the effect will be visible in the first month.
Move it into the system and invite your colleagues. A digital QMS works when everyone uses it, not just the quality manager.
Measure. The number of open actions, missed deadlines, time spent preparing for the audit. Compare after six months.

Book a free consultation. In 30 minutes we show you the E-kakovost platform on an example from your industry: how your documents, deadlines and actions would be organised. No obligation. Choose a time →

If you do not have the standard yet, at the same meeting we look at your existing system and tell you what would have the greatest effect. Slovenian companies can also obtain a subsidy of up to 60 % for implementing ISO standards.

In the coming weeks we will present one module of the platform every Tuesday: what it solves, how it works and why to use it. We start with audits.

Business process optimisation as the foundation of company quality

Fri, 30 Jan 2026 00:00:00 GMT

A company’s quality today is no longer measured solely by the final product or service, but by how the company works as a whole. Customers, business partners and employees increasingly judge orderliness, responsiveness and consistency — in other words, the processes behind every product.

Why quality is not a coincidence

Companies with orderly processes make fewer mistakes, respond faster to change and onboard new colleagues more easily. Where processes are not documented, knowledge stays in individuals’ heads — and leaves with them. A documented, measured and regularly reviewed process, on the other hand, is something you can improve month after month.

Where to start

First identify your key processes: those that directly create value for the customer. For each one, define an owner, inputs and outputs and performance measures. Only once you can see a process can you improve it.

The ISO 9001 standard is not bureaucracy here but a proven framework: it requires a process approach, clear responsibilities and continual improvement. Companies that implement it for real (and not just “for the certificate”) report fewer complaints, shorter lead times and greater customer trust.

Digitalisation as an accelerator

Paper-based quality systems quickly go stale. When documentation, internal audits, corrective actions and indicators live in a digital platform, quality becomes part of everyday work — not a project everyone remembers a week before the audit.

Would you like a review of your processes? Book a free 30-minute consultation.

ISO quality standards: what, why and how to turn them into a competitive edge

Wed, 28 Jan 2026 00:00:00 GMT

In a business world where competitiveness is tightly linked to trust, efficiency and compliance with market and legal requirements, ISO standards are becoming the foundation of long-term business success. It is no longer just about obtaining a certificate — it is a way of working.

The three standards you meet most often

ISO 9001 (quality management) is the most widespread standard in the world. It requires a process approach, clear responsibilities and demonstrable continual improvement. For customers the certificate is a signal that the company has its work under control.

ISO 14001 (environmental management) systematises the control of environmental impacts: from resource consumption to waste handling. It is increasingly a requirement in tenders and in the supply chains of larger customers.

ISO 45001 (occupational health and safety) reduces risks to employees, the number of incidents and the costs and liabilities that come with them.

Why it pays off

The certificate opens doors: many customers, especially in the automotive, logistics and construction sectors, only work with certified suppliers. But the real value is internal — orderly processes, fewer mistakes, faster onboarding of new colleagues and management that decides on the basis of data.

It is also worth knowing that Slovenian companies can obtain up to 60 % in subsidies for implementing management systems, which significantly lowers the initial investment.

The road to the certificate

The road leads from a gap assessment and the preparation of documentation through an internal audit to the certification audits (stage 1 and stage 2) with an accredited body. With an experienced partner the process typically takes from a few months to a year, depending on the size and maturity of the company.

Thinking about certification? Let’s check together where you stand and how much subsidy you can obtain.

Product life cycle assessment (LCA): a key step towards an effective ISO 14001

Sun, 25 Jan 2026 00:00:00 GMT

Sustainable business today is no longer a matter of choice but a strategic decision. Companies that want to remain competitive in the long run need to understand the impact of their products and services on the environment — from beginning to end. This is where life cycle assessment (LCA) comes in.

What LCA is

LCA is a method for systematically evaluating the environmental impacts of a product across its entire life cycle: from raw-material extraction, production and distribution to use and end-of-life handling. The result is not a single number but a complete picture of where in the chain the greatest impact arises — and where it can be reduced most cheaply.

The link to ISO 14001

The ISO 14001 standard requires organisations to apply a life cycle perspective when identifying environmental aspects. This does not mean every company has to carry out a full LCA study — but it does mean that environmental impacts have to be assessed beyond the company’s own gates: in purchasing, transport, product use and disposal.

How to approach it in practice

Start with one representative product or service. Map the phases of its cycle, gather data on material and energy consumption and identify the biggest impacts. Even a simplified analysis often reveals surprising savings — in packaging, transport or the choice of materials.

Companies that build LCA into their environmental management system find it easier to answer customers’ questions about their carbon footprint, apply for tenders more successfully and make better development decisions.

Need help integrating the life cycle perspective into your ISO 14001 system? Get in touch.