Notices. Who asked, who answered, when. Replies thread themselves.

The formal paper trail of a project used to live everywhere except where you could find it. An RFI was an email. A client instruction was a PDF in someone's inbox. A notice to a subbie was a phone call you hoped you had written down. When a claim or a dispute came round, you went hunting through threads to reconstruct who asked what, who answered, and when. Notices replaces that. It is the formal communication register for a project: RFIs, Client Instructions, Site Instructions, Consultant Advice Notices, Notices to Subcontractor, all issued and tracked as proper records. Each one is a numbered document with its email, its timeline, and its response state attached. The register User story As a Project Manager, I never had a single view of which formal notices were still waiting on someone, so I can now open one screen and see exactly what is outstanding, who owns it, and what is due. Before Outstanding RFIs and instructions lived in your inbox and your memory. Working out what was still open meant scrolling email and asking around. After One register, organised by where the ball sits. Awaiting them shows what you have issued and are still waiting on. Awaiting me shows what has landed back with you to action. All, Closed, and Draft round it out. Each row carries a colour-coded type rail, a status, the owner, and how many days until or past due. Filter by type, sender, recipient, or due date. Impact You walk into a project meeting knowing the state of every formal notice without preparing for it. The moment a notice is answered, it drops out of your open queue on its own. Issue a notice, send a real email, get a numbered document User story As a PM, raising a formal RFI meant writing an email and hoping I would have a clean record of it later, so now I issue it once and end up with a numbered document, a PDF, and an email that goes out under my own name. Before A notice was an ad-hoc email. No canonical version, no number, no record of who opened it, nothing you could cleanly attach to a claim. After Pick the type, add recipients from the project directory, set the clause category and response date, write the question, and attach drawings straight from the project document store. On issue, the notice is numbered, a PDF is generated, and an email goes out to each recipient from your own address with your signature. Recipients do not need a Deep Space login to read it or reply. Impact One consistent way to raise any formal notice, and the output is claim-ready and audit-ready the moment it leaves your hands. The recipient gets a normal email; you get a tracked record. Replies thread back on their own User story As a PM, the answer to an RFI used to sit buried in my sent items while the register said nothing, so now the reply lands on the notice itself and the status updates without me touching anything. Before You would send the question, the answer would come back by email, and the two lived in separate inboxes. Keeping any register in step meant manually copying replies across, so it never stayed current. After When a recipient replies to the notice email, their answer appears on the notice timeline in full, and the notice transitions to responded automatically. The timeline shows the whole sequence in order: issued and delivered, opened, responded, and the reply body itself. Nobody re-keys anything into Deep Space. Impact The register reflects reality on its own. The notice becomes the single place the question, the answer, and the proof of when each happened all live, which is exactly what you reach for when a variation or a delay claim turns on who knew what and when. How to use it Open Correspondence → Notice on any project. The register loads on Awaiting them. Click any row to open the document, or + New notice to issue one. A beta shaped by your feedback Notices started as a problem you kept raising: the formal paper trail living in inboxes, phone calls, and memory. This is our first answer to it, and it's a beta on purpose, the bones are here and we're building outward. Still to come: the Overdue tab, and broader notice-type access (today it follows your project role). More will land. Keep the feedback coming. It's exactly how Notices got this far, and it's how we'll decide what's next. Deep Space · Construction runs better here · Published 5th June 2026