What got shipped over the weekend - Your directory decides who gets the tender, and KAI reads the site forms

Published 21 September 2026 Features Default contacts: the directory decides who gets addressed As a contract administrator, I had no way to tell Deep Space which person at a subcontractor should receive a tender invitation, so every invite either went to one stale email on the company record or blasted the whole company. Now I flag the right people once on the contact list and Deep Space addresses them automatically, for tenders, accounts, documents and notices. Before "Primary contact" lived in five different places across the platform, and the addressing flows read the wrong ones. A tender invitation fell back to whatever single email was sitting on the company's directory record, or, failing that, went to every verified member of the company. The estimator you actually deal with was no more likely to receive it than anyone else, and there was nowhere to say otherwise. After Every contact on a company can now be flagged as a default for Tender, Delivery, Accounts, Documents, Notices or General. The flags show as green pills in a Default For column on the Company Directory, the Client Directory, the Contacts view and Project Settings, and you set them from the (i) contact card. It is a pool, not a single slot, so the estimator and the general manager can both be Tender defaults and both receive the invitation. One contact can hold several flags. Tender publishing now works down a clear chain: the person you nominated by hand, then the company's Tender defaults, then its General defaults, then the directory main contact, then every verified member as a last resort. The invite screen warns you with an amber chip before it ever reaches that last step. Impact Correspondence starts landing with the person who can act on it. An invitation to tender reaches the estimator instead of the accounts inbox, a payment schedule reaches accounts instead of the site manager, and the amber chip tells you which companies still need a default set before you find out the hard way. The flags are your workspace's own settings, so they never change a company's record for anyone else on Deep Space, and they steer addressing only, never anyone's access. How to use it Directory, Company Directory, open a company, Contacts tab, then the (i) button on a contact and Edit. Tick the areas that person should be the default for, and Save. Clients work the same way from the Client Directory. The Contacts tab on a company in the Company Directory. The Default For column shows each contact’s flags, here an estimator set as the default for both Tender and Accounts. KAI reads your DS Site forms and submissions As a project manager, checking whether a subcontractor had done their induction meant opening the register and scrolling, so I can now ask KAI in words and get the answer from the register itself. Before Site sign-ons, inductions, inspections, SWMS, permits, incident reports and dockets were filled in on DS Site and read back one register at a time. Answering "has anyone from this company inducted on this job" meant knowing which register to open and reading it yourself. After KAI can now read DS Site forms and submissions from the console at the foot of any Deep Space page. Ask which forms exist, what has been submitted and by whom, what a single submission says in full, or whether anything is missing. Filter by form, by submitter and by date range in plain language, and combine all three. KAI reads DS Site as you, using your own account, so you see exactly what your channel role allows and nothing more. Answers are scoped to the project you are in, and it answers from the register rather than from memory. If a form has no submissions for your project, it says so rather than guessing. Impact The safety and delivery paper trail becomes something you can interrogate in a sentence. "Which permits to work have been submitted, and who submitted them?" replaces a register hunt, and a clear "none" for a project and period is an answer you can act on rather than an empty screen you have to second-guess. Known limitations This is an alpha release. KAI reports that a field carries an attachment but does not open the file or return a download link, so open the submission in DS Site for that. Dates are strictly after or before the date you give, so "since 20 June" does not include the 20th. Large registers come back a page at a time. KAI reads these registers and never fills one in: it cannot submit, edit, approve or delete a form, and it cannot change anyone's DS Site access. Each workspace is linked to one DS Site channel and KAI will not read another. The KAI console open at the foot of the Site Inspections register, answering a question about which site diary entries were submitted on the project, who submitted them and when. Have something you want to see in Deep Space? Tell us through the feedback portal in the platform. We read every submission and a good number of the entries above started there.