While every contract has unique characteristics specific to the commercial transaction, there are certain features that lend themselves to standardization. Indeed, most contracts have been assembled by business and legal teams with a ton of “cutting and pasting” from various contract templates; however, with a lack of systemic control. This can create what is known as content customization, worse yet and a ‘legal exception’ given the amount of complexity and risk a simple word change can generate. That is, content changes in the document assembly process can trigger a significant change in the intent or context and not be caught by the ‘naked eye’ in such process. So, if your company is a behemoth, or the proverbial “800 pound gorilla”, then maybe you can get away with just locking down your assembly process so no internal changes can be made. And even not allow for editing or negotiation with your counterparty.
Legally speaking, contracts can be interpreted in vastly different ways. From verbal contracts, called express contracts, to implied and quasi contracts, project managers need to plan for all possibilities.
Traditional contracts can have several pitfalls that can be avoided through the use of technology. Think about what a contract traditionally has been: a single, lengthy, paper-based document that is time consuming to create and, therefore, does not get updated regularly.