Create a scope statement

The first thing you need to include in your documentation about any process is a scope statement. Scope statements should be clear, yet as all-encompassing as possible. For example, if you have 48 sales processes, there is not necessarily a need to create 48 sets of process documentation.

Presumably, most, if not all, the sales processes will fall into just a few categories such as manage leads and opportunities, design solution steps, deliver the solutions, and deliver the services. All of these can be included in one a process library and be embedded in Process Master’s as needed.

That library, then, would have a scope statement such as "This guide will cover the following processes:" with a simple file structure to contain them all in the order needed. We recommend that you have a look at this video which will enable you to do this without needing to make any major financial or time investments