• To promote standardization and reduce manual entry time across projects, admins can create Quality Form Templates in their Autodesk Build-configured Project Template. Any project created from that project template will then have pre-configured form templates available.
• In “Project List”, admins navigate to “Project Templates” and create or choose a project template.
• Within the Build Configuration, they will select “Forms” and click “Create”, then “Create Template”; see the “Creating Form Templates” section below for details. Form Templates in Project Templates has a few differentiations noted below:
• If building a new form:
  • From the contribution mode menu, only “Single Contributor” is selectable.
  • To finalize, permissions are restricted to roles for contributors and reviewers.
• If starting from a PDF:
  • To finalize, permissions are restricted to roles for contributors and reviewers.
• Forms can be modified in the Template List and organized into folders.
• Forms can also be imported from other company Build projects or previous tools by clicking “Import”. To import from another project that was built out, an admin selects “Autodesk Build”, then selects the project and up to 50 Form Templates.

• Creating Form Templates is an essential step to standardizing data collection and accelerating quality checklist entry. Setting up a template within a project is similar to setting up for Form Templates within a Project Template.
• In a Project, admins will navigate to the Forms tool, select “Templates”, and click “Create”.
• Next, they either upload an editable PDF or build a new form.
• If building a new form:
  • Admins begin with either a pre-formatted template or a blank one. In both cases, they will then specify the template title, type, and a description of the form.
  • Forms are split into sections that contain items for response including Equipment Materials, Notes, Weather, Work Log, Signature, or Questions. Each section and item (aside from Notes and Weather) has space to provide a description to give project teams additional context when they fill out the form.
  • Questions:
    • Each section can have multiple questions that can be added, deleted, and moved up or down by using the icons in the bottom right of the question box.
    • On the bottom left, users can make questions required or have conditional logic to require or suggest a photo or an issue.
    • The question type can be adjusted by selecting from the dropdown options on the right.
  • Pre-formatted templates:
    • Sections are pre-loaded based on selections
    • These sections can be modified as needed.
    • New sections can be added by selecting “New section” on the black “Add section” menu.
  • Blank templates:
    • To add a new section, admins click the black toolbar on the right and select the type from “Add section”.
    • Adding items like questions or signatures is located on the black toolbar in “Add item to section”.
  • Once finished, admin will click “Save”.
  • They then can select how contributors will work:
    • Single contributor – One contributor creates and submits each report.
    • Multiple contributors in sequence – One contributor at a time can edit a report. They have the flexibility to assign a report to another contributor.
    • Multiple contributors in parallel –Multiple contributors can edit a report at the same time. Any of them can submit.
  • To finalize the form, the permissions for the contributors and reviewers for roles, companies, or individual members are assigned. The manager is automatically assigned as the form creator, and roles or members can be added.
  • The admin then clicks “Create” to add the form to the Form Templates list.
• If starting from a PDF:
  • Starting from a PDF gives teams the opportunity to directly import existing quality observation and checklist forms they currently use.
  • The template name, type, and form components (like weather and notes) are specified. Then admins will select single contributor as the default.
  • Next, roles, members, or companies are selected as contributors and reviewers.
  • Clicking “Create” will add the form to the Form Templates list.
• Forms can be modified in the Template List and organized into folders.

• Teams can fill out forms on both the web and mobile. Foremen, Superintendents, or others in a similar role, performing a Quality Checklist walkthrough start by navigating to the Forms tab and clicking “Create Form”. Within the drop down, they can search and select one of the quality checklist forms.
• The form will load the templated information and sections. The observer then fills in the form details and provide responses to sections. Required questions are marked with a red asterisk (and the word “Required” on mobile)
• They can create an issue, attach a photo, or write a note on the spot. References can also be added by linking photos, files, issues, assets, or other forms.
• If a form is set up for multiple contributors editing in sequence, users can click on “Assignee” and select who they would like to reassign the draft form to.
• To collaborate on forms with stakeholders, members can hover and click the “Chat Icon” to add comments and “@” mention a specific person to draw their attention an item in need of response.

Editing Forms

• A quality engineer or manager can quickly find specific drafts or submitted forms by leveraging the sorting and filtering options within the Forms tab. Drafts and assigned forms can be edited; submitted forms cannot.
• The column headers can be clicked to sort the Forms list based on name, date, ID, status, creator, and last update.
• Under the funnel icon, forms can be filtered by date, creator, status, location, and template type.
• Additionally, forms can be searched through the search bar at the top.

