Architekwiki
  • WIKI
  • Start Here
  • Resources
  • Other
    • Reading List
    • OFFPLAN
    • Details
    • About
    • Sign Up
    • Terms of Use
  • WIKI
  • Start Here
  • Resources
  • Other
    • Reading List
    • OFFPLAN
    • Details
    • About
    • Sign Up
    • Terms of Use

Architekwiki

A Resource For Architects
Subscribe

Written Agreements - Gotta Have 'Em

7/24/2016

 
Contracts

Should You Have Written Agreements

Everyone urges you to have written agreements for your design projects. There really isn't a good reason for not having a contract. However, we were rarely able to accomplish the goal of 100% of projects having a written agreement. 

Our best effort to achieve this goal was to simplify the process. The two tools that we found helpful were a Letter Of Engagement, and our own Standard Agreement. There isn't anything wrong with standard AIA agreements. They aren't even hard or time-consuming to complete. But formality and exactitude get in the way.
​
The problem we found with industry-standard agreements is that too many of our projects started out with a vague scope of work or with us doing programming work for the client. This kind of fuzzy kickoff inevitably slides into actually designing the project without a point at which the preliminary work stops and Basic Services starts. We found that only the need or desire to change the form of billing would act act as a signal that the scope of work has firmed up to the point that a contract could/should be written. So we went a different route.
​

Legal Issues
In the early stages of our typical engagement we found that we could only complete an AIA agreement by filling in "TBD" for the project description and for the fee. We found that we would have to spend twice the effort to get a real written contract.

Instead we developed a Letter of Engagement. The
Letter of Engagement easily solves this vagueness by recognizing it and simply stating what we know. To get things underway we proposed that we would be paid by the hour until the project comes into focus. Our standard Letter of Engagement does this and is simple to send off to the client for a signature. We reference our standard terms and conditions and also reference an AIA agreement as the basis for issues that aren't being addressed.

The second tool that we used was a very similar document, our Standard Agreement For Professional Services. This is just a bit more than a proposal form. In fact we often use it as a proposal form, but it is very easy to edit by adding specifics of the project and the fee and subtracting any special conditions that are not applicable.

Either of these agreements could be called up from our server, edited, converted to PDF, electronically signed, and emailed to the client in less time than you we could decide which AIA contract to use. Not to mention completing it with their software or online. Nevertheless, AIA agreements would be my first choice if it weren't for the way reality intrudes and undermines the goal of having a written agreement. 

By using these two tools, we had about an 80% completion rate for contracts. That was far from perfect, but our professional liability guy stopped bugging us. Maybe we were close to the industry average.

The newest AIA agreements seem to recognize and embrace the fuzziness of the initial engagement. However there is still the need to revisit the contract periodically and to update it with new information. That just never seems to happen. 

Picture
Editable copies of our Letter of Engagement and our Standard Agreement are found in the Architekwiki Archive as part of "MGMT-01". Access to the archive is a perk of being a subscriber.

SUBSCRIBE NOW


​###
Fred Pucciano link
9/6/2018 11:58:30 am

I would like to share some of your ideas.

Rick Wolnitzek link
9/6/2018 02:14:45 pm

Sure. Check out my Terms of Use. (https://www.architekwiki.com/terms-of-use.html)


Comments are closed.
    Resources

    Start Here

    Picture

    Picture

    Trello-PM

    FeeCalqs

    Picture

    Terms of Use
    Your use of Architekwiki is implicit agreement with the 
    ​
    Terms of Use.

    RSS Feed


    Categories

    All
    Business Development
    Communications
    Concepts
    Design
    Detail
    Estimating
    Finances
    Legal Issues
    Management
    Miscellaneous
    Money
    MyCorbu
    People
    Planning
    Process
    Projects
    Records
    Services
    Specifications
    Standards
    Time
    Tools


    Archives

    February 2021
    January 2021
    December 2020
    November 2020
    October 2020
    September 2020
    August 2020
    June 2020
    April 2020
    March 2020
    February 2020
    January 2020
    December 2019
    November 2019
    October 2019
    September 2019
    August 2019
    July 2019
    June 2019
    May 2019
    April 2019
    March 2019
    February 2019
    January 2019
    December 2018
    November 2018
    October 2018
    September 2018
    August 2018
    July 2018
    June 2018
    May 2018
    April 2018
    March 2018
    February 2018
    January 2018
    December 2017
    November 2017
    October 2017
    September 2017
    August 2017
    July 2017
    June 2017
    May 2017
    April 2017
    March 2017
    February 2017
    January 2017
    December 2016
    November 2016
    October 2016
    September 2016
    August 2016
    July 2016
    June 2016
    May 2016
    April 2016
    March 2016
    February 2016
    January 2016
    December 2015
    November 2015
    October 2015
    September 2015
    August 2015
    July 2015
    June 2015
    May 2015
    April 2015
    March 2015
    February 2015
    January 2015
    December 2014
    November 2014
    October 2014
    September 2014
    August 2014
    July 2014
    June 2014
    May 2014
    April 2014
    March 2014
    February 2014
    January 2014
    December 2013
    November 2013
    October 2013
    September 2013
    August 2013
    July 2013
    June 2013
    May 2013
    April 2013
    March 2013
    February 2013
    January 2013
    December 2012
    November 2012
    October 2012

    Resources
VISIT ARCHITEKWIKI'S RESOURCES
Picture
Architekwiki | Architect's Resource | Greater Cincinnati | (859) 444-4560
© 2012-2020   Architekwiki​