John Steinke
07-13-2010, 04:06 PM
Before getting into the specifics, I'd like to make a few general observations.
The first is that, by definition, an inspection report is an opinion. Your opinion. No one else's. I don't care if you're repeating what someone else said - it has your name on it.
What's a opinion? After all, it's been said that opinions are like fingers .... most folks have a handfull or two. So what makes your opinion stand out?
One of the early chief engineers at Ford said it first: When everyone has an opinion, the opinion that's accompanied by data stands out.
Now ... as to report format ....
The most obvious part of a report is the title. This should instantly make clear, even at a casual glance, just what property is addressed by the report. Next declare when and for whom the inspection was done. Full disclosure.
If the report is based, in part, on other inspections of the same property, this should also be declared.
The 'meat' of the report is simply your conclusions / opinions. Like a school paper, this is a good time to use footnotes. The body of the report is not the place to cite code, discuss history, etc.
Along with your conclusion, the body is also where you might find it appropriate to suggest a fix. If you do suggest a fix, be concrete and positive; don't just say "fix it." If you doubt a fix is practible, say so. If you're not qualified to suggest a method, declare your limitations.
After the body of the report is the place for two other sections:
The first, as mentioned, are the footnotes. Here is where you can elaborate- perhaps offering your opinions as well as to what would be better (perhaps because of more recent code changes). In the footnotes you have the opportunity to explain some of the factors that led to your opinion. For example, in a studio apartment you might want to explain how you determined where the 'kitchen' ended and the 'bedroom' began.
The other is where you can discuss history, and other background information, that may be relevant to the property. For example, if you KNOW the place was under water in the 90's, or you KNOW the place was once considered as the site of the new bus terminal.
Remember, the report is supposed to be read - so make it readable. If you spend all day with your nose buried in a code book, your writing is apt to adopt that style - a real put-off.
Writing also tends to reveal your attitudes. If you think you're smarter than everyone else, that's sure to come through .... and not likely to win repeat customers.
While you need to be clear, it is also necessary to avoid layers of qualifying statements - especially when facts are discoverable. "The house was built in 1966" sounds a lot better than "The house appears to be a mid-60's style ..."
Finally, be very, very clear as to what you know is a fact, and what you think / conclude / believe / were told.
As a closing statement, you might want to include an 'advert.' This is where you can list what sets you apart from the other guy
Those are my thoughts. What are yours?.
The first is that, by definition, an inspection report is an opinion. Your opinion. No one else's. I don't care if you're repeating what someone else said - it has your name on it.
What's a opinion? After all, it's been said that opinions are like fingers .... most folks have a handfull or two. So what makes your opinion stand out?
One of the early chief engineers at Ford said it first: When everyone has an opinion, the opinion that's accompanied by data stands out.
Now ... as to report format ....
The most obvious part of a report is the title. This should instantly make clear, even at a casual glance, just what property is addressed by the report. Next declare when and for whom the inspection was done. Full disclosure.
If the report is based, in part, on other inspections of the same property, this should also be declared.
The 'meat' of the report is simply your conclusions / opinions. Like a school paper, this is a good time to use footnotes. The body of the report is not the place to cite code, discuss history, etc.
Along with your conclusion, the body is also where you might find it appropriate to suggest a fix. If you do suggest a fix, be concrete and positive; don't just say "fix it." If you doubt a fix is practible, say so. If you're not qualified to suggest a method, declare your limitations.
After the body of the report is the place for two other sections:
The first, as mentioned, are the footnotes. Here is where you can elaborate- perhaps offering your opinions as well as to what would be better (perhaps because of more recent code changes). In the footnotes you have the opportunity to explain some of the factors that led to your opinion. For example, in a studio apartment you might want to explain how you determined where the 'kitchen' ended and the 'bedroom' began.
The other is where you can discuss history, and other background information, that may be relevant to the property. For example, if you KNOW the place was under water in the 90's, or you KNOW the place was once considered as the site of the new bus terminal.
Remember, the report is supposed to be read - so make it readable. If you spend all day with your nose buried in a code book, your writing is apt to adopt that style - a real put-off.
Writing also tends to reveal your attitudes. If you think you're smarter than everyone else, that's sure to come through .... and not likely to win repeat customers.
While you need to be clear, it is also necessary to avoid layers of qualifying statements - especially when facts are discoverable. "The house was built in 1966" sounds a lot better than "The house appears to be a mid-60's style ..."
Finally, be very, very clear as to what you know is a fact, and what you think / conclude / believe / were told.
As a closing statement, you might want to include an 'advert.' This is where you can list what sets you apart from the other guy
Those are my thoughts. What are yours?.