
This picture says 1,000 words … not so good if you are the blasting contractor on a project. Well, believe it or not, there are always a wealth of emails and other documents produced in litigation that help "make the case" for the other side.
Take, for the example, the e-mail I found in the files of one superintendent entitled "PROJECT DELAYS" … the words could not have been clearer … "I think we need to begin to tell management that we are late. We also need to consult the claims team to determine how late we really are."
On another case, I found this nugget: "Although we should give them notice of this claim, let’s wait until our equipment has left the port on their vessel before telling them."
Best Practices advises that you should have a written document management policy in place. This policy should define and describe the role of the following:
- Critical project documentation, such as correspondence, meeting minutes, daily reports and logs, calendars and diaries, accounting records, submittals, schedules, photographs, etc.
- Non-critical documentation, such as personal emails, instant messages, text logs, blog trails, website traffic logs, etc.
The advent of project management software packages (i.e., Prolog Manager, Expedition, plansandspecs, Microsoft Project), as well as other web based platforms, enhances document control by allowing the user to track revisions, store master files, and streamline the review process. However, the human element is still involved. Any policy must set appropriate boundaries and guidelines for the following:
- Personal use of email (…a good place to find "mismanagement" emails…)
- Use of profanity (…I always search for the juicy four-letter words…good emails…)
- Risks of informal communications (…see emails above…)
- And, of course, a document retention policy (…don’t shred right after lawsuit is filed…)
Failure to formulate a policy that addresses these simple areas almost guarantees that the bad little email will get created and produced.
As an architect and a concerned citizen, I am frequently required to evaluate the cost of a particular technology or artifact, and then voice my opinion or advise a client as to its value. Cost accounting is typically framed within the context of manufacturing or production. In this model, all contributing costs are determined (by one of several competing methods) only up to the moment a manufactured item is produced. Thus contributing expenditures are the sole determinant of value; cost accounting is hence inherently historical. Furthermore, it is inherently consumerist: in its particular analysis of the cost of production it implicitly treats the artifact as relevant only through the production process; afterwards consideration for the artifact is discarded in effect by neglect. At no time are the costs of the consequences of the artifact considered. In order to shed some light on some of the implicit difficulties in measuring cost, let’s look at a couple of seemingly innocuous commonplace technologies.
Not only is the private industry demanding ways to integrate BIM into projects, so too is the public industry. Earlier this month, Wisconsin (through its
In other words, the authority to revoke LEED certification from a project raises legal concerns beyond the scope of LEED’s 
I know that I am a few hours early, but Governor Phil Bredesen is scheduled to sign the Tennessee Clean Energy Future Act of 2009 today at 1:30pm. He will be joined by key legislators, as well as members of his
Just when you thought it was safe to put up your study books, your on-line prep exams, and your stacks of flash cards … there is a new professional certification available for all you sustainable design players. 
You don’t always say what you mean. And you don’t always mean what you say.