Template examples

The fastest way to understand Norbital is to see a full operational workflow, not an isolated feature. These examples follow shipped starter workspaces and show how a builder combines collections, policies, hooks, apps, and automations into a working system.

1. Construction — project operations

Template: Construction

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.
• Carry inspection photos, RFI attachments, and claim evidence as file fields with per-record row predicates on your policy grants.
• Use automations to check external compliance portals on a schedule.
• Build an operations app with project dashboards and issue queues.

2. HR & Payroll — statutory compliance

Template: HR & Payroll

Multi-country HR and payroll from effective-dated employment facts:

• Keep employment, time, and leave as effective-dated records so history is queryable.
• Model statutory contribution rules as data, then compute payroll against them.
• Gate payroll runs and manual adjustments behind approvals.
• Use automations for scheduled payroll cycles and compliance checks.
• Build apps that answer “what does this employee’s pay look like this month” instantly.

3. CRM — quote to cash

Template: CRM

B2B quote-to-cash with revision history and financial flows:

• Keep customer-priced quotes with revision history as linked collections.
• Track fulfilment, invoicing, purchasing, stock, and payments in and out.
• Keep quote lines, invoicing, purchase orders, and stock changes in typed collections with field-level masks on the sales and finance policies.
• Use automations for invoice reminders and stock reorder points.
• Build apps for sales, fulfilment, and finance on the same live data.

4. Field Operations — dispatch and evidence

Template: Field Operations

Dispatch each day’s jobs from a weekly roster, then verify the work actually happened:

• Import the weekly roster and create that day’s job assignments in one pass.
• Contractors send photos and evidence from the field over WhatsApp; an agent files them against the day’s assignments.
• Gate variations to scope and budget behind approvals.
• Flag evidence that does not match the assigned site — a job claimed at the wrong site is flagged as suspect.
• Build field and office apps against the same live replica.

How to adapt these templates

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.
5. Scope policies to teams before going live.