Showing posts with label code inspection. Show all posts
Showing posts with label code inspection. Show all posts

Saturday, May 15, 2010

"...But The City Approved It!"

It happens to me several times each year; I inspect a home for a buyer, I point out a construction defect, then I get a call from an angry seller or seller's agent, accusing me of being wrong.

If someone challenges my call, I'm always happy to provide an authoritative reference to prove that I'm not just throwing my opinion around.  I can give code references to prove my calls if I'm challenged.  This is why it's important for home inspectors to know building codes, even though they're not doing code inspections... but I digress.

The crazy argument that I sometimes get from home sellers and seller's agents is that a defect that I reported on is not a problem, because the defect wasn't identified as a part of the permit inspection process.  The argument sounds like this:
Angry Home Seller:  "That hole in my roof is fine!  You had no right to tell the person buying my house that it's wrong."
Me: "That hole is not acceptable.  It will leak water in to the house."
Indignant Home Seller:  "That roof was just installed a month ago, and the installation meets the requirements for the Minneapolis Building Code."
Me:  "What makes you say that?"
Misinformed Home Seller: "The City of Minneapolis approved the permit.  That means it meets the city's code."
While a hole in the roof is an extreme example, the logic applied by this home seller is just as flawed when it comes to other less extreme defects, such as improper nails in joist hangersimproper furnace ventingattic bypasses on new construction... you name it.

Municipal inspectors often have very full schedules and don't have the luxury of taking their sweet time during inspections like I do.  If a municipal inspector misses a violation of the code, it doesn't mean that the violation was approved.


To prove my point, I'll even give you a code reference from the Minnesota State Building Code (insert smiley winky face).

1300.0210 Inspections
Subpart 1. General. Construction or work for which a permit is required is subject to inspection by the building official and the construction or work shall remain accessible and exposed for inspection purposes until approved. Approval as a result of an inspection is not approval of a violation of the code or of other ordinances of the jurisdiction. Inspections presuming to give authority to violate or cancel the provisions of the code or of other ordinances of the jurisdiction are not valid. It shall be the duty of the permit applicant to cause the work to remain accessible and exposed for inspection purposes. Neither the building official nor the jurisdiction is liable for expense entailed in the removal or replacement of any material required to allow inspection.


Good times.



Reuben Saltzman, Structure Tech Home Inspections - Email - Twin Cities Home Inspector
Facebook Reuben's LinkedIn Page Follow StructureTech on Twitter ASHI Certified Home Inspector - Click To Verify Click to subscibe to Reuben's Blog

Thursday, January 28, 2010

Why Don't Home Inspectors Mention Code?

Home inspections are not ‘code’ inspections, and a lot of home inspectors even treat the word ‘code’ as taboo.  They call it the ‘C-word’.  I recently had a home inspector tell me he’s not even allowed to use that word in Kentucky.  This is such a taboo word that I don't use it either, but I don’t think it has to be this way.

The basis of taboo 
Three of the largest home inspection organizations make it clear in their Standards of Practice that home inspectors are not required to report on code compliance.  For example, the ASHI Standards of Practice state that “Inspectors are NOT required to determine compliance with regulatory requirements (codes, regulations, laws, ordinances, etc.).”  There is nothing in the standards prohibiting home inspectors from determining compliance… it’s just not a requirement.

Where ‘code’ plays a role in home inspections
Home inspections are conducted to educate the client – usually a home buyer.  The ASHI Standards of Practice states that Inspectors are required to report on Unsafe conditions, which is defined as a condition that is judged to be a significant risk to bodily injury during normal, day-to-day use; the risk may be due to damage, deterioration, improper installation, or a change in accepted residential construction standards.

Accepted Residential Construction Standards
This is not defined, but my interpretation of this means ‘building codes’.  This is how construction standards are defined.  Inspectors in different parts of the country have different building codes, so they also have different construction standards.  What is acceptable in one part of the country might be unacceptable in Minnesota.  Home inspectors should be expected to know what’s acceptable in their part of the country, and they should be able to prove it if necessary – this means citing code.

It’s always a judgement call
Since 2003, the National Electric Code has required arc-fault circuit interrupters (AFCIs) for bedroom circuits.  AFCIs prevent fires.  Does the lack of an AFCI breaker in a home built before 2003 constitute an unsafe condition?  What about a new construction home?  Should a home inspector call out missing AFCIs in homes built before 2003?  What about new construction homes?  If a home inspector doesn’t answer ‘yes’ to the last two questions or ‘no’ to the last two questions, they’re basing their answer on ‘code’, not ‘unsafe’ conditions.  Us home inspectors call this is a ‘construction defect’, but why not call a spade a spade?  It’s a code violation.

Reuben Saltzman, Structure Tech Home Inspections - Email Golden Valley Home Inspections