Purchase Order Issuance for General Contracting

Open the approved subcontractor award recommendation and leveling sheets for the trade or vendor you are issuing a commitment to. Confirm which firm was approved, for what scope, and at what base and alternate values.

Review the prime contract and any company standards to see whether this trade should be under a subcontract agreement, a purchase order, or a service agreement. Note any client-mandated forms or required flow-down clauses.

Determine whether you are awarding the full scope, only a portion (such as early packages), or a preliminary service (like preconstruction or design-assist). Write a one-line description summarizing what this specific PO will cover.

Compare the final agreed price (including any negotiated adjustments after selection) to the number in the award recommendation. If differences exist, make sure they are documented and agreed in writing (email or notes).

Based on scope and phasing, decide whether you will issue one commitment for all work or separate POs for different phases or locations. Note this decision in the project’s commitment log so the team stays consistent.

Write a brief note in the commitment or PO planning log indicating which partner is being awarded, what document type will be used, and what scope portion and value are included in this issuance.

Open the trade partner’s final proposal or quote that was used for selection, along with any follow-up emails that changed pricing, alternates, or clarifications. Confirm you are using the latest agreed version.

From the proposal and leveling sheet, list exactly which items are included in the award: base scope and any accepted add or deduct alternates. Write out the description and agreed amounts for each item.

Using the estimate-to-budget mapping, assign each portion of the trade partner’s price to one or more cost codes. Decide how detailed you want the coding (for example, splitting labor and materials or phasing by area) and record the breakdown in a simple table.

Extract important inclusions and exclusions from the proposal that need to appear in the scope of work. Highlight responsibility boundaries (for example, who provides hoisting, waste removal, temporary power, or minor concrete).

Check whether prices are quoted with or without tax, whether freight and delivery are included, and whether there are any escalation clauses or limited validity dates. Note any conditions that must be captured in the PO language.

Summarize the pricing breakdown, cost codes, inclusions, exclusions, and commercial assumptions in a simple one-page “Commitment Data Sheet.” Save it in the commitments folder as the working reference for drafting the PO.

Log into your accounting or project management system and navigate to the commitments or purchase order module. Make sure you are in the correct project using the right job number.

Start a new commitment entry and select the correct vendor or subcontractor from the approved vendor list. If they are not in the system, follow your vendor setup process before continuing.

Fill in the project name, project number, trade description, and a concise title for the commitment (for example, “BP-03 Concrete – XYZ Concrete Inc.”). Verify that the billing and remit-to addresses for the partner are correct.

Enter the agreed total value for the commitment as taken from the Commitment Data Sheet. If the system allows, break out separate line items for base work and accepted alternates so they can be tracked individually.

Using your prepared coding breakdown, add line items or distributions by cost code and assign the corresponding amounts. Double-check the totals to ensure they still add up to the agreed value.

Save the commitment as a draft record, noting in the description or notes that this is a “Draft – Pending Review.” This prevents it from being used prematurely for payments or reporting.

Using the bid package matrix, selected proposal, and leveling notes, write a clear scope of work document. Describe the work in practical terms, list major inclusions, and explicitly state key exclusions and clarifications.

At the top or bottom of the scope, list the exact drawing issue dates, specification volumes, and addenda that apply to this trade. Include titles, dates, and sheet/spec numbers so there is no ambiguity.

Add short bullets indicating who is responsible for common shared items like layout, patching, firestopping, equipment pads, and waste removal. Use simple, direct language so it is obvious which party owns each task.

In the commitment system, upload the scope of work document as an attachment or link and ensure it will be included when the PO or subcontract is printed or exported. Label it clearly (for example, “Exhibit A – Scope of Work”).

Attach or link any other critical reference documents such as schedules, phasing diagrams, logistics plans, or special details that are unique to this trade. Avoid overloading the PO with the entire drawing set if your system already references them elsewhere.

In the main PO or subcontract body, include a clause or note stating that “Scope of work is defined in Exhibit A” and that the listed drawings and specifications form part of the agreement. This ties the attachments legally to the commitment.

Open your company’s standard subcontract or PO template for the project type. Note default payment terms, retainage percentage, insurance requirements, and any standard flow-down language.

Check the owner contract for clauses that must be flowed down to subcontractors (for example, insurance limits, waivers of subrogation, schedule obligations, and change order processes). Highlight those that are relevant to this trade.

In the commitment record, choose or enter the correct payment terms (for example, net 30 days after approval) and retainage percentage. Ensure these align with both your company standard and the prime contract.

Decide whether this subcontractor or vendor must provide certificates of insurance, additional insured endorsements, and/or performance/payment bonds. Note any specific limits or forms required and ensure the commitment language reflects them.

