M-03.1 Process documentation - process maps
M-03.1Process documentation – process maps refers to regulation 5(a). A process map standard is one possible way of documenting a process, procedure or system as required by regulation 5(a).
Procedure
Effective documentation offers opportunities for improving productivity in the workplace. Effective documentation makes information easy to find, use and understand when organised in a logical format.
All process maps will be based upon the (organisation’s name’s) process map template and should contain (but are not limited to) the following items.
1 Heading - left-hand side:
1.1 Process function: Name of the function area relative to the process (ie, building consent authority, Technical or Management)
1.2 Process name: Name of the documented process – this name must remain consistent when used within any related process maps/narratives.
1.3 Process chart/purpose: A description of what the process map is illustrating.
1.4 Key process owner: This is the key role responsible for writing and maintaining this process documentation.
2 Heading - right-hand side:
2.1 Version, Date and Page: Document control features.
2.2 Process Code: All process maps should be allocated a unique number for ease of identification and to facilitate the linking of process maps.
3 Process map content
3.1 All maps should have a key describing the process map symbols and their meanings.
3.2 No employees’ or contractors’ names should be used within the process map. Where a responsibility is identified on the process map, the responsible role should be noted only.
3.3 Process inputs and outputs (interfaces with other processes) should be detailed in the appropriate bands, including their unique process code.
3.4 The differentiation between building consent authority and territorial authority functions should be clearly identified.
3.5 All software system transactions, relative to the process, should be identified within the map.
3.6 All processes external to the document should be documented or referenced.
3.7 Where appropriate, input/output processes and process step narratives will be hyperlinked to their respective locations (electronic versions).
(Example Only)
Example Building Consent Authority Function: Technical [JPG 410 KB, 2854 x 2038]
Back to top