Skip to main content

OX Park & Node Parking Playbook

Quick context​

Parking and staging are infrastructure revenue streams — not sub-franchise products. Park-level parking is managed by the Master Franchisee; Node-level parking is owned/operated by the Node Partner (Master may lease node office/space). All bookings, invoices and settlements must flow through the OX Platform so revenue splits (Master / Node / Franchisor / Platform) are automatic and auditable.

1. Purpose & scope​

  • Provide secure, insured parking and staging for tractors, harvesters, trailers and linked service-provider vehicles.
  • Minimize asset idle time and create a monetizable facility (per-slot/day or monthly lease).
  • Act as an operations hub for operator handoffs, fuelling/refills (where permitted), minor checks and loading.
  • Integrate with OX Platform for booking, proof-of-arrival/departure, billing and automated settlement.

Fits into: OX Park (central hub) and OX Nodes (local spoke) as defined in the 4-Layer Network and Node Partner frameworks.

2. Where parking sits in the commercial model​

  • Asset owner: Master (Park); Node Partner (Node).
  • Operator: Asset owner operates day-to-day (Master or Node ops team).
  • Booking & payment: Customer or linked service provider books via Platform; Platform collects payment and settles to asset owner net of Platform/Franchisor fees.
  • Value drivers: location (near demand cluster), security, covered slots, add-on services (washing, minor service, fueling facilitation), priority booking.

3. Facility design & minimum specs​

Site & surface​

  • Graded, well-draining surface; paved for high-use Parks, compacted gravel acceptable for Nodes.
  • Clear bay demarcation with painted numbers and signage.
  • Loading/unloading zone separate from long-term parking.

Infrastructure​

  • Entrance gate with guard post & visitor log.
  • CCTV coverage: entry/exit + all bay aisles with 24/7 recording retention (30–90 days depending on legal/regulatory needs).
  • Lighting for night operations, safe walkways and marked vehicle lanes.
  • Drainage & oil/grit traps; fuel-handling area must be physically isolated and comply with local regulations.
  • Basic wash area, tyre inflation point and minor consumables storage (optional).

Safety & environment​

  • Fire extinguishers at intervals; spill kits for fuel/oil; MSDS for any hazardous consumables.
  • Perimeter fencing & controlled access; signage for safety PPE where needed.

4. SOPs — core operational workflows​

4.1 Check-in / Check-out (platform-integrated)​

Check-in (on arrival):

  1. Driver/Operator arrives and provides Booking Ref or Operator ID.
  2. Ops staff record vehicle ID, operator ID, odometer/hours reading, condition photos (front, rear, key damages) — upload to Platform.
  3. Assign bay number and issue slot pass (digital QR or printed).
  4. If pre-payment required, verify Platform payment; otherwise record post-pay arrangement in system.

Check-out (on departure):

  1. Driver returns with booking ref; Ops staff verify condition (take departure photos).
  2. Close booking on Platform — record any damage claims, extra services used (washing/repair), outstanding fees.
  3. Trigger invoice/credit note via Platform if adjustments required.

Notes: Photos and timestamped records are mandatory for dispute resolution and insurance claims.

4.2 Inspection & daily logs​

  • Daily bay inspection checklist (visual checks for leaks, damage, obstructions).
  • Weekly deep inspection: surface condition, drainage, signage, lighting.
  • Incident log: immediate entry of any safety or theft incidents with photos, witness statements and CCTV clip ID.

4.3 Add-on services​

  • Washing: track start/end times and materials used.
  • Minor services: include job card, parts used and operator sign-off. Major repairs must be offloaded to authorized Workshop Subs.
  • Fueling: if facilitating, ensure third-party fuel vendors comply with safety SOPs and have insurance; Master/Node must keep evidence of vendor compliance.

4.4 Security & access control​

  • Gate log for every entry/exit.
  • Restricted access to key control rooms and admin.
  • CCTV monitoring with daily person-in-charge (PIC) checks.
  • Night guard rota + emergency contact list.

5. Insurance, liability & compliance​

Insurance​

  • Asset owner must maintain:

    • Property insurance (assets & infrastructure)
    • Public liability insurance (third-party)
    • Goods-in-care custody cover OR clause clarifying owner’s liability limits for parked machinery (clearly communicated to customers)
    • If fueling offered → environmental liability & hazmat cover.

Liability & claims​

  • Platform photo evidence + logged condition reports are primary proof for claims.
  • Claims triage: Ops team logs claim → Master/Node loss control verifies → insurer claim submitted within SLA (e.g., 48 hours) → provisional settlement/hold managed by Platform escrow if needed.
  • Contract must state caps & exclusions (normal wear & tear, pre-existing damage).

Compliance​

  • Local municipal rules for vehicle parking & fuel storage.
  • Environmental rules for waste oil disposal.
  • Worker safety laws for staff handling machinery.

6. Staffing & roles​

  • Parking Manager (Park / Node-level) — overall P&L & operations for parking.
  • Shift Supervisors / Gatekeepers — check-in/out, daily logs, incident reporting.
  • Security Guards — maintain perimeter & night watch (rotational).
  • Service Coordinators — manage washing, minor service scheduling and vendor coordination.
  • Finance / Reconciliation (shared) — reconcile booked revenue, incident reserves, settle with Platform reports.

Headcount depends on scale: pilot Park (10–20 slots) may need 1 manager + 2 gate staff + 2 guards; scale up for larger yards.

7. Pricing model & examples (pilot ranges)​