Issues have several fields that quickly resolve problems that may arise during projects. These details can be standardized, reported on, and used to identify trends. Analyzing these trends helps teams create plans to address issues before they occur.

• Title: Titles ensure all stakeholders quickly understand the issue.
• Status: Status has four states to designate resolution progress: Open, Pending, In Review, and Closed.
• Type: Types organize issues. An issue type creates a label for identifying issues under important information like specialty trades. Each type is arranged under an organization category, like quality or safety. In set-up, Admins can also for quick identification when using pushpins in sheets or assets, identifying status (active or inactive), and selecting from created custom fields.
• Description: Provides space for any necessary context or information about the issue.
• Assigned to: Issue creators can use “Assigned to” to designate a responder for any issue created. This will send a notification for response to an individual member, a role like Quality Manager,
• Watchers: Designating individuals as watchers lets issue creators alert stakeholders without the expectation for them to help resolve the issue.
• Location: A drop-down that brings up the locations available within the project allowing issue creators to detail where an issue occurred.
• Location details: A free text field that helps provide additional context to the location selected. For example, a mechanical room on the second floor location can be selected with “behind the AHU unit” for further details on a drywall damage issue.
• Due date: Due date designates the resolution date expected by the issue creator.
• Start date: Used to identify when the issue in question began.
• Placement: Issues can be directly placed, or removed, on a model, file, or sheet from issue creation in the Issues log.
• Root cause: Root causes identify why an issue occurred by creating a label to identify the underlying cause. Each root cause is organized under a root cause category, like quality or safety. . Reports and dashboards are able to filter by root cause, providing key stakeholders with actionable information on how to prevent issues in the future.

• Within a Project Template, admins can create Issue categories and types, custom fields, and root causes with default information prefilled for all projects.
• Any project created from that project template will have these fields pre-populated. This standardizes data for teams and saves time-on-site when filling out identifying issues in the field.
• In “Project List”, admins navigate to “Project Templates” and create or choose a project template.
• Within the Build they will select the “Issues” tool, then click “Create” within the “Types”, “Custom fields”, or “Root causes” tabs.

• After a project is set up, admins can further customize issues within the Issues tool, under the “Settings” menu.
• Project Admins can create and customize issue categories and types, add custom fields, root causes, and create templates.
• In each tab within “Settings”, admins can keep projects up to date and organized by selecting a type, custom field, root cause, or template and edit or manage the information on the right-side menu.

PRO TIP: Issue categories and types can be edited to show, hide, and reorder fields. Select an issue type and in the “Edit type” menu on the right, select the “Manage fields” tab. There, use the visibility icons to designate if the field is shown or hidden and use the move icon to reorder the position of the field.

• When an issue is assigned to a project member, they receive an email notification. To see the details of the issue, the assigned project member follows the link in the notification email. Alternatively, any project member can access issues from the Issues tool within Autodesk Build. And if the issue is referenced on another tool—for instance, on a form—they’ll be able to check its details from that tool, as well.
• Assigned issues are also visible in the “Your assigned work” under the “Work status” section of the Autodesk Build home page.
• When an issue is created, its automatic status is “Open”. As the issue is being addressed, assignees select the issue and update the status to “Pending” or “In review”. Once the problem is resolved, the issue status should be changed to “Closed”.

PRO TIP: Web and mobile users can ‘@’ to mention a specific user—or a company, or a role—in the comment field of issues. This will notify the user by email and draw their attention to the specific issue.

• Both web and mobile users can quickly find the issues they are looking for by leveraging the sorting and filtering options under the Issues tool.
• The issue list can be sorted based on title, ID, status, and due date. On web, users can just click on the column header to sort by that attribute. On mobile, sorting options show up after tapping on the funnel icon.
• Under the funnel icon, several filtering options are available, including filtering by assignee, due date, status, root cause, creator, etc.
• By clicking the gear icon, teams can search and check or uncheck details to hide, reorder, or freeze columns in the issues log providing only the necessary details.

PRO TIP: The quickest way for mobile users to check the issues assigned to them is to scroll down in Home to “Your assigned work” under “Work status”, where they can see right away the issues assigned to them.