If there are special commercial conditions for this trade (for example, milestone billing, stored materials, or extended warranties), add them into the terms or as a short “Special Conditions” section in the PO.

Before moving on, have the project manager or contracts lead quickly review commercial settings for this commitment to ensure they match project expectations and company policy.

In your ERP or budget tool, compare the commitment value by cost code against the current approved budget. Note where the commitment is over, under, or matching budget at the code level.

Open the subcontractor award recommendation and Estimate_to_Budget mapping for this trade. Confirm that the commitment value and scope reflect the same basis you used when leadership approved the selection.

If the commitment exceeds budget in certain codes, identify why. It may be due to clarifications, additional scope, or differences between estimate assumptions and final negotiations. Decide whether a budget adjustment or contingency draw is needed.

If the commitment is under budget, note where savings are coming from (for example, value engineering, competitive pricing). Decide whether to leave the difference as unallocated contingency or adjust the budget codes.

If you change budgets or contingency allocations based on this commitment, record the change in your Budget Adjustments log with the date, description, and related cost codes.

Add a short note to the commitment record stating how it compares to budget and selection notes. This helps future reviewers and supports transparency during project reviews.

Check company policy and project-specific rules to see who must approve commitments at this dollar value and risk level (for example, project manager, operations manager, or executive).

Compile the draft PO or subcontract, scope of work exhibit, Commitment Data Sheet, and any key correspondence or clarifications into a small approval packet. Include a one-paragraph summary of the award rationale.

Use your ERP or project management platform to start the formal approval workflow, attaching the approval package or linking to the commitment and its documents.

As approvers review the commitment, be available to answer questions about scope, pricing, or terms. If they request changes, document them and update the PO draft accordingly, then re-submit as needed.

Once all required approvers have signed off in the system or via email, note the approval date and any conditions (for example, “pending receipt of updated insurance certificate”). Ensure the commitment status reflects approval.

Update the commitment status to indicate it is approved and ready for issuance. Avoid making further changes unless a formal revision is required later.

From the commitment system, generate the official PO or subcontract document, including all exhibits and attachments. Review the output quickly to ensure formatting is correct and all pages are present.

Email the PO as a PDF or send it via your electronic signature platform, depending on company practice. Use a clear subject line and a short message explaining that this is the formal award for the scope discussed.

Specify how you need the partner to accept the PO (for example, by signing and returning electronically or by signing in an e-sign system). Provide any instructions or deadlines for returning the signed document.

Confirm that the partner received the PO by checking read receipts or portal status. If you do not hear back within a reasonable timeframe, follow up with a phone call or reminder email.

When the signed PO or subcontract comes back, check that all required pages are signed, any initials are present where needed, and no unauthorized changes have been made by the partner.

Upload the fully executed commitment to the project’s Contract/Commitments folder and attach it in the commitment system. Mark the PO as “Executed” or equivalent to show it is now in force.

Verify that the commitment in the accounting system shows the correct executed value and status. Correct any discrepancies in amounts or coding now before invoices start arriving.

If your system uses a schedule of values or breakdown for billing, set up the line items based on cost codes, phases, or work categories. Make sure these align with how progress will be measured in the field.

If your PM platform tracks commitments separately, ensure that the PO record is created or synchronized there, with correct values and scope references. Link it to related RFIs, submittals, or change events if your system supports that.

Let the accounting or AP team know about any unusual billing arrangements for this PO (for example, milestone payments, stored material terms). Provide them with a copy of the commitment summary if helpful.

Share a short summary of the executed PO with the project manager and superintendent, highlighting scope, value, key exclusions, and any schedule commitments made by the trade partner.

Confirm that vendor setup is complete in accounting (W-9, banking info if needed) so that when the first invoice arrives it can be processed without delay.

Maintain a log listing each PO or subcontract, vendor name, scope description, original amount, current amount, and status (for example, draft, executed, revised, closed). Store this log in the project controls folder or use your system’s built-in reporting.

When a new PO is executed, enter its number, date, amount, and key notes into the log. Include a reference to related selection notes or change events if applicable.

Follow company policy for how changes to commitments are handled (for example, via change orders or PO revisions). Ensure that no one manually edits executed commitments without creating a traceable revision.

When a PO is revised, record the revision number, date, reason (such as owner change, scope clarification, or VE), and link to the associated change order or change event. Update the current amount in the log.

Use the PO log and system reports to regularly compare total committed amounts by cost code to the budget. Flag areas where commitments approach or exceed budget so the project team can address issues early.

Update the log whenever a new PO is issued or revised. Provide periodic snapshots to the project manager and operations leadership so they can see commitment status and trends at a glance.