Week of July 27, 2026

Picking a department on a dashboard selects every phase belonging to it, and the phase list beside it is a multiselect you can adjust: uncheck what you do not want, add a phase from another department, and every figure on the page follows the set. Every metric can be filtered this way now, not just some of them.

Before this, the Department filter did not change the figures on the Department Head tabs. The phase list also no longer offers phases you have retired.

Filtering Planning by a date range now keeps any order that touches that range, and expanding one shows everything inside it.

Before, a component scheduled outside the window could not be expanded, and its stages simply were not there. Nothing said they had been filtered out, so a job read as if it had fewer stages than it does. Anyone planning a quarter was looking at an incomplete picture of it.

The filter also follows you now. Pan the chart past the range you loaded and the range widens to match what is on screen, so the chip, the address bar and what you are looking at always agree. Panning loads what you scroll into, with a pill telling you it is fetching, and the zoom stays legible at both ends instead of collapsing into unreadable columns.

Two production dashboards built from customer workshops, and the widget types they needed, which every dashboard can now use.

The production dashboard covers planned against actual, by project or by phase, with rows that open into what is behind them: planned, spent, expected to date, percent complete, and how far over or under that leaves you. Hours break down by project and by person, and stalled orders list what is on hold, showing only the topmost held item rather than repeating it down the tree.

The second dashboard splits by team, with prefab quality reporting on-time delivery, first pass yield and rework trends, and a Completed This Week section counting finished orders per day for the current week.

New for any dashboard: bullet charts, stacked bars, tree tables that total their children, and progress bars that can show a target. Plan against actual also opens about three times faster than it did, from roughly twenty six seconds to eight and a half.

A location can now belong to a project. Every new project gets a Jobsite location of its own, and a project's locations live on a Locations tab in its details.

Prefab work runs from a shop to a jobsite, and until now there was nowhere to put the jobsite. Locations belonged to departments, so the only way to record where a delivery was going was to write the address on the project itself, where it could not carry coordinates, a timezone, or delivery instructions for the driver.

A location holds its full address, its coordinates, its timezone, delivery instructions and notes. Addresses are the same six fields everywhere in the app now, including on vendors, and a partial address saves. Settings → Locations shows department and project locations from one selector.

Connecting Smartsheet now means signing in to Smartsheet. Pasting an access token still works and stays a first-class option, but it is no longer the only way.

The token route made setting up an integration a job for whoever could find the token, and onboarding calls were being spent walking people through it. It also left the connection resting on one person: a personal token dies when they leave, and a Smartsheet administrator can expire it organisation-wide without anybody here knowing until the sync stops.

Signing in belongs to the organisation rather than the person, and the connection renews itself. If it ever does need attention, the integration says so and offers Reconnect.

The Planning export now has a Tags column, and the import reads it back. So you can retag a few hundred orders in a spreadsheet and upload it, rather than opening them one at a time.

Tags are how a lot of shops regroup work: by panel run, by area, by whoever is picking it up next. Deciding to regroup meant editing every order by hand, which in practice meant not regrouping. One shop that wanted to reorganise their panel groupings had no way to do it at all.

The tag list in the app refreshes when the import finishes, so tags you created in the spreadsheet are ready to filter by straight away.

Pulling timesheet data through the API returns every record across every page, however many pages the result runs to.

The Union Code and Per Diem Code fields show as soon as Costs is turned on, and you can create a code from the picker by typing it: the list offers to add the code you just typed.

Before this, both fields waited for codes to exist, and there is no screen for adding the first one. Adding a code that already exists now tells you so.

Cost codes, union codes and per diem codes are also available over the API and documented. Retiring a code means marking it inactive rather than deleting it, because time already booked to it refers to it by name.

See details on a timesheet record opens the phase or component the hours were logged against, and the back button returns you to where you came from.

Before this it opened the order containing that work, leaving you to find the right level yourself. Overhead records show no link, because overhead time is not logged against a place in an order.

Reads from the worker API leave archived people out by default, which is how every other archived record in the app already behaved. Lists, searches and counts show your current roster.

Scrolling the planning chart sideways is smooth now, and the dates header no longer lags behind the bars underneath it.

The header used to be redrawn in step with the scroll, one frame late, so it visibly slid out of alignment with the columns it labels and was worst while more of the plan was loading. It is now pinned to the scroll position directly, so the two move as one thing.

Dragging the divider between the table and the chart, and drawing a selection box across bars, are no longer slow either.

Every figure on the on time delivery dashboard now opens the jobs that produced it, across all three tabs. The monthly trend chart does the same: click a month and you get that month's deliveries with their on-time flags.

A percentage tells you there is a problem and nothing about where. Working out which jobs were late meant leaving the dashboard and rebuilding the same question somewhere else, which is enough friction that people stop asking.

Each detail view lists every contributing job, not a top ten, and nests down through phase, component and stage. It inherits whatever project, phase and reporting date you already had set, so you are looking at the same slice you clicked from.

Overhead tasks set to All Departments now appear in the overhead picker on a timecard, alongside the ones tied to a specific department.

Before this the picker listed only department-specific overheads, so org-wide overhead could not be booked to a timecard.

Every KPI card on a dashboard now has a cog that opens its colour thresholds, so you can say what counts as good, what counts as a warning, and where the boundaries sit. Only a handful of cards were coloured at all before.

Worth a look if you read these cards: metrics where lower is better, like rework and dead time, now colour the right way round, so a card you are used to seeing green may look different.

A boundary can be tied to a figure you already keep, so moving your on-time delivery target moves the card colour, the target line on its trend and the chart labels together instead of you editing three places. Thresholds can also be shared by name across cards, so a change made once lands everywhere it is used. Edits apply as you make them and are saved for everyone in your organisation.

Opening the deliverable drawer from a card's progress action on Build now lets you move to Overview and edit from there, with a brief spinner while it loads.

Before this, switching to Overview from that entry point emptied the drawer.

The discuss action on a Build card also opens this same drawer now, on Comments, rather than a panel of its own.

When you assign people to work on Build and any of them are not checked in yet, you now get the option to check all of them in together.

In a shop where the foreman is the only one with an account, everyone's attendance goes through one person on one screen. Marking a crew present one name at a time was the slowest part of starting a shift, and it happened every morning.

The prompt appears however you finish assigning, whether that is Done, Create batch, or starting work from a QR scan. Anyone already checked in is left alone.

A column we add hidden stays hidden, even if you have saved a column layout for that table. Your own choices are applied on top of the defaults, so a column you hid stays hidden and one you turned on stays on.

Before this, a newly added column could appear in a saved layout.