I will attend to confoo conference, it will be a little different then Pycon conference. It is a web conference that will take place in Montreal. I am looking forward to some talks on scaling, memcache, cloud computing and python web framworks. I might also attend to the training “Relational Database Applications with TurboGears” from Christopher Perkins. I look to talk to some other passionate guys.
Knowing that I am flirting with the idea of doing consulting, I was looking for advices about common mistakes and better ways to evaluate client contracts. Contracts can put you in obligations you haven’t thought and make you slip your deliveries, force you to make more work than planned and worst, jeopardize your relationship with clients. Root cause is most likely unclear expectations on both sides. With some spaghetti clauses that only juridic lawyers can understand, it is easy to fall in this path and everyone loose at this game.
RIM (Régionale de ingénieurs de Montréal/ordre des ingénieurs du Québec), was organizing a training Workshop called “Business Contracts 2.0”. The presentation from Gilles Thibault of edilex was extremely interesting.
Currently, their is no established standard to create contracts. Basically their is as many form as the number of lawyers out there. Most of the time, lawyers are the only one comfortable with them because they’ve wrote them and it is in their juridic jargon. Unfortunately it doesn’t help much who really used them. Most of the time, clients and contractors have hard time understanding them but it is a lucrative process for high hour rate paid lawyers. According to Gilles, lawyer will disappear if they can’t provide better services for contracts (a little bias).
Edilex is proposing a template for contract to ensure nothing is missing and enforce structure to ensure clear expectation between each party. A contract need a table of content, its like a plan.
Proposed Template blocks:
- Identification & location (name + birth->juridic name + rights applicable)
- Party identification (Physic/moral-Society/union/coop ->representative liquidator Trustee/power delegation etc. )
- Preamble (context used for fall-back defect clauses)
- Lexicon (clarification/disambiguation & shorter sentences)
- Object (simple/multiple;utility conditions/redaction)
- Cost (adjustment/payment method/warranty/phase delivery etc.)
- Attestations party A (not obligation/warranty-improve trust-don’t want to fight about obligation and duty to disclose information)
- Attestations party B
- Reciprocal obligations
- Obligations party A (Align with Business process/order of execution)
- Obligations party B
- Special provisions (orphan/specific/bi-directional)
- General provisions
- End of contract (resolution/termination)
- Start of the contract
So basically, why a template?
- Clearly define what it include and isn’t (You can’t remove sections)
- Provide table of content (Don’t need to reread all the contract)
- Find holes/unclear-possible point of conflicts
- Reduce dramatically judge interpretation during conflict
- Can help deciding to not get involve in the project (risk/client honesty)
- Provide structure/uniform frame
- Enforce clarity
I will try to apply some of those ideas and it is making me way less scared and equipped to sign new contracts. I really like this approach.