Quality Breaks Where Communication Fails

A real case from QA/QC management practice

Your tests are completed, but your client doesn’t trust the results. This was exactly the situation a contractor came to us with. The Client was dissatisfied with the quality of documentation for the hydrostatic testing of an industrial boiler. Although the work had been formally completed, the process raised concerns and confidence in the results was missing.

At first glance, it looked like a typical “documentation issue” — a situation where many clients start with a documentation quality check.

In reality, it was something entirely different:

What we actually found

During the analysis, it became clear that the problem was not related to requirements or technical complexity, but to broken communication between the parties involved.

The Client’s expectations …

  1. were not formally documented or aligned
  2. were treated as a formality rather than as part of project quality
  3. were interpreted differently by the Contractor and the Technical Client

As a result:

  • the Client did not trust the test results
  • there was a risk of repeated comments and loss of time
  • the process became unpredictable and difficult to manage

Our solution: a management-driven QA/QC approach

Instead of issuing formal comments or putting pressure on the Contractor, we applied a QA/QC approach focused on process alignment and communication.

1. Internal Meeting — the Key Step

This stage was critical. The Client’s expectations were translated into clear, practical requirements.

We collected the Client’s expectations and converted them into actionable criteria for:

  • invitations to hydrostatic testing
  • the required documentation package
  • the structure and logic of test result reporting

2. External Meeting with the Contractor

The expectations were communicated transparently and without blame:

  • we explained why documentation quality is critical
  • demonstrated how documentation affects acceptance and trust
  • established a single, shared set of rules

The focus was not on formal compliance, but on the principle that documentation is a tool for trust, not a box-ticking exercise.

Results

Before the next hydrostatic test, the Contractor:

  • submitted a properly prepared test request
  • presented clear and transparent test results
  • provided a complete documentation package

This case shows that quality is built through proper communication “before”, not control “after”

QA/QC management helps identify the real root causes of problems and eliminate them before they turn into risks, conflicts, and time losses.

Want to manage quality — not consequences?

Contact us to discuss how to build an effective QA/QC system tailored to your project needs.

Leave a comment

Your email address will not be published. Required fields are marked *