• Team members like Safety or Quality Managers can use the Reports tool to add additional detail to reports, or schedule reports on open issues to follow-up with specialty contractors on.
• The Reports tool can create these reports and an additional “Issue summary status” report with more options and customizations.
• A manager can navigate to the Reports tool and click “Create report” in the “Reports log” tab:
  • Issue detail: A PDF report with filters by standard and custom fields and sort by Status, Title, Description, Start date, Due date, Location, Location details, or Created on. Next, they select options of a Cover page, Table of contents, Sheet overview, Custom fields, Comments, and Photos.
  • Issue status summary: A grouped-by-company PDF report with optional cover page and filters by issue type and sort “Unresolved”, “Company”, or “Overdue”.
  • Issue summary: Exported in both PDF and Excel and be grouped by Location, Company, or Category. Available filters: standard and custom fields and sort by Status, Title, Description, Start date, Due date, Location, Location details, Updated on, or Created on. Selectable options include a Cover Page and Table of Contents.
• Clicking “Run report” will give these managers the option to run this report once or to save it as a report template to run in the future.

If saved as a report template, managers can “Schedule report” in report’s three-dot menu in the “Templates” tab. Once  saved, Safety or Quality Managers can directly download to their device, email, or share with stakeholders via a link on a regular basis.

• Teams can create tags to provide more information about the images they upload to Autodesk Build. Tags can be used to help easily document project work, enabling teams to track the type of work and equipment, jobsite location, and even the subcontractor.
• Once uploaded, photos are automatically tagged through the “Autotags” feature, which utilizes machine learning to apply categories and tags (like MEP Systems, Ductwork Conduit or Openings, Door, Window) to photos. These are displayed in the “Autotags” section in photo details below “Tags”.
• Tagging is flexible: Users can manually add multiple tags to a photo, either when uploading it or afterwards. After selecting a photo, simply click on the “Tags” button to see already associated tags or add new ones. Autotags together with manual tags can make organizing and finding photos easy, powerful, and customizable.

PRO TIP: Set up photo tags at the beginning of the project, so that all uploaded photos can be tagged in the same manner. This makes it easier for team members to find specific images.

• To configure permissions and to set the workflow roles for project members, click “Permissions”.
• For RFIs, default workflow roles are based on roles within the project. Use the drop-downs to edit the permissions.
• To assign a specific user, role or company, and new workflow role, use the drop-downs at the top of the screen and select “Add”.

RFI Permissions

• Setting up RFI types allows project managers to configure their RFI workflows by creating different RFI types in one project. To configure the RFI workflow, click “RFI types” then “Create RFI type”.
• There are two options: the default workflow with one reviewer, and the second workflow with one reviewer and one coordinator.
• Set the default reviewer and coordinator for each RFI type.

PRO TIP: The flexibility to customize workflows at an RFI level is useful for projects that require different RFI types for different stakeholders. Project managers can specify the default reviewer and coordinator for each of the RFI Types. For example, a project manager can create an RFI type related to electrical contractors where the preset coordinator and reviewer will then be affiliated with electrical trades.

RFI Workflow Setup

• Project Admins can now configure custom fields to be added as additional information to each RFI. Custom fields support custom numeric, textual values, and single/multi select list of values. To create custom RFI Fields, click “Custom fields”.
• Select “Create custom field”
• Input the Custom field title, select the custom field type from the drop-down menu and provide a description for the field.

Custom RFI Fields

• After selecting which item type to reference, an “Add reference” window will appear. Use the search field to quickly find the item to reference.
• Select the item and click “Add” to connect it to the RFI.
• For Photos and PCOs, this process creates a bidirectional relationship. This means in the referenced item, the linked RFI is visible.

PRO TIP: Users can upload photos directly to the RFI. Once the RFI has been created, users can also upload files directly to the RFI.

RFI Fields and Entries

• To create and link a new RFI, select “Create new” and fill in the critical information before selecting “Create RFI”.
• An RFI is then created and automatically linked to the markup. This creates a bidirectional relationship between the two. Users will be able to jump to the markup when looking at the RFI item.

PRO TIP: After linking an RFI to a Markup, use the Text tool to add the RFI number within the Markup. This makes it easy to see which RFI applies to which Markup.

Create an RFI on mobile

