Once we’ve worked out a project specification with a client, we sign a contract that includes the project specificaiton. This topic explains why we do this and a bit about our standard contract.
For more detail on how we handle other aspects of project management, see
Why and how we use contracts
When you want to get some work done, a contract often feels like an annoying piece of administration. We understand this. The reason we use contracts, even for some of our smaller jobs is because they protect ourselves and our clients against underforseen issues. A contract helps to clearly define the contours and scope of our relationship with our clients.
In addition to our standard contract, we also use contracts provided by our clients. We are open to using a contract provided by a client, subject to our review. In particular we always seek to ensure:
The contract reflects the agreement between the parties about what work is to be done for what price.
The contract does not affect Pavilion’s ownership of, copyright of, or licencing of, its open source assets.
Our standard contract
This is our standard contract:
Broadly speaking, it deals with the following topics. Feel free to respond below to ask about any of these topics in more depth.
What work for what price
Primarily our contract identifies:
Our relationship with the client.
What work is to be done.
What payment is to be given for the work.
Changes and updates
It also deals with things that may change after the contract is signed:
Changes to the price for the work.
How the price of new projects under the same contract is figured out.
How to deal with disagreements about the work or payment.
Protecting rights and interests
Our contract seeks to protect both Pavilion’s and our client’s rights and interests:
It protects the ownership of, and copyright and licences for, Pavilion’s open source assets.
It protects our clients confidentiality.
It provides a mechanism for the enforcement of Pavilion and our client’s rights.