Forms

The e-Builder Forms module helps you manage business processes by streamlining the circulation of documents, drawings, and other required communications. An electronic log is captured of all actions taken on a form, once it has been initiated. Logs are recorded throughout the life of the form, which aids auditing, reporting, and retrieval. Account administrators can create an endless number of forms to mimic processes traditionally routed around the office in paper format. All of the appropriate users are notified instantly via email when a new issue requires their attention or when an item has arrived in their court. With instant notifications, e-Builder reports and increased visibility for the whole team, the entire process becomes more secure and efficient.

Forms are created according to your business processes, and can be manually routed to select users and copied to any of the roles on your projects. Such forms might include RFI's, Accident Reports, and Project Issues. Unlike paper forms, e-Builder's electronic forms allow you to check on the status of a particular issue by simply logging into e-Builder and going to the Project Forms page. Forms provide a complete audit trail/history and can be customized based organizational need.

Types of Forms

There are two form types available in Trimble Unity Construct:

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.