New: Job/project display format setting in Purchasing Documents
BuildOps now gives your company control over how jobs and projects are displayed across all purchasing documents. A new Job/Project Display Format setting in Procurement Settings lets you choose from three display options — so every team member sees job and project references in the format that matches how your company structures its identifiers.
What's new:
A new company-level setting in Procurement Settings controls how jobs and projects appear across all procurement surfaces.
Three display format options are available, giving your company the flexibility to match how your team references job numbers and custom identifiers.
Job Custom Identifier / Project Name only
Job / Project Number only
Number + Name
The setting applies company-wide, ensuring a consistent experience for every user on your team across all purchasing documents.
How to get started:
Navigate to Procurement Settings and look for the new Job/Project Display Format option. Select the format that best suits your team's naming conventions. The change takes effect immediately across all purchasing documents.
Users who have permission to view and edit Procurement Settings will be able to view and change the Job/Project Display Format setting.
Audit Log Tab for Purchase Orders & Subcontracts
Purchase Orders and Subcontracts now include a new Audit Log tab that gives your team a complete, chronological history of every key action taken on a document — from creation and approval through to receipts and bills. No more guesswork about what changed or who acted on a document.
How to access it
Open any Purchase Order or Subcontract from your procurement list.
On the document detail page, click the new Audit Log tab.
Browse the full chronological history of actions taken on that document.
No configuration required. The Audit Log is available immediately on all existing and new documents.
Tracked Actions: Purchase Orders
Action Label | When It Is Recorded |
Created PurchaseOrder | A new Purchase Order is created |
Approved PurchaseOrder | The PO status changes to Approved |
Edited PurchaseOrder Quantity/Amount | Line quantities or amounts are manually changed, or changed via a Commitment Change Order (CCO) |
Voided PurchaseOrder | The PO status changes to Void |
Exported PurchaseOrder | The PO is exported to the accounting system |
Created PurchaseOrderReceipt | A Receipt is created against the PO |
Posted PurchaseOrderReceipt | A Receipt status changes to Posted |
Exported PurchaseOrderReceipt | A Receipt is exported to the accounting system |
Voided PurchaseOrderReceipt | A Receipt status changes to Void |
Created Bill | A Bill is created against the PO |
Posted Bill | A Bill status changes to Posted |
Exported Bill | A Bill is exported to the accounting system |
Voided Bill | A Bill status changes to Void |
Audit Log tab on the Purchase Order Detail Screen
Tracked Actions: Subcontracts
Action Label | When It Is Recorded |
Created Subcontract | A new Subcontract is created |
Approved Subcontract | The SC status changes to Approved |
Edited Subcontract Quantity/Amount | Line quantities or amounts are manually changed, or changed via a Commitment Change Order (CCO) |
Voided Subcontract | The SC status changes to Void |
Exported Subcontract | The SC is exported to the accounting system |
Created Bill | A Bill is created against the SC |
Posted Bill | A Bill status changes to Posted |
Exported Bill | A Bill is exported to the accounting system |
Voided Bill | A Bill status changes to Void |
Note: Deleted Receipt and Deleted Bill actions currently cannot be displayed - only voiding action can be tracked via the Audit Log.
Audit Log tab on the Subcontract Detail Screen
Lists & Tasks on Web
BuildOps now includes a native Lists module inside Projects on web, purpose‑built for managing punch items, inspection checklists, safety reviews, and any operational task list your team needs.
From the web, you can:
Use the Lists tab inside a project to build structured lists for punch items, QA/QC, safety, and more.
Create, assign, complete, reject, and approve tasks with required resolution notes for clear accountability.
Work in Grid View for detailed filtering and sorting, or Kanban View for visual status tracking.
Import task lists from Excel using a template to get started quickly.
Export lists to Excel to share with GCs, owners, inspectors, and other external stakeholders.
Keep web and mobile in sync so field teams always see the latest tasks.
This feature will be enabled for all customers on May 6, 2026.
Learn More
If you want detailed, step‑by‑step instructions (including how to use the Lists tab on web and manage tasks across Grid and Kanban views), please see the feature documentation: Project Lists & Tasks on Web
Create Lists/Tasks from Drawings on Web
You can now link project tasks directly to drawing annotations on web, so your punch items and field work are tied to the exact location on the plan where the issue exists.
From the drawing viewer on web, you can:
See all task references overlaid on a drawing using the updated Reference Sidebar, which now includes both RFIs and Tasks tabs.
Associate an annotation to an existing task or create a new task on the fly using the Task Association modal.
Jump from a task in the Lists page to the exact drawing and annotation it’s linked to using the new Drawing References section in Task Details.
Remove task–drawing references from either side (drawing or task) without deleting the underlying task or annotation.
All changes stay in sync with the existing Lists and Tasks on Web experience and with the mobile app, so field and office teams are always working from the same source of truth.
This feature will be enabled for all customers on May 6, 2026.
Learn More
For detailed instructions (including how to use the Reference Sidebar, associate annotations, and navigate between tasks and drawings), please see the feature documentation: Create Lists/Tasks from Drawings on Web.
CRM+ Tracking Bid Due Dates on Opportunities
You can now add a Bid Due Date to Opportunities so your team always knows exactly when each bid is due and can prioritize work around upcoming deadlines.
What’s new
A new Bid Due Date field is available on all Opportunities as an optional date field.
You can set and update this date from:
The Create Opportunity form (under Additional Information).
The Opportunity detail view.
The Opportunity list view, where it is available as a column and can be edited inline.
This makes it easy for sales teams to see upcoming bid deadlines at a glance and keep deals moving.
This update is automatically available to all CRM+ customers. Any user who has access to Opportunities can view and edit the Bid Due Date field.
Where you’ll see Bid Due Date
Create Opportunity
When creating a new Opportunity, you’ll see a Bid Due Date field in the Additional Information section. Use the date picker to set when the bid is due before saving the Opportunity.
Opportunity Creation Form
Opportunity detail view
On the Opportunity detail page, Bid Due Date appears as an editable field. You can set, change, or clear the date at any time from this view.
Opportunity list view
In the Opportunity list view, Bid Due Date is available as a column. You can click directly into the date cell to set or update the value without opening the Opportunity; changes save automatically.
Required Field on Opportunity Milestones
Admins can configure Bid Due Date as a required field on any milestone in Sales Process Settings. When an Opportunity is moved to a milestone that requires it – whether from the list view, kanban board, or detail view – a required-fields modal will prompt the user to fill in the Bid Due Date before the move can proceed.
More Reliable NetSuite Inbound Syncs
BuildOps now processes inbound NetSuite requests one at a time for each company. This reduces sync failures caused by NetSuite’s concurrent request limits and makes inbound syncs more reliable.
Why This Matters
NetSuite limits how many SuiteTalk API requests can run at the same time based on your subscription. Previously, when multiple inbound requests were sent at once, NetSuite could reject the extras with a concurrent request limit error. Those syncs would then fail and need to be retried.
How This Update Helps
BuildOps now routes inbound NetSuite traffic through a dedicated per-company queue that processes one request at a time. This means inbound calls to NetSuite are sent in order, one after another, instead of in parallel, helping them stay within NetSuite’s concurrency limit even when multiple syncs are queued up. This change is fully behind the scenes, with no new screen, setting, or button.
No action is required. This update is automatically applied for all customers using the NetSuite integration.
Avalara Tax Sync for NetSuite
What’s New:
BuildOps now integrates with Avalara for customers using NetSuite, automating sales and purchase tax calculation on transactions synced from BuildOps to NetSuite. The integration supports both Legacy Tax and SuiteTax configurations, and works alongside the BlueCollar cost-code breakdown for purchasing tax lines.
In short, this release is about making sure Avalara-calculated tax from BuildOps carries through to NetSuite in the correct format for each company’s NetSuite tax setup.
How it works:
Legacy Tax: BuildOps sends one consolidated Purchase Tax line and one consolidated Sales Tax line. Avalara’s per-jurisdiction breakdown is preserved in the memo field of each tax line, giving accounting teams audit detail without fragmenting the tax journal.
BlueCollar-enabled companies: Purchase tax lines are additionally broken down by Cost Code, so taxes flow into the correct job-cost buckets.
SuiteTax: Line-level tax detail is sent through NetSuite’s taxDetails table. Detailed SuiteTax behavior is documented in the related NetSuite > SuiteTax Integration release notes.
Avalara integration setup in BuildOps.
Legacy Tax invoice example.
SuiteTax invoice example.
Legacy Tax purchase tax example.
SuiteTax purchase tax example.
To use this functionality, customers must first set up their Avalara integration in BuildOps, then continue transacting in BuildOps as normal for invoicing and purchasing flows, and export those transactions to NetSuite.
NetSuite BlueCollar Support for Unit Billing Projects
What's New:
You can now use Unit Billing Projects with the NetSuite BlueCollar project financials integration. If your company uses NetSuite and BlueCollar, this update helps keep your quantity-based project financials aligned between BuildOps and NetSuite. Instead of relying on manual workarounds, you can manage Unit Billing Projects in BuildOps while syncing the related project financial data to BlueCollar for reporting and accounting visibility.
Why This Matters
Unit Billing Projects are designed for work that is priced and billed by quantity, unit of measure, and unit price rather than a single fixed contract amount.
Previously, Unit Billing Projects were not fully supported in the NetSuite BlueCollar integration. This meant teams using this project type could run into gaps when trying to keep BuildOps and NetSuite aligned, creating extra manual work and increasing the risk of mismatched financial data.
With this update, you can manage Unit Billing Projects with more confidence that your project financial data is flowing through the integration as expected.
What’s Included
Schedule of Values Sync for Unit Billing Projects
For Unit Billing Projects, BuildOps now sends quantity, unit price, and contract value details from your Schedule of Values to BlueCollar. This helps NetSuite reflect the structure of your Unit Billing Project more accurately.
Budget Support for Unit Billing Projects
Budget structures tied to Unit Billing Projects can now sync through the integration. This includes support for values such as Install Units and Labor Hours where applicable, helping your project budget stay aligned between BuildOps and NetSuite.
Quantity-Based Change Order Support
Change Orders for Unit Billing Projects can now support quantity-driven and unit-price-driven updates. This helps approved project changes roll up correctly to the related budget and Schedule of Values.
This update is available for customers using both the NetSuite BlueCollar integration and Unit Billing Projects. If you are interested, please reach out to your Customer Success Manager.
Standard Reports: Refresh Timestamps
We’ve added improved refresh visibility for the 7 latest reports in the Standard Reports Package.
Previously, reports displayed only the number of minutes since the last refresh. With this update, you will now see:
Last Data Refresh – shows the exact date and time the report data was last updated
Estimated Next Data Refresh – shows the expected date and time of the next scheduled refresh
This enhancement provides better transparency into report data freshness and helps users more easily understand reporting latency without relying on a relative time indicator.
Note: Both timestamps are displayed in UTC (Coordinated Universal Time)
Included Reports
This update applies to the following reports in Standard Reports Package.:
