Netvett · Sentinelborough\City of Westminster
UTC 20:12:32
Console home

Sentinel · feature a

Omni-Route CSV compiler AI clustering

Drop the borough's weekly care manifest (Postcode · Time · Duration). The AI clusters micro-visits into geographically efficient macro-routes for City of Westminster, ready to broadcast to the Pro-ID ledger. Verified carers see the routes on their Jobs board the moment you broadcast.

Netvett Sentinel · Feature A

Omni-Route CSV compiler

Drag in the borough's weekly care manifest (Postcode, Time, Duration). We cluster micro-visits into geographical macro-routes for City of Westminster so you broadcast to the ledger instead of routing by hand.

Download sample CSV
Concierge clusters

Drop Excel/CSV here, or choose a file

Postcode · time · duration (minutes)

Demo compiler runs in the browser. Production will persist manifests, recompute clusters with road-time estimates, and enqueue ledger broadcasts server-side.

AI-clustered output · demo preview

7 routes40 visits
RoutePostcodesVisitsDurationDensityDrive avg.
Route AlphaSW1A63h 0mHigh4m
Route BravoW1J–W1K94h 30mHigh3m
Route CharlieNW142h 0mMedium6m
Route DeltaW273h 30mMedium5m
Route EchoWC152h 30mMedium5m
Route FoxtrotSW763h 0mHigh4m
Route HotelNW831h 30mLow8m
AI clustering optimises for postcode contiguity + drive-time. The actual breakdown will refresh from your uploaded manifest.

Workflow · after broadcast

  1. 01

    Routes appear on the Jobs board

    Every verified health & social care Pro-ID sees the broadcast on their candidate dashboard. No agency filter, no gatekeepers.

  2. 02

    Staff click Apply

    The carer's dossier (DBS, RTW, references, training, witnessed credentials) is bundled and dispatched to the borough + the named client representative.

  3. 03

    Authorise interview

    The borough and client representative review and click "Authorise interview". The carer receives the meeting details for a private intro with the client.

  4. 04

    Hire

    If the client likes the carer, "Hire" confirms the assignment. The Pro-ID becomes the named provider for the package; the route locks to them in the ledger.

Phase 2 wires this workflow to the live vacancies + matching engines. Today the broadcast preview confirms the contract.