Due: January 15
·         a password-protected back office dashboard
·         a system for adding, editing and deleting information about "towns", including the option to upload one or more images, description and other custom values, such as geolocation
·         a system to add, edit and delete "hotels" (including guest houses, B&Bs and hostels), with the option to upload one or more images, description and other custom values such as email address, telephone number, accreditations (eg. star ratings) and website URL. 
·         a back office pricing system to set hotel booking fees based on number of days and number of walkers
·         hotel listings will have at least two priority levels, with paid listings appearing at the top of the list (where there is more than one priority listing for a town, top positions will be assigned randomly)
·         in addition, hotels will have at least two priority levels, with an expiry date for paid priority listings, after which their customer-facing listing will change its appearance
Due: January 31
·         one-time import all current town, route and hotel data ready for editing (currently stored in a single MS Access file)
·         a system to add, edit and delete "routes" for walking holidays (eg. Coast to Coast), specifying the list of towns and villages along the route with the option to upload one or more images, description and other customer values (eg. season start and end dates)
And a system to assign hotels to routes by "milepost" (for instance, The Old Brewery Guest House is at milepost 116 on the Coast to Coast route and The Albert Hotel is at milepost 1). Note that some hotels might be on multiple routes and therefore will have multiple mileposts. In principle, for SEO purposes, if a hotel is on more than one route it might be helpful to display different descriptions for the same hotel on each route. The current thinking as that hotel data will not include number and type of rooms or tariff, but might optionally include a low/medium/high price rating or advisory

Due: February 15
·         a back office pricing system to set the cost of baggage transfers on a route-by-route basis, with optional exceptions for specific transfers (eg. Great Langdale to Keswick on the Cumbria Way is charged double) and practical limitations such as minimum and maximum bag numbers per person and/or per party. Transfer pricing for each route will either be per-transfer (eg. Coast to Coast) or fixed-price (eg. Sea to Sea Package Deal) with a maximum number of transfers for a fixed-price package
·         Customer accounts - register, log in, edit profile, view future and past itineraries, view payment history (without payment hystory - will be done after payment is ready)
·         the core baggage/accommodation booking system: customers will create and save "itineraries" by selecting hotels, or in some cases private addresses, along a walking route (see document "Luggage Transfer Customer Journey / Luggage and Accommodation pp 4-6" for details). This may include multiple nights at a single location, although the default will be one night.
·         Hotel listings will have minimal data in order to reduce the admin cost of keeping the data up to date, but will include an image slideshow of multiple photos in some cases. There will also be a reCaptcha-protected enquiry form and a stat should be logged for each validated email enquiry. An itinerary will be validated based on logical restrictions, such as maximum distance per transfer, and practical restrictions, such as the season date range (eg. 24 March to 13 October) and direction (ie. to optionally allow walkers to take the reverse Hadrian's Wall route)
·         hotel listings pages need to have SEO-friendly URLs and we will set up 301 redirects from all old URIs to the most relevant new ones

Due:  February 28
·         a simple, template-driven content management system for the marketing and information pages, home page, menus, header and footer, news posts. It could be off-the-shelf, if you have a preference, or completely bespoke, but it will need to be easy to use for non-technical people (example from the current live site: http://www.sherpasvan.com/trails/hadrians-wall.asp)
·         Google Maps integration - for example, for each town/village, we could plot the local hotels on a Google Map and for a customer's itinerary we would show all of the hotels they have chosen on a Google Map

Due:  March 15
·         an ecommerce shopping basket system to display the customer's costs as they are accrued
·         a secure checkout process for customer payments, including email confirmations to customer and back office
·         a back office list of hotels approaching their priority expiry date and a list of recently expired priority hotels
·         a back office system to view and edit completed and incomplete customer itineraries

Due:  March 31
·         a back office table of completed and incomplete itineraries per day with a graph across a specified date range
·         back office dashboard graph of page statistics according to a specified date range
·         a system to log number of visits per page, per route and per town per day
·         a back office stats report of hotels sorted by number of email enquiries logged
·         back office daily email stats report showing number of bookings, top page visits for the day and number of hotel email enquiries