Scope Description of Work

I start out with a "definition of work" contract. This is a lessen where my computer agrees to clear me a limited sum to organisation the send in a limited sort of hours. The idea is not to organisation the entire send here, but to acknowledge that my time is valuable, and they should clear me at least a cypher of my hourly evaluate to help entertainer up the plans for the lessen itself.

Whether or not you crapper get your clients to concord to that, you should entertainer up a lessen that includes the orbit of impact to be delivered. This should include:

* The sort of pages to be built
* The sort of programs, scripts, or CGIs to be built
* The sort of graphics to be created
* The amount of noesis to be written
* A margin of nonachievement - ie. the proportionality overage for the above where the lessen needs to be revisited

For example:

5-7 Web pages with 1 contact modify and CGI or PHP script. Each page module hit between 2 and 5 graphics and 3-6 paragraphs of text to be created by the designer. If, in planning, more than 10 Web pages, 1 script, or 50 graphics are needed, the lessen module need to be amended.

Remember, that the computer must concord to your contract. I hit found it good practice to hit them initial the orbit of impact section as well, so that they are certain they understand what you are delivering and what needs more negotiation.
Dates on the Project

Good contracts allow dates. While it crapper be tempting to leave it up to the client, after every they poverty the site fixed, don't they? Many clients module get busy with another things or just block if you don't hit hard dates cursive in the lessen for both you and them. Some of the dates I same to allow are:

* Signed lessen cod date
* Start of work
* Plans or designs completed
* Approval of plans or designs by client
* Content cod dates for client
* Milestone releases for designer
* Invoice dates (with amount that module be invoiced)
* Site completion date
* Review by clients cod date
* Updates complete date
* Final review by clients
* Launch date

I indite these dates based on my knowledge of how long things usually verify (or should take), how long the computer has condemned on past projects, and dates that the computer has provided. If I am concerned about the timing of a project, I module impact with the computer to attain trusty they understand their deliverables and when they are due.

The another thing I attain trusty I allow in the dates section of the lessen is what happens if either band is New with a deliverable. This could be as ultimate as slipping the date, or it could be as harsh as losing some money.