Skip to content

Industry Use Cases

Industry Use Cases

The fastest way to understand Norbital is to picture a full operational workflow, not an isolated feature. These examples show how a builder might combine collections, policies, hooks, apps, and automations into a working solution.

Patterns, not shipped templates
Each example below is an implementation pattern you can adapt — not a downloadable template. Norbital ships two starter workspaces today: hr-payroll and construction. Start from one of those or from scratch, then use these patterns for ideas.

1. Construction

Use case: project-centered operations with BIM visibility, workforce compliance, and commercial readiness

  • Model projects, work packages, issues, and workforce records as linked collections.
  • Use file fields for BIM models, inspection reports, and compliance documents.
  • Gate high-value mutations such as change orders behind multi-step approval workflows.
  • Use automations to check external compliance portals on a schedule.
  • Build an operations app with project dashboards and issue queues.

2. Creative Agencies

Use case: client approval workflows, freelancer payout reconciliation, and campaign reporting

  • Model campaigns, deliverables, freelancers, and invoices as collections.
  • Use approval workflows on client-facing deliverables before they are released.
  • Add file fields for creative assets that need client sign-off.
  • Build a client services app with campaign dashboards and approval queues.
  • Use hooks to notify account managers when approvals are pending.

3. Events & Exhibitions

Use case: exhibitor asset collection, vendor dispatch, and VIP request tracking

  • Create collections for events, exhibitors, vendors, and VIP requests.
  • Use apps with dedicated views for logistics, catering, and compliance.
  • Add automations to collect and verify exhibitor assets before deadlines.
  • Use hooks for on-site dispatch coordination and live issue tracking.
  • Build an event operations app with vendor status boards and dietary tracking.

4. Facility Management

Use case: automated PPM scheduling, mobile service reports, and tenant fault reporting

  • Model facilities, equipment, service contracts, and fault reports as collections.
  • Use automations for scheduled preventive maintenance triggers.
  • Add file fields for service reports, certificates, and compliance documents.
  • Use record labels that combine asset ID, location, and service status for readability.
  • Build a facilities app with maintenance calendars, fault queues, and contractor views.

5. Freight Forwarding

Use case: milestone tracking, quotation generation, and driver dispatch with ePOD

  • Model shipments, milestones, carriers, and quotations as linked collections.
  • Use automations to monitor shipment milestones and trigger status updates.
  • Use hooks to alert stakeholders when shipments approach critical checkpoints.
  • Add file fields for bills of lading, delivery orders, and proof-of-delivery documents.
  • Build an operations app with shipment status boards and driver dispatch views.

6. Manufacturing

Use case: digital job cards, production scheduling, and mobile QC tracking

  • Model work orders, equipment, QC checkpoints, and production batches as collections.
  • Build apps that group technical specs, QC results, and maintenance history.
  • Add approval workflows on production sign-offs and equipment maintenance requests.
  • Use file fields for CAD files, technical drawings, and inspection reports.
  • Build a shop floor app with job queues, equipment status, and defect tracking.

7. Wholesale Trade

Use case: command center dispatch, B2B customer ordering, and digital signature tracking

  • Model orders, customers, dispatch runs, and return requests as collections.
  • Use record labels that combine order number, customer name, and delivery status.
  • Add approval workflows on credit notes and high-value returns.
  • Use automations to check inventory levels and trigger reorder alerts.
  • Build a dispatch command center app with order boards, driver assignments, and return tracking.

How To Adapt These Patterns

  1. Start with the collection model and record labels.
  2. Add hooks for validation, side effects, and alerts.
  3. Shape apps for the people doing the work.
  4. Add automations and remote functions only where they add clarity.