The scale and specification of some sites often call for a prototype to be created to get a feel for how the site will look and navigate. This is an advantage when the full requirements for the new application are unknown and several avenues need to be explored before committing to a design and application.

There needs to be an objective and budget that needs to be adhered to. The hard part of any prototype is seeing the potential 'haves' but not having the budget to do it. Realistic targets and objectives need to be detailed first so the requirements are agreed to. The prototype should be used purely to ensure the application reaches its objective rather so the importance of the requirements stage is still crucial.

Once the prototype is created it can be reviewed and modules added or amended. This can be for something as simple as a registration process - creating the form, the acknowledgement and the authorisation - so all can see and feel how it will look and change anything before detail is captured. Or it could be for a very large site where there is extensive information and need it all to map together and work in synergy.