{
  "version": 15,
  "schemaVersion": "1.0",
  "asOf": "2026-10-18",
  "title": "Own plot physical survey & site-visit checklist",
  "summary": "The commercial brief is recorded; physical and statutory feasibility is not yet established. Use this section to commission the visit, capture evidence and resolve parcel-specific gaps.",
  "site": {
    "name": "Proposed Upper Kharadi project",
    "latitude": 18.551876,
    "longitude": 73.966402,
    "pinUrl": "https://maps.app.goo.gl/srjt3WC34J2pqmTUA",
    "coordinateStatus": "user_provided_reference",
    "parcelIdentity": null,
    "measuredLandAreaSqm": null,
    "boundaryGeoJSON": null,
    "surveyDate": null,
    "fieldSurveyComplete": false,
    "buildabilityVerified": false,
    "developmentSaleableSqft": 2500000,
    "targetSaleableSqft": 1000000
  },
  "statusLegend": [
    {
      "id": "user_provided",
      "label": "User provided",
      "meaning": "Accepted brief or location input; not independently surveyed."
    },
    {
      "id": "planning_assumption",
      "label": "Planning assumption",
      "meaning": "Editable commercial/design model; not sanctioned or measured."
    },
    {
      "id": "not_established",
      "label": "Survey / document verification needed",
      "meaning": "No supported own-plot value is available."
    },
    {
      "id": "document_unmatched",
      "label": "Document match unresolved",
      "meaning": "Archived document exists, but does not yet establish a fact for our parcel."
    },
    {
      "id": "different_site",
      "label": "Different site — excluded",
      "meaning": "Known separate site; no permissions or dimensions transferred."
    },
    {
      "id": "not_reviewed",
      "label": "Not reviewed",
      "meaning": "Catalogued source has not been read in a usable format."
    }
  ],
  "prefills": [
    {
      "id": "pin",
      "label": "Supplied site reference",
      "value": "18.551876° N, 73.966402° E",
      "rawValue": {
        "latitude": 18.551876,
        "longitude": 73.966402
      },
      "status": "user_provided",
      "sourceId": "USER-SITE",
      "sourceTitle": "User-supplied site map pin",
      "sourceDate": null,
      "scope": "Use to locate the visit and catchment. Surveyor must tie this point to a named parcel and measured boundary."
    },
    {
      "id": "development",
      "label": "Development brief",
      "value": "25 lakh sq. ft. saleable",
      "rawValue": 2500000,
      "status": "user_provided",
      "sourceId": "USER-AREA",
      "sourceTitle": "Accepted project and launch area basis",
      "sourceDate": "17 Oct 2026 model snapshot",
      "scope": "Commercial planning brief only; not land area, FSI area, sanctioned built-up area or measured capacity."
    },
    {
      "id": "launch_target",
      "label": "Launch sales target",
      "value": "10 lakh sq. ft. saleable",
      "rawValue": 1000000,
      "status": "user_provided",
      "sourceId": "USER-AREA",
      "sourceTitle": "Accepted project and launch area basis",
      "sourceDate": "17 Oct 2026 model snapshot",
      "scope": "Sales scenario target on the same saleable basis; it does not establish a physically approvable release."
    },
    {
      "id": "area_rule",
      "label": "Planning area convention",
      "value": "RERA carpet + exclusive terrace",
      "rawValue": null,
      "status": "planning_assumption",
      "sourceId": "MODEL-AREA",
      "sourceTitle": "Accepted loading and preliminary design assumptions",
      "sourceDate": "17 Oct 2026 model snapshot",
      "scope": "Keep RERA carpet, terrace, balcony, land area and FSI calculations as separate fields."
    },
    {
      "id": "loading",
      "label": "Standardized comparison loading",
      "value": "40% over developer planning carpet",
      "rawValue": 40,
      "status": "planning_assumption",
      "sourceId": "MODEL-AREA",
      "sourceTitle": "Accepted loading and preliminary design assumptions",
      "sourceDate": "17 Oct 2026 model snapshot",
      "scope": "Editable preliminary model; not proof of competitor loading or statutory FSI entitlement."
    },
    {
      "id": "own_terrace",
      "label": "Own exclusive terrace assumption",
      "value": "0 sq. ft. in current preliminary types",
      "rawValue": 0,
      "status": "planning_assumption",
      "sourceId": "MODEL-AREA",
      "sourceTitle": "Accepted loading and preliminary design assumptions",
      "sourceDate": "17 Oct 2026 model snapshot",
      "scope": "Unapproved design assumption; replace only after the architect supplies a matched unit-area schedule."
    },
    {
      "id": "survey_identity",
      "label": "Village / survey / hissa / CTS numbers",
      "value": "Not established",
      "rawValue": null,
      "status": "not_established",
      "sourceId": "SITE-AUDIT",
      "sourceTitle": "Existing site-linkage and evidence-gap audit",
      "sourceDate": "2026-10-15",
      "scope": "Obtain exact revenue village, taluka and parcel identifiers before applying any permission."
    },
    {
      "id": "boundary",
      "label": "Measured parcel boundary and land area",
      "value": "Not established",
      "rawValue": null,
      "status": "not_established",
      "sourceId": "SITE-AUDIT",
      "sourceTitle": "Existing site-linkage and evidence-gap audit",
      "sourceDate": "2026-10-15",
      "scope": "No verified closed own-plot polygon or measured land-area reconciliation is available."
    },
    {
      "id": "access",
      "label": "Legal access and approach width",
      "value": "Not established",
      "rawValue": null,
      "status": "not_established",
      "sourceId": "SITE-AUDIT",
      "sourceTitle": "Existing site-linkage and evidence-gap audit",
      "sourceDate": "2026-10-15",
      "scope": "Measure physical carriageway and right-of-way separately; obtain documentary access rights."
    },
    {
      "id": "levels",
      "label": "Topography, datum and drainage levels",
      "value": "Not established",
      "rawValue": null,
      "status": "not_established",
      "sourceId": "SITE-AUDIT",
      "sourceTitle": "Existing site-linkage and evidence-gap audit",
      "sourceDate": "2026-10-15",
      "scope": "No signed own-site topographic survey, benchmark or contour dataset is established."
    },
    {
      "id": "authority",
      "label": "Planning authority / zoning / FSI / height",
      "value": "Not established",
      "rawValue": null,
      "status": "not_established",
      "sourceId": "SITE-AUDIT",
      "sourceTitle": "Existing site-linkage and evidence-gap audit",
      "sourceDate": "2026-10-15",
      "scope": "Do not infer jurisdiction from neighborhood name, competitor permission or the unmatched S. No. 39 package."
    },
    {
      "id": "survey39",
      "label": "S. No. 39 document package",
      "value": "Available in archive; plot match unresolved",
      "rawValue": null,
      "status": "document_unmatched",
      "sourceId": "BRO-11",
      "sourceTitle": "S. No. 39 demarcation drawing",
      "sourceDate": null,
      "scope": "Demarcation, DP, zoning, height and valuation sheets are a document-matching lead, not own-plot facts."
    },
    {
      "id": "northern_site",
      "label": "Northern land-opportunity drawings",
      "value": "Different site; excluded from own-plot facts",
      "rawValue": null,
      "status": "different_site",
      "sourceId": "BRO-00",
      "sourceTitle": "Building permission for a separate land opportunity",
      "sourceDate": "2023-08-04",
      "scope": "Archived reference coordinate is about 2.128 km north by straight-line calculation. Do not transfer its permissions or dimensions."
    },
    {
      "id": "plot2d",
      "label": "Mundhwa Plot 2D drawing",
      "value": "Available in archive; plot match unresolved",
      "rawValue": null,
      "status": "document_unmatched",
      "sourceId": "BRO-19",
      "sourceTitle": "Mundhwa Plot 2D layout",
      "sourceDate": null,
      "scope": "Do not transfer the drawing’s road widths, reservations, existing structures or land deductions."
    },
    {
      "id": "geotech",
      "label": "Ground, groundwater and utilities capacity",
      "value": "Not established",
      "rawValue": null,
      "status": "not_established",
      "sourceId": "SITE-AUDIT",
      "sourceTitle": "Existing site-linkage and evidence-gap audit",
      "sourceDate": "2026-10-15",
      "scope": "Physical observation, geotechnical investigation and provider confirmations still required."
    },
    {
      "id": "capacity",
      "label": "25 lakh sq. ft. buildability reconciliation",
      "value": "Pending matched survey and architect review",
      "rawValue": null,
      "status": "not_established",
      "sourceId": "USER-AREA",
      "sourceTitle": "Accepted project and launch area basis",
      "sourceDate": "17 Oct 2026 model snapshot",
      "scope": "Current unit mix and revenue remain commercial scenarios until the gross-to-net land and entitlement bridge is signed."
    }
  ],
  "sources": [
    {
      "id": "USER-SITE",
      "title": "User-supplied site map pin",
      "fileName": null,
      "pages": [],
      "date": null,
      "scope": "Location reference supplied by the user. Point coordinate is not a cadastral boundary, ground control or legal parcel identity.",
      "status": "user_provided",
      "url": "https://maps.app.goo.gl/srjt3WC34J2pqmTUA"
    },
    {
      "id": "USER-AREA",
      "title": "Accepted project and launch area basis",
      "fileName": "continuation_state_v14.json",
      "pages": [],
      "date": "17 Oct 2026 model snapshot",
      "scope": "Accepted user planning brief: 25 lakh sq. ft. development and 10 lakh sq. ft. sales target are saleable area. These are not measured land area or sanctioned development capacity. The date refers to the V14 snapshot, not the date of the original user confirmation; that original instruction date is not independently logged.",
      "status": "user_provided"
    },
    {
      "id": "MODEL-AREA",
      "title": "Accepted loading and preliminary design assumptions",
      "fileName": "launch_plan_v14.json",
      "pages": [],
      "date": "17 Oct 2026 model snapshot",
      "scope": "Planning carpet = RERA carpet + exclusive terrace; modeled saleable = planning carpet × 1.40 by default. Balcony excluded. Own terrace zero is an explicit preliminary design assumption. The date refers to the V14 snapshot, not the date of the original user confirmation; that original instruction date is not independently logged.",
      "status": "planning_assumption"
    },
    {
      "id": "SITE-AUDIT",
      "title": "Existing site-linkage and evidence-gap audit",
      "fileName": "management_narrative.json",
      "pages": [],
      "date": "2026-10-15",
      "scope": "Geography section and unresolvedDataRequisites priority 1; pin 18.551876,73.966402; separate JLL site about 2.128 km north; S. No. 39 package not matched to this pin; parcel boundary and current approved plan remain outstanding.",
      "status": "document_reviewed"
    },
    {
      "id": "BRO-00",
      "title": "Building permission for a separate land opportunity",
      "fileName": "#Building Permission_04-08-2023.pdf",
      "pages": [
        1,
        2,
        3,
        4,
        5,
        6,
        7,
        8,
        9,
        10,
        11,
        12,
        13,
        14
      ],
      "date": "2023-08-04",
      "scope": "Different JLL land opportunity at 18.570559,73.962050, approximately 2.128 km north of supplied pin by straight-line calculation. Scanned technical contents not fully interpreted; no permission or area imported.",
      "status": "different_site"
    },
    {
      "id": "BRO-06",
      "title": "Layout for the separate northern site",
      "fileName": "LAYOUT.pdf",
      "pages": [
        1
      ],
      "date": "2024-06-06",
      "scope": "Contextual design document from the separate northern site. Not the proposed plot; no road, layout, FSI or building capacity adopted.",
      "status": "different_site"
    },
    {
      "id": "BRO-11",
      "title": "S. No. 39 demarcation drawing",
      "fileName": "DEMARCATION KHARADI  SR NO  39.pdf",
      "pages": [
        1
      ],
      "date": null,
      "scope": "Drawing in archive refers to Kharadi S. No. 39. Spatial and legal linkage to user pin is unresolved. Marathi labels and dimensions are not reliable own-site measurements.",
      "status": "document_unmatched"
    },
    {
      "id": "BRO-12",
      "title": "S. No. 39 development-plan sheet",
      "fileName": "DP PLAN KHARADI  SR. NO 39.pdf",
      "pages": [
        1
      ],
      "date": "2005-11-30",
      "scope": "Archived draft DP sheet/publication reference; not proof of current zoning, reservation or road lines on the proposed plot. Original source date and current authority status must be checked.",
      "status": "document_unmatched"
    },
    {
      "id": "BRO-13",
      "title": "S. No. 39/4(P) aviation/defence height NOC",
      "fileName": "HEIGHT PERMISSION LETTER MOD NOC Dt. 15-07-2024 (SR NO 39) PERMISSIBLE HEIGHT 75.20 M.pdf",
      "pages": [
        1,
        2,
        3,
        4
      ],
      "date": "2024-07-15",
      "scope": "Archive NOC addresses Kharadi S. No. 39/4(P). Pages 1–2 condition applicability on coordinates and elevation; the document does not establish land ownership or all other approvals. No permitted height or ground elevation is adopted for the user plot.",
      "status": "document_unmatched"
    },
    {
      "id": "BRO-14",
      "title": "S. No. 39 ready-reckoner rate sheet",
      "fileName": "RR RATE KHARADI SR NO 39.pdf",
      "pages": [
        1,
        2
      ],
      "date": "2025-26",
      "scope": "Unmatched archived valuation sheet. Does not establish own plot identity, current ASR value or project tax jurisdiction.",
      "status": "document_unmatched"
    },
    {
      "id": "BRO-15",
      "title": "S. No. 39 zoning/demarcation sheet",
      "fileName": "ZONING DEMARCATION KHARADI SR NO 39.pdf",
      "pages": [
        1
      ],
      "date": null,
      "scope": "Unmatched scanned drawing; detailed Marathi technical annotations are not reliably interpreted. No zoning or buildability conclusion imported.",
      "status": "document_unmatched"
    },
    {
      "id": "BRO-19",
      "title": "Mundhwa Plot 2D layout",
      "fileName": "DECCAN PAPER MILL - PLOT 2D - LAYOUT-Model.pdf",
      "pages": [
        1
      ],
      "date": null,
      "scope": "Title/labels identify Plot 2D, Mundhwa. Spatial and ownership linkage to proposed plot is not established. Its roads, reservations, well, transformer, dimensions and structures are not facts about our plot.",
      "status": "document_unmatched"
    },
    {
      "id": "BRO-DWG",
      "title": "Catalogued CAD attachments",
      "fileName": null,
      "pages": [],
      "date": null,
      "scope": "Nine CAD attachments were catalogued in the existing broader source register but not opened. No CAD polygon, dimension or approved-plan claim can be imported until files are read and the parcel is matched.",
      "status": "not_reviewed"
    }
  ],
  "categories": [
    {
      "id": "identity",
      "title": "Parcel identity & pre-visit pack",
      "description": "Tie every measurement and document to the exact proposed parcel.",
      "items": [
        {
          "id": "identity-01",
          "title": "Confirm the pin on the ground",
          "task": "Locate the supplied pin, entrance and parcel vicinity; record where the pin falls relative to the claimed boundary.",
          "method": "Ground GNSS observation and annotated location sketch; do not treat phone GPS as cadastral control.",
          "deliverable": "Dated location sheet with coordinates and pin-to-parcel relationship.",
          "owner": "Surveyor",
          "priority": "critical",
          "kind": "field_measurement",
          "baselineStatus": "open",
          "sourceIds": [
            "USER-SITE"
          ]
        },
        {
          "id": "identity-02",
          "title": "Establish legal parcel identifiers",
          "task": "Obtain revenue village, taluka, district, survey/gat number, hissa/subdivision and CTS identifiers where applicable; list every component parcel.",
          "method": "Match owner-supplied records to current Land Records entries.",
          "deliverable": "Parcel identity schedule with no unresolved aliases.",
          "owner": "Owner representative + Land Records surveyor",
          "priority": "critical",
          "kind": "document_check",
          "baselineStatus": "open",
          "sourceIds": [
            "SITE-AUDIT",
            "BRO-11"
          ]
        },
        {
          "id": "identity-03",
          "title": "Obtain current land-record pack",
          "task": "Collect digitally signed 7/12 or property card as applicable, mutation entries, cadastral/measurement maps and approved subdivision/amalgamation records.",
          "method": "Use official Mahabhumi services and record issue dates, authenticity checks and parcel references.",
          "deliverable": "Indexed dated records; note any inaccessible or absent record.",
          "owner": "Land Records specialist",
          "priority": "critical",
          "kind": "document_check",
          "baselineStatus": "open",
          "sourceIds": [
            "SITE-AUDIT"
          ]
        },
        {
          "id": "identity-04",
          "title": "Reconcile title and possession scope",
          "task": "Have counsel match deeds, development rights, ownership shares, easements, mortgages, claims and possession boundaries to the parcel schedule.",
          "method": "Document review and owner clarification; a physical survey does not certify title.",
          "deliverable": "Counsel’s parcel-linked title/access exceptions list.",
          "owner": "Property counsel + owner representative",
          "priority": "critical",
          "kind": "specialist_review",
          "baselineStatus": "open",
          "sourceIds": [
            "SITE-AUDIT"
          ]
        },
        {
          "id": "identity-05",
          "title": "Prepare the visit and document register",
          "task": "Log document title, revision, author/authority, date, pages, stamp/signature and parcel reference; separate proposals from approvals.",
          "method": "Version-controlled register; bring cadastral and claimed-boundary overlays.",
          "deliverable": "Visit brief with unresolved document matches and drawings to test.",
          "owner": "Survey coordinator",
          "priority": "high",
          "kind": "document_check",
          "baselineStatus": "open",
          "sourceIds": [
            "BRO-00",
            "BRO-06",
            "BRO-11",
            "BRO-12",
            "BRO-13",
            "BRO-14",
            "BRO-15",
            "BRO-19",
            "BRO-DWG"
          ]
        },
        {
          "id": "identity-06",
          "title": "Arrange authorized safe access",
          "task": "Obtain landowner/site access permission, safe escort, equipment access and agreed scope. Check drone operator, current airspace and flight permissions if drone work is proposed.",
          "method": "Pre-visit risk assessment; use applicable official aviation guidance and lawful survey access.",
          "deliverable": "Visit plan, safety brief and any required survey/flight permissions.",
          "owner": "Survey lead + owner representative",
          "priority": "high",
          "kind": "pre_visit",
          "baselineStatus": "open",
          "sourceIds": [
            "USER-SITE"
          ]
        }
      ]
    },
    {
      "id": "boundary",
      "title": "Boundary, control & land-area reconciliation",
      "description": "Produce a defensible measured polygon, with uncertainty and legal-record differences visible.",
      "items": [
        {
          "id": "boundary-01",
          "title": "Establish control, instruments and datum",
          "task": "Record coordinate reference system, units, horizontal/vertical datum, benchmark origin, instrument model, calibration and control-point accuracy.",
          "method": "Fit-for-purpose total station/GNSS/level network designed by surveyor.",
          "deliverable": "Control report, coordinate list and benchmark photos.",
          "owner": "Licensed surveyor",
          "priority": "critical",
          "kind": "field_measurement",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "boundary-02",
          "title": "Measure every boundary segment",
          "task": "Capture corners, bearings, lengths, monuments, bends and abutting parcels; close the traverse and document adjustment and accuracy achieved.",
          "method": "Ground control and independent closure/check observations; no invented tolerance.",
          "deliverable": "Signed closed boundary plan with vertex schedule and closure statement.",
          "owner": "Licensed surveyor / Land Records surveyor",
          "priority": "critical",
          "kind": "field_measurement",
          "baselineStatus": "open",
          "sourceIds": [
            "BRO-11"
          ]
        },
        {
          "id": "boundary-03",
          "title": "Compare record, claimed and occupied lines",
          "task": "Overlay cadastral/demarcation, deed, fence/wall and measured lines without forcing them to coincide. Record gaps, overlaps and encroachments.",
          "method": "Common-coordinate overlay plus corner and frontage photographs.",
          "deliverable": "Color-coded discrepancy plan and quantified area differences.",
          "owner": "Surveyor + property counsel",
          "priority": "critical",
          "kind": "field_measurement",
          "baselineStatus": "open",
          "sourceIds": [
            "SITE-AUDIT",
            "BRO-11",
            "BRO-15"
          ]
        },
        {
          "id": "boundary-04",
          "title": "Reconcile the land-area ledger",
          "task": "Compare each parcel’s recorded area with measured gross area, road surrender/acquisition, reservations, easements and retained/developable land.",
          "method": "Parcel-by-parcel area statement in sq. m and sq. ft.; state conversion and avoid duplicate deductions.",
          "deliverable": "Gross-to-net land schedule with evidence for every deduction.",
          "owner": "Surveyor + architect + counsel",
          "priority": "critical",
          "kind": "specialist_review",
          "baselineStatus": "open",
          "sourceIds": [
            "USER-AREA",
            "BRO-12",
            "BRO-19"
          ]
        },
        {
          "id": "boundary-05",
          "title": "Verify abutters and disputed edges",
          "task": "Record neighboring parcel identifiers and uses, shared boundaries, boundary stones, occupation claims and inaccessible lengths.",
          "method": "Ground inspection and official demarcation process where needed; do not resolve a dispute by moving a line.",
          "deliverable": "Boundary exception log with Land Records referral actions.",
          "owner": "Land Records surveyor + owner representative",
          "priority": "high",
          "kind": "field_measurement",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "boundary-06",
          "title": "Deliver parcel geometry",
          "task": "Prepare a closed CAD/GIS polygon and reconcile north arrow, scale, survey date, coordinates and parcel labels across files.",
          "method": "Validate geometry against the signed survey and control schedule.",
          "deliverable": "DWG/DXF plus GIS polygon/GeoJSON and signed PDF; mark provisional geometry clearly.",
          "owner": "Surveyor",
          "priority": "high",
          "kind": "deliverable",
          "baselineStatus": "open",
          "sourceIds": []
        }
      ]
    },
    {
      "id": "access",
      "title": "Access, frontage & road conditions",
      "description": "Separate what exists physically from legal rights and adopted road proposals.",
      "items": [
        {
          "id": "access-01",
          "title": "Measure road and plot frontage",
          "task": "Measure each plot frontage, road right-of-way boundaries, usable carriageway, shoulders, footpaths and obstructions at critical sections.",
          "method": "Ground cross-sections tied to parcel boundary; distinguish sanctioned width from measured width.",
          "deliverable": "Access plan with measured sections and bottlenecks.",
          "owner": "Surveyor",
          "priority": "critical",
          "kind": "field_measurement",
          "baselineStatus": "open",
          "sourceIds": [
            "SITE-AUDIT"
          ]
        },
        {
          "id": "access-02",
          "title": "Check continuous legal access",
          "task": "Trace the entire approach to the public road; confirm ownership, access easements, shared/private stretches and access restrictions.",
          "method": "Counsel reviews access documents against measured route.",
          "deliverable": "Parcel-linked access-rights memo and unresolved links.",
          "owner": "Property counsel + surveyor",
          "priority": "critical",
          "kind": "document_check",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "access-03",
          "title": "Match widening, DP and proposed roads",
          "task": "Obtain current authenticated road lines and acquisition/surrender status; compare to existing edges and the land ledger.",
          "method": "Authority part-plan/road records plus surveyed overlay; archived draft lines stay provisional.",
          "deliverable": "Road-line overlay with current status and potential land impact.",
          "owner": "Architect / planning consultant",
          "priority": "critical",
          "kind": "document_check",
          "baselineStatus": "open",
          "sourceIds": [
            "BRO-12",
            "BRO-19"
          ]
        },
        {
          "id": "access-04",
          "title": "Inspect junctions and entry levels",
          "task": "Record turning constraints, sight lines, divider openings, road gradients, gate levels, queues and pedestrian crossings.",
          "method": "Measured plan/levels plus dated photos; traffic and fire specialists test proposed entries.",
          "deliverable": "Entry constraints sheet and specialist actions.",
          "owner": "Surveyor + traffic/fire consultant",
          "priority": "high",
          "kind": "field_measurement",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "access-05",
          "title": "Assess construction and service access",
          "task": "Test delivery, crane/plant, emergency and service routes; identify overhead wires, weak culverts, narrow turns and third-party crossings.",
          "method": "Site walk and route survey; obtain engineering load/clearance review where necessary.",
          "deliverable": "Construction access constraints and permissions list.",
          "owner": "Civil/traffic engineer",
          "priority": "high",
          "kind": "specialist_review",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "access-06",
          "title": "Record seasonal and public-realm conditions",
          "task": "Record ponding, broken surfaces, informal parking, bus stops, pedestrian desire lines, lighting and any monsoon access interruptions.",
          "method": "Dated field observations; separate reported incidents from measured/official evidence.",
          "deliverable": "Photo-linked approach condition log with follow-up dates.",
          "owner": "Survey coordinator",
          "priority": "normal",
          "kind": "field_observation",
          "baselineStatus": "open",
          "sourceIds": []
        }
      ]
    },
    {
      "id": "topography",
      "title": "Levels, contours & grading",
      "description": "Establish a common datum before testing drainage, height or basement design.",
      "items": [
        {
          "id": "topography-01",
          "title": "Install and verify benchmarks",
          "task": "Identify reliable reference benchmark and set protected site benchmarks; record reduced levels, descriptions and independent level-loop closure.",
          "method": "Differential leveling/control checks using surveyor-defined specification.",
          "deliverable": "Benchmark schedule, sketches, photographs and closure report.",
          "owner": "Surveyor",
          "priority": "critical",
          "kind": "field_measurement",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "topography-02",
          "title": "Capture terrain and breaklines",
          "task": "Measure spot levels, slopes, ridges, depressions, embankments, retaining walls, road crowns and abrupt grade changes across the parcel.",
          "method": "Total station/GNSS survey on agreed density with added breaklines; record inaccessible zones.",
          "deliverable": "3D points, breaklines and terrain model with coverage limits.",
          "owner": "Surveyor",
          "priority": "critical",
          "kind": "field_measurement",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "topography-03",
          "title": "Prepare contours and sections",
          "task": "Produce contours and longitudinal/cross sections appropriate to terrain and proposed grading; state interval, method and accuracy.",
          "method": "Generate from checked terrain data; independently verify critical high/low points.",
          "deliverable": "Contour plan and sections referenced to the common benchmark.",
          "owner": "Surveyor + civil engineer",
          "priority": "high",
          "kind": "deliverable",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "topography-04",
          "title": "Tie adjoining ground and road levels",
          "task": "Extend the survey sufficiently beyond boundaries to understand entry grades, downstream drainage and neighboring ground interfaces.",
          "method": "Authorized observations at critical off-site points; flag any inaccessible or assumed levels.",
          "deliverable": "Boundary-interface and approach-level sections.",
          "owner": "Surveyor",
          "priority": "high",
          "kind": "field_measurement",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "topography-05",
          "title": "Check earthworks and retaining implications",
          "task": "Identify filled/excavated areas and preliminary cut/fill, retaining, basement-ramp and erosion constraints without treating estimates as final design.",
          "method": "Civil engineer reviews checked terrain model and geotechnical limitations.",
          "deliverable": "Grading constraints sketch and earthwork assumptions.",
          "owner": "Civil + geotechnical engineer",
          "priority": "high",
          "kind": "specialist_review",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "topography-06",
          "title": "Verify elevation for any height clearance",
          "task": "Measure site/building-corner elevations in the required datum and match coordinates, validity and conditions of any own-site aviation/defence clearance.",
          "method": "Survey certificate plus authority/architect check. Never inherit the S. No. 39 height NOC.",
          "deliverable": "Own-parcel elevation/height-clearance reconciliation.",
          "owner": "Surveyor + architect / aviation specialist",
          "priority": "critical",
          "kind": "specialist_review",
          "baselineStatus": "open",
          "sourceIds": [
            "BRO-13"
          ]
        }
      ]
    },
    {
      "id": "drainage",
      "title": "Stormwater, watercourses & flood evidence",
      "description": "A dry-day observation alone cannot establish monsoon or flood safety.",
      "items": [
        {
          "id": "drainage-01",
          "title": "Map drains and water features",
          "task": "Survey watercourses, nallas, streams, channels, ponds, wells, culverts, inlets and visible flow paths within and adjoining the parcel.",
          "method": "Ground plan and levels; identify natural versus constructed features.",
          "deliverable": "Water-feature layer with photo references and measured dimensions.",
          "owner": "Surveyor + drainage engineer",
          "priority": "critical",
          "kind": "field_measurement",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "drainage-02",
          "title": "Measure outfall and invert levels",
          "task": "Capture invert, bed, bank, culvert and drain levels, flow directions and available outfall route on the common datum.",
          "method": "Authorized survey; no confined-space entry by survey crew.",
          "deliverable": "Drainage long-sections and outfall level schedule.",
          "owner": "Surveyor + drainage engineer",
          "priority": "critical",
          "kind": "field_measurement",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "drainage-03",
          "title": "Establish flood lines and restrictions",
          "task": "Obtain applicable authenticated flood-line, river/nalla boundary and buffer records and identify issuing authority, datum, date and parcel overlay.",
          "method": "Authority records plus hydrologist/planner review; no fixed setback assumed.",
          "deliverable": "Dated flood/watercourse constraints overlay with unresolved approvals.",
          "owner": "Hydrologist + planning consultant",
          "priority": "critical",
          "kind": "document_check",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "drainage-04",
          "title": "Record ponding and monsoon history",
          "task": "Document observed waterlogging, stains, debris, erosion and reports of inundation; distinguish interviews from dated measurements or official records.",
          "method": "Photo log and documented follow-up, including wet-season visit if needed.",
          "deliverable": "Evidence-graded drainage and flood-risk log.",
          "owner": "Drainage engineer",
          "priority": "high",
          "kind": "field_observation",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "drainage-05",
          "title": "Test lawful stormwater disposal",
          "task": "Check downstream continuity, receiving-system ownership, capacity evidence, third-party easements and need for attenuation or drainage improvements.",
          "method": "Engineer assessment and authority/landowner confirmations; an apparent outlet is not permission.",
          "deliverable": "Preliminary stormwater strategy and consent/capacity gaps.",
          "owner": "Civil/drainage engineer",
          "priority": "critical",
          "kind": "specialist_review",
          "baselineStatus": "open",
          "sourceIds": []
        }
      ]
    },
    {
      "id": "utilities",
      "title": "Utilities & service capacity",
      "description": "Map visible assets now; confirm concealed routes and capacity with providers.",
      "items": [
        {
          "id": "utilities-01",
          "title": "Survey water supply assets",
          "task": "Locate supply lines, meters, chambers, tanks and borewells; record pipe details where safely observable and known connection points.",
          "method": "Ground survey plus provider record cross-check.",
          "deliverable": "Water layer and separate demand/availability confirmation request.",
          "owner": "Surveyor + MEP engineer",
          "priority": "high",
          "kind": "field_measurement",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "utilities-02",
          "title": "Survey sewer and wastewater assets",
          "task": "Locate sewers, manholes, invert/cover levels, STP/septic assets and potential connections; do not infer spare capacity from proximity.",
          "method": "Provider records and safe external survey; qualified crew for specialist inspection.",
          "deliverable": "Sewer level plan and connection/capacity evidence gaps.",
          "owner": "Surveyor + drainage/MEP engineer",
          "priority": "high",
          "kind": "field_measurement",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "utilities-03",
          "title": "Map power assets and constraints",
          "task": "Locate poles, overhead lines, substations, transformers, feeder routes and servitudes; record observed clearance issues for specialist review.",
          "method": "Ground survey and electricity-provider plans; no probing near live services.",
          "deliverable": "Power constraints layer and provider clearance/capacity confirmation.",
          "owner": "Surveyor + electrical engineer",
          "priority": "critical",
          "kind": "field_measurement",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "utilities-04",
          "title": "Map telecom, gas and other services",
          "task": "Locate visible telecom/gas ducts, markers, chambers and utility crossings; obtain provider searches before excavation or boreholes.",
          "method": "Records search and qualified utility detection/trial verification where needed.",
          "deliverable": "Coordinated utility plan distinguishing verified, indicated and unknown routes.",
          "owner": "Utility survey specialist + MEP engineer",
          "priority": "high",
          "kind": "specialist_review",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "utilities-05",
          "title": "Confirm service rights, capacity and diversion",
          "task": "Document providers, easements, connection approvals, diversion requirements, external works, lead times and responsibility/cost basis.",
          "method": "Written provider/authority confirmations and engineer coordination; location alone is not capacity.",
          "deliverable": "Utilities feasibility matrix with unresolved costs and approvals.",
          "owner": "MEP engineer + planning coordinator",
          "priority": "critical",
          "kind": "document_check",
          "baselineStatus": "open",
          "sourceIds": []
        }
      ]
    },
    {
      "id": "features",
      "title": "Existing structures & site occupation",
      "description": "Separate existing conditions from the structures shown on unmatched drawings.",
      "items": [
        {
          "id": "features-01",
          "title": "Survey buildings and structures",
          "task": "Record footprints, approximate height/storeys, use, plinth/roof levels and condition of permanent/temporary structures on and near the boundary.",
          "method": "Measured plan and photo log; structural assessment by qualified engineer where needed.",
          "deliverable": "Existing-conditions drawing and structure schedule.",
          "owner": "Surveyor + structural engineer",
          "priority": "high",
          "kind": "field_measurement",
          "baselineStatus": "open",
          "sourceIds": [
            "BRO-19"
          ]
        },
        {
          "id": "features-02",
          "title": "Record occupation and third-party use",
          "task": "Map tenants, occupants, cultivation, informal paths, storage and disputed or inaccessible areas without photographing people unnecessarily.",
          "method": "Authorized inspection and owner/counsel verification; do not infer possession or vacant title.",
          "deliverable": "Occupation constraints map and legal follow-up actions.",
          "owner": "Owner representative + property counsel",
          "priority": "critical",
          "kind": "field_observation",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "features-03",
          "title": "Locate site features and walls",
          "task": "Survey walls, fences, gates, sheds, wells, tanks, pits, retaining structures and abandoned foundations.",
          "method": "Feature-coded observations tied to boundary and common levels.",
          "deliverable": "Feature inventory with removal/retention status left unconfirmed until reviewed.",
          "owner": "Surveyor",
          "priority": "high",
          "kind": "field_measurement",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "features-04",
          "title": "Identify demolition and stability constraints",
          "task": "Check retained/shared walls, adjoining foundations, dangerous structures, asbestos or other suspect materials and demolition permissions.",
          "method": "Structural/hazardous-material specialist review; visual suspicion is not laboratory confirmation.",
          "deliverable": "Demolition constraints and investigations/permissions register.",
          "owner": "Structural engineer + specialist",
          "priority": "high",
          "kind": "specialist_review",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "features-05",
          "title": "Record practical site logistics",
          "task": "Identify safe survey setup, temporary access, material staging, security, construction drainage and neighboring property protection constraints.",
          "method": "Site walk with engineer and owner representative.",
          "deliverable": "Logistics constraints sketch and immediate make-safe actions.",
          "owner": "Construction/civil engineer",
          "priority": "normal",
          "kind": "field_observation",
          "baselineStatus": "open",
          "sourceIds": []
        }
      ]
    },
    {
      "id": "ground",
      "title": "Ground conditions & geotechnical investigation",
      "description": "Visual reconnaissance cannot establish bearing capacity or foundation design.",
      "items": [
        {
          "id": "ground-01",
          "title": "Observe ground and prior land use",
          "task": "Record fill, exposed rock/soil, erosion, dumping, settlement, excavation and evidence of former industrial/agricultural use.",
          "method": "Dated reconnaissance with historical-record review where available.",
          "deliverable": "Ground-conditions log separating observations from interpretations.",
          "owner": "Geotechnical engineer",
          "priority": "high",
          "kind": "field_observation",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "ground-02",
          "title": "Design the geotechnical investigation",
          "task": "Agree borehole/test locations and depths, sampling and laboratory programme for the actual development, groundwater and excavation questions.",
          "method": "Qualified geotechnical engineer sets scope after boundary, utilities and design review.",
          "deliverable": "Approved investigation plan and access/service-clearance checks.",
          "owner": "Geotechnical engineer",
          "priority": "critical",
          "kind": "specialist_review",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "ground-03",
          "title": "Investigate groundwater and foundations",
          "task": "Obtain logs, tests and groundwater observations sufficient for foundations, basement uplift, dewatering, excavation support and retaining design.",
          "method": "Authorized geotechnical investigation with seasonal limitations recorded.",
          "deliverable": "Signed geotechnical report with coordinates, datum, raw logs and design parameters.",
          "owner": "Geotechnical engineer",
          "priority": "critical",
          "kind": "specialist_review",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "ground-04",
          "title": "Test contamination and infiltration where relevant",
          "task": "Assess contamination, aggressive ground/water and infiltration/percolation requirements based on site history and proposed systems.",
          "method": "Environmental/geotechnical specialist scopes sampling and tests; no assumed soil classification or percolation rate.",
          "deliverable": "Test results, limitations and mitigation/further-work recommendations.",
          "owner": "Geotechnical + environmental specialist",
          "priority": "high",
          "kind": "specialist_review",
          "baselineStatus": "open",
          "sourceIds": []
        }
      ]
    },
    {
      "id": "environment",
      "title": "Trees, environmental constraints & hazards",
      "description": "Document observed features; obtain applicable official protection or clearance records.",
      "items": [
        {
          "id": "environment-01",
          "title": "Inventory trees and vegetation",
          "task": "Map tree positions, species where identifiable, girth/canopy and condition; identify potential retention conflicts.",
          "method": "Qualified tree inventory with numbered photos; competent authority confirms any permissions required.",
          "deliverable": "Tree schedule and retention/removal approval gaps.",
          "owner": "Arborist / landscape specialist + surveyor",
          "priority": "high",
          "kind": "field_measurement",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "environment-02",
          "title": "Check protected land and environmental status",
          "task": "Verify applicable forest, wetland, waterbody, heritage, hill-slope or other notified restrictions and prior environmental permissions against the exact parcel.",
          "method": "Official records and environmental/planning review; absence from a web map is not clearance.",
          "deliverable": "Parcel-specific environmental constraints and approvals register.",
          "owner": "Environmental + planning consultant",
          "priority": "critical",
          "kind": "document_check",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "environment-03",
          "title": "Record nuisance and hazard context",
          "task": "Record noise, dust, odour, traffic, high-tension assets, hazardous operations, waste and sensitive neighboring uses with date/time and direction.",
          "method": "Site observations; specialist measurements if needed, not subjective compliance certification.",
          "deliverable": "Context risk map and targeted measurement actions.",
          "owner": "Environmental / acoustic specialist",
          "priority": "high",
          "kind": "field_observation",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "environment-04",
          "title": "Plan mitigation and evidence follow-up",
          "task": "Identify erosion, runoff, dumping, public safety and construction-environment controls needed for investigations and future works.",
          "method": "Engineer review of observed conditions and verified constraints.",
          "deliverable": "Environmental follow-up plan with responsible roles and evidence requirements.",
          "owner": "Environmental + civil engineer",
          "priority": "normal",
          "kind": "specialist_review",
          "baselineStatus": "open",
          "sourceIds": []
        }
      ]
    },
    {
      "id": "planning",
      "title": "Planning permissions & buildable capacity",
      "description": "These items require matched authority records and professional review; the surveyor alone cannot certify entitlement.",
      "items": [
        {
          "id": "planning-01",
          "title": "Confirm the competent authorities",
          "task": "Determine current planning authority, local body, revenue and service jurisdictions for every component parcel and effective date.",
          "method": "Official boundary/appointment records and written clarification where ambiguous.",
          "deliverable": "Jurisdiction matrix with dated supporting evidence.",
          "owner": "Architect / planning consultant",
          "priority": "critical",
          "kind": "document_check",
          "baselineStatus": "open",
          "sourceIds": [
            "SITE-AUDIT"
          ]
        },
        {
          "id": "planning-02",
          "title": "Obtain current zoning and part plan",
          "task": "Obtain parcel-matched current zone/part-plan certificates; check roads, reservations, amenity obligations, acquisition and proposed versus sanctioned status.",
          "method": "Competent authority records overlaid on measured boundary.",
          "deliverable": "Authenticated planning-constraints plan with evidence dates.",
          "owner": "Architect / planning consultant",
          "priority": "critical",
          "kind": "document_check",
          "baselineStatus": "open",
          "sourceIds": [
            "BRO-12",
            "BRO-15"
          ]
        },
        {
          "id": "planning-03",
          "title": "Match every permission and NOC",
          "task": "Check land identity, drawing revision, approval number/date, conditions, validity and coordinates for NA/use conversion, layout/building permission, CC and relevant NOCs.",
          "method": "Read originals/certified copies; no transfer of S. No. 39 or Plot 2D approvals.",
          "deliverable": "Permission matrix marking matched, superseded, expired or unresolved records.",
          "owner": "Architect + property counsel",
          "priority": "critical",
          "kind": "document_check",
          "baselineStatus": "open",
          "sourceIds": [
            "BRO-00",
            "BRO-06",
            "BRO-11",
            "BRO-13",
            "BRO-19"
          ]
        },
        {
          "id": "planning-04",
          "title": "Set the applicable planning rule basis",
          "task": "Confirm current applicable regulations/amendments and parcel-specific road, use, fire, height, setback, open-space, parking and access requirements.",
          "method": "Architect/planning/fire specialists apply current rules after jurisdiction and site identity are resolved.",
          "deliverable": "Signed design-constraint schedule; no generic numeric threshold imported.",
          "owner": "Architect + fire/planning consultants",
          "priority": "critical",
          "kind": "specialist_review",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "planning-05",
          "title": "Reconcile land to statutory development area",
          "task": "Calculate eligible net land, base/premium FSI, TDR and other provisions only where documented; show deductions and approval-dependent components separately.",
          "method": "Architect prepares area statement linked to surveyed land and verified rules/rights.",
          "deliverable": "Gross land → eligible land → permitted FSI/built-up bridge with approval gaps.",
          "owner": "Architect + planning consultant",
          "priority": "critical",
          "kind": "specialist_review",
          "baselineStatus": "open",
          "sourceIds": [
            "USER-AREA"
          ]
        },
        {
          "id": "planning-06",
          "title": "Reconcile statutory area to saleable brief",
          "task": "Keep land, FSI/built-up, common/service areas, RERA carpet, exclusive terrace, balcony and modeled saleable as separate schedules. Test whether 25 lakh saleable fits the approved envelope.",
          "method": "Architect’s massing/unit schedule plus transparent reconciliation; 40% loading is a commercial assumption, not a statutory conversion.",
          "deliverable": "25 lakh sq. ft. feasibility bridge and supported capacity range.",
          "owner": "Architect + development manager",
          "priority": "critical",
          "kind": "specialist_review",
          "baselineStatus": "open",
          "sourceIds": [
            "USER-AREA",
            "MODEL-AREA"
          ]
        },
        {
          "id": "planning-07",
          "title": "Validate release and product-mix fit",
          "task": "Test current unit sizes/mix against feasible blocks, circulation, parking, amenities, phasing, infrastructure and approval timing; retain the 10 lakh target as a commercial scenario until supported.",
          "method": "Architect and development team review signed survey, constraints and entitlement bridge.",
          "deliverable": "Documented keep/change recommendation for inventory and phase release.",
          "owner": "Architect + development manager",
          "priority": "critical",
          "kind": "specialist_review",
          "baselineStatus": "open",
          "sourceIds": [
            "USER-AREA",
            "MODEL-AREA"
          ]
        }
      ]
    },
    {
      "id": "context",
      "title": "Off-site context & buyer experience",
      "description": "Visit context can refine design hypotheses; it does not establish demand, absorption or legal access.",
      "items": [
        {
          "id": "context-01",
          "title": "Document approach and destination routes",
          "task": "Record actual route, visit date/time, traffic conditions, entry barriers and walkability to relevant roads/employment/services.",
          "method": "Timed route observations; distinguish radial distance from road distance and one-trip time.",
          "deliverable": "Dated route log and access/commute constraints.",
          "owner": "Survey coordinator + development team",
          "priority": "normal",
          "kind": "field_observation",
          "baselineStatus": "open",
          "sourceIds": [
            "USER-SITE"
          ]
        },
        {
          "id": "context-02",
          "title": "Observe neighboring massing and views",
          "task": "Record adjoining building footprints/heights, privacy conflicts, overlooking, shading, orientation and view obstructions.",
          "method": "Survey/photo bearings; daylight/wind conclusions require specialist modeling where material.",
          "deliverable": "Neighbor-context and orientation diagram.",
          "owner": "Architect + surveyor",
          "priority": "high",
          "kind": "field_observation",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "context-03",
          "title": "Check amenities and nuisance claims",
          "task": "Verify existence/access of nearby schools, shops, transport, healthcare and nuisance sources without adopting marketing distances as measured facts.",
          "method": "Dated visit/map evidence and lawful public observation.",
          "deliverable": "Context evidence log with exact route/basis and verification date.",
          "owner": "Development research team",
          "priority": "normal",
          "kind": "field_observation",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "context-04",
          "title": "Separate development context from supply",
          "task": "Note visible work on neighboring sites, project boards and access changes as dated observations, not current inventory, bookings or achieved possession.",
          "method": "Photo/document log with source and scope; further official research separately.",
          "deliverable": "Dated context change log without absorption or stock claims.",
          "owner": "Development research team",
          "priority": "normal",
          "kind": "field_observation",
          "baselineStatus": "open",
          "sourceIds": []
        }
      ]
    },
    {
      "id": "deliverables",
      "title": "Handover, checks & sign-off",
      "description": "Complete means an evidence-backed field pack has been reviewed; it never means all risks are cleared automatically.",
      "items": [
        {
          "id": "deliverables-01",
          "title": "Issue a signed survey drawing set",
          "task": "Deliver boundary, topography, access, utilities and existing-conditions plans with common datum, north, scale, legend, parcel IDs, survey date, author and revision.",
          "method": "Cross-check PDF/CAD/GIS against raw observations and control schedule.",
          "deliverable": "Signed dated PDF plus editable CAD/GIS and survey metadata.",
          "owner": "Survey lead",
          "priority": "critical",
          "kind": "deliverable",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "deliverables-02",
          "title": "Provide raw measurement and photo evidence",
          "task": "Supply control/level/traverse records, point files, instrument/accuracy notes, numbered dated photos with locations/directions and inaccessible-area limits.",
          "method": "Indexed private handover; protect personal data and preserve originals.",
          "deliverable": "Traceable evidence index and raw measurement package.",
          "owner": "Survey lead",
          "priority": "high",
          "kind": "deliverable",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "deliverables-03",
          "title": "Issue the discrepancy and missing-evidence log",
          "task": "List every conflict, assumption, unmeasured area, unmatched document, unknown service and pending authority confirmation; assign role, next action and due date.",
          "method": "Joint surveyor/architect/counsel review; do not silently close missing items.",
          "deliverable": "Action register with evidence references and accountable roles.",
          "owner": "Survey coordinator",
          "priority": "critical",
          "kind": "deliverable",
          "baselineStatus": "open",
          "sourceIds": [
            "SITE-AUDIT"
          ]
        },
        {
          "id": "deliverables-04",
          "title": "Review coordinated constraints and capacity",
          "task": "Overlay legal, planning, drainage, utility, tree, geotechnical and access constraints; agree retained and developable land before finalizing massing.",
          "method": "Interdisciplinary review with documented disagreements and conditional areas.",
          "deliverable": "Coordinated constraints plan and signed capacity reconciliation.",
          "owner": "Architect + engineers + counsel",
          "priority": "critical",
          "kind": "specialist_review",
          "baselineStatus": "open",
          "sourceIds": [
            "USER-AREA"
          ]
        },
        {
          "id": "deliverables-05",
          "title": "Sign off each discipline separately",
          "task": "Obtain surveyor measurement acceptance, counsel parcel/title/access review, architect entitlement review, engineer ground/services review and management acceptance.",
          "method": "Named-role sign-off with date, revision, qualifications and unresolved exceptions; checklist completion alone is not approval.",
          "deliverable": "Discipline sign-off matrix and management decision note.",
          "owner": "Development manager",
          "priority": "critical",
          "kind": "deliverable",
          "baselineStatus": "open",
          "sourceIds": []
        },
        {
          "id": "deliverables-06",
          "title": "Update the app only from supported findings",
          "task": "Replace unknown fields only with attributable parcel-matched evidence; retain prior values, date and provenance. Re-run area, unit-count and financial scenarios if supported capacity changes.",
          "method": "Reviewed change log; local checklist notes remain user-entered until evidence is validated.",
          "deliverable": "Versioned app/data update with exact recommendation changes and remaining gaps.",
          "owner": "Data curator + development manager",
          "priority": "high",
          "kind": "deliverable",
          "baselineStatus": "open",
          "sourceIds": [
            "USER-AREA",
            "MODEL-AREA"
          ]
        }
      ]
    }
  ],
  "references": [
    {
      "id": "REF-LAND",
      "title": "Maharashtra Mahabhumi: official land-record and measurement services",
      "url": "https://mahabhumi.gov.in/",
      "scope": "Official entry point for digitally signed land records, maps and e-Mojni measurement services. Obtain records for the actual parcel; viewing a portal does not validate our boundary.",
      "accessed": "2026-10-18"
    },
    {
      "id": "REF-MOJ",
      "title": "Land Records department: e-Mojni 2.0 FAQ",
      "url": "https://www.bhumiabhilekh.maharashtra.gov.in/HelpAndFAQs/HelpAndFAQs",
      "scope": "Official guidance directs citizens through Mahabhumi to e-Mojni Version 2. Current application requirements and any official demarcation process must be checked with the Land Records office. Search-visible official FAQ inspected; full-page retrieval failed during this review.",
      "accessed": "2026-10-18"
    },
    {
      "id": "REF-PLAN",
      "title": "PMRDA Development Permission: current services and jurisdiction framework",
      "url": "https://www.pmrda.gov.in/en/development-permission/",
      "scope": "Official overview lists permission and zoning services and distinguishes applicable regulatory frameworks by jurisdiction. It does not establish which authority or rules apply to our still-unidentified parcel.",
      "accessed": "2026-10-18"
    },
    {
      "id": "REF-ZONE",
      "title": "PMRDA Zone Certificate and Part Plan service",
      "url": "https://zonecertificate.pmrda.gov.in/ZC/",
      "scope": "Official certificate application service, relevant only if PMRDA is the competent authority for the actual parcel. No application submitted and no own-site certificate obtained.",
      "accessed": "2026-10-18"
    },
    {
      "id": "REF-DCPR",
      "title": "Official PMRDA DCPR 2018: document and site-plan information framework",
      "url": "https://www.pmrda.gov.in/wp-content/uploads/2025/03/PMRDA-DCPR-2018.pdf",
      "scope": "PDF pages 26–27 (printed pages 15–16), regulations 6.2.2–6.2.4 are an official reference for land-identity/area records and site-plan information. Used to inform the document checklist only; jurisdiction, current amendments and applicability remain unverified for our plot. No FSI, setback, height or road-width entitlement adopted.",
      "accessed": "2026-10-18",
      "pages": [
        26,
        27
      ]
    },
    {
      "id": "REF-DRONE",
      "title": "Airports Authority of India DigitalSky: current drone airspace and permission guidance",
      "url": "https://digitalsky.aai.aero/",
      "scope": "If drone survey is proposed, the operator must check current official airspace, applicable operating requirements and permissions. No own-site zone, flight approval or blanket permission requirement has been asserted.",
      "accessed": "2026-10-18"
    }
  ],
  "qualifications": [
    "No physical site visit, signed own-plot measurement report or parcel-matched authority certificate has been supplied or completed by this update.",
    "The supplied pin is a location reference, not a surveyed/legal boundary; no own-site land area, contour, frontage, road width, FSI, height or zoning value is prefilled as verified.",
    "25 lakh sq. ft. and 10 lakh sq. ft. are accepted saleable commercial planning inputs, not measured land area or authority-certified buildable capacity.",
    "Developer planning carpet = RERA carpet + exclusive terrace; modeled saleable = that base × 1.40 by default. Balcony remains separate. Own terrace zero is an unapproved design assumption.",
    "The S. No. 39 package, northern separate-site drawings and Mundhwa Plot 2D sheet must not be treated as permissions, land deductions or measurements for this plot.",
    "Field observation, measured evidence, authority document, professional interpretation and user-entered note are different evidence classes. A checked item or typed note does not independently verify a fact.",
    "A surveyor measures physical conditions; legal title/access, planning entitlement, geotechnical design and environmental/utility capacity require the appropriate qualified reviewer and authority evidence.",
    "This is a comprehensive commissioning checklist for the current brief, not a certified survey specification or an exhaustive statement of applicable law. Survey professionals must adapt method, extent and accuracy to the actual terrain, proposed design and competent authority.",
    "No fixed local road, setback, flood buffer, FSI, contour interval, borehole depth or drone clearance threshold has been guessed. The relevant professional must establish and document the applicable requirement.",
    "Use a reason and reviewer for items marked not applicable. Keep blocked or unavailable evidence visible rather than treating it as zero or complete.",
    "Raw private emails, chat media, source PDFs, CAD and personal contact details are not rehosted in the app. Source filenames and page references identify the private evidence without exposing it.",
    "Existing market, product-mix and itemized revenue calculations remain unchanged by this checklist. Revisions require supported parcel capacity and design findings."
  ],
  "criticalGates": [
    {
      "id": "identity",
      "title": "Parcel identity and boundary",
      "status": "not_ready",
      "requires": [
        "identity-02",
        "identity-03",
        "identity-04",
        "boundary-02",
        "boundary-03",
        "boundary-04"
      ],
      "why": "No exact legal parcel or measured closed own-site boundary has been established."
    },
    {
      "id": "access",
      "title": "Lawful and workable access",
      "status": "not_ready",
      "requires": [
        "access-01",
        "access-02",
        "access-03",
        "access-04"
      ],
      "why": "Physical widths, continuous legal access and current authority road lines remain unresolved."
    },
    {
      "id": "engineering",
      "title": "Levels, drainage, ground and service feasibility",
      "status": "not_ready",
      "requires": [
        "topography-01",
        "topography-02",
        "drainage-02",
        "drainage-03",
        "drainage-05",
        "utilities-05",
        "ground-02",
        "ground-03"
      ],
      "why": "No own-site checked terrain, flood/outfall, ground investigation or provider capacity pack is established."
    },
    {
      "id": "planning",
      "title": "25 lakh saleable buildability bridge",
      "status": "not_ready",
      "requires": [
        "planning-01",
        "planning-02",
        "planning-03",
        "planning-04",
        "planning-05",
        "planning-06",
        "planning-07"
      ],
      "why": "Commercial saleable brief has not been reconciled to verified land, entitlement and a feasible design."
    },
    {
      "id": "review",
      "title": "Coordinated evidence and professional sign-off",
      "status": "not_ready",
      "requires": [
        "deliverables-01",
        "deliverables-03",
        "deliverables-04",
        "deliverables-05"
      ],
      "why": "Checklist progress and user notes do not replace reviewed, parcel-matched discipline deliverables."
    }
  ],
  "counts": {
    "categories": 12,
    "checks": 64,
    "criticalChecks": 35,
    "measuredOwnSiteFacts": 0,
    "ownSiteAuthorityDocumentsMatched": 0
  },
  "reviewMetadata": {
    "reviewedExistingFiles": [
      "management_narrative.json geography section and unresolvedDataRequisites[0]",
      "continuation_state_v14.json acceptedAreaRules",
      "broader source inventory",
      "S. No. 39 demarcation PDF page 1 visually inspected",
      "S. No. 39 height NOC OCR pages 1–2 and page 2 image visually inspected",
      "Mundhwa Plot 2D layout PDF page 1 visually inspected",
      "Official PMRDA DCPR 2018 PDF pages 26–27 extracted and read for document/site-plan checklist structure"
    ],
    "privacy": "No private contact, email, sender, raw media or absolute source paths included.",
    "checklistProgressMeaning": "Task tracking only; a completion status is not independent evidence validation.",
    "baseline": "All checklist items begin open. No real field measurements or professional approvals have been inferred."
  }
}
