Step 1 · Purpose
What the report has to achieve.
What we do, in detail
Technical inspection, establishing who must issue a report, engineering support, and technical files.
Program 01 · Scope in writing
Technical inspection
An examination is only meaningful if its boundaries are written down: what was examined, what was not, by which method, and what that method cannot see. So that goes in the report, along with anything concealed, inaccessible or not dismantled. A report describes the condition found at the time, by that method. It does not warrant how something will behave next year, and a report that implies otherwise is doing you no favours.
Step 2 · Status
Whether it is reserved to a body.
Step 3 · Scope
In writing, including exclusions.
Step 4 · Report
Findings, method and limits.
Step 1 · The requirement
Who is asking for the report.
Step 2 · The status
Accredited, approved, or neither.
Step 3 · The scope
Checked method by method.
Step 4 · The answer
Us, or somebody else.
Program 02 · The useful question
Who must issue it
This is the service clients did not know they needed. Several Belgian examinations may only be performed by a body holding a specific approval, and accreditation itself runs per scope, so a certificate on a wall proves nothing about the method you need. We establish what status your report requires, tell you whether we hold it for that scope, and where we do not we say so and point you to a body that does. Losing work that way is cheaper than issuing a worthless document.
Program 03 · Not an architect
Engineering support
Technical support on the engineering side: calculation, specification, review of what a supplier has proposed. Two limits get stated at the outset. We are not a firm of architects, and in Belgium plans and supervision for works subject to a building permit are reserved to an architect, so your project needs one regardless of us. And where we have had a hand in a design, we do not then act as its independent inspector.
Step 1 · The problem
Stated technically, not vaguely.
Step 2 · The constraints
Including who else is required.
Step 3 · The work
Calculation, specification, review.
Step 4 · Handover
Documented and explainable.
Step 1 · What exists
The documentation actually held.
Step 2 · What is missing
Listed rather than assumed.
Step 3 · The register
Open findings, owned and dated.
Step 4 · Closure
Re-examined and recorded as such.
Program 04 · Findings closed out
Technical files
Most inspection findings are not lost because nobody understood them. They are lost because nobody owned them. We assemble the technical documentation a site actually needs, keep the register of open findings, and follow each one to closure with a date and a name against it. Where remedial work is required, it is done by you or your contractor and the re-examination is identified as a re-examination, not quietly folded into the original report.
Need a report, or need to know who must issue it?
A free first conversation, with no obligation.