Get started with Field

Track inspections, maintain quality, and ensure everything runs smoothly on the construction site.

Key features

Issues helps you capture and track problems you find during site inspections. Each issue has a status telling you what stage it's at, and you can quickly see who it's assigned to.
All issues have a unique issue number and an audit trail so it's easy to see who's done what.
Inspections are used for structured site inspections. Use either checklists or fillable PDFs.
Daily Reports keep track of important site details such as weather, site numbers, and equipment. Sections and entry fields are customizable to meet your site needs.
Punchlists group related issues together so you can capture, manage, share, and track them from one single view. Punchlists use the same permissions as issues. If Punchlists is not enabled for your organization, the Project Admin from the Aconex project-owning organization should raise a service request, requesting it to be enabled.
Keep track of your issues and inspections using reports and export issue lists to Excel to send to others.
Use the mobile app to capture or view information when you're on site.

Initial set up

Step 1: Add Field Project Administrator's

Field Project Administrators configure the areas and issue types that will be used on your project.
They also add users and other organizations that will be working in Field.
Field project ownership is transferrable. This means you can add Field Project Administrators from any organization. They do not have to be from the Aconex project-owning organization.

Step 2: Set up an area hierarchy

The Field Project Administrator must set up an initial area hierarchy before adding users, otherwise no issues can be added.
After the initial hierarchy is set, areas can be added or removed at any time. If an area is deleted, sub-areas under it are also deleted. If an area has already been used (for example an issue was added to it), it can’t be deleted.
Field Project Administrators or Inspector Administrators can configure location detail suggestions. This saves inspectors time capturing issues on site. They are only visible to inspectors within the organization that created them. Each organization maintains its own separate list of location descriptions.

Step 3: Set up issue types and descriptions

Field Project Administrators configure the issue types used on the project. These are used to categorize issues so you can find them later.
Use project fields to capture more details about your issues.
Similar to location detail descriptions, Field Project Administrators or Inspector Administrators can configure issue description suggestions. This saves inspectors time capturing issues on site. They are only visible to inspectors within the organization that created them. Each organization maintains its own separate list of issue descriptions.

Step 4: Create inspection templates

Inspection checklist templates can be created manually or copied from another project.
Grouping your checklists into template categories helps your inspectors find the template they need to use on-site.
A template can be reused multiple times and it can be updated at any time.
Updates to a template will not change the existing checklists that were already created from the template.
You can also create editable PDF form templates.

Once the areas are set up, the Field Project Administrator can add users who'll be working with issues, inspections, and daily reports.
Learn how to add users from your own organization, and other organizations.
Different roles can be assigned to users depending on the work they need to do. See Field user permissions.
When adding other organizations to work with, decide if you want to assign or share issues and inspections with them. Those organizations also need to add your organization to work with them and decide if they want to share or assign issues they create to your organization.

An Inspector captures an issue. The status of the issues will be Open.
The inspector assigns the issue to the user or organization responsible for fixing it. The status of the issues remains Open.
The issue can be reassigned without creating a new issue.
The assignee fixes the issue and changes the status to Work Done. Note: Issues set as Work Done will appear as Ready to Inspect to the inspector who assigned the issue.
The inspector inspects the issue and changes the status to either Closed or In Dispute.

An Inspector starts an inspection from the list of published checklist templates.
Inspections can be assigned or shared with other organizations on your project.
A new inspection has the status of Not started. It changes to In Progress while it's being worked on. The inspector sets it to Closed when finished.
You can close an inspection at any time, even before all items have a response — if, for example, it contains more items than are available for inspection.
You can re-open an inspection that’s been closed if you want to keep working on it. You'll be asked to provide a reason for reopening.