Following a successful feasibility study at stage 2, we now move into a detailed User Specification. It contains two detailed planning documents plus a process flow diagram, a simple (14 steps) procedure, glossaries, etc. This document (the user specification) is the key project document that will detail all user requirements, both in operational and functional terms, action plans, timelines, budget for resources and set the standards for the rest of the project. Small projects with limited resources and fast-tracking projects (that is, those not required to perform a feasibility study) begin with this document. International IT planning document. (F-1009)

Following an approved user specification at stage 3, the next step is the preparation of a detailed System Specification, that will be approved by the board as the basis for all system development to follow. After this is finalised and approved, all changes to the plan must be represented by a change request and costed, approved and recorded in the amendment record in stage 5. We have also given real definition to the implementation plan and the procurement plan which become the key documents for project reporting in the stages to follow. We have also included a process flow diagram, a simple (16 steps) procedure, glossaries, etc. International IT planning document. (F-1010)

A separate plan document for an implementation plan which is drawn up after all the other documents in the system specification have been finalised, based on stage 4 of BS5515 (1984). It contains a detailed planning document including a broad account of system architecture, key components in the deliverable, a list of tasks, project temporal analysis, resource requirements, risk analysis, budgets, sign-offs and development requests. This is just a separate format for documents also contained in the full white paper F-1010. International IT planning document. (F-1019)

This code of ethics for a Help Desk links in directly in with the Service Level Agreement for the IT industry. This is a more technical look at ethics because it has to properly describe the risks involved, and to discuss four levels of response under the Service Level Agreement, in order to understand the ethics involved in the Help Desk. It explains the technical reasons why these ethical considerations are unavoidable and therefore why many help desks are operating unethically in today's climate. It translates the ethical statement into practical objectives. International corporate policy. (C-5006)

Two simple models for forming an Agency Agreement between an IT supply & support company and a sales agency; the "Shop Front Model" and the "Scouter's Model". (F-0003)

The first step in building a team is to put some structure into the commitment to quality. Here Dr. Mark builds a detailed mission statement that has something for every member of the team, for each group in the team and for the team over all. Dr. Mark says: "I'm not suggesting you use mine; it's offered to get you thinking along those lines". International planning profile. (F-4000)