Clear, concise, and consistent filenames improve process documentation. I’ve adopted the following convention for naming process files:
The structure of a filename
- Organization—The name of the business or organization. If the name is long (e.g., Human Scale Business), use initials (e.g., HSB).
- Process Name—Nominalize the verb describing the process’s main action. For example, “Invoice client” (the main action) becomes “Client Invoicing” (the process name or label). Click here for more.
- Version—Significant versions are numbered sequentially: 1.0, 2.0, 3.0, etc. Revisions are numbered sequentially: 1.1, 1.2, 1.3, etc. The first draft of a process should have the version number 0.1.
- Extension—The extension indicates the format (e.g., .bpmn indicates a BPMN XML 2.0 file format).
