How Corridor works
From an unlisted farmhouse-with-a-yard to a NET-30 invoice paid by a Tier-1 EPC — six steps, all run through one operations layer.
- 01
Partner lists a housing + yard asset
A supply partner fills a structured spec — sleepsTotal, parkingType, parkingLoadRatingT (axle load), storageClass, fenced yard, three-phase, heavy-vehicle access, mess room — alongside photos and the monthly rate. The infrastructure spec, not the bedroom count, is what makes it filterable to EPC.
- 02
Compliance vault gets verified
The partner uploads insurance, public & employer liability, ISO 45001, gas/electrical, background checks, and food hygiene to a per-org vault. Platform staff verify each (with magic-number MIME sniffing so a renamed .txt can't pose as a PDF), and expiry dates drive a renewal queue.
- 03
Procurement browses by project & infrastructure
An EPC client filters live listings by country, nearby project type (offshore wind, data-centre, substation), secured-infra flags, and rate. The crew's project site is the anchor; distance-to-project is the sort key.
- 04
Accreditation opens the door
Before a partner can bid on a client's deployments, they must complete the client's approved-supplier accreditation cycle (6–12 months). Corridor tracks the cycle per client–partner pair, the required vault categories, and the target completion date, so the gating status is visible on both dashboards.
- 05
Deployment + booking requests
The client raises a deployment for a crew, allocates beds across the chosen sites, and sends booking requests. Partners accept, decline, or counter the monthly rate. Accepted requests become contracted bookings under the deployment.
- 06
Consolidated invoice + payouts
Corridor raises one NET-30 invoice rolling up every confirmed site — gross housing + infra, +13% enterprise take, +€750/site/mo SaaS fee, +19% VAT — computed by the same engine as the calculator. Per-partner payouts are minted at issue and accrue on the partner dashboard immediately.