PCO in Construction: From Material Change to Order Release

Ordering against a revised drawing before its purchasing authority is clear can leave the wrong material on site. A PCO in construction commonly means a potential change order: a record used to develop and track a possible change, its pricing and its progress through the project’s change process.

For material buyers, the useful question is what the PCO connects: the source revision, the affected package, the supplier’s price, the schedule consequence and the person responsible for the next decision. PCO terminology and statuses vary between systems. A pricing review or budget status should be read in its project context; record the actual document authorizing the purchase separately. This guide provides a source-specific terminology comparison and a blank material-release record, rather than a universal approval sequence.

• Preserve the source drawing, bulletin, RFI or submittal reference and revision.
• Keep requested pricing, reviewed pricing and order authorization in separate fields.
• Identify both the next action owner and the person authorized to release the affected purchase.
• Leave unknown prices, impacts and authorization references blank until confirmed.

What does PCO mean, and why do the terms differ?

Potential change order is the terminology used in ProjectTeam’s PCO manual. Its form tracks possible scope-related cost and revenue changes, can include cost proposals, and supports subsequent creation of change orders. That is a product workflow, not a definition of authority for every contract.

Read the full term on the source document before transferring an item into a shared log. In particular, a word describing an amount is not necessarily the name of a document or its approval status.

For example, Penn State’s ICCO training describes an ICPCO used to obtain and review service-provider pricing and hold it for a later grouped approval process. The owner-specific example shows why receiving a price and completing the approval route should have distinct records. It does not prescribe the route for another project.

How does a construction bulletin relate to a PCO?

Treat the bulletin as the source document to investigate: read its stated purpose, attachments, revision and required response. Its title alone does not tell a buyer whether to seek pricing, replace a drawing in the package or release an order.

A bulletin, a PCO and a change order answer different administrative questions. The comparison below uses AIA documents as explicitly named examples; it does not make every project’s “bulletin” equivalent to an AIA form.

The boundaries above come from AIA’s instructions for G710, G701 and G714. The directive route matters: a buyer should not turn “price unresolved” into an automatic rule that no directed work can proceed. Equally, a pricing request should not become an assumed release instruction. The actual contract and issued documents govern the decision.

What should the buyer capture when a revision arrives?

Start with the difference between the previously referenced scope and the new information. Our suggested worksheet follows the affected material package through that difference, so the next person can reconstruct what needs a decision.

Consider a hypothetical revision that relocates an opening in a partition. The administrative task is to identify the drawing revision, affected material list and existing purchase scope, then obtain the necessary technical and commercial responses. The photograph shows the kind of assembly under discussion; it supplies no dimensions or design approval.

1. Identify the source. Record the bulletin, RFI response or drawing number, revision and issue date. Note which previous reference it changes.
2. Locate the affected package. Name the material package, supplier and relevant purchase order or subcontract. Identify whether material is unquoted, quoted, ordered, fabricated or delivered using the current records.
3. Request the commercial difference. Obtain the supplier’s revised scope and price reference, including additions, omissions and exclusions. Ask separately about an existing order’s cancellation, rework or delivery consequences rather than assuming them.
4. Record the timing question. State which activity or required delivery is affected. Keep the supplier’s confirmed response separate from the project’s requested date and any proposed contract-time adjustment.
5. Assign the decision and handoff. Name who will resolve each outstanding point, the required response date and the evidence needed before the purchasing record changes.

Autodesk’s Potential Change Orders documentation links cost items to affected budgets, contracts and suppliers, and describes creating or linking PCOs from RFIs, issues and submittal items. The worksheet adapts that traceability principle into a neutral buying record. Use the specification-comparison guide if the unresolved point is what the revised material requirement actually includes.

Does an approved PCO mean the material can be ordered?

The status word alone does not answer that question. Check what was approved, by whom, in which workflow, and which document carries the purchasing instruction for this package.

For example, Autodesk distinguishes budget and cost statuses. Its manual explains that moving a PCO from Draft to Open affects its inclusion in budget or contract calculations. Those are software behaviors; do not translate “Open” into a purchasing release. Likewise, distinguish a proposed amount from the evidence behind a reviewed amount.

Use separate status fields instead of a single “approved” checkbox:

Record the actual authorization reference separately from the PCO status. This is the central control in our suggested record. A reviewer’s name can identify a follow-up contact without proving that person’s authority to approve a purchase. If the route is unclear, escalate through the project’s document-control and contract-administration process.

Use the blank PCO-to-material-release record

Copy the fields below or download the blank PCO material-release CSV. The download contains headings and empty records. It is an editorial worksheet, not an AIA form, a software export or a completed project example.

Use a separate row for each affected material package when the supplier, release scope or decision owner differs. Keep the same source PCO reference on those rows so the team can see the shared origin without merging separate purchasing decisions. In the CSV, each input has its own column for filtering and follow-up.

An empty amount means the price is unknown; it does not mean zero cost. An empty schedule-impact field means the response is outstanding; it does not confirm no delay. Preserve dated source documents rather than overwriting earlier quotes with a new number and losing the comparison.

When release is documented, transfer the authorized scope and revision into the material procurement log. That log tracks the broader package journey; this worksheet preserves the change and its release evidence. Carry unresolved decisions into the OAC meeting action record with a named action owner, while keeping the formal change documents in their proper process.

Sources and method

Updated October 2026. Muros Construction compiled this independent editorial guide with AI assistance from primary documentation fetched on October 15, 2026. ProjectTeam and Autodesk support the attributed PCO workflow examples; Penn State supplies one owner’s internal process; Trimble Vista supplies the source-specific “Pending Change Order” wording. The linked AIA G710–2017, G701–2017 and G714–2017 instructions support the named document distinctions, not a claim that every project uses those forms or editions.

The blank worksheet, field grouping and material-buyer checks are our editorial synthesis. No project prices, review periods, lead times, tested outcomes or contract-specific authority have been supplied. Apply the actual project’s current agreements, issued instructions and authorized communication route when completing the record.