What Got Shipped Today - 14/10/26 - Notices you can settle by hand, approvals within your own authority, and cost code pickers that stay on budget

Published: 14 October 2026 Features Settle a notice when the answer arrives off-platform User Story As a project manager, I issued an RFI to five companies and got my answer at a site meeting, so I can now record that answer, drop the companies that never needed to reply, and move the RFI on without waiting for emails that will never come. Before Every company on the To line had to reply by email before an RFI or other notice moved to Responded. Your own colleagues landed on To by default, so your own company was "awaited" too. If the answer came by phone, at a site meeting or through the client's portal, the only way out was to close the notice. After The issuer now has a Change status menu on every notice. Mark responded records an answer that came in outside the platform: pick the company, write how the answer arrived (a note is required), and the timeline shows it with a manual badge. Not required moves a company from To to For information with a reason, no email sent, and once everyone else has answered the notice settles to Responded on its own. In the composer, people from your own company now default to FYI, and other companies to To. Works across RFIs, submittals, contract and site instructions, and the other notice types. Impact Notice registers reflect what actually happened on the job, every manual change carries who, when and why, and RFIs stop sitting on "awaiting" because someone was copied in. (1) Mark responded records an answer received outside the platform. (2) Not required waives a company that no longer owes a response. Both ask for a reason that lands on the timeline. Known limitations Only users from the issuing company can change status. Reopen is coming next. Approvals skip the steps you already have authority for User Story As a project manager with a $50k PO limit, I raise a steady stream of small POs, so I want the ones inside my own limit to approve themselves instead of waiting on me to approve my own work. Before Every record went through the approval workflow, even when the person who raised it was an eligible approver with a limit that covered the amount. They either approved their own submission (an extra click and notification) or it was routed past them. After A new workspace setting on Delegation of Authority, Auto-approve within submitter's authority. When it is on and the submitter's own limit covers the amount, those approval steps are satisfied automatically and written to the audit trail. Steps above their limit still route to the next approver as normal. It applies to POs, subcontracts, variations, claims, head contracts, payment schedules, tender recommendations and invoices. Off by default. Impact Routine commitments get issued the moment they are raised, approvers only see the decisions that need them, and the audit trail still shows the step was authorised. (1) The new Auto-approve within submitter's authority setting on the Delegation of Authority page. It is off until you switch it on. Known limitations Turning this on relaxes segregation of duties for amounts within each person's limit, so check it fits your approval policy first. KAI builds the subcontract claim from the claim schedule User Story As a contracts administrator, subbies send a one-line invoice with a detailed claim schedule attached, so I want the draft claim built from the schedule's lines rather than keying them in by hand. Before KAI read the invoice. Most subcontractor invoices are a single line ("Progress claim 4, $36,000"), so the draft subcontract claim had one line and someone keyed in the real breakdown from the claim schedule. After When an invoice and a claim schedule arrive in the same email, KAI keeps the invoice as the invoice and builds the draft claim lines from the claim schedule, mapped to the schedule of values and variation lines. The invoice total is used as the control total against the schedule. If only an invoice arrives, nothing changes. Impact Draft claims land with the right lines already in place, ready for site to check and certify. (1) The invoice and the claim schedule arrive together. (2) KAI notes the lines come from the claim schedule, with the invoice total as the control. (3) Each schedule line is mapped to its SoV or variation line. (4) The retention row is recognised as not claimable and left out. (5) The claim total matches the invoice. Improvements Cost code pickers start with this project's budget codes User Story As a commercial manager, I was scrolling past a hundred workspace cost codes and $0 cost centres to code a line, so I now see only the codes in this project's budget, with the full list one tick away. Before Most cost code pickers listed every code in the workspace, including cost centres and codes the project had no budget for. After Link budget lines on the head contract SoV, Add SOV Item on subcontract variations, and purchase order lines now default to the cost codes in this project's Budget Register. A Show all cost codes tick box brings back the full list, a code already on the record always shows, and a project with no budget yet still shows everything. Impact Faster coding, and far fewer lines coded to something that is not in the budget. Site Photos: grouped by the day they were taken, and moved between albums in one step User Story As a site manager, several of us upload from our camera rolls days later, so I want photos grouped by when they were taken and to be able to tidy albums without doing it twice. Before Photos were grouped by the day they reached Deep Space, so a batch uploaded on Friday all landed on Friday. Moving photos meant Add to album, then opening the old album and removing them. After Photos with capture data are grouped and sorted by the date they were taken, with existing photos backfilled. Photos without it fall back to the upload date as before. Inside an album, select photos and choose Move to album to move them to another album, or a new one, in one action. Large selections are handled in batches. Impact The timeline reads like the job did, and sorting a big unclassified album is a few clicks. (1) Inside an album, select photos and use Move to album to move them in one step. Download a whole folder, subfolders and all, as one ZIP User Story As a document controller, I need to hand over a full folder of drawings, so I want one download that includes every subfolder. After Project and Company Documents can now download a whole folder, with its subfolders, as a single ZIP. Selections over 100 files now download instead of failing. Impact Handovers and tender packs go out in one download instead of folder by folder. Open the Document Register to every subcontractor on the project User Story As a builder, I want every trade on the job to see the current registered documents in the portal, without adding each one to every distribution list. After A new switch in Project Settings, Advanced, Document Register: "All subcontractors with portal access to this project can open registered documents". When it is on, any subcontractor with portal access to the project can open every registered document. Register update emails still go only to the distribution list. Off by default. Impact Trades always work from the current set, and document control has one less list to maintain. (1) Project Settings, Advanced. (2) The new Document Register switch opens every registered document to subcontractors with portal access to the project. Off by default. What the subcontractor sees in the portal once it is on. (1) Document Register tab. (2) Every registered document can be viewed and downloaded, not just the ones transmitted to them. People and company lists sort A to Z, with sortable headers After The User Directory and the Project Settings Team lists (including External Stakeholders) now sort A to Z by default, and column headers can be clicked to sort. Impact Finding a person or company in a long list takes seconds. Fixes Attachments on Outlook-forwarded emails now show in the Project Inbox Real attachments on emails forwarded from Outlook were treated as inline images and hidden. They now show as attachment chips in the thread view, signature and embedded images stay hidden, and the paperclip in the grid matches. Emails already affected have been corrected. Published site inspection exports include observation photos The exported PDF of a published site inspection now includes the photos attached to each observation. (1) The published inspection PDF now carries each observation's photos under its details. Site Photos tidy-ups Photos uploaded in the Deep Space web app now show who uploaded them instead of "Unknown user". Transparent images print on a white background in the photo PDF report, and a missing thumbnail no longer leaves a broken tile or album cover. Have feedback or an idea? Share it through the feedback portal in the platform. We read every one.