A document process template answers what gets written down about a process, as distinct from the procedures beneath it. The process document holds the trigger, the end state, the roles, the sequence of tasks with the hand-offs between roles, where the controls sit, what records the process leaves and which procedure each task points to. It is a page or two and it changes rarely. The process documentation template on this site sizes it from the task count, roles and hand-offs, and prints the reading time and the number of hand-offs.
The boundary and the roles
The trigger and the end state as a sentence each, then the roles as positions. The process from order paid to tracking sent, across sales admin, picker and packer. This is the paragraph an auditor or a new manager reads to know what the process is before reading how it is done.
The task sequence and the hand-offs
The tasks in order, each named, with the role that does it and the hand-off marked wherever the next task belongs to a different role: what is passed, how, and what tells the receiver it arrived. No numbered steps here; each task has its own procedure. The template counts the hand-offs, which is the first measure of where the process will stall.
Controls and records
Where in the sequence a check happens, who does it and what it prevents: the address validation before the label, the reconciliation before the close. Then the records the process leaves and where they are kept. This is the section a customer or regulator reads, and it is a list rather than prose.
The pointers to the procedures
Each task names the procedure that holds its steps, by name and version. The process document does not repeat the steps; when a form changes, the procedure is revised and the process document is not. RunbookDesk Pro keeps the process and its procedures linked with separate version histories.
Questions people ask about document process template
How long should a process document be?
A page or two. If it is longer, it has started listing steps that belong in the procedures.
Do I need a diagram?
A swimlane helps when the hand-offs are many; it is a view of the task sequence and carries the same task names.
Is the template free?
Yes: the process documentation template sizes the document and counts the hand-offs without an account.