• RFI Creators and Managers on Android and iOS can create RFIs from their mobile device.
• To go to the RFI tool on mobile, users click on the “More” icon at the bottom on the right.
• To create an RFI, press “Create RFI”, and add necessary information before pressing “Create”.
• Note: 
  • Only Photos and Videos can be added when creating an RFI on mobile.

• • Other Project references can be added on mobile after the RFI is created, except for Schedule references.
  • Schedule references added in via web are viewed only on web.

RFI Numbering

Creating an RFI from an Issue:

• Open an Issue record. Within the “Details” tab, scroll to linked references and select “Add reference” then “RFI”. 
• A linked RFI box will appear. Select the “Create new” button. 
• When prompted, add in all RFI details, and click “Create” when done. This information will copy over from the RFI but can be altered directly in the RFI record.
• All issue information is automatically copied to the RFI, including references and markups.
• Once the RFI is created, a bi-directional relationship between the RFI and Issue is established. Activity is captured in the Issue activity log.

Linking RFIs to Issues: 

• To link RFIs to Issues, follow the same steps as above. However, when the link RFI box appears, select the RFI(s) from the list and click “Add”. 
• To unlink an RFI, select the “X” and “Unlink”. 

Accessing Linked RFIs: 

• From the Issue record, only Admins and RFI Managers can access/view the linked RFI details.  
• From the RFI record, only users with the following Issue permission levels can access/view the linked Issue details:
  • View All
  • View and Create
  • Full Control

Creating a PCO from an RFI: 

• In the Project Management module, open the RFI record. Within the Details tab, scroll to linked references and select “Add reference”.
• A linked PCO box will appear. Select the “Create new” button.
• A form will open. Fill in the PCO name and description, then select “Create PCO”. This information will copy over from the RFI to the PCO, but it can be altered directly in the PCO record.
• Once the PCO is created, a bi-directional relationship between the RFI and PCO is established, and the activity is captured in the RFI activity log.

Linking RFIs to PCOs: 

• To link an RFI to a PCO, follow the same steps as above. However, when the linked PCO box appears, select the PCO from the list and click “Add”.
• To unlink a PCO, select the “X” and “Unlink”.

Accessing Linked RFIs and PCOs from the list views: 

• Only Admins and RFI Managers can view linked PCOs.
• Within the RFI list view in the linked references column, select the PCO number to open the PCO in Cost.
• In the Cost Management Module within the PCO details flyout panel, select the RFI to be directed to the RFI to the RFI in Build.

Web

• To edit an RFI, click to open an RFI, and use the pencil icon to edit any necessary fields.
• Editable fields have a pencil icon. Click the icon to edit. Admins can edit additional fields in a closed RFI and add references.

Mobile

• In the Autodesk Construction Cloud mobile app, tap “More” on the bottom right, then “RFI”.
• From the RFI list, tap the desired RFI to open the RFI details.
• All fields, except the RFI ID and Type, are editable including the Title, Ball-in-Court, Due Date, Question, Suggested Answer, etc.

• Once the RFI is ready, select “Submit to reviewer” or “Submit to coordinator”.
• If the RFI type with only a reviewer is selected, the manager can then customize the RFI number, assign the Reviewer and Co-Reviewers, and select the due date.
• If the RFI type with a Coordinator is selected, the manager can then customize the RFI number, assign the Coordinator and Co-Reviewers, and select the due date. Coordinator assigns the Reviewer if needed.
• Co-reviewers can contribute information to the response through comments but cannot add an official response.
• Coordinator and Reviewer are both able to add official response.
• The RFI status will update to Open.  

PRO TIP: Project Admins have permission to add a response to an RFI on behalf of a Reviewer or a Coordinator. In the activity log, the action will reflect that the admin “acted on behalf” of the assigned Reviewer.

Mobile

• In the Mobile app, tap “More” on the bottom right then “RFI”.
• From the RFI list, tap the desired RFI to open the RFI details.
• Select “Submit to reviewer”.
• Similar to web, select the Reviewer or Coordinator, co-reviewers, Due Date, and Watchers.
• The RFI status will update to Open.

• The Reviewer and the Coordinator can attach supporting documents within the Reference section of the RFI. To add a local file, select “Add References”, then “Files”. Users access documents within Autodesk Build or select “Upload new” and drag and drop local files.
• If the RFI type with a Coordinator is selected, when ready, Coordinator either selects “Submit official response” or select “Forward to Reviewer” to assign and forward RFI to a Reviewer. Use the status drop-down menu to select “Answered”. Add the official response, then click “Done”.
• If the RFI type with just a Reviewer is selected, when ready, select “Submit official response”. Use the status drop-down menu to select “Answered”. Add the official response, then click “Submit”.
• If there is an issue with the RFI, the Reviewer can reject it by setting the status to “Rejected”.

