This guide is based on UK law. It was last updated in February 2008.
In addition, the recent profile of issues relating to web site accessibility, the potential risks associated with on-line trading, and the obligations set out under the data protection legislation have caused many web site providers to revisit their web sites with a critical eye.
There are pitfalls to the web development process however, and it would be an ill-advised developer who, having received the client's instructions, starts the development process without first considering (a) the legal aspects of his relationship with the client; and (b) the extent of any obligations he may have as a matter of law.
If a legal agreement is in place with the client before any work is started, both parties will have certainty in relation to the obligations of the other. More importantly from a business continuity perspective are the issues of payment for work and ownership of your intellectual property. This guide sets out in broad terms the areas which should be covered in your agreement with the client.
It is important to clearly identify the services to be provided to each client. This approach means that each client knows what services to expect and you will have certainty in relation to your entitlement to payment.
Where you have agreements with other parties (e.g. with a telecoms company), the terms of such agreements must be taken into account in any agreement with the client. If you rely on a third party for the performance of any of the services being provided to the client, you can only give warranties and undertakings to your client in relation to those services which are consistent with the warranties and undertakings which have been given by that third party to you.
You may be providing consultancy services to your clients before, during and after development of their web site. Clients should be consulted so that a specification is produced for the desired performance of the web site: this is critical if they are seeking your advice on how those requirements will be realised on the web site and at what cost.
It is essential that you do not hold yourself out as an expert in the client's business. Take care with the "pitch" made to the client and the types of statements or representations made by you (or your staff) to prospective clients. From a liability perspective, it is vital not to make promises or statements to the client which are untrue or unfounded.
You need to consider and set out clearly what you will do for the client. Issues to consider include:
If you are providing maintenance services of any kind, the agreement should also set out the extent of the maintenance services to be provided, for example:
Clients want web sites which have some guaranteed functionality. The software and technology you use must be of a type which can support the client's chosen area of operation in a number of technical environments. It is therefore important to get as detailed a brief as possible in relation to the specification for the web site which should include, for example, the client's instructions on functionality, accessibility, use (in particular use by the client of any information collected by them via the web site, which may trigger obligations under the Data Protection Act).
A detailed brief will also enable you to advise the client whether the specification it requests is feasible and/or appropriate, and to ensure that the client's expectations are managed (it will know what it can expect from the web site in terms of technical capability).
The client may have tight time scales in which it wants the web site developed as it may have planned a formal launch, or the "go live" date may be published in advertisements. It is important that these timescales (including any interim timescales) are specified in the agreement. The extent to which any failure to meet these timescales is dealt with should also be specified (for example will any such failure allow the client to terminate its relationship with you or to withhold payment?)
If the client insists that time is of the essence it is important to ensure that the appropriate obligations are placed on the client in terms of the timing and the format in which the content should be provided.
Once you have a basic specification, you can agree an implementation plan with the client for the web development. The implementation plan should clearly specify any deliverables which are the responsibility of the client, and when it must deliver them to allow you to deliver the web site on time. You should also define any acceptance tests to be carried out to determine whether the web site has been developed in accordance with the specification, including details of who will carry out any such tests and when they will take place.
The agreement should also clearly set out the payment terms, the timing of payment, whether payment is conditional upon any "triggers" (for example successful acceptance tests or the provision by you of an invoice containing certain information), whether the fee is exclusive or inclusive of VAT, and whether the client is entitled to withhold any element of the payment (and in what circumstances) are examples of issues which should be considered.
If you are adding content to the web site or hosting the web site, you should be aware of your potential liability for defamation (see OUT-LAW'S guide on Defamation).
Certain defences may be available to you for content which you did not originate.
Protection may also exist for you if you host any content on behalf of third parties. However you should be careful that you do not become liable for any alleged or defamatory content posted by a third party.
You may create a number of things for a client in developing the web site, e.g. development of branding, graphics, databases, the web site itself and associated materials for the client. In the absence of any agreement to the contrary, you will own the intellectual property rights in anything you create for the client. It is therefore important to identify what should belong to the client, in what circumstances and whether your fee will need to be adjusted to reflect this.
Where the client is providing much of the content and graphics for the web site, and particularly where the client is a large corporate organisation, you may find that the justification for your retaining all intellectual property rights connected with the work done by you will be lower.
In any event, if the client is providing the content, make sure the client gives you a warranty that it has obtained all consents required to use/reproduce any content to which third party intellectual property rights relate.
If you want to be able to use the applications developed for a particular client in other projects you must make it clear that all intellectual property rights in the applications belong to you, and offer a royalty free licence to use those applications to the client to facilitate this.
Things can and do go wrong. The agreement should specify what will happen if the relationship terminates before the web site is completed. For example, it should specify whether you will be entitled to payment in relation to any work properly carried out by you prior to termination, and what will happen to any materials generated by you as a consequence of the web site development.
If the web site is in any way interactive, then personal information about site users may be collected. Such information must be obtained lawfully and in accordance with the provisions of the Data Protection Act. If the provisions of the Act are not complied with, the client may be unable to use the information it has collected and may also be subject to enforcement action in relation to its breach – both outcomes which are likely to have a detrimental financial impact on the client and may also generate bad publicity for them (and you).
Although the obligations of the Data Protection Act rest with the client, you need to produce a web site and database which complies with the data protection legislation. This means providing fields which enable certain information to be collected, and including functions in the software which enable the client to carry out its business in accordance with data protection law.
See also: