Northbank TowerAdmin setup
Sign in
Mock setup: Sign in as a site manager to load and save setup through the spine.

Site onboarding

Enter assets, paths, constraints, and readiness rules.

Admins can define the operating model that booking will use: capacity assets, movement paths, release constraints, rollout surfaces, and tenant-specific defaults.

Test booking path

Site profile intake

Admin-entered site setup.

Enter the operating assumptions that booking will use later: site identity, default path, readiness model, and rollout state. Saved capacity assets feed the booking availability model.

UnsavedSign in as a site manager to load and save setup through the spine.
Capacity assets
4
Path nodes
6
Readiness gates
4
Rollout links
3

Add capacity asset

Dock, lift, gate, lane, staging area.

Add path node

Sequence the booking movement path.

Add readiness rule

Define release gates and holds.

Add rollout link

Set audience-specific setup surfaces.

Add customization

Capture site-specific defaults.

Generated setup preview

Northbank Tower

Dock A -> Goods Lift 2 -> Basement ramp is the default tenant path. The setup model keeps asset capacity, path handoffs, and readiness rules in one operational configuration.

Code
NBT-SYD
Rollout
Internal setup
Readiness
Capacity first, readiness before release

Capacity assets

Asset limits drive slot recommendations.

4 mapped
Dock APrimary dock
Ready
Capacity
2 medium rigid turns per hour
Limits
3.4m clearance, 7m bay, no tailgate overhang
Readiness dependency
Marshal required above 70% load
Dock BShared service lane
Review
Capacity
1 small rigid or van turn per hour
Limits
Street queue cap: 2 vehicles
Readiness dependency
Security confirms street hold before release
Goods Lift 2Vertical path
Ready
Capacity
45 minute hold with 10 minute buffer
Limits
2.4m x 1.6m x 2.2m, blanket required
Readiness dependency
Lift booking locks when COI and crew count pass
Forecourt GateArrival control
Review
Capacity
1 active check-in, 1 standby
Limits
No staging before booked window
Readiness dependency
Driver mobile and rego required for SMS release

Path graph

Every booking moves through explicit handoffs.

6 nodes
  1. 01
    Street holdQueue buffer

    No early arrival before T-15

    Security confirms vehicle
  2. 02
    Forecourt GateReadiness gate

    Release only when driver, rego, and COI pass

    Gate sends arrival event
  3. 03
    Dock ACapacity asset

    One active unload per bay

    Marshal starts path
  4. 04
    Goods Lift 2Vertical hold

    Lift buffer attaches to path booking

    Tenant floor contact confirms access
  5. 05
    Basement rampMovement path

    No lobby crossing, no noisy works after 15:00

    Installer clears freight
  6. 06
    CloseoutException check

    No-show and overstay require reason code

    Manager closes path

Readiness rules

Release controls stay configurable.

Gate
COI before releaseTenant and vendor readiness

Any booking with external crew

Gate SMS stays blocked until certificate is valid
Gate
After-hours manager approvalCapacity exception

Window starts before 07:00 or after 18:00

Booking enters Awaiting Approval with SLA timer
Gate
High-load marshalDock path capacity

Dock load exceeds 70% or two active paths overlap

Marshal asset becomes required path dependency
Hold
Driver identity gateArrival readiness

Driver mobile or rego missing at T-60

Tenant gets readiness hold and reminder

Rollout surfaces

Each audience gets a setup link.

Customization controls

Site rules are visible before live writes.

Slot duration40m default, 10m buffer

Furniture and joinery paths expand to 60m when lift load is high

Approval cutoff15:00 prior business day

Late requests stay possible but use exception approval

Tenant overridesOps-only

Tenants can request exceptions; managers own final capacity decisions

Notification cadenceT-24h, T-2h, T-60m

Readiness holds suppress gate release until missing fields pass