81.3.1 Make a list of the types of jobs (maps to Latitude Job Types) your business has.
NOTE:
You may also need to include sub-types of "Job Types" (maps to Latitude Task Type)
Break each "Job Type" down into small isolated single work processes
Each single work process should be a finite, repetitive procedure with a specific beginning, middle and end.
These become the Steps of your workflow.
Break each "Step" down into as many discrete activities as possible, the more granular, the better.
These activities are actions your employees need to do to complete the step.
These would become the Actions of your workflow.
NOTE:
Action granularity on a particular step works best when each action is assigned to a different person performing different roles. When these 'actions' start to become too detailed and are only assign to one role, it may be best to just create a single action and use register item notifications to run them. "Follow-ups" are one example you don't need actions for. It may be best to just create a register item notification to remind an employee (or group of employees with the same role) to follow-up something at a later date, see "How do I handle Reminders and Notifications" -> "Register Item Notifications".
81.3.2 Workflow Example
A "Survey" job type may have the following workflow:
Step 1 - Job Set Up
Action 1.1 - Determine completion date
Action 1.2 - Compile project information
Step 2 - Field Operations
Action 2.1 - Schedule crews
Action 2.2 - Log field work
Action 2.3 - Approve field work
Step 3 - Drafting
Action 3.1 - Compile and process project data
Action 3.2 - Complete drafting plans
Action 3.3 - Validate plans
Action 3.4 - Deliver documents and register plans
Step 4 - Invoice
Action 4.1 - Send invoice
Action 4.2 - Get paid
Action 4.3 - Close job