Skip to main content

Cluster Boundary Checklist

This checklist expands the minimal list into concrete tasks, owners, required documents, timelines, acceptance criteria, and platform fields to populate.

A. Pre-launch (T-90 to T-7 days)​

  1. Obtain official taluk boundary & village list

    • Owner: Master Franchisee / Legal
    • Documents: Government taluk map (PDF), village list CSV, taluk code
    • Timeline: T-90 days
    • Acceptance: Taluk boundary file uploaded to OX Platform; village list matches government source.

  2. Finalize OX Park location & land documentation

    • Owner: Master Franchisee / Node Partner
    • Documents: GPS coordinates, land ownership/lease agreement, site photos
    • Timeline: T-60 days
    • Acceptance: Land deed/lease uploaded; site passed site-readiness checklist.

  3. Platform cluster record creation

    • Owner: Platform Ops
    • Platform fields to populate: ClusterID, TalukCode, ParkGPS, ParkLandDoc, VillageListRef, DefaultSettlementRules
    • Timeline: T-45 days
    • Acceptance: Cluster record exists and is accessible by Franchisor and Master roles.

  4. Plan Nodes, Booking Centers & Outposts

    • Owner: Master Franchisee
    • Documents: Node location list + GPS, Booking Center operator details, tentative Outpost list
    • Timeline: T-45 days
    • Acceptance: Node and Booking Center list uploaded; distance validations (nodes within 10–15 km of Park; Booking Centers ≤5–7 km to local villages) pass.

  5. Procurement & Dark Store setup plan

    • Owner: Master / OX Inputs / OX Spares
    • Documents: Dark store capacity plan, SKU list, replenishment schedule
    • Timeline: T-30 days
    • Acceptance: At least one Node or Booking Center stocked for pilot SKUs; replenishment SLA agreed.

  6. Sub-franchisee pre-selection & training plan

    • Owner: Master Franchisee
    • Documents: Candidate list, KYC docs, proposed Sub agreements, training curriculum
    • Timeline: T-30 days
    • Acceptance: X pilot Subs approved by Franchisor and enrolled in training.

  7. Banking & Settlement setup

    • Owner: Platform Ops / Finance
    • Documents: Master bank details, tax registrations, settlement account setup
    • Timeline: T-21 days
    • Acceptance: Settlement flows tested in sandbox; settlement schedule configured.

  8. Regulatory & compliance checks

    • Owner: Legal / Master
    • Documents: Local licences, environmental clearances (if required), insurance proof
    • Timeline: T-21 days
    • Acceptance: All mandatory licences uploaded and verified.

B. Launch Week (T-7 to Launch Day)​

  1. Hardware & Connectivity readiness

    • Owner: Platform Ops / Master
    • Documents: POS device list, internet provider confirmation, power backup plan
    • Timeline: T-7 days
    • Acceptance: POS devices paired in platform; connectivity stress-test completed.

  2. Training & SOP sign-off

    • Owner: Master / Franchisor
    • Documents: Training attendance sheets, SOP ack forms
    • Timeline: T-5 days
    • Acceptance: All pilot Subs and Node staff complete mandatory training and acknowledged SOPs.

  3. Mock transactions & settlement test

    • Owner: Platform Ops / Finance
    • Documents: Test transaction logs, settlement reconciliation report
    • Timeline: T-3 days
    • Acceptance: End-to-end transaction flow (booking → payment → settlement) passes QA.

  4. Pilot marketing & farmer outreach

    • Owner: Master / Marketing
    • Documents: Outreach plan, demo event schedule, FPO/co-op contacts
    • Timeline: T-3 days
    • Acceptance: At least Y farmers registered for pilot events; contact list uploaded.

C. Launch Day (T=0)​

  1. Go-live checklist

    • Owner: Master / Platform Ops / Franchisor (observer)
    • Tasks: Enable cluster on platform, activate pilot Subs, open booking channel, start dark-store replenishment
    • Acceptance Criteria: Bookings visible in platform ledger; first bookings processed successfully; at least one fulfillment executed.

  2. Operational monitoring (first 72 hours)

    • Owner: Master / Platform Ops
    • Checks: Service response time, failed bookings, payment exceptions
    • Acceptance: No critical exceptions (>1% failed bookings) and SLA response times within configured thresholds.

D. Post-launch Stabilization (T+1 to T+90 days)​

  1. Weekly reconciliation & ops review (first 4 weeks)

    • Owner: Master / Finance / Platform Ops
    • Documents: Weekly settlement report, discrepancy logs
    • Acceptance: Settlement mismatches <0.5% after reconciliation.

  2. Inventory & dark-store tuning

    • Owner: Master / OX Inputs / OX Spares
    • Tasks: Adjust SKUs, reorder points, lead times based on demand
    • Acceptance: Dark-store fill rate >90% for pilot SKUs.

  3. Sub & farmer feedback loop

    • Owner: Master / Franchisor
    • Tasks: Collect NPS, fix critical SOP gaps, retrain if needed
    • Acceptance: Farmer NPS ≥ target (configurable) and reduction in operational complaints month-over-month.

  4. Performance review & scale decision (T+90 days)

    • Owner: Franchisor / Master
    • Criteria: GMV targets, SLA compliance, farmer adoption, inventory KPIs
    • Decision: Green (scale), Amber (optimize + extend pilot), Red (pause & remediate)

E. Platform Fields to Populate (minimum)​

  • ClusterID, TalukCode, ClusterName
  • ParkGPS, ParkLandDocRef, ParkCapacity
  • NodeList: [Node ID, GPS, Capacity, HostName]
  • BookingCenters: [CenterID, VillageName, OperatorID, GPS]
  • Outposts: [OutpostID, GPS, Seasonality]
  • VillageListRef (official village code list)
  • SurveyNumberMapping (land -> SurveyNo -> Owner)
  • MachineryInventory: [MachineID, Type, Owner, BaseNode, SerialNo]
  • SubFranchiseeRoster: [SubID, ServiceType, KYCRef, ApprovedBy, ActivationDate]
  • SettlementAccountRefs (Master, Subs)
  • SLA Configs (response_time_minutes, max_distance_km)

F. KPIs to Monitor (first 90 days)​

  • Territory GMV (monthly)
  • Active Subs (count) & activation rate
  • On-time service fulfillment (% within SLA)
  • Dark-store fill rate (% for pilot SKUs)
  • Farmer NPS
  • Average platform settlement accuracy (% matched transactions)
  • Avg response time for machinery requests (minutes)

G. Sign-off​

  • Master Franchisee Representative: __________________ Date: _________
  • OX Franchisor Representative: _______________________ Date: _________
  • Platform Ops Representative: ________________________ Date: _________