Field Observation Business Process
Use the Field Observation business process to record observations at a site, including quality, safety, and general observations. This business process is typically used by an architect or engineer.
Characteristics
This is a Project-level business process with a workflow, provided in the system template.
Record Statuses
Canceled | terminal status |
|---|---|
Closed | terminal status |
Rejected | terminal status |
Awaiting_Review | non-terminal status |
Pending_Approval | non-terminal status |
Sent_for_Revision | non-terminal status |
Workflow
The default workflow for the Field Observation business process is set up in a certain way; however, it may be used differently by your organization. Typically, a user with the necessary permissions can create the record and either move it directly to the end step or send it to others for review or approval. The recipients in the second step can approve or reject the record or send it on to others.
Creating a Field Observations Record
Create a Field Observation record by navigating to Field Management / Field Observation on the Project/Shell tab, or from the Tasks log on the Home tab or relevant Project/Shell tab. Act on an existing Field Observation task that has been assigned to you from the Tasks log.
Complete the Field Observation form and attach related documents, if needed. After completing the form, click Send and select an action in the Workflow Actions list to determine the next step in the workflow. Click Send to route the form to the next assignee.
Note: You must enter a value in all required fields (*) before you can save the form.
- Go to your Project tab and switch to User mode.
- In the left Navigator, select Field Management, and then select Field Observation.
- On the Field Observation page, click Create. Refer to the tables below to complete the form. You can click Save at any time to save a draft version of the form. Draft versions are stored under Drafts.
- To add attachments, click Attach Files
on the Attachments tab. - After completing the form, click Send.
- On the Workflow Action Details tab, select who should receive this Field Observation.
- If permitted, you can add users to the CC list. These users will receive a notification about this Field Observation but are not assigned a task.
- If permitted, you can adjust task due dates for all users, or set individual task due dates for each assignee.
- Click Send.
- In the Notification window, review the content and click OK.
The record moves to the next step in the workflow.
Completing the Field Observation Form
Key Information
Key information about these field observations is provided below.
Field Name | Access | Description |
|---|---|---|
Title | Required | Enter a title. |
Observation Date | Editable | The date of the observation |
Observation Type | Editable | The type of the observation being recorded |
Target Completion Date | Editable | The targeted completion date for the action item. To be updated as needed, particularly when reassigning the Action Item. |
Area | Editable | The specific area for the Incident item |
Location/Equipment | Editable | Location or equipment of this observation |
Description
Scope description and anything else needed for describing this field observation
Field Name | Access | Description |
|---|---|---|
Short Description | Editable | Enter a description of 250 characters or fewer. This short description might be used in logs, dashboards, and reports. |
Detailed Description | Editable | The detailed information about the short-description field. The field size can be expanded. |
Resolution | Editable | Add additional information about how the noted observation is managed and resolved. |
Location
Location of the Field Observation. This can be completed by selecting an Area, by adding your current location (on mobile), or by choosing an area on a map.
Field Name | Access | Description |
|---|---|---|
Latitude | Editable | The latitude of an area |
Longitude | Editable | The longitude of an area |
Record Information
Field Name | Access | Description |
|---|---|---|
Record Number | Read-Only | System-assigned record number |
Creator | Read-Only | Creator of this record |
Creation Date | Read-Only | Date that the record was created |
Status | Read-Only | Record status for a workflow BP record is based on the workflow action preceding the current workflow step. |
Record Last Update Date | Read-Only | Date that the record was last updated |
Business Process Record URL | Read-Only | A shareable link to this record, for anyone with the necessary permissions |
Project Name | Read-Only | Name of the project |
Project Number | Read-Only | Unique Project Number |
Additional Information
The Field Observation Additional Information block is reserved for future use by your organization.
Field Name | Access | Description |
|---|---|---|
Field Observations Date Picker UDF 1 | Disabled | Reserved for future use by your organization |
Field Observations Date Picker UDF 2 | Disabled | Reserved for future use by your organization |
Field Observations Decimal UDF 1 | Disabled | Reserved for future use by your organization |
Field Observations Decimal UDF 2 | Disabled | Reserved for future use by your organization |
Field Observations Date Only Picker UDF 1 | Disabled | Reserved for future use by your organization |
Field Observations Date Only Picker UDF 2 | Disabled | Reserved for future use by your organization |
Field Observations Picker UDF 1 | Disabled | Reserved for future use by your organization |
Field Observations Picker UDF 2 | Disabled | Reserved for future use by your organization |
Additional Notes
The Additional Notes block is reserved for future use by your organization.
Field Name | Access | Description |
|---|---|---|
Field Observations Text 255 UDF 1 | Disabled | Reserved for future use by your organization |
Field Observations Text 255 UDF 2 | Disabled | Reserved for future use by your organization |
Field Observations Text 255 UDF 3 | Disabled | Reserved for future use by your organization |
Field Observations Text 255 UDF 4 | Disabled | Reserved for future use by your organization |
Field Observations Long TEXT UDF 1 | Disabled | Reserved for future use by your organization |
Field Observations Long TEXT UDF 2 | Disabled | Reserved for future use by your organization |
Last Published Monday, April 14, 2025