What were the challenges?
- Searching for a piece of information from Request for Inspections is near to impossible or extremely time consuming due to its paper based processes
- Difficult to keep track of ongoing activities for Request for Inspections, especially of those that failed the inspection
- High effort and workload to compile data into an Excel in order to generate a monthly statistical report
Before Implementing SnagR
The inspection team submits up to hundreds of Request of Inspection by paper to the developer each day. The submissions are made physically on site. Each submission has 4 copies, so relevant parties keep one for their reference at each workflow stage.
How did SnagR help?
- Digitalise Request for Inspections submissions
- Automate reporting to summarise submission statuses by location, trade and sub trade
- Enable search for Request for Inspections by keyword text in the form, submission date, location, etc.
After Implementing SnagR
The Request for Inspection form is digitalised on SnagR. Engineers can submit the form via website or app based on their preference. Their existing workflow is mirrored in SnagR by using custom workflow.
Collaboration takes place, and multiple parties are involved in the process. Teams are configured with a permission set to protect data integrity.
Here are some examples of automated reporting:
What is required to set this up?
- Request for Inspection form in PDF, png or jpeg
- List of users and contractors who will have to submit the form
- List of current workflow stages and mappings to permission sets for teams or users
- List of locations that require Request for Inspections submissions
- Existing statistical reports (if any)
Note
Here are the main features used in SnagR: