Autodesk

Construction Cloud™
Quick Reference
Guide
Overview
Autodesk Construction Cloud™ (ACC) is a cloud-based construction management and collaboration
solution. The Autodesk Construction Cloud™ offerings are unified by utilizing Autodesk Docs as the
common data environment. With centralized file management, you can navigate and have integrated
workflows throughout a project. On the Autodesk Construction Cloud™ platform:

• Autodesk Build - The best of PlanGrid and BIM 360 put together with new functionality to create a
comprehensive field and project management solution. Autodesk Build also includes the Autodesk
Construction Cloud app with new capabilities for field workers.
• Autodesk BIM Collaborate - Enables project teams to align and execute on design
intent by managing the entire design collaboration and coordination workflows
from a single solution to reduce rework, improve productivity and accelerate
project delivery.
• Autodesk Docs - You can organize your files and folder for use throughout your
project. You can distribute files to the field, publish sheets, conduct file reviews,
create transmittals, and track file issues.
https://help.autodesk.com/view/BUILD/ENU/?guid=About_Autodesk_Construction_Cloud
Pictures and information were collected from Autodesk Construction Cloud™ and associated help resources
Index
• ACC Online Help • Submittals
• Correspondence • Transmittals
• Schedule • Assets
• Meetings • Change Orders
• Request for Information (RFI)
• Issues
• Reviews
• Sheets
 ACC Online Help
For additional Help, Tips or Training Videos, there are online
resources available for the Autodesk Construction Cloud. To access
these:
1
1. Select the ⹔ from the top right corner of the
ACC webpage, next to your profile name.
2. Select: 2A
A. Help for the help page and tips. The help page 2B
that opens will be for the application you are
currently in.
B. Learning Center for training module and
videos.

Return to Index
 ACC Help Page
2
On the ACC Help Page, topics can
be navigated:
1. From the legend on the left
hand side
2. Using the search bar at the 1
top right.

Return to Index
 1
Learning Center
Note: You must sign into the
Learning Center using your ACC
profile
1. Select Courses from under the
Learn tab at the top of the page. 2
2. Select the ACC Product from the
list to open the list of modules

Return to Index
 Learning Center
3. Select a module from the list 3
4. Select Register

You can now proceed through the

module at your own pace. Your
progress will be saved as you go. 4

Return to Index
 https://help.autodesk.com/view/BUILD/ENU/?guid=About_Correspondence

Correspondence
Communications regarding critical project information are to be
documented using the Correspondence function on the ACC Build
Module. To document an email:
Option 1 – Include the project’s ACC email address as a recipient.
bayside_post_smolt_facility-s6qgabqfwpiuxzg@corr.acc.autodesk.com
Note: Only email addresses with permission to the project can file emails to ACC using this function.

Return to Index
 https://help.autodesk.com/view/BUILD/ENU/?guid=About_Correspondence

Correspondence
Option 1 – Include the project’s ACC email
address as a recipient. 1A
bayside_post_smolt_facility-s6qgabqfwpiuxzg@co
rr.acc.autodesk.com
Note: Only email addresses with permission to the
project can file emails to ACC using this function.
To copy the email address from ACC: 2
1. Navigate to Correspondence
A. Build
B. Correspondence 3
2. Select File from email
3. Copy the address
1B
Return to Index
 Correspondence 1A
3
Option 2 – ACC Correspondence Function 2
1. Navigate to Correspondence
A. Build
B. Correspondence
2. Select +Create
3. Entering the required recipients, details 1B
or attachments.

Note: Using this function will allow for a non-member

to be added to the correspondence contact list. Under
the To or CC dropdown, select Create non-member and
enter recipients contact information. Non-members will
be able to view and respond to the correspondence by
email, but will not be added as a project member.

Return to Index
 Correspondence (Review)
To view documented correspondences:
1. Navigate to Correspondence
A. Build 1A
B. Correspondence
2. List can be searched by: 2
A. Search Bar 2B
B. Filtering details
3. Select from list
1B

Return to Index
 https://help.autodesk.com/view/BUILD/ENU/?guid=About_Schedule

Schedule
1A
The project master schedule will
be kept in the Schedule tool in ACC
Build.
1. Navigate to: 2
A. Build
B. Schedule
2. Select a Schedule from list

1B

Return to Index
 https://help.autodesk.com/view/BUILD/ENU/?guid=About_Schedule

Schedule (Updating Schedule)

To update an existing schedule in ACC, upload the latest file
version from the browser by either:
1. From list:
A. Select Menu ⋮ 1A
B. Select Update Schedule
2. From open schedule, select Update Schedule
1B

Return to Index
 Meetings
The Meetings tool in ACC Build provides a space to create an agenda
and record minutes from meetings held. An agenda can be set up from
either a previous meeting to carry over ongoing items, or as a new
meeting. This will ensure an efficient use of participants time and allow
for the minutes to then be documented as record.

Return to Index
 Meetings (Create New Agenda)
1A
1. Navigate to:
A. Build
B. Meetings
2. Select + Create Meeting
2

Note: New items or changes

are saved automatically

1B

Return to Index
 Meetings (Create New Agenda)
3. Enter Agenda details 3A 3G 3H
A. Title 3B
B. Date & Time
C. Meeting Description
D. Discussion Topics and Items. As 3C
many can be added as needed
E. Meeting Summary 3D
F. Attachments (external files as
required)
G. Invitees 3E
H. References (internal ACC files
as required)
3F
Return to Index
 Meetings (Recording Minutes)
During meetings, open the
appropriate agenda and record
minutes as they are addressed. 7
1. Add text details to items
2. Add Assignees or Due Dates to
Items
3. Add attachments or references to
items 3 4
4. Add Cost details 2
5. Change Item Status
6. Add new Items or Topics 5
7. Mark Agenda as Minutes
6
Return to Index
 Meetings (Create Follow-up)
To create a Follow-up meeting to and
existing meeting or agenda by
either:
1. From the main meeting list, 1
select + Follow-up
2. From and open meeting:
A. Select Menu ⋮
2B
B. Select Create follow-up

A window will pop-out to select a 2A

date for the follow-up meeting
Return to Index
 https://help.autodesk.com/view/BUILD/ENU/?guid=RFIs_Overview

Request for Information (RFI)

Throughout the project, if additional information is required, a formal
Request for Information (RFI) can be submitted. This allows for members to
submit a documented request, assign the appropriate parties and track its
status. Any supplemental references or information should be included in
the RFI submission to provide clarity of the request.
• Creating
• Reviewing
• Workflow
• Statuses
• Notifications
Return to Index
 Request for Information (Create)
1A
1. Navigate to: 3
A. Build 2
B. RFIs
2. Select +Create RFI .
3. Enter as much detail as possible. 1B
Additional documents can be added to
the RFI by selecting the Add References
drop-down. If there is a potential cost
implication, select PCO under the
references drop-down and either select
and existing PCO, or create a new PCO.
4. Select Create to submit
4
Return to Index
 Request for Information (Reviewing)
1. Navigate to RFI: 1A
A. Build
B. RFIs 2B
2. Search by: 2A
A. Search Bar
B. Filtering details 1B
3. Select from list

Return to Index
 Request for Information (Reviewing)
4. Review details of 5
request and add details
A. Comments
B. References/Documents
4A
C. RFI History
5. Submit Official
Response (Answered or
Rejected)
6. Manager will Close and 4C
Distribute 4B

Return to Index
 Request For Information (Workflow)

Return to Index
 Request For Information Statuses
• Creation: An RFI is created with a default status of 'Submitted'. If it can't be completed
immediately, the status can be set to 'Draft' by the creator.
• Submission: Once completed, the creator submits the RFI, transferring its ownership to the
manager.
• Review: The manager submits the RFI to the reviewers, changing the status to 'Open'.
• Response: Reviewers provide their official response, changing the RFI status to 'Answered'.
• Rejection: Optionally, reviewers can manually set the status to 'Rejected', delegating the
query to another party.
• Closure: Post-response, the manager sets the status to 'Closed', and distributes the RFI to all
project members.
• Void: If the RFI becomes irrelevant, it can be marked 'Void' from the status drop-down
menu.

Return to Index
 Request for Information
(Notifications)

Return to Index
 https://help.autodesk.com/view/BUILD/ENU/?guid=Issues_About

Issues
When a potential issue or conflict has come up that needs to be
addressed or monitored, the Issues page can be used. This allows for
members to submit a documented Issue, assign the appropriate parties
and track its status. Any supplemental references or information should
be included in the submission to provide clarity of the issue.
• Creating
• Reviewing

Return to Index
 Issues (Creating) 1A
3
1. Navigate to: 2
A. Build 1B
B. Issues
2. Select +Create Issue
3. Enter as much detail as
possible. (References can
be added after the issue
is created)
4. Select Create

Return to Index
4
 Issues (Creating)
5. Once an Issue is created, it can
be edited by opening it from
the list on the Issues page.
6. Additional documents can be
added by selecting the Add
5
References drop-down. If
there is a potential cost
implication, select PCO under
the references drop-down and
either select and existing PCO,
or create a new PCO.

6
Return to Index
 Issues (Reviewing)
1A
1. Navigate to Issues:
A. Build
2B
1B 2A
B. RFIs
2. Search by:
A. Search Bar
B. Filtering details
3. Select from list

Return to Index
 Issues (Reviewing) 4C

4. Review details of selected

Issue and add details
A. Comments
B. References/Documents 5
C. Issue History Log
4B
5. Update Status. Resolved
Issues should have a
“Closed” status

4A
Return to Index
 Issue Statuses

Return to Index
 https://help.autodesk.com/view/DOCS/ENU/?guid=Reviews

Reviews
When files are ready to issued, they can be sent for a formal review and
approval using the Review function. Members designated as reviewers
can review and comment on the files, and members designated as
approvers can give final approval for the files to be used.
• Create
• Reviewing
• Workflow

Return to Index
 Reviews (Create)
1A
1. Navigate to Reviews
A. Docs 1B
B. Reviews 3
2. Select +Create Review 2
3. Select Files
4. Select Create

4
Return to Index
 Reviews (Create) 5

5. Select a pre-set Approval Workflow

6. Enter a title for the Review
7. Enter Notes (optional)
8. Select Submit 6

Return to Index 8
 Reviews (Create from Files)
Reviews can also be generated directly
from a file or folder.
1. Select the menu ⋮ next to a file
2. Select Submit for Review
3. In the pop-up enter information as
per previous page:
• Approval Workflow
• Review Title
• Enter Notes 2
• Select Submit

Return to Index 1
 Reviews (Reviewing)
1. Navigate to Reviews: 1A
A. Docs 1B 2B
B. Reviews 2A
2. Search by:
A. Search Bar
B. Filtering details
3. Select from list

Return to Index
 Reviews (Reviewing)
4. Select Start Review
• If you are a reviewer, this will 4
start the initial review.
• If you are an approver, this will 5
start the final review. 6
5. Review Progress
6. Open and Review files
• Add comments
• Add file mark-ups

Return to Index
 Reviews (Reviewing)
8. Select Review Status
9. Select Submit Review 8
A window will pop-up to add 9
comments and submit review

Return to Index
 Reviews (Workflow)

Return to Index
 https://help.autodesk.com/view/BUILD/ENU/?guid=Upload_And_Publish_Sheets

Sheets
• Project drawings will be documented using Sheets in ACC Build.
Documents that are revised are to done so by creating a new version
of the document with the same file name. ACC has a built-in function
that enables changes to be compared across different revisions.

Return to Index
 Sheets (Creating New)
1A
1. Navigate to:
A. Build 1B
B. Sheets
2
2. Select + Add Sheets

Return to Index
 Sheets (Creating New)
3. Add Files
A. From existing files from the
Files tool in ACC
B. Selecting from your computer 3A 3B
C. Dragging and dropping into the
box
3C
4. Select Next to Version Set

4
Return to Index
 Sheets (Creating New)
5. Select the sheet
version:
A. New Version Set
B. Existing Version Set 5A 5B
6. Select next to sheet
numbers

Return to Index
 Sheets (Creating New)
7. Review Sheet Numbers (dwg
numbers). ACC should extract the
sheet number automatically, but if
it is wrong or missing, select the 7A 7C
checkbox, then modify by:
A. Draw area on the sheet where the
number is identified to extract. This
is useful if multiple sheets are
uploaded with details in the same 7B
position in the title blocks.
B. Manually enter sheet number
C. Editing the sheet numbers 7 8
8. Select Next to titles and tags
Return to Index
 Sheets (Creating New)
9. Review Sheet Titles. If they are
wrong or missing, select the
checkbox: 8A 8C
A. Draw area on the sheet where 9
the title is identified to extract
B. Manually enter drawing
numbers
C. Edit with rules
8B 9
10. Add or edit Tags (optional)
11. Select Publish Sheets 9 11

Return to Index
 Sheets (Adding Revisions)
When adding revisions to existing 1 2
sheets, files are added the same as
new sheets. The important step is to
ensure the sheet numbers remain
the exact same and update the
version to the newest version set.
1. Upload file
2. Update Version
3. Review/Edit Sheet Number 3
Note: When the same sheet
number is used, the revision history Note
will be shown.
4. Continue same as creating a
new sheet 4
Return to Index
 Sheets (Reviewing)
1A
1. Navigate to:
A. Build
1B
B. Sheets 2
2. Search by:
A. Search Bar
B. Filtering details 3
3. Select from list

Return to Index
 https://help.autodesk.com/view/BUILD/ENU/?guid=Submittals_Overview

Submittals
Items from suppliers and contractors which require approvals (material
specifications, shop drawings, paint specs, etc.) can be reviewed using
Submittals in ACC Build. This ensures that there is transparency and
that the project is proceeding according to the design specifications.
The project manager may create a submittal item and assign to a
contractor for requested feedback, or a contractor may create a
submittal item with relevant information and submit for approval.
Submittals may be individual items, or as packages of multiple items.

Return to Index
 Submittals (Roles)
Role Description
Typically a subcontractor or supplier. This role is responsible for submitting documents for approval. Responsible contractors
Responsible can
contractor • Create items
• Add submittal documents and add comments
• Submit to managers for review.
A Submittal manager is typically a general contractor and are responsible for many parts of the submittal process, including:
•Creating items and packages
Submittal •Assigning items to responsible contractors and reviewers
manager •Creating the review workflow
•Sending items to review
•Closing and distributing items

Required A Required reviewer is typically an architect or member of the design team and are responsible for reviewing and then
reviewer approving or rejecting a submittal. A submittal item can’t move to the next step until all required reviewers respond.

Optional An Optional reviewer is typically an engineer or consultant who is asked to give feedback. A submittal item can move to the
reviewer next step even if optional reviewers haven’t responded.
Watchers are various project stakeholders who receive notifications via email on status changes for submittal items and may
Watcher
add comments or attachments to a submittal, but they can’t provide a review response.

Return to Index
Return to Index
 Submittals (Create Item Submittal
Request)
1A
1. Navigate to:
A. Build 3
B. Submittals
2. Select + Create Item in 2
the Items tab
1B
3. Enter details
• Spec Section
• Submittal Title
• Contractor
• Required Dates
4. Select Create
Return to Index
4
 Submittals (Submit for Review)
1. Review and add comments
or reference material. 2
Note that references are
only supplemental, not
part of the submittal to be
approved.
2. Select Submit 1

1
Return to Index
 Submittals (Submit for Review)
3. In the pop-out window,
add the files for review.
4. Select Done to submit. 3

Return to Index
 Submittals (Manager Review)
Project Manager 2
1. Review submittal to
ensure requested
documents and details
have been included. Add
details as required.
2. Submit for Review or Step
Back to request more
detail from contractor
2

Return to Index
 Submittals (Manager Review)
Project Manager
3. Review Documents. Mark-
ups can be added in the
document viewer. When 3
the document is closed, it
will create a copy with the
markups on the
submission.
4. Select Done to advance
4

Return to Index
 Submittals (Review)
Reviewer 2
1. Review comments and
references on submittal
2. Select Review from either
the status bar or the
Review Step section

2
Return to Index
 Submittals (Review)
Reviewer
3. Review submitted
documents. Mark-ups or
new documents added by 4
previous reviewers will 3
appear under their review
section.
4. Select a Response for
approval
5
5. Select Done
Return to Index
 Submittals (Close & Distribute)
Project Manager 2
1. Review responses from
assigned reviewers
2. Select Close and
Distribute

Return to Index
 Submittals (Close & Distribute)
Project Manager
3. Review submittal 4
documents and reviewer 5
approvals
3
4. Copy final approved
documents. This will show
the approved files at the
top of the submittal.
5. Select Final Response
6. Select Done 6

Return to Index
 Submittals (Notifications)

Return to Index
 https://help.autodesk.com/view/DOCS/ENU/?guid=Transmittals

Transmittals
A transmittal is a formal means of sending files to another project
member or team. Using the Transmittals tool creates a record of when
files are sent to other project members or teams. Note that only
project members can receive a transmittal.

Return to Index
 Transmittals (Create)
1. Navigate to: 1A
A. Docs
B. Transmittals 1B 2
2. Select + Create
Transmittal 3
3. Check the files to include
4. Click Select Files

4
Return to Index
 Transmittals (Create) 5A
5B
5. Enter details
A. Title (Email Subject Line)
B. Recipients
C. Review list of files 5C
D. Message
6. Select Create

5D

Return to Index
6
 Transmittals (Create from Files)
Reviews can also be generated directly from
a file or folder.
1. Select the menu ⋮ next to a file or folder 1
2. Select Create Transmittal
3. In the pop-up enter information as per
previous page:
A. Title (Email Subject Line)
B. Recipients
C. Review list of files
D. Message 2
E. Select Create

Return to Index
 Transmittals (Reviewing)
1. Navigate to Transmittals 1A
A. Build 2B
B. Correspondence 1B
2A
2. List can be searched by:
A. Search Bar
B. Filtering details 3
3. Select from list

Return to Index
 Transmittals (Reviewing)
4. Review Transmittal
A. Review Details 4C
B. View Files
4A
C. Download Files
4B

Return to Index
 https://help.autodesk.com/view/BUILD/ENU/?guid=About_Assets

Assets
• The Assets tool in Autodesk® Build allows teams to easily track and
manage the lifecycle of all project's assets and equipment, from
design through commissioning and handover.

Return to Index
 https://help.autodesk.com/view/BUILD/ENU/?guid=Cost_Change_Orders_Overview

Change Orders
• Workflow Overview
• Potential Change Orders (PCO)
• Cost Items
• Request for Quotation (RFQ)
• Change Order Request (COR)
• Owner Change Order (OCO)
• Supplier Change Order (SCO)

Return to Index
 Change Order Workflow Overview
Change to
Change Order Owner Change
Supplier No
Request (COR) Order (OCO)
Contract?

Yes

Out Of Scope
(Budget Change)

Supplier
Potential Additional Potential Change In Scope
Add Cost Items Is Cost Known? Yes Scope? Change Order
Cost Identified Order (PCO) (Cost Change)
(SCO)

No

RFQ

Return to
Change Orders
Return to Index
 Return to
Change Orders
Return to Index
 https://help.autodesk.com/view/BUILD/ENU/?guid=Cost_Potential_Change_Orders

Potential Change Orders (PCO)

When an item is identified that has the potential to have an impact to
the project budget or supplier contract, a Potential Change Order can
be created to document the impact.
• Workflow Overview
• How to generate a PCO
• From Cost Page (Admin Only)
• From Issue
• From RFIs
• Adding details to PCO
• toPCO Next Steps
Return
Change Orders
Return to Index
 Potential Change Order Statuses
(Budget)

• Draft: During the creation state of a PCO. Documents can't be generated.

• Open: When a PCO is set to Open, it formally enters into the system. All of its cost items are also set to
open. You can now generate an RFQ, COR, OCO, or SCO, depending on the scope.
• Submitted: Submitting the change order for approval activates this status. Cost items can no longer be
added or removed.
• Accepted: The owner accepted the budget change through a COR.
• Approved: The owner approved the budget change through an OCO.
• Executed: All parties have signed the budget change order.
• Rejected: Not accepted by the owner. You can revise and resubmit.
Return to
Return to Index
Change Orders
 Potential Change Order Statuses
(Cost)

• Draft: During the creation state of a PCO. Documents can't be generated.

• Open: When a PCO is set to Open, it formally enters into the system. All of its cost items are also set to
open. You can now generate an RFQ, COR, OCO, or SCO, depending on the scope.
• Pricing: Proposed price is agreed to for the cost change. Cost items can no longer be added or removed.
• Proposed: Cost items can no longer be attached to the PCO.
• Approved: The cost change is approved.
• Executed: All parties have signed the cost changes.
• Rejected: You can revise and resubmit.

Return to
Return to Index
Change Orders
 Potential Change Orders (Create
from Cost Page)
1. Navigate to PCO Tab
1A
A. Cost Management
B. Change Order Page
C. PCO Tab
2. Select + Add 1B
3. Enter relevant details 1C
Note: A Cost Item must be
added to move PCO
forward
2
Return to
Change Orders
Return to Index
 Potential Change Orders (Create
from Issue)
1. Navigate to Issue Page 1A
A. Build
B. Issues Page
Note: A PCO must be added to 1B
an existing Issue, it cannot be
added while creating a new
Issue. 2
2. Open an existing Issue

Return to
Change Orders
Return to Index
 Potential Change Orders (Create
from Issue)
3. In the details box on the right side:
A. Scroll down to References and select
the “Add references” drop down
B. Select “PCO”.

3B

Return to 3A
Change Orders
Return to Index
 Potential Change Orders (Create
from Issue)
4. Reference PCO
4B
A. An existing PCO can then be selected by 4B
clicking the checkbox next to it; or
B. Generate new PCO
• Select + Create
• Enter title and description for new PCO.
4A
5. Select Add PCO

Return to
Change Orders
Return to Index 4
 Potential Change Orders (Create
from RFI)
1. Navigate to RFI Page 1A
A. Open Build
B. RFIs
2. Select RFI
A. Open an existing RFI; or
B. Select + Create RFI to enter a new RFI 2B

1B
2A

Return to
Change Orders
Return to Index
 Potential Change Orders (Create
from RFI) New RFI
3. Reference PCO
A. Scroll down to References and select the “Add
references” drop down
B. Select “PCO”.
3A
Existing RFI

3B

Return to
Change Orders 3A
Return to Index
 Potential Change Orders (Create
from RFI)
4. Reference PCO
4B
A. An existing PCO can then be selected by 4B
clicking the checkbox next to it; or
B. Generate new PCO
• Select + Create
• Enter title and description for new PCO.
4A
5. Select Add PCO

Return to
Change Orders
Return to Index 5
 Potential Change Orders (Next
Steps)
1. Once a PCO is ready for approvals, select the
PCO from the list of PCOs
2. In the window on the right, select Set as Open 2

1
Return to
Change Orders
Return to Index
 Potential Change Orders (Next
Steps)
• If the cost of the change is not known, generate an RFQ
• If the change to an in scope item (cost change), generate a Supplier Change Order
(SCO)
• If the change is to an out of scope item (budget change), generate a Change Order
Request (COR), then an Owner Change Order. A Supplier Change Order may also be
required if there will be a change to a supplier’s contract.
• If the change is out of scope (budget change) and approved, generate an Owner
Change Order (OCO)

Return to
Change Orders
Return to Index
 https://help.autodesk.com/view/BUILD/ENU/?guid=Cost_Cost_Items

Cost Items
All change orders are made up of either a single or multiple Cost Items.
These are the individual items that will be linked to the associated
budgets and contracts. To enter a Cost Item from the Cost Item Tab:
1. Navigate to the Cost Item Tab 1A
A. Cost Management
B. Change Order Page
C. Cost Item Tab
2. Select + Add
1B
This will create a new row where the following
data fields must then be filled in: Name, Scope (In /
Out), Budget Code, Contract Name, Estimated Cost (if
known)
1C
2
Return to
Change Orders
Return to Index
 Cost Items (Assigning from Cost
Item Tab)
To assign a cost item to a PCO:
1. Select the menu ⋮ on an
individual Cost Item
2. Select Assign
3. Select PCO
4. Select the PCO to assign the 1
Cost Item to.

Return to 3 2
Change Orders
Return to Index
 Cost Items (Assigning from PCO Tab)
1. From the PCO tab; 1
2. Select the menu ⋮ on a PCO
2
3. Select Add Cost Item
This will create a new row where the following
data fields must then be filled in: Name, Scope
(In / Out), Budget Code, Contract Name,
Estimated Cost (if known)
3

Return to
Change Orders
Return to Index
 Cost Item Dollar Values
Cost items include five Values which will appear on all change order tabs:
• Estimated. For one PCO, a general contractor (GC) estimates the value. An estimate is not required to
advance an item.
• Proposed. GC asks the supplier to provide the estimation of the cost item of an RFQ (Request For Quotation)
and record the estimation into the Proposed value.
• Submitted. The cost item value shows in the Submitted column when a GC submits the COR (Change Order
Request) to an owner's review.
• Approved. After an owner's initial review, a GC combines multiple CORs into one OCO (Owner Change Order)
and signs the legal change order document with an owner. The OCO value is recorded as Approved.
• Committed. After the OCO or COR is approved, a GC will sign an SCO (Subcontractor Change Order) with the
supplier. The value is recorded as Committed.

Return to
Change Orders
Return to Index
 Cost Items Statuses (Budgets)
Cost items status automatically update with status changes from PCOs or CORs.

• Draft: During the creation state of a change order.

• Open: When a PCO is set to Open, it formally enters the system. All of its cost items are
also set to open. You can now generate an RFQ, COR, OCO, or SCO.
• Submitted: Submitting the change order for approval activates this status. Cost items can
no longer be added or removed.
• Accepted: The owner accepted the budget change in a COR.
• Approved: The owner approved the budget change in an OCO.
• Executed: All parties have signed the budget change.
• Rejected: Not accepted by the owner. You can revise and resubmit the change order
Return to
containing this cost item.
Change Orders
Return to Index
 Cost Items Statuses (Costs)
Cost items status automatically update with status changes from PCOs or CORs.

• Draft: During the creation state of a PCO.

