Agreeing The Contract And Site Map

Based on the document we prepared in the planning stage, we set out a site map that shows all the pages that will appear on the site when it is first set up and how they will fit into a hierarchy and be linked to each other. By hierarchy, we mean that pages will frequently be in a parent/child relationship with other pages and this matters because the parent pages will appear in the main menu at the top of each page. We don’t want that menu to contain so many items that it confuses the visitor.


Now is the time to prepare a contract that will be signed by both parties – designer and customer. The contract should be as detailed as possible, and should incorporate:

  • The site map and original planning document
  • Whether the customer has already obtained details of FTP host, username, login information and database configuration or whether this is to be done by the designer
  • The price, with payment terms and a detailed account of what is included in the price and what is left out
  • A statement indicating when copyright passes from the designer to the customer
  • A definition of how project completion will be defined
  • A simple timeline
  • Termination clauses

10363854753_0fcefc1d9f_oWhat is included and what is not

When we were defining exactly what would be in the website, some items are likely to have been available only by payment. For example, there may be:

  • Images in which someone else has copyright
  • Features to be installed on the website that are proprietary and for which a developer must be paid. The list of such features would be long but examples are:
  • product carousels
  • sliders
  • Mailchimp or other mailing list software
  • paid analytics
  • e-commerce facilities

The cost of these will have been included in the contract price and the designer will now set about obtaining them.