Lots of field work => lots of field forms

Brownfields redevelopment projects require a lot of environmental field work.  A lot.  In some cases, a project may require weekly visits during the entire construction timeline.  Sometimes daily visits.  And when a Brownfields redevelopment project lasts 18-24 months, that’s a lot of routine site visits.  Which equates to a boatload of field forms.  Unless you have a good process in place, managing boatloads of hand-written field forms on a regular basis for a Brownfields project will become unwieldy quickly.

Just imagine if these were paper forms, collected daily for a period of 12 months.  That’s at least 20 field forms per month x 12 months = 240 paper forms that will need to be scanned to email, extracted from email, and then uploaded to a cloud storage site.  Have you thought of the file naming convention for these forms?  What if its not consistent?  Hell, it’s NEVER going to be consistent if humans touch it.  Or put there on a timely basis.

And what about photos?  If you take just 3 photos per day, that’s 720 photos.  How are those being managed?  Is someone dumping all these images to their laptop, and then transferring them to a Dropbox folder?  How will you know which photo was taken when?  Are you renaming each photo, so that unintelligent image file names like img_9214.jpg are renamed to something like 2022-08-24_AOC_Inspection_John_Smith.jpg?  What if multiple people are involved?  How will that impact any semblance of consistency in file naming?

Two examples of routine Brownfields redevelopment field work

For purposes of this article, we are going to assume that the environmental investigation phase has been completed, areas of concern have been delineated, the regulators are satisfied with the proposed action plan, and we are stepping into the construction phase.

From my experience, two types of routine field work are common at this stage of a Brownfields project: Area of Concern Inspections and Vapor Intrusion Mitigation System (VIMS) Inspections.

1. Area of Concern (AOC) Inspections

 Scenario: An area of elevated metals contamination was discovered in shallow subsurface soils during the investigation phase.  This area was delineated, and the proposed plan is to monitor construction activities to ensure this AOC is not disturbed during the heavy equipment construction phase.

While each AOC is unique in its own way, and may require specific things to check for that may not apply to another AOC, it’s best to try to “genericize” these as much as possible.  Using table grids in your field forms helps with this.  The example below is from Mid-Atlantic’s version of an AOC inspection form template running on a phone.

 

And here’s the output format of this AOC inspection form illustrating a completed/submitted form.

2. Vapor Intrusion Mitigation System (VIMS) Inspections

 Scenario: An area of volatile organic compound (VOC) vapors in shallow subsurface soils was identified at the location of a proposed building footprint. An active VIMS is being installed, which will consist of vapor barriers and sub-slab depressurization via a blower connected to a suction pit dug into the slab in order to vent vapors outdoors.

Like the AOC Inspection form, you can create a fairly generic VIMS Inspection form, and use table grids to handle most systems you will encounter.

Here’s what the Mid-Atlantic VIMS Inspection form template looks like on a phone.  You can see how you could add rows to the checklist table to handle most of your particulars.  Just remember to keep your forms simple.  In the case of field forms, a “less is more” approach is the best course of action, as your field folks are busy already and don’t need to spend gobs of valuable field time filling out forms.  The idea is to get them in and out of your form as quickly as possible.

 

Here’s an example of a submitted VIMS Inspection form.

 

Lots of integration possibilities!

Once you start using a digital system like XForms to collect field data digitally, there are all sorts of ways to leverage that data and optimize your workflows.  Examples:

  • Auto-send submitted forms via email to your Project Manager, with the form PDF attached
  • Auto-upload form PDF to a Slack or MS Teams channel
  • Auto-upload form PDF to a cloud storage (OneDrive, Dropbox, Box, Sharefile, etc)
  • Auto-upload photographs captured in XForms to specific folders in could storage of Teams/Slack channel
  • Auto extract form data and insert into PowerBI, MS Access, AirTable, Smartsheet, Clickup, etc
  • Auto extract geolocation and timestamp metadata from submitted forms and insert into ArcGIS or other online mapping tool

Two examples:

1. Auto-upload PDF to OneDrive

Here’s a visual example of an integration from XForms to OneDrive/Sharepoint.  Whenever a user submits a Brownfields form (or any form) into the system, an integration picks up the auto-generated PDF and inserts it into the appropriate project folder on OneDrive, which is mapped to Sharepoint.  In the animated gif below, notice that the filenames all follow a consistent pattern, something that would be near impossible if humans did this.

 

2. Auto-upload photographs to specific folders in OneDrive

Another, albeit similar, example.  An integration extracts all photos taken with XForms, and inserts them into a specific “Photos” folder inside the project folder.  This is something useful for long-term Brownfields redevelopment projects, as you can easily see the site’s progress and changes over time fairly readily.  Also notice that the image filenames have consistent names that can be used for sorting and for finding specific ones easier.

 

Wanna improve your Brownfields redevelopment field work data collection?

Click/tap the button below