Pre-defined feature size to stamp in Field Map

[JenniferRedstone]

Does anyone know if it is possible to create a workflow that a user could select a pre-defined size for a polygon and place it on a Field Map? Our field crews do a lot of excavation for cultural heritage or contaminated soil and their sampling program is based on a 5 x 2 m or 1 x 1m grid. We can pre-populate the feature service with those polygons to get them started; however often times the excavation expands while the crew is in the field and they need to be able to add more grid boxes. We're looking for a option where they could add a feature, almost like a stamp that automatically snaps to the other boxes in the grid and then they can populate the fields with the necessary details. Normally they would need to add several boxes to the grid to cover the expanded area. This is a fairly repetitive task for our teams across multiple projects so looking for a user-friendly option that allows for consistency among the workers. 

Our field staff predominately use Field Maps, Survey 123 and Experience Builder (office review). 

[Eugene_Adkins]

I know a polygon can be copied in Field Maps (if the published feature has the proper settings) but what I'm not certain of is how the snapping functionality would work in Fields Maps because you don't want to distort the shape or create gaps between the grids, and in Pro to move a polygon with the snapping functionality enabled you must use the control button along with the mouse which may not be possible in Field Maps. Also, I'm not certain about simply copying the polygon in your case because you may need to avoid the duplication of a grid number or some other unique attribute information. Long story short - a polygon can be copied in Field Maps.

Though, to further the story, one workaround you may consider is this:

• Create a field in your polygon data that would distinguish between grids that are known to be involved in the project and grids not involved (i.e. something as simple as "Project Grid?" with a Yes/No domain).
• Create your grids as you normally would and flag the "Project Grid" field as "Yes"
• Create additional grids that extend beyond the known project area and flag the "Project Grid" field as "No"
• When you bring this layer into your map view simply duplicate the layer, and set a filter for the first layer (called Project Grids) that restricts the grids to only show those marked as "Yes" in the "Project Grid" field, and set a filter for the second layer (called Potential Project Grids) to only show those marked as "No" in the Project Grid field ... this will allow for two different layers that can be toggled on/off, and by updating the status from "No" to "Yes" in the "Project Grid" field, the newly designated grid will appear in the desired layer.
• If you want to avoid duplicating layers you can assign a unique values symbology to this feature based on the status of the "Project Grid" field status (i.e. "Yes" could be green in color, and "No" could be red in color). This way, if the project grows beyond the initial area, there are available grids that can be easily identified by its symbology.