Workspaces for the industries and teams using UtilityHub.
Start from a workspace when you want the sidebar, search, and tool list to stay aligned with one domain instead of showing the whole platform at once.
Start from a workspace when you want the sidebar, search, and tool list to stay aligned with one domain instead of showing the whole platform at once.
7 published workspaces are currently live across UtilityHub.
A focused technology workspace that keeps software delivery tools together so teams can search, transform, inspect, and review without starting from a generic utility catalog.
A focused mechanical workspace that keeps dimensional review, revision checks, and recurring calculations together so engineers do not have to jump through unrelated utility categories first.
A focused civil workspace that keeps drawings, quantities, hydraulics, and formula lookup in one browser-local home without dragging in unrelated utilities.
A focused electrical workspace that keeps load checks, cable sizing, conduit fill, panel schedules, and formula lookup in one browser-local home without the generic catalog noise.
A focused medical workspace that keeps handovers, report comparisons, and note de-identification together so clinicians see only the workflows that matter most.
A focused mining workspace that keeps shift handover, water-transfer checks, and revision review close to the field workflow without unrelated tools in the way.
A focused operations workspace that keeps handover notes, revision review, and redaction together so field teams do not need to sift through unrelated utilities.
UtilityHub is moving away from a flat catalog because context matters almost as much as the individual utility.
A civil user should not have to search through software delivery tools, and a platform engineer should not have to sift through engineering calculators, just to find the next step.
People usually think in review, sizing, handover, revision, or validation tasks. Workspaces make the shell and sidebar follow that mental model more closely.
Even when the total platform grows, each workspace should still feel like a focused toolkit rather than a giant undifferentiated directory.
These examples show why the workspace shell matters beyond simple navigation cleanup.
A platform or product team can stay inside formatters, inspectors, diff tools, API helpers, and delivery support tools without mixing those searches with engineering calculators or field handover utilities.
An engineering user can move between formulas, sizing checks, revision comparison, and handover support inside one smaller shell that feels closer to the real sequence of work.
As UtilityHub grows, workspaces help the site stay understandable for field, clinical, mining, and operations users who should not have to decode a developer-first catalog to find the next useful tool.
Short answers for teams deciding whether to start from a workspace or from the full catalog.
A workspace is a filtered version of the UtilityHub shell where navigation, search, and the visible tool set stay aligned with one domain or team context.
A flat catalog becomes harder to search and harder to trust as it grows. Workspaces reduce noise so people can find the next relevant tool faster.
No. Workspaces narrow the context for easier browsing, but the broader UtilityHub catalog, guides, and collections are still available when needed.