Technology in Architectural Practice

I have a copy of a "Quality Assurance Document Review Checklist" from the University of Notre Dame Office of the University Architect from 2006 (2008).  We gave some thought to using it as the basis for a program.  It covers projects from concept through construction.  It does have some very specific parts and some terms that might be revised to more generic.  It can be found online.
-------------------------------------------
Joseph Stypka AIA
Vice President, Director Specifications
Murphy/Jahn Architects
Chicago IL
-------------------------------------------

Checklists are absolutely critical for overall QA of a project, for content that can be quantified. Without detailing the checklists themselves, I see value in keeping up with checks at all project phases.

Since the owner's program is the beginning of the project, it is certainly important to check the earliest sketches against the program. At the same time, the "big hitters" of the applicable codes need to be checked at the outset. As the project progresses, the checks become more definite and more detailed. Also, in the early stages, I have found a peer review by a disinterested party to help open additional possibilities or narrow selections, or both, for design considerations.

I have also found, that for primarily technological purposes, it is valuable to have a review performed by a professional not involved in the project, if available. With large projects sometimes the details get lost in the details.
-------------------------------------------
Charles Graham AIA
Architect
O'Neal, Inc.
Greenville SC
-------------------------------------------