Week of September 28, 2026
Most of this week is about getting a delivery where it's going. Location pickers on a delivery now start from the projects on the cargo, each project's jobsite and the spots inside it first, and a delivery carrying cargo for several projects can set up an unload stop for each one in a click. New projects also start with your company's standard locations, such as Main Gate or Laydown Yard, set once under Company settings, Deliveries.
The Plan vs Actual tab on production dashboards follows the dates you pick. Choose Last Week and the cards, the charts and the This Period table cover that week, and a new Finished vs Spent card puts the share of the budget finished beside the share spent. Trends follows the project you pick in the same way.
Work that is waiting on earlier work shows Waiting, and only work that is ready to start shows To Do, so filtering for To Do shows what your crew can pick up now. A connected Smartsheet sheet can carry the same Waiting word on its rows.
The Nested search on Planning finds an order by any phase or component in it, and AI Chat pauses a long question with a Continue button instead of giving up on it. Checks on a form's choice questions read as the condition they fire on. The rest of the week is smaller fixes: typing 1230 in Timesheets gives 12:30 PM, a pick list can be renamed, completing a stage only asks about materials still to record, and archived stages stay out of stage filters.
Delivery stops and location pickers start from the cargo's jobsites
Improved · Delivery
Location pickers on a delivery now start from where the cargo is going and where it leaves from. In the To field and on unload stops, the locations of the projects on the cargo sit at the top, under On this delivery, each project's jobsite and the spots inside it first. In the From field and on load stops, your department locations come first, led by the department that built the cargo. Everything else is still in the list below a divider, and search still finds any location in your organization.
When a delivery carries cargo for more than one project, the Itinerary tab offers Set up a stop for each project. One click adds an unload stop at each project's jobsite (filling the empty unload stop first) and sends each project's cargo to its own stop. If cargo is added later, or ends up at another project's stop, the same place offers to move it. Add stop also starts at the next project that doesn't have a stop yet.
Project locations now show their project wherever a delivery names a place, such as Jobsite (Main Street Clinic), so two jobsites on one trip read apart.
New projects come with your standard locations
New · Delivery · Settings
Set your company's usual project locations once, such as Main Gate, Laydown Yard, or Electrical Room, under Company settings > Deliveries > Standard project locations. Every project created after that gets them under its Jobsite, ready to pick as a delivery stop. Existing projects stay as they are.
The standard locations use the Jobsite's address, so filling in the Jobsite once covers all of them. Add, rename, or archive any of them per project from the project's Locations tab.
You can also pin a location to an exact spot. The new project form and the location form now take a latitude and longitude, and pasting a pair copied from a map fills in both.
Plan vs Actual and Trends follow the dates and project you pick
Improved · Insights
The Plan vs Actual tab on your production dashboard now shows how the dates you picked went. Choose Last Week and the cards, the charts and the This Period table cover that week: the hours the schedule called for, the hours booked, and the work finished. This applies to production dashboards set up with the revised Plan vs Actual tab.
A new Finished vs Spent card puts those side by side: the share of the budget finished in those dates against the share spent. Green means the work finished was worth more than the hours it took. Every card opens a project-by-project breakdown for the same dates, and clicking a project or a bar opens a page that follows the dates too.
Two tables sit one above the other. Plan vs Actual: This Period covers the selected dates, and Plan vs Actual: All Time covers the whole job. They share the same columns in the same order, so a stage reads straight across from one to the other: % complete, % spent, variance, hours scheduled or budgeted, spent, remaining and earned. Every row opens down to the order, and Group by on the table switches between stage then order and order then stage. Charts that still cover the whole job say All time under their title.
A single step estimated at more than 1,000 hours is left out of planned, earned and budget, and the Planned Hours card shows how many were left out, so one mistyped estimate can't swing the page.
On the Trends tab, choosing a project now shows that project's finished orders, the hours on each and the running average, and the figures above the chart follow the same project. Trends also counts each order at the level the work was done: where an order is split into sub-orders, each sub-order is its own point on the chart, and where it isn't, the order is. An order with some work of its own and some in sub-orders shows both, each with its own hours.
Work waiting on earlier work shows Waiting
Maintenance · Orders · Planning · Integrations
A phase, stage or step shows Waiting until the work before it is done, however it got its place in the order: added later, linked to the work before it, or moved in the list. Only work that is ready to start shows To Do, so filtering for To Do shows what your crew can pick up now.
Completing the last stage of a phase makes the phase after it To Do straight away, the same as completing the phase itself. Work you put on hold stays on hold when other work in its order is added, linked or reordered.
Phases that come in from a connected Smartsheet sheet follow the order in its Successor column the same way. Orders whose work was linked before this change are corrected on request.
Your sheet shows which work is waiting
New · Integrations
Rows that are waiting on earlier work in BuildingSwell now get your Waiting word on the sheet, and switch to your To Do word once that work is done. Map a word to the new Waiting outcome in the connection's status mapping to turn it on. The word also has to be an option in your sheet's Status column, and the status mapping has to send changes to the sheet: Push, or one of the Two-way options.
A Waiting typed on the sheet means nothing has started on that row, the same as To Do. Whether it waits or is ready to start comes from the order of the work, so a row with nothing unfinished before it shows To Do. Without a Waiting word in the mapping, waiting rows keep getting your To Do word, as before.
Find an order in Planning by any phase or component in it
New · Planning
In the Nested view on Planning, the search box now finds an order by the name or ID of any phase or component in it, including one nested inside another. Type a phase or a component and the order that holds it comes back, the same way it already comes back for its own name, number, project or route.
The order shows and expands as it always has, with everything in it. A phase name that most orders share, like Design, brings back every order that has it.
Stage names are not part of this search. Rename or move a phase or component and the search follows it to its new name and order; archive it and it no longer finds the order.
AI Chat pauses long questions instead of giving up
Improved · AI
Some questions need many lookups, such as comparing every phase across several routes and the people assigned to each. When AI Chat reaches its working limit on a question like that, it no longer fails with a request to try a narrower question. It stops, writes a short note of what it found so far and what it has not checked yet, and shows a Continue button that picks the work up from that note.
Questions like that also finish sooner. Route reads now name the people assigned to each stage, AI Chat runs several lookups at once, and a follow-up question remembers what the previous answer looked up.
When a lookup fails, the chat now shows the error's own message instead of technical details.
Form checks read as the condition they fire on
Maintenance · Forms
A check on a choice question now means what it looks like it means. Is on Test 1 fires when the inspector picks Test 1. Is not on Test 1 fires when they pick anything else.
Each check also says in one line when it fires. Set Is on Test 1 with Then: Warn and record, and the check reads Warns when the answer is "Test 1". You can tell what an inspector will see without filling the form in to find out.
This is what lets two checks on one question work together. Is Test 1, warn alongside Is Test 2, block now does exactly that: a warning on one answer, a block on the other. A pair like that used to fire one of the two whichever option was picked.
Checks you built earlier behave exactly as they always have. Where one reads differently now, it is describing the same behaviour in the new wording: a check that used to say the answer had to be Test 1 now says it fires on every answer that is not Test 1, which is what it was already doing.
A question nobody could answer will not go live. If the checks on a question leave no answer that gets past them, sending the form live is refused and the question is named, so you can fix it while the form is still a draft. Both of the checks above set to Block finishing would do it: pick Test 1 and one blocks, pick Test 2 and the other does. So would a minimum above a maximum on a number question, or two different values a text answer would have to match at once.
Whether the question is required makes no difference. Leaving a question blank is not an answer to it, so a question with every option blocked is refused either way.
Warnings never count against this. A question answered with a dozen warnings on record is a question that was answered, and checks that overlap or disagree are yours to write.
A signature question no longer asks for the same thing twice. Marking it required already means it has to be signed, so the separate Must be signed check is gone from the builder. A template that already has one keeps working.
You can see a form's checks after it goes live. Opening a question on a live form used to show a blank copy of what the inspector sees, which said nothing about how the question was set up, and a live version cannot be edited, so there was nowhere else to look. It now shows the question read-only, checks included. Preview still shows the inspector's view.
On a question with more than one answer box, each check now sits under the box it applies to rather than in one list under the whole question, so you can see which box a warning is about. And when a question like that is required, every box says so, because all of them have to be filled. That used to surface only when you tried to finish the form.
Completing a stage only asks about materials still to record
Maintenance · Orders
When you complete a stage, the app asks you to record materials only for the steps that still have some left, and fills in what remains rather than the full plan. Steps you already recorded are skipped. Before, those steps were offered their full planned amount again.
When the same part is listed more than once on a step, for example once per sub order, completing the step offers one total for that part, and Mark consumed on the Materials tab records exactly what is left across its lines.
Typing 1230 in Timesheets gives 12:30 PM
Maintenance · Timesheets
Typing a 24-hour time into Start time or End time in Timesheets now reads 1200 to 1259 as the afternoon, so 1230 becomes 12:30 PM. 0000 to 0059 is still just after midnight, and adding am or pm to what you type always decides it.
Shift and break times read what you type the same way.
Rename a pick list from its page
Maintenance · Orders
You can now rename a pick list after you create it. Open the list, click its name at the top of the left panel, type the new name and press Enter. Press Escape to leave the name as it was.
Archived stages stay out of stage filters
Maintenance · Planning · Build · Forms
When you filter by stage in Planning, Build or Forms, the list offers only the stages you still use. Stages you've archived no longer appear there.
Restore a stage from Settings > Archived and it's back in those lists.