Quality Consulting: Build Consistency into Processes and Services

Quality consulting helps an organization connect customer requirements with the way its work is designed, delivered and improved. The aim is practical consistency: people understand what is expected, processes have clear ownership and recurring problems lead to useful action. Quality is not limited to a final inspection or the appearance of a certificate.

What does quality mean for a service business?

A service has requirements even when its output is less tangible than a manufactured product. Accuracy, agreed scope, timely communication and a clear handover may all matter. The relevant criteria depend on the service and the commitments actually made. A general ambition to “exceed expectations” does not replace an agreed understanding of the work.

ISO describes quality management through processes that support meeting customer and applicable requirements, with continual improvement. Its guidance distinguishes quality assurance (QA), which focuses on providing confidence that quality requirements will be met, from quality control (QC), which focuses on fulfilling those requirements through appropriate operational activities and checks. Both can contribute, but they answer different questions.

Three complementary views

This editorial comparison is a way to structure a quality discussion; it is not a universal audit checklist.

Where consultancy can contribute

A quality-related engagement may focus on process design, responsibilities, measures or management system implementation. The appropriate scope depends on the organization’s need and the agreed service. It should not be assumed that every engagement includes a comprehensive audit, certification preparation or redesign of every department.

The useful starting conversation identifies the business issue at an appropriate level. Repeated rework, unclear handovers or inconsistent service information can indicate different priorities. The proposal and agreement then establish which activities and outputs are included. This keeps expectations aligned without creating an open-ended commitment.

A useful assignment might start with one recurring handover problem. The agreed outputs could include a map of the current process, verified causes, a revised handover rule, a pilot and an effectiveness review. The organization provides access to relevant evidence, appoints an owner and approves operational changes. The consultant supports analysis and implementation within the agreed scope; the organization remains responsible for running the process. Agree how the work will be accepted before it begins, so a completed document is not mistaken for a working improvement.

Make process ownership practical

Many quality problems appear between functions rather than within a single task. One team may finish its work while the next receives incomplete information. A process owner helps connect the steps and identify where a decision or handover needs clearer responsibility.

Ownership does not mean one person performs every activity. It means the organization knows who coordinates the process, who approves changes and how issues are escalated. Procedures should reflect this arrangement in language that the people doing the work can use.

An illustrative service handover

Imagine a business receiving a customer request, preparing a quotation and handing the agreed work to an operations team. If a change discussed during the quotation is not reflected in the handover, the team may deliver against an earlier understanding. Inspecting the final output may reveal the mismatch, but the more useful improvement concerns how approved changes are communicated.

This hypothetical example is not an ATMACSS client case. It shows the difference between correcting an individual result and improving the process that produced it. The appropriate change depends on the actual workflow and authority arrangements.

Make the acceptance point explicit. Before operations starts, it should be able to identify the approved scope, current version, promised date and person authorized to resolve a discrepancy. If the customer requests a change, assess its effect on work, timing and cost and obtain the required approval. Preserve the link between the decision and the instructions used for delivery. More signatures are not automatically better control; the control must address the actual risk.

Use measures that reveal the issue

A quality measure should help the organization decide what to improve. The number of completed tasks can show throughput, but it may hide repeat work. Customer feedback can reveal an experience, but an isolated comment should be interpreted with context. Combine suitable evidence rather than treating one number as a complete description.

For the hypothetical handover process, define a first-time accepted handover as one the receiving team can use without returning it for missing or incorrect required information. If 45 of 50 handovers meet that definition during the agreed period, the first-time acceptance rate is 45 ÷ 50 × 100 = 90%. With an illustrative target of at least 95%, the result falls short by 5 percentage points. These figures explain the method; they are not a benchmark or an ATMACSS result.

Count each handover once and record the reason for any return. Distinguish a correction to incomplete information from a newly approved customer requirement, and do not quietly remove difficult cases from the denominator. A key performance indicator (KPI) becomes useful when its definition, target, source, owner and review frequency are clear. Review the severity of errors alongside the rate: one serious scope error can matter more than several minor omissions.

Changing a definition can change a trend. Make such changes visible so that a report does not imply an improvement caused only by a revised calculation.

Quality management and ISO 9001

ISO 9001 is a management system standard related to quality. ISO’s current overview introduces the 2026 edition. Organizations considering certification or a transition should check the applicable requirements and arrangements with the relevant certification body. Use the published standard and applicable transition guidance to plan the work; do not assume that every organization follows the same timetable.

Consultancy and certification have separate roles. ATMACSS can provide implementation and readiness consultancy within an agreed scope; certification decisions belong to the external certification body. A certificate is not a guarantee that every output will be error-free.

Turn improvement into a repeatable cycle

Use Plan–Do–Check–Act (PDCA) to organize the handover improvement. Plan the requirement, suspected cause, proposed control and evidence needed. Do a limited trial with an assigned owner. Check actual handovers against the agreed criteria and investigate exceptions. Act by adopting the change, adjusting it or trying another approach when the evidence does not support it. Repeating the cycle is more useful than introducing a form and assuming the issue has disappeared.

Internal audit can examine whether agreed arrangements are implemented and effective, using objective evidence and appropriate impartiality. It complements day-to-day checks rather than replacing them. Management review then considers what the findings mean for priorities, resources and wider risks. Neither activity should become a count of documents completed without a decision about how the work performs.

Separate correcting one result from preventing recurrence

In the service-handover example, a correction fixes the immediate mismatch. Corrective action addresses the cause of the problem to prevent recurrence. Preventing recurrence requires examining why the approved change did not reach operations. Check the actual sequence of events before assigning a cause. A reminder to be more careful may leave the information flow unchanged.

Compare the agreed requirement, the approved change and the version used by the delivery team. Identify where responsibility, access or communication failed. Select an action that addresses the demonstrated issue, such as a controlled handover point with a clearly assigned owner. Avoid adding approvals that do not resolve the cause.

After the change, inspect relevant subsequent handovers. Can the team identify the current approved scope? Do exceptions reach the person with authority to resolve them? Record the evidence and any remaining limitations before concluding that the action worked.

This is an illustrative improvement method, not a universal audit checklist. It distinguishes a corrected individual result from evidence of a more reliable process. It also gives management a basis for deciding whether the action is effective or needs revision.

Explore ATMACSS services for ISO implementation and certification readiness. Scope, deliverables and terms are defined in the proposal and agreement.