Use pilot ranges; tune after 90 days.

  • Per-slot / per-day: ₹20–200 / day (varies by facility quality, location and demand).
  • Priority / covered slot: +20–50% premium.
  • Monthly lease (contractor): ₹2,500–30,000 / month per slot depending on demand & locality.
  • Washing: ₹50–500 per wash (size/type dependent).
  • Minor service / inspection fee: ₹100–1,000 per job-card (parts extra).
  • Damage deposit or escrow: optional security deposit for long-term parked machinery (refundable).

All prices shown on Platform; taxes and Franchisor/Platform fees applied as per settlement rules. These are pilot bands — adjust in local pricing strategy. (See settlement flow below.)

8. Platform integration & settlement flow​

Booking flow​

  1. Customer / service provider searches for nearest Park/Node slots on Platform → selects date/time & slot type → pays via Platform payment gateway OR chooses pay-on-arrival with pre-authorization hold.
  2. Platform creates booking record with booking ref & ETA; asset owner sees slot inventory in dashboard.

Onsite flow & proof​

  • Ops staff scan QR or enter booking ref → Platform records check-in photos & timestamps.
  • On departure, Platform stores checkout photos & finalizes booking.

Settlement​

  • Platform calculates gross booking value → deducts Platform fee and Franchisor royalty → settles net to asset owner per configured schedule (T+1/T+2).
  • For claims/disputes, Platform places disputed amount in escrow per SOW until resolution.
  • Node Master rent flows: if Master uses Node office or Node parking, Master pays Node Partner via Platform invoicing or monthly settlement per Facility Agreement.

9. KPIs & SLAs​

Operational SLAs

  • Check-in time: ≤ 10 minutes from arrival (for pre-booked).
  • Condition photo & record: mandatory at check-in/out (0% exceptions).
  • Incident report to Master Ops: within 1 hour of discovery.

Performance KPIs

  • Parking utilization rate (% slots occupied) — target ≥ 60% in first 90 days in pilot (adjust per market).
  • Average revenue / slot / day.
  • Incident rate (security/claims) per 1000 slot-days — target ≤ 1% in pilot.
  • Claim resolution time — median ≤ 14 days.
  • Platform reconciliation accuracy — target ≥ 99%.

10. Revenue splits, accounting & taxes​

  • Platform implements settlement splits configured in the Franchise System (Master/Node/Franchisor/Platform).
  • Asset owner invoices platform or relies on platform ledger to receive automated settlements; monthly P&L reconciliations required.
  • Taxes: GST (or local tax) applicability depends on nature of service (parking, storage, service) — confirm with finance / local tax advisor.

11. Launch checklist — Parking (step-by-step)​

Pre-launch (site & legal)​

  1. Confirm site control (ownership/lease) and land-use permissions.
  2. Conduct environmental & safety checks (drainage, fire safety).
  3. Install perimeter fencing, lighting and CCTV; set up gate & visitor log points.
  4. Demarcate bays, number signage and prepare admin kiosk.
  5. Put in place insurance policies (property, liability, goods-in-care).
  6. Finalize pricing & slot inventory on Platform; configure booking cadence & cancellation rules.

Operational readiness​

  1. Hire Parking Manager & gate staff; train on SOPs.
  2. Run check-in/check-out drill with mock vehicles and platform bookings (7-day simulation).
  3. Validate CCTV footage retention & retrieval workflow for claims.
  4. Test incident and claims workflow with sample mock incident and insurer notification.

Pilot (first 14–30 days)​

  1. Open with limited slots (10–20) and limited hours (e.g., 08:00–18:00).
  2. Monitor bookings, utilization, reconciliation and customer feedback daily.
  3. Conduct weekly finance reconciliation and incident review meetings.
  4. Adjust pricing & add-on services based on demand.

Scale (post-pilot)​

  1. Increase slots, extend hours, offer monthly leasing to contractors.
  2. Add value-add services (washing, priority slots, minor service bay) if utilization supports margins.
  3. Implement longer-term hiring plan & security schedules for night operations.

12. Incident & dispute handling (template steps)​

  1. Immediately secure site & evidence (photos, CCTV clip ID).
  2. Log incident in Platform with booking ref and parties involved.
  3. Notify Master Ops & insurer within SLA (e.g., 24 hours).
  4. Hold disputed amount in Platform escrow if claim value > threshold.
  5. Investigate, obtain witness statements and estimate damages.
  6. Decide provisional payment (repair/replacement) per facility SOW and insurer guidance.
  7. Close claim and release escrow or raise contra-invoice as needed.

13. Sample templates (to copy & adapt)​

  • Check-in form fields: Booking Ref | Vehicle ID | Operator ID | Arrival time | Bay no. | Condition photos (3) | Pre-existing damage notes | Staff initials.
  • Check-out form fields: Booking Ref | Departure time | Condition photos (3) | Damage noted? (Y/N) | Extra services used | Final invoice ref.
  • Incident report: Date/time | Bay no. | Booking Ref | Parties involved | CCTV clip ID | Photos | Initial assessment | Actions taken | Claim ref.
  • Parking invoice line-items: Slot charge, Add-on (wash/service), GST (applicable), Platform fee (separately captured), Net settled.

14. Practical recommendations & pilot focus​

  • Start with a small slot count and strong ops discipline (photos + timestamps) — evidence reduces disputes.
  • Automate settlement & reconciliation with Platform exports; reduce manual invoicing.
  • For fuel or hazardous services, prefer third-party vetted vendors with documented insurance & safety compliance.
  • Maintain transparent T&Cs for customers listing owner liability caps and claim process.

15. Next deliverables I can prepare (pick one)​

  • Short Master ↔ Node Parking Facility Annex (sample lease + SLA + pricing schedule).
  • Incident & claims template pack (printable forms + platform JSON payloads).
  • Pilot pricing & revenue model spreadsheet (per-slot P&L calculator).

Tell me which of the three you want first and I’ll generate it immediately.