What Got Shipped Today - 21/8/26 - One Tender Packages page, your own trading names, Xero links on every record

Seven changes reached production today. The through-line is convergence: two tender screens becoming one, a directory that finally holds a builder's own trading names, and a click-through from every record we push into Xero. Features Subcontractor Tendering: one Tender Packages page, with Related Items that actually count User Story As a Contract Administrator running buyout, I had to work a trade package across two near-identical screens and neither one told me whether my subbies had come back, so I can now run the package from one row that carries recipients, workflow and live related items together. Before Preconstruction → Subcontractor Tendering carried two screens for the same thing. The beta Tender Tracker (Outgoing) showed who a package had gone out to plus any notes. Bid Package Management showed value, workflow state, issue date and tender type. Both listed the same packages and the same totals, and neither was usable on its own, so you bounced between them to assemble one picture of a trade. Worse, the Related Items column on every row read RFIs 0 / CL 0 / 0 no matter what was actually happening on that package. The counts were hard-coded and wired to nothing. After One Tender Packages page. The register keeps the four summary tiles and the deadline banner, and each row now carries the package and trade, project, due date with an Overdue or Due soon chip, value, status and workflow, and the recipient avatar stack with a +N overflow. Expand a row and two panels open. Tender Recipients lists every invited subcontractor in full rather than as an avatar, each with its real invite state (Invited, Accepted, Bid received, Declined) and a running bid and declined tally. You can see at a glance how many of the six you invited have actually priced it. Related Items sits beside it, and those cards are now live. RFIs counts the queries raised against that specific package and how many are still awaiting a response from you. Notices to Tenderer counts the formal correspondence issued out to bidders. Tender Documents counts what is actually attached to the package and expands to a linked file list, with an empty state prompting you to attach before issuing. Click any card and a slide-over opens on that package's notices, with Raise RFI right there. Raise one and it comes back pre-typed and pre-linked to the package, and the count moves immediately. Impact The Related Items column stops being decoration. A trade package now answers its own questions, so you can see whether a bidder has come back, what has been asked, and what has been issued without leaving the row. Chasing a slow subbie starts from the register instead of from your inbox. Making that work meant giving every notice a typed link back to the record that spawned it, with an open vocabulary from day one. That plumbing extends to variations, subcontracts and progress claims, so the same treatment lands elsewhere rather than being a one-off for tendering. Known limitations The beta Tender Tracker (Outgoing) menu entry has not been retired yet. That happens once parity is signed off. Invite states show the real vocabulary the platform holds, so there is no Viewed state. Per-invitee view tracking does not exist yet. Clarification Notices are not counted on the register yet. Raising a clarification against a package and counting it alongside RFIs and Notices to Tenderer is the next piece of work. The Tender Documents card reads the package's attached files rather than a CDE-controlled tender issue set. Aligning those follows. A Company Directory that holds your own trading names User story As a Contract Administrator, the directory showed me a subcontractor under a legal name nobody on site uses and froze when I scrolled a long list, so I can now set the trading name we actually call them and move through the list at speed. Before. A company came into your workspace under one name and stayed there. If a subbie trades under something other than the entity on the ABN, that was your problem to remember. There was no way to retire a company you had stopped using, so directories only ever grew, and long lists could slow the browser to a crawl or freeze it outright. After. Three things changed. Companies open in a proper slide-out drawer with resizing, stacked tabs and per-tab Edit, matching the pattern the Head Contract and Subcontract registers use. You can attach one or more of your own trading names to any company and set one as primary, which drives display and lookups across the workspace. The original name stays visible in the list as an option you can always return to. And a company can be archived out of your workspace and un-archived later. Archiving is deliberately scoped. It soft-removes the company from your directory without touching the shared record, so archiving a company in your workspace can never affect another builder's. The stable reference underneath never moves, which means archiving and renaming are display decisions, not data loss. The long-list slowdown is fixed too, so large directories scroll properly. Impact. The directory now reflects how a builder actually talks about their subbies and suppliers, rather than how a tax record does. Cleanup becomes safe, because archive is reversible and never reaches beyond your own workspace. Build a purchase order line straight from a supplier price list User story As a Contract Administrator, I had rates sitting in a price list and still typed them into every purchase order by hand, so I can now pull the line from the list and keep the link back to it. Before. Price lists reached the BoQ but stopped there. Raising a purchase order meant retyping a rate you had already captured, with nothing recording where the number came from. After. The New PO flow can add lines from a workspace price list. Pick the list, choose the item, and the line lands with its rate. Each PO line built this way keeps its lineage back to the price list item it came from. Impact. The same rate now flows from price list to estimate to commitment without being retyped at any step, and the purchase order can be traced back to the quoted rate rather than to somebody's memory of it. Improvements Click through to Xero from every record you have pushed User story As a Commercial Manager, I could jump from an invoice straight to its bill in Xero but had to hunt for everything else, so I can now click through from any record that carries a Xero object. Before. The click-through into Xero existed on exactly one surface, the Invoice Register detail drawer, for converted purchase order invoices and subcontract claims. Everything else pushed into Xero left you to open Xero separately and search for it, which on a busy job means matching a reference by eye across two browser tabs. After. The same click-through now runs across the record types that hold a Xero object: head contract invoices and progress claims, credit notes, payment schedules, and purchase orders in the detail drawer. More usefully, you no longer have to open a record first. Where a register or list already shows a Xero status, that indicator is now the click target itself. It works on the Invoice Register, the head contract invoice register, the head contract claim register and the subcontract claim register. No new columns, no wider rows, nothing moved. Links open in a new tab so you keep your place in the register, and clicking the badge opens Xero without also opening the row's drawer. The reference shown is always the number the object genuinely carries in Xero, never the internal Deep Space id, and nothing renders at all until the record actually holds a Xero object. Credit notes route to the credit note view rather than the invoice view, so the link lands on the right document type. Impact. Reconciling a job stops being a tab-matching exercise. From any register row that says it is in Xero, one click puts you on the right object. Known limitations. The purchase order register has no Xero indicator to convert yet, so purchase orders link from the drawer only. The subcontract invoice register shows a Xero status derived from a flag rather than a stored reference, so those cells are not clickable until the underlying record carries an id. Subcontractors get a task breakdown of just their own bookings User story As a subcontractor, the programme showed me everything or nothing useful, so I can now see the full construction programme and a clean list of only the bookings that are mine. Before. The subcontractor programme did not mirror what the builder sees, and it did not isolate the subcontractor's own work. Finding your bookings meant reading the whole programme and picking out your rows. After. The programme tab carries a My bookings task breakdown alongside the full view-only programme, listing only that company's bookings, with Respond available directly on any row still waiting on them. Impact. A subcontractor opens the programme and immediately sees two things that matter: the job as the builder sees it, and the short list of what they personally owe a response on. The builder-owned progress figure stays builder-owned; nothing here lets a subcontractor edit the authoritative programme. One clearly labelled Construction Programme in the subcontractor portal User story As a subcontractor, I was shown two separate schedules and a menu label that did not say what it was, so I now see one programme called what it is. Before. The portal offered Planning, which told a subcontractor nothing, plus a Weekly Work Plan and a Lookahead alongside the programme itself. Three schedule surfaces for a party who needs one. After. Planning is renamed Construction Programme, and Weekly Work Plan and Lookahead Planning are no longer shown to the subcontractor role. Nothing is deleted and the builder side is unchanged. Impact. A subcontractor lands on one schedule with a name that describes it. Less to explain during onboarding, and no more guessing which of three schedules is the real one. Fixes Clients no longer land on an under-construction Milestones tab User story As a client invited to a project, I opened Milestones and was told the module was under construction, so that tab is no longer shown to me. Before. A client accepting a portal invite could open Program then Milestones and be met with a message saying the module was under construction. From the client's side that reads as an account that was never set up properly, which is a poor first impression on a live job. After. The Milestones tab is hidden for the client portal until it carries real content, using the same mechanism that already hides other unbuilt surfaces. Impact. A client sees the tabs that work and none that apologise. The older client portal inside the platform keeps its working Milestones view, so nothing usable was hidden. Something here you would do differently, or something missing you need? Tell us through the feedback portal in the platform. It goes straight to the people who build this.