About Forms

Forms are customizable, electronic input screens used to record specific data elements. Your account administrator can create any number of forms necessary to support your internal business processes. Forms are created according to business processes and may be routed to various team members or roles on your projects. Workflow forms can be routed to a number of different user roles, across organizations, and externally to non-e-Builder users as well. Unlike paper forms, electronic forms in e-Builder allow you to check on the status of forms, including whose court the form might be in, by simply logging into e-Builder and going to the Project Forms page. This enhances communication among team members, as there is little room for error. Due dates, comments, attachments, requests, and field information are all easily accessible by all parties involved in a form's life cycle. Form data and usage information can also be pulled into reports by anyone who has access to the form.

Types of Forms

There are two form types available in e-Builder:

Static Forms (Non-Routable): Static forms are one-way communications to team members, often communicating the procedural information status of specific items. Static forms are mainly for informational purposes. Team members can be notified of static postings using the copy (CC) functionality, but static postings are not routed.

Examples of static forms include:

Daily Log Reports
Accident Reports
Field Observations
Warranty Trackers

Workflow Forms (Routable): Workflow forms are routed communications to team members, used when a specific response is necessary from the recipient(s). For example, Workflow forms are used to send someone an item that requires approval or a written answer to a question. Workflow forms use the ball in court mechanism to indicate who is currently responsible for taking action on an item. When the form is in your court, you can edit the data fields in the form and then send the form on to the next person in the route. The form will then land in the next person's court. When a workflow is initiated, the recipient and all users cc'd receive e-mail notification of the posting and all subsequent activity on the workflow.