Do you place disclaimers in your contract and/or reports for any missed issues other than hidden/latent issues?
Bit of a different perspective here, but it is also why any good report writing software will never include the word “code” in a feature or report output.
We use the word “standards” if anything, but only if the inspector chooses to enable that feature for an item in the report.
Building codes are beyond the scope of the SOP in my understanding, so we didn’t want to have anything that makes it look like the user should be including code quotations in their narratives. Or that the client would get that impression.
What I’ve been told, but not sure about, is that if incorrect building codes are quoted or misapplied, it may even be a potential liability issue for the inspector. I’ll have you guys tell me I’m wrong on that one or not
So are you only parroting what other HI’s have said and you have no real opinion on the subject?
Yes, for unverifiable issues (issues that can’t be confirmed without further analysis or testing) such as Radon, mold, asbestos, etc.
I am actually surprised at how many guys are acting like they have never seen this before… I see this all the time and have actually never called it out.
I have called out insulation under the connection, but never the placement of the clamp.
I thought insulation under the clamp was the issue. It’s not much, but it is still affecting the clamping of the actual conductor, in my opinion.
Every perspective is welcome here and thank you for sharing yours.
What you are describing is a game of semantics. The “Codes” are the required “standards” Builders are to use when directed to by the local AHJ. Of course there are other standards/authoritative sources along with the manufacturer’s requirements. However as a generic word to include all of these references then “standards” would be a preferred word in a narrative and then an actual citation of that “standard” to follow it.
In my opinion it would be a great asset to anyone purchasing a report writing software package to be able to select a set of narratives that are based on specific “standards” with the actual “standards” citation at the end of the narrative. Of course it is obvious why this would not be offered as it can very labor intensive to create. So narratives are typically written in generalities to fit many different situations.
However that same issue should be taken into consideration for all canned narratives in report writing software and even the word “standards” should be left out as well. After all what might be a “standard” today may well not be next week when it is found to be flawed.
You will undoubtedly have many various opinions on this however with regards to quoting “codes” or “standards” that should be left to new construction related inspections. The “codes” and “standards” that are incorrectly quoted and/or misapplied leave no real liability to the Inspector. Instead they can greatly harm their credibility when the Builder displays to the Buyer how the Inspector is wrong. I have never seen the liability angle here and maybe others might?
Are we good with codes? Can we move on to opinions on Stab-lok breakers? Or maybe who has the best software or insurance.
I feel ladders or foundations would be more fun
The liability with using the phrase “does not meet code” goes back to implying that you performed a “code inspection” on the entire home.
The word “code” comes with a certain connotation that suggests you verified the home was or was not
built to all applicable codes in place at the time of construction or modification, if applicable.
Some may even prefer “Footers”.
There is no implication that a “code inspection” was performed on the entire home if the client’s expectations are properly managed as I spoke of above.
As I stated above the use of code citations in a report should be left to new home construction related inspections. Also as I stated above:
Part of misquoting and/or improperly applying the codes are from not using the proper version that was required to be followed by the Builder when the home was built. For that the Inspector must know what the local AHJ or other controlling authority required and must use those code cycle versions.
I guess it might be different if you work in a very small area, or in a a large metro area where all of your work is performed under one jurisdiction. As for me, I sometimes travel 60 miles plus in different directions every day of the week. There is no way to keep track of the different codes that may have been in affect for every type/age of home in each of the individual areas I service.
My average commute for inspections is 55 miles one way. So I can understand the time lost due to that.
Again I only quote “code” for new construction even though I do use it as a reference when making a decision whether to call out an issue or not on an existing home (sans 1 year warranty inspections which also are quoted with “codes”), especially for safety items.
As a result I am only concerned about the new build required codes which are specified on the local AHJ’s WEB page and/or in the municipalities code or ordinances. These are all available here typically from the municipalities WEB site even for smaller AHJ’s. As a part of the inspection these are checked before the inspection along with that AHJ’s amendments to the codes.
Using “codes” and “standards” in an inspection is an intensive activity but it is to the benefit of the client. What the OP stated, and is quoted here, is no different wherever you go in the country.
I think it started out as insulation, then A couple guys were talking about the clamp connection, and now it’s all focused on code…
Shouldn’t that actually say… “Does not meet minimum code…”?
Nope, go back and read post #8.
There is no such thing as “minimum” or “maximum” code. Each code item has exceptions and additions to deal with specific circumstances.
Since it’s a new build it might be proper to say “current code.” Current code for any particular jurisdiction may not be the most recent ICC adoption.
Morning Paul.
SoP: We do not cite code.
Electrical: Observation:
Poor circuit conductor termination on OCPD. Insulator jacket pinched impeding full conductor contact. Can/May cause current impedance.
Recommend: A licensed electrical contractor:
1: properly terminate circuit conductor termination on OCPD.
Act upon any recommendations therein.
I also use the phrase “not up to current standards” as opposed to using the word “code” in some areas of my reports.
From Ohio SOP:
1301$17-1-17-Rule-N.xml (ohio.gov)
(E) A licensee is not required to determine or offer an opinion about any of the following items in a home inspection report for a property inspected:
(1) The condition of a system or part of system installed in a property that is not
readily accessible;
(2) The estimated remaining life of a system or part of a system;
(3) The adequacy or efficiency of a system or part of a system;
(4) The source or causes of conditions or deficiencies in the property;
(5) The estimated costs to correct deficiencies in the property;
(6) Forecasting future conditions about the property, including but not limited to,
forecasting the failure of systems or parts of system in a property;
(7) The appropriateness or suitability of a property for any use other than for
residential purposes;
(8) The compliance of a system or parts of a system in a property with
past, present or future requirements which include but are not limited to
codes, regulations, laws, ordinances, builder specifications, installation and
maintenance instructions, care or use guides;