Mobile

• On Mobile, the Reviewer and Coordinator can submit an official response by going into the individual RFI and selecting “Submit Official Response”.
• Coordinator is able to assign and forward RFI to a Reviewer by selecting “Forward to reviewer” and then specify the Reviewer by clicking on “Reviewer”.
• Use the status drop-down menu to select “Answered”. Add the official response, then click “Submit”.
• If there is an issue with the RFI, the Reviewer or Coordinator can reject it by setting the status to “Rejected” and adding in the corresponding response.

• When the Reviewer or Coordinator submits the official response, the RFI Manager will be notified via email. The Manager is the only role who can close and distribute the response.
• If the answer is not suitable, the Manager can reopen the RFI and send it back to the Reviewer or the Coordinator.
• If it is suitable, they can select “Close and distribute,” add comments letting the team know how to proceed, and click to distribute the answered RFI to the entire project team.
• Closed RFIs are visible to all users with access to the RFI tool.

• Project Admins and RFI Managers can re-open closed and distributed RFIs by selecting “Reopen RFI”.
• In the comments field, include the reason for re-opening the RFI. To create a revision, select the checkbox next to “Create revision”. When done, select “Reopen”.
• The RFI will revert to the previous state, and, if a comment was included, it will appear in the activity log.

ProTip: Under “Advanced settings”, Project Admins have the option to change Reopening RFI settings. On each project, Project Admins can configure settings to either allow or disallow the reopening of closed RFIs on the Project.

Web

• Use the funnel icon to filter. Sort by clicking the column headers, and customize the column view via the control icon.
• Use the search bar to search for an RFI title or ID.
• Users can configure the RFI view and select which columns to display.

PRO TIP: Users can configure the RFI view and “hide” columns that are not necessary by using the “Settings” gear icon at the right of the list.

Mobile

• Within the mobile app, click on the “More” icon on the bottom left and select RFIs.
• There is a search bar at the top of the RFI list view. Users can search by RFI title or ID.

Search and Filter RFIs

Export via RFI Tool 

• In the Web version of Autodesk Build, select the RFI tool. 
• To export a summary list of all RFIs, select “Export”.
• Users can edit the title, choose the file format, and customize the report to either include or not the cover page and the table of contents. Select “Run report”. Once done, the report can be downloaded or made shareable with a link. If the export panel is closed before the report is generated, the report will be emailed once done.
• To export a detail report of an individual RFI, open the desired RFI. Click the “Export” icon in the top right corner.
• Users can edit the title and decide to include several options in the report. Select “Run Report”. Once done, the report can be downloaded or made shareable with a link. If the export panel is closed before the report is generated, the report will be emailed once done.

Creating Reports via the Reports Tool 

• Users can create two RFI reports using the Reports tool in Autodesk Build—an RFI detail or a Summary Report.
• Select “Reports” from the left toolbar in Autodesk Build and press “Create report”.
• Select either “RFI detail” or “RFI summary report”:
  • RFI Summary reports – PDF version include the RFI Status, ID, Title, Created by, Ball in court, Due Date and Question and Question and Official Response.
  • RFI Summary reports – Excel version include Title, Ball in court, Question, Suggested answer, Location, Location details, Status, Official response, Due date, Cost impact, Schedule impact, Priority, Discipline, Category, External ID, Created by, Created on, and Affected trades.
  • RFI Detail reports include all information, including all references and the activity log that is within individual RFIs across the selected RFIs.
  • Note: Based on the size of the RFI detail report, the report is limited to 50 RFIs per request.

• Once the report is customized, press “Run report” and “Select” if this is a onetime report or should be saved as a template that can be run again later or scheduled.

• Configure permissions, default values, responses, types, review templates, and add advanced settings by navigating to the Submittals list and select “Settings” in the top right.
• To assign a Submittal Manager, select “permissions” and enter member, company, or role to act as the Submittal Manager.
• To set default manager, review time, and watchers list, select “Default value”.
• To customize approved, revise and resubmit, and rejected responses, select “Responses”.
• To add different Submittals types, select “Types”.

Submittal Permissions

Standardize the Submittal Review Process

• Project admins and Submittal Managers can customize the review workflow by adding multiple review steps and multiple reviewers per step. They can then save custom review workflows as templates and edit them as needed.
• To do so, select “Settings” on the top right corner of the Submittals page and then select “Review Templates”
• After selecting “Add templates”, Submittal managers or Project Admins can add the template name, multiple review steps, multiple reviewers, and review time in days.

PRO TIP: Use these templates when creating a new submittal item or later in the process by selecting “Choose Template” at the bottom of the Submittals workflow table.

• To ensure information is imported correctly, download the sample template.
• Once information is in the template, upload the file and select import items.

Submittal Items

Creating Submittal Packages

• Submittal Packages are a group of Submittal Items. They are not required to go through the review process.
• Project Admins and Submittal Managers can create and delete packages in the “Packages” tab.
• To create a package, select “Create package”, select the spec section and provide a package title, then select “Create”.

• • At the Item level: In the Submittal Item list view, go to the Submittal Item row. Select the three dots located under the settings gear.
    • If the item is not in a package, select “Add to package”. A drop-down list will appear. Users can search for the package that they want to add the item to.
    • If the item is in a package, users will have the option to “Move to package” or “Remove from package”.

Submittal Packages

• If no changes are needed, add a review workflow or choose a template by selecting “Add review workflow” or “Choose template” at the bottom left of the workflow table.
  Note: to create a template, refer to 1. Configure Submittals Settings.
• Proceed by selecting “Submit for review” in the workflow bar.
• The Submittal Manager will edit the due date, select watchers and add notes , if needed.
• They will review the previously attached documents in the pop-up screen. The Submittal manager can copy or upload new attachments, and if needed create annotations or place stamps to the attachments.
• To submit for review, select “Done”.

PRO TIP: To ensure that the Reviewer has all necessary project context, add in project references such as Files, Sheets, Assets, Issues, PCOs, Photos, RFIs, and Forms to the submittal item

Reviewing the Submittal Item

• Reviewers will be notified of the submittal item via email.
• If changes need to be made, select “Step Back” to return the item to the Submittal manager or the previous reviewer, depends on which step of the workflow the reviewer is at.
• If no changes are needed, proceed by selecting “review” in the workflow bar.
• Review the attached documents in the pop-up screen. Reviewers can then copy or create annotations, add in a cover page, and place custom stamps to the previously uploaded attachments or upload new attachments directly.

• In the same pop-up screen, select a review “response”using the drop-down list at the top.
• Add necessary  comments and click “Done”.

PRO TIP: Users can add in comments or mention team members with “@” within the activity log. This increases collaboration.

PRO TIP: Project Admins and Submittal Manager have permission to act on behalf of Reviewers, providing teams with the flexibility of process while allowing the correct Reviewer to be displayed in the Reviewer field and reports. The activity log will show the Project Admin logged the response.

• Once the item is approved by the Reviewers, the Submittal Manager needs to close it and distribute it.
• Open the item and select “Close and distribute”.
• Include the Responsible Contractor, and, in the Watchers section, identify team members who should be aware of the approved Submittal Item via email.
• Review all the attached documents submitted by all the reviewers in the pop-up screen. Add a “final response” and final response attachment Either upload attachments directly or copy or create annotations and place stamps to a previously uploaded attachment.
• Once the item is closed it will either be available for viewing by all project members or only team members involved in the workflow. Depends if closed submittals visibility toggle is ON or OFF in the Submittals settings. 

PRO TIP: Admins and Submittal Managers can re-open closed items. With the closed item, select “Workflow action” button in the top right corner, then select “Reopen”. The item will be re-opened to its latest state. Managers and Admins can send it reviewers or close and distribute it.

Responding to a Revision

• The Responsible Contractor will be notified of the revision request via email.
• Open the item, and submit revised attachments if needed.
• Once done, the document will appear above the Revision 1. The revision number will depend on how many revisions were made.
• Select “Submit to Manager”. The Submittal Manager can now send the revised item(s) to the Reviewers

• As Submittal Items move through the workflow (forward and backward), and/or any value or attribute changes, the system automatically tracks the activity.
• The tracking dates are visible in the activity log of the Submittal Item.

• Within the mobile app, team members can access Submittals by selecting “More”, then “Submittals”.
• All approved Submittal Items are accessible to either the entire project team or the team members involved in the workflow only. Depend on the “Closed item visibility” setting.
• Submittal Items in progress are available only to those involved in the submittal process.
• In the list view, by default, Submittal Items will be grouped by Submittal Spec sections.
  • Note: Users can choose not to group, or group by specs or package.
• Tap to open an item and reference the details.

Web

• Select the Submittal Tool from the toolbar on the left of Autodesk Build.
• Within either the “Items” or “Packages” tab, select the funnel icon to access the filter options.
• To sort, click the column headers. To customize the columns within the “Items” list view, the user should select the control icon, then check the items they wish to see.
• To search, use the search bar to search by submittal title, spec section, ball in court, or package.

Mobile

• Users can use the search bar to search by submittal number, title, or spec section.

Filter and Search

• To export a detailed report of a Submittal Item, open the item. Click the “Export” icon in the top right corner.
• Users will have the option to export the PDF with or without attachments embedded.
  • If the user selects “Export with attachments”, attachments are limited to 60 MB each and up to 30 attachments can be embedded. If there are more than 30 attachments, no attachments are embedded, and the report will have a list of all attachments with links out to them.

• Once the format type is selected, users can customize the report by renaming the report title, selecting the file format, applying filters, and choosing how the report will be sorted and which option to include.
  • Users can filter by status, spec section, ball-court, due date, priority, package, type, response, or created at.
  • Multiple filters can be applied to ensure only the necessary information is included in the report.
• Once the report is customized, press “Create report”, and select if this is a onetime report or should be saved as a template that can be run again later or scheduled.

• Set up all custom Categories, Sub-Categories, Statuses, and Attributes before adding any Assets.
• Click on the “Assets” tool from within Autodesk Build.
• Click on “Settings” to see a dropdown of options to customize:
  • Categories
  • Custom Fields
  • Status Sets
  • Permissions
• Click on any of these options to start creating customizations, and then click the blue “Create” button within each section.

Configure Customizations

• Set different permission levels based on user, company, or role.
• Click on the “Assets” tool from within Autodesk Build.
• Click on “Settings” and select “Permissions”.
• Add new members or edit existing members’ permission levels:
  • View
  • Edit
  • Create
  • Manage

Permission Setup

Manual entry

• Click on the “Assets” tool from within Autodesk Build.
• On the top , click the “Create asset” button.
• Add all relevant information.

PRO TIP: Alternatively, rooms, areas, or sections of your project can be identified as Assets. This would allow statuses, attributes, checklists, and other documentation to be tied to those rooms, and to be available through the mobile app or from a QR code scanned from your device. The workflow is the same as adding a piece of equipment as an Asset.

• Link an existing document:
  • Once files have been added to a folder, click on a particular Asset.
  • Click on the “References” tab and click the dropdown to “Add References”. Then select either a File or Sheet option.
  • Within the pop-up window, navigate to select one or multiple files.

Add Reference to Asset

Link to an existing Form:

• Click on the Asset from either a mobile device or desktop.
• Click on the “References” tab.
• Click the dropdown menu to “Add references” and select “Forms”.
• Scroll or search for the desired form(s). Select one or multiple Forms and click “Add forms”.

Create Form from Asset

• Link any existing Issue or log a defect by creating a new Issue and connecting it directly to a particular Asset.
• Click on the Asset from either a mobile device or desktop.
• Click on the “References” tab. Then click the dropdown menu to “Add references” and select “Issues”.
• Click on the “Create” button to add a new Issue, or search/scroll existing Issues and select any that should be linked to the Asset.

Create Issue from Asset

• Link any jobsite photos directly to an asset to improve documentation and add clarity for handover.
• Click on the asset from either a mobile device or desktop

• Click on the “References” tab and click the dropdown to ‘Add References’ and select ‘Photos’.
• Click on the ‘Upload new’ button to add a new photo or search / scroll existing photos and select any that should be linked to the asset.

Add Reference to Asset

• View the Asset module via iOS app
• Access all relevant information for each specific asset while onsite by:
  • Scanning a barcode
  • Viewing / filtering list views

Import from Assets back to Assemble:

• In the Assets tool, select “Export all”.
• Open Excel export and map the output back to Assemble.
• Click “Update Assemble” within the Assemble Excel Add-In to push data back into Assemble.