• Open: When a PCO is set to Open, it formally enters the system. All of its cost items are also
set to open. You can now generate an RFQ, COR, OCO, or SCO.
• Pricing: RFQ containing this cost item was sent to a supplier for pricing.
• Proposed: A price is proposed and agreed on the cost changes. Cost items can no longer be
attached to the PCO or RFQ.
• Accepted: The general contractor accepted the cost change.
• Approved: The owner approved the cost change.
• Executed: All parties signed the cost change.
• Rejected: You can revise and resubmit the change order containing this cost item.
Return to
Return to Index
Change Orders
 https://help.autodesk.com/view/BUILD/ENU/?guid=Cost_Request_for_Quotation

Request for Quotation (RFQ)

• A Request for Quotation (RFQ) is a formal request sent to suppliers for
pricing.

Return to
Change Orders
Return to Index
 Request for Quote Statuses

• Draft: During the creation state of the RFQ. Documents can't be generated.
• Open: When an RFQ is set to Open, it formally enters into the system. RFQ documents can be generated.
• Pricing: RFQ was sent to the supplier for pricing. Can add cost items and generate documents.
• Proposed: The proposed price is agreed upon for the cost change. Cost items can no longer be attached to the RFQ.
• Revise and Resubmit: One from the party hasn't accepted the change order and requested revision. Check what is
required and submit revised change order.
• Accepted: The change order is accepted. You can generate a SCO.
• Rejected: You can revise and resubmit.
Closed: Extra status, set when a request is closed.
• to
Return
Change Orders
Return to Index
 https://help.autodesk.com/view/BUILD/ENU/?guid=Cost_COR_OCO_SCO

Change Order Request (COR)

A Change Order Request (COR) is the upstream request for a change to
the budget.

Return to
Change Orders
Return to Index
 Change Order Request Statuses

• Draft: During the creation state of a COR. Documents can't be generated.

• Open: When a COR is set to Open, it formally enters into the system. COR documents can be generated.
• Submitted: Submitting the change order for approval activates this status. Cost items can't be added or removed. PCOs can't be attached.
• Revise and Resubmit: One from the party hasn't accepted the change order and requested revision. Check what is required and submit revised
change order.
• Accepted: The owner accepted the change order. You can generate an OCO or SCO.
• Approved: The owner approved the OCO containing this COR.
• Executed: All parties have signed the OCO containing this COR.
• Rejected: The owner didn't accept the COR. You can revise and resubmit the COR.

Return to
Return to Index
Change Orders
 https://help.autodesk.com/view/BUILD/ENU/?guid=Cost_COR_OCO_SCO

Owner Change Order (OCO)

An Owner Change Order (OCO) is an upstream change to the project
budget which will impact the owner’s cost.

Return to
Change Orders
Return to Index
 Owner Change Order Statuses

• Draft: During the creation state of an OCO. Documents can't be generated.

• Open: When an OCO is set to Open, it formally enters into the system. You can now generate OCO documents.
• Submitted: Submitting the change order for approval activates this status. Cost items can't be added or removed. PCOs and
CORs can't be attached.
• Revise and Resubmit: One from the party hasn't accepted the change order and requested revision. Check what is required
and submit revised change order. Only project administrators can set this status when the change order is already executed.
• Approved: The owner accepted the change order. You can generate an SCO.
• Executed: All parties have agreed to the change order.
• Rejected: Not accepted by the owner. You can revise and resubmit the OCO.

Return to
Return to Index
Change Orders
 https://help.autodesk.com/view/BUILD/ENU/?guid=Cost_COR_OCO_SCO

Supplier Change Order (SCO)

A Supplier Change Order (SCO) is a downstream change to a supplier’s
original contract. This could be due to an Out-of-Scope item added to
the project, or an In-Scope item which may have been missed.

Return to
Change Orders
Return to Index
 Supplier Change Order Statuses

• Draft: During the creations state of an SCO. Documents can't be generated.

• Open: When an SCO is set to Open, it formally enters into the system. SCO documents can be generated.
• Sent: The cost change is approved and the SCO is sent to the subcontractor. Cost items can't be added or
removed.
• Executed: All parties have signed the change order.

Return to
Change Orders
Return to Index