Default Engineering Design Workflow

 

This document outlines the step-by-step workflow used to manage engineering design jobs from initial creation through final client delivery. Each phase includes defined status tracking, role assignments, and decision points to ensure clear communication and accountability across all teams.

Each job in the system is tracked across four key status dimensions, all visible from the job overview page:

  • Job Status — the overall lifecycle stage of the job
  • Data Collection Status — tracks field collection progress
  • Design Status — tracks design and revision progress
  • Review Status — tracks QC and review progress

 

Statuses update as team members take actions in the system. Role assignments (Fielder, Designer, Reviewer) are entered manually and drive substatus transitions within each phase.

Workflows can be created and edited in the Model Editor. The steps outlined here are for the Default Engineering Design workflow.

 

Step 1: Job Creation

A new job is created on the App Overview page and assigned a draft name. This action:

 

  • Initiates the job in the workflow
  • Sets all statuses to Not Started

 

In this stage, jobs can be predesigned ahead of field deployment.

Workflows are configured based on specific models. The active model is displayed in the dropdown at the top right of the App Overview page. 

 

Step 2: Data Collection

On the map page, use the buttons under Job Settings to track attributes and update the job status. "Ready for Data Collection" pushes the Job Status to Data Collection. This allows the user to name the job and then assign the main fielder. Once the fielder is assigned, the job is ready for field collection.

 

These buttons trigger the following:

 

  • Job Status moves to Data
  • Data Collection substatus moves to In Progress

 

Completing Data Collection

Once field work is complete, mark the job as Data Collection Complete from the office. This button triggers the following:

 

  • Data Collection Status moves to Complete
  • Job Status advances to Design

 

Step 3: Design

Assigning a Designer

Assigning a Designer to the job triggers the following:

 

  • Design substatus moves to In Progress

 

Field Recollection (If Needed)

If the Designer identifies missing or insufficient field data, they can trigger a Field Recollection Required status. This status exists to manage subcontractor access permissions — moving to a new status allows the data collection group to regain access to the job.

 

When Field Recollection Required is triggered:

 

  • Job Status moves to Field Recollection Required
  • Data Collection Status updates to reflect recollection in progress
  • Design Status updates to Field Recollection In Progress

 

Once recollection is complete, use the button to complete the Field Recollection status:

 

  • Data Collection Status returns to Complete
  • Design Status updates to Field Recollection Complete
  • The Designer can continue work or trigger another recollection loop if needed

 

Advancing to Review

While in the Design Status, the job should be fully extracted, all make ready designs are complete, and pole loading analysis performed. When the designer is satisfied with the job design, they mark it Ready for Review. Ready for Review triggers the following:

 

  • Job Status moves to QC & Review
  • Design Status is Complete

 

Step 4: QC & Review

Assigning a Reviewer

Assigning a Reviewer to the job triggers the following:

 

  • Review Status moves to In Progress

 

Review Outcomes

The Reviewer has two paths:

Option A: Ready for Delivery

  • Advances the job to the Ready for Delivery phase
  • All three substatuses (Data Collection, Design, Review) display as Complete

 

Option B: Revisions Required

  • Reviewer leaves feedback notes
  • Job returns to Design status with substatus Revisions in Progress
  • Review status displays Design Revisions Required
  • Designer addresses revisions, then marks Revisions Complete
  • Job re-enters the Review phase for re-review
  • The recollection loop is still available at this stage if needed

 

Step 5: Ready for Delivery

The Ready for Delivery phase serves as a final internal checkpoint before the job is handed off to the client. This step is used to:

 

  • Confirm all required exports have been downloaded
  • Verify deliverables are complete and correctly formatted
  • Perform any last-minute quality checks before client handoff

 

Once the internal check is complete, the team marks the job as Delivered to Client.

 

Step 6: Complete

Marking the job as Delivered to Client moves it to Complete status. The job exits the active workflow view, indicating it has reached the end of the process.


Once a job reaches the Completed status it will not display in the App overview page by default. Use the Advanced Filters feature at the top of the App Overview page to toggle on completed jobs.