🌐 Portals are Live - External coordination, built into the system that runs the project

Overview Construction projects do not fail because of what happens inside the builder's system. They fail because of what happens outside it. The RFI that sits in a consultant's inbox for four days. The document issued to the wrong revision because the subcontractor was working from an email attachment. The client who calls asking for a progress update because nobody sent one. Every touchpoint with an external party is a potential gap between what the project record says and what is actually happening on the ground. Most builders have solved the internal problem. The budget is tracked. The programme is managed. The delivery register is maintained. But the moment a subcontractor needs to raise a clarification, or a consultant needs to respond to an RFI, or a client wants to understand where their payment claim stands, the information leaves the system. It goes into email. It goes into spreadsheets. It goes into phone calls that nobody records. Portals bring it back. Subcontractors, consultants, and clients now operate inside dedicated, purpose-built environments connected directly to the live project record. Not a stripped-down version of the internal system. A separate, lightweight workspace built specifically for how each external stakeholder wants to work: log in, see what is relevant to them, respond, and move on. What This Release Delivers Three portals. Three stakeholder types. One project record. Three portal types are live at launch, each scoped precisely to a different external party with a different set of operational needs. The subcontractor sees delivery and commercial workflows. The consultant sees design coordination and quality. The client sees financial visibility without internal exposure. Nothing bleeds across. Subcontractor Portal Clarity for trade contractors, without the noise Trade contractors do not want to navigate a head contractor's project management system. They want to know what is open, what needs a response, and which documents apply to their scope. Everything else is noise that slows them down. The Subcontractor Portal Dashboard surfaces exactly that. Headline counts across every active category: RFIs (split by open and draft), Site Instructions, Action Items, Claims, Tenders, and Submittals. Below that, a Recent Activity feed shows the latest items across all categories in a single chronological view, so nothing sits unnoticed. An action item logged on 26 March, a Site Instruction issued on 21 March, an RFI raised on 17 March, all visible the moment the subcontractor logs in. The left navigation tells the full story of what a subcontractor can access: Site Instructions, RFIs, Photos, Action Items, Submittals, Workforce and Plant under Delivery, Claims under Commercial, Planning, Lookahead, and Weekly Work Plan under Program, and Documentation directly. Every module a subcontractor legitimately needs is present. The internal team's commercial controls, budget registers, and delivery management are not. When a subcontractor raises an RFI, it does not go into an email. It enters the structured register directly, timestamped, prioritised, flagged for programme and cost impact, and immediately visible to the internal commercial and delivery teams. The full technical description travels with it. The response thread stays attached. The resolution is on record. When subcontractors work inside a controlled environment, RFIs remain traceable, documentation stays version-controlled, and discussions stop disappearing into email chains. Across multiple projects running simultaneously, that discipline compounds quickly. Consultant Portal Design coordination inside the project record Consultants work across many contractors and many systems. The more friction in the access, the lower the quality and speed of their engagement. A consultant who has to dig through emails to find the right drawing revision, or who responds to an RFI in a separate thread that never makes it back to the project register, creates downstream risk for everyone. The Consultant Portal removes that friction entirely. The dashboard gives them an immediate overview of all activity relevant to their scope, structured identically to the subcontractor experience but scoped to their role. RFIs requiring response are visible immediately. Consultant Advice Notices, Clarifications, Reviews and Approvals, Certificates, and Meeting Correspondence each have a dedicated module. The left navigation under Quality gives consultants structured access to exactly the workflows their engagement requires. Responses to RFIs feed directly into the live project record. A Consultant Advice Notice issued through the portal sits in the project's documentation register immediately. A clarification response is timestamped and traceable. Design coordination becomes part of the same governed workflow as commercial and delivery, not a parallel activity managed through email that someone on the internal team has to consolidate later. Access Control Permission configured per role, per feature, per portal type Every portal is company-scoped, project-bound, and permission-controlled at the feature level. Access is not a binary on or off switch applied to a whole portal. Each role is configured feature by feature, giving the internal team precise control over exactly what each external stakeholder can see and interact with. Three role types are available: Client, Consultant, Subcontractor. Each is tagged with its portal type, making the permission structure immediately readable across the workspace. New roles can be created and configured without touching project-level settings. Commercial integrity is protected across every portal type. Internal financial data, budget modelling, and delivery controls are not accessible to any external role. The simplification does not come at the cost of control. Approvals and audit trails remain intact. That is the design. In Practice One project. Three external parties. Zero email archaeology. A head contractor running three concurrent commercial fitouts invites their electrical subcontractor into the Portal on the Riverside Business Park project. The subcontractor logs in, sees nine open Action Items and two open RFIs tied to their scope, and raises a clarification on distribution board capacity directly into the structured register. It is timestamped, flagged as high priority with programme and cost impact confirmed, and visible to the internal commercial and delivery teams within seconds. No email. No forwarding. No consolidation required. On the same project, the hydraulic consultant receives a notification about an RFI requiring their response. They log into their portal, navigate to the RFI under Documentation, review the full technical description and the attached drawings, and respond through the Correspondence tab. The response is tied to the live project record immediately. The internal team sees it without doing anything. The client logs into their portal to check where the latest payment claim stands. They see the claim status, the variations register, and the lookahead programme for the next four weeks. No internal cost model is visible. No separate report was prepared. The information was already there, structured, current, and exactly what they needed. External Invite -> Scoped Portal Access ->RFI / Document / Claim -> Live Project Record -> Internal Team Notified Why It Matters Coordination complexity scales faster than project count When a builder moves from two projects to five, the number of external parties does not double. It multiplies. Subcontractors across different trades. Consultants across different disciplines. Clients with different expectations of visibility and reporting cadence. Without a structured coordination layer, the administrative load becomes the project risk. Every untracked RFI is a potential dispute. Every document issued outside the register is a version control problem waiting to surface at the wrong moment. Every client update prepared manually across five jobs is time spent on administration instead of delivery. Portals bring external participation into the same governed environment as budgets, schedules, delivery registers, and HSEQ workflows. External stakeholders get simplicity. Internal teams retain control. The project record stays complete because the coordination that used to happen around the system now happens inside it. How It Fits Deep Space is no longer just internal Portals connect external participation directly to the same registers and workflows the internal team operates from. RFIs raised by subcontractors feed the RFI register. Documents accessed by consultants reference the project document register. Claims and variations visible to clients link to the commercial workflow. Deep Space has always been the system of record for the project. Portals extend that record to every party the project depends on. The builder stays in control of what each stakeholder sees. The project record stays intact. The coordination that used to happen in parallel, in email, in separate tools, now happens inside the same system that manages the work. What's Next V1 is live. The roadmap continues. This is the first full release of Portals and it is already operational across Subcontractor, Consultant, and Client environments. The foundation is in place for deeper workflow integrations, expanded external automation, tighter linkage to commercial events, and smarter per-stakeholder reporting visibility. Deep Space is no longer just where you manage projects internally. It is where your entire project ecosystem coordinates, without the chaos that usually comes with it.