Where does design assistance end and professional sign-off begin?

Kavita TanCost Engineering · 26 yrs

Your rule is the correct one and it is worth stating even more narrowly: never write the words compliant, complies or in accordance with as a conclusion about a jurisdiction where you are not registered. Say what standard you designed to, what checks you performed, what assumptions you made, and what remains to be verified. The compliance statement is an act of professional certification and it belongs entirely to the person who seals. I have seen this go wrong not through anyone trying to overstep but through a helpful email — an engineer confirming to a contractor that a detail is fine, with no seal and no intention to certify, and that email being produced later as the basis on which construction proceeded.

The practical control that has worked for me across four jurisdictions is a fixed limitations block on every deliverable, not just the final report. It states the standard used, that the work is design assistance provided to the registered engineer of record, that no compliance determination for the jurisdiction is made, and that the deliverable is not for construction until sealed. Putting it on calculation sheets and model exports as well as reports matters, because the documents that circulate informally are the ones that create the exposure, and a calculation sheet with no limitations block on it travels a long way.

Aisha BhattDam Engineering · 25 yrs

Verified expertise in Dam Engineering

Working across several jurisdictions, the line I have settled on is about who is making the judgement rather than about the words used. If the reviewing engineer has enough information to independently reach the conclusion and would be professionally negligent not to check it, you are providing design assistance. If they would have to take your word for something material, you are effectively certifying regardless of what the cover sheet says. That test is more useful than the wording rules because it tells you what to deliver: full assumptions, full calculation trail, the governing cases identified, and the things you were uncertain about flagged rather than smoothed over.

Which means the deliverable for design assistance is substantially more transparent than a sealed deliverable for a client, not less. A sealed report can reasonably state a conclusion and hold the working in an appendix. A design assistance package needs the reviewing engineer to be able to reconstruct the judgement, so anything I could not resolve goes in an open items list with what I would need to close it. It costs more to produce and it is the only version of the arrangement that actually works.

Kenji RahmanSystems Engineering · 21 yrs

Strongly agree on saying out loud that a platform badge changes none of this, and I would extend it: verification tells a client that credentials were checked, which is a statement about identity and qualification, not about authority to practise in their jurisdiction. Those get conflated constantly by clients who are not engineers, and the conflation is usually not deliberate — verified reads as approved. The burden of correcting that falls on the engineer in the engagement, every time, and the correction is better made in writing at proposal stage than verbally later.

The clause I include at proposal stage rather than at delivery is that the scope is design assistance to an engineer of record whom the client is responsible for appointing, and that the appointment must be in place before the work starts. Raising it at proposal is a much easier conversation than raising it when a client is asking you to confirm something is fine to build, because at that point they have a schedule problem and you are the obstacle. Getting the engineer of record named in the contract removes the question entirely.