What Got Shipped Today - 10/8/26

Published 10 August 2026 A commercial and drawings day. Dates that stop being hand typed, a payment schedule state that no longer disappears when it is sent back, drawings you can correct in bulk, and a win rate that finally tells the truth. Features Change a metadata field across a whole selection of drawings User Story As a contract administrator, I had to open and edit every registered drawing individually to correct one field, so I can now select the set and apply the change once. Before. Once drawings were in the document register, metadata was per document. Correcting the Set on twenty drawings meant twenty edits. After. Select multiple register entries, tick the fields you want to change, type the new values, and apply. Unticked fields are left exactly as they are. Impact. Fixing a promotion mistake across a drawing set stops being a reason to avoid fixing it. Improvements A tender that never went ahead no longer counts as a loss User Story As an estimator, I had to file shelved projects as Lost, so I can now mark them Not Proceeding and trust my win rate. Before. Outcomes were Won, Lost and No Bid. A job that simply died, shelved by the client or defunded, had to go somewhere, and it went to Lost. Every dead project dragged the hit rate down, which made the number too soft to show anyone. After. Not Proceeding is available as an outcome once a tender has been submitted. It sits in its own status filter with its own value total, and it is excluded from the win rate denominator entirely. Impact. Win rate becomes a number you can put in front of a board. Bid and no bid analysis starts from a truthful base rather than one polluted by projects nobody ever won. A payment schedule sent back for revision now says so on the register User Story As a contract administrator, a revoked payment schedule dropped silently back to Draft as if it had never gone out, so I can now see that it went for approval and came back. Before. Revoking an internally approved payment schedule put it back in Draft. The register gave no clue that the schedule had ever been submitted, approved or reversed. The round trip existed only in the underlying data. After. Revoking or rejecting lands the schedule in Revise and Resubmit, an amber state on the register with its own filter option. While it sits there you can re certify individual lines, and the subcontract's cumulative certified position adjusts by the difference rather than double counting. Resubmitting runs a fresh approval chain against the new certified total, so crossing a delegation threshold re resolves to the right approver. Accept, dispute, edit and delete are all blocked while the schedule is parked, so re approval is the only way out. A new Activity tab in the schedule drawer shows the whole round trip, newest first, with the old and new values on any re certified line. Impact. The history of a contested certification is now visible to everyone who opens the record, which is the entire point of a payment schedule under security of payment legislation. No more schedules that quietly look like they were never submitted. Claim periods and payment schedule due dates fill themselves in User Story As a contract administrator, I hand typed dates the platform already knew, so I can now check a prefilled date instead of deriving it myself. Before. On a new progress claim, the claim date and due date prefilled but the claim period From and To were empty and required, so every claim meant hand typing two dates that were almost always just the month of the claim. On the Issue Payment Schedule modal, every field prefilled except the one with a statutory consequence: the due date. After. Claim period defaults to the first and last day of the claim date's month, and re derives if you change the claim date, unless you have deliberately edited it. Payment schedule due date derives from the subcontract's own payment terms applied to the claim's month, using the same calculation the subcontract record already displays. Both stay editable for a negotiated date. Impact. The payment clock now starts from the terms you agreed rather than from whatever someone typed at 5pm. Two records that should always match can no longer drift apart. Drawing review keeps your zoom, and you can drag to move around User Story As a contract administrator reviewing a drawing set, my zoom reset to 33% on every drawing, so I can now set it once and keep flicking. Before. Moving to the next drawing in the promote viewer reset the zoom. Getting back in meant repeated clicks on plus, and moving around the sheet meant using the scroll bars. After. Zoom persists across drawings for the session, you can type an exact zoom percentage, and you can click and drag to pan the drawing itself. Impact. Checking metadata against a set of thirty sheets stops being a fight with the viewer. Fixes Tender Register tiles update the moment you change a tender User Story As an estimator, I changed a tender's stage and the summary tiles kept showing the old numbers, so I can now trust what the top of the register tells me. Before. Changing a stage or outcome from the drawer or the tracker, or saving commercials, wrote to the database but left Live tenders, Closing this week, Submitted awaiting and Win rate showing pre change figures until a full page refresh. Worse, the update was sometimes applied to the wrong row entirely, and project name and address could drop off the updated tender until the next refetch. After. All four tiles and the list row recompute immediately on any tender change in your session, against the correct tender, with project details intact. Impact. The register stops lying to you between refreshes, and a stage change no longer risks quietly corrupting a different tender's row. Known limitations. Changes made by another user still require a refresh to appear. Folders in the document explorer sort by name again User Story As a contract administrator, my smart folders appeared in the order they happened to be created, so I can now find one by scanning alphabetically. Before. The smart folders list in the explorer's left pane had no ordering at all. New folders landed at the bottom regardless of name, and renaming one did not move it. Sitting directly above a correctly sorted folder tree, it read as if folders had simply lost their sort order. After. Smart folders sort naturally by name on load, on creation and on rename, so Set 2 comes before Set 10 rather than after it. Impact. A pane you scan dozens of times a day behaves the way you expect. Regression tests now cover it so it cannot silently drift again. The Client column on client payment schedules and invoices shows the client User Story As a contract administrator reconciling what a client owes, the Client column was always a dash, so I can now scan and filter by client. Before. Client Payment Schedules and Invoices (to Client) rendered a dash in the Client column on every row, even though each record pointed at a head contract and that head contract had a client. The Head Contract Register resolved it correctly, so the data was there and the join simply was not being followed. After. Client resolves through to the parent head contract on both registers, matching the Head Contract Register. Impact. On a workspace with several clients, that column is the only way to scan schedules by who owes you. It works now. Something here you would change, or something missing you need? Tell us through the feedback portal in the Deep Space web app. Every entry above started as someone telling us it was wrong.