BluEnt is a global technology company delivering data-driven, scalable solutions in digital transformation, software development, and enterprise consulting.
Latest platforms, AI-assisted workflows and expert craftsmanship combine to deliver technically superior, speedy, and exceptionally accurate deliverables.
QA MethodologyThe sequence does not vary by package size.
Every deliverable is checked by someone other than the person who produced it, then reviewed by a named senior reviewer before it reaches the client. That sequence does not vary by package size, by platform or by account.
By a detailer other than the one who produced the work. The person who drew a set is the worst possible reader of it, because they read what they intended rather than what is on the sheet.
Senior review.
By a named senior reviewer in the client's time zone, before issue.
Neither stage is skipped for a small package or a familiar account. The value of a check that is sometimes omitted is close to nil, because nobody downstream knows which sets received it.
Checking is a recorded process rather than an assurance.
What is checked
Against the standard the project specification names, and against the conventions recorded for that account.
Whether the set carries the standard the specification names, and whether the sections support the grade
Whether surface exposure categories are distinguished where the grade requires it
Whether hardware is specified to the level the grade expects
Whether specification references are placed where a reviewer will check them
Whether deviations are declared rather than drawn
Whether schedules resolve
Whether scribe and tolerance strategy is shown rather than assumed
Whether the account's own conventions have been applied
What is measured
First-pass approval rate, tracked and reported per account.
The measure is the proportion of submittals that clear review without a substantive comment, on that client's work.
Comment themes.
Where a package does come back, the recurring reasons are recorded, because a pattern across several packages is usually a documentation issue rather than a drawing one.
Query and RFI volume,
which is frequently more informative about the design documentation than about the detailing.
These are reported to the account they belong to. A client sees their own figures.
What is not published
No aggregate first-pass figure.
A single site-wide number would combine accounts with very different documentation quality, standards and reviewers, and it would mean little. Each account is measured on its own work and told its own result.
No internal productivity, efficiency, throughput or training measures.
Those are operational management information, not supplier assurance.
No accuracy percentage.
No measure of that kind is established, and quoting one would be inventing it.
How it is reported
Per account, on the account's own packages. Where a first-pass rate matters to a procurement process, it is discussed against that account's actual record rather than against a published figure.
The checking method itself is set out on the quality and standards page in the terms a client reads.
QA Methodology
What is checked and how, and what is measured per account.