Project Baghbaan
Agroforestry Carbon Sequestration · South Punjab, Pakistan · Carbon Craft UK
Pilot On Track
Reporting Period
MRV Officer
What this proves
Metric 10 ft × 10 ft Plot 15 ft × 15 ft Plot Combined Status
What this proves
10 ft × 10 ft Plot
15 ft × 15 ft Plot
Excellent
Good
Weak
Not rated / dead
Survival & Replanting
10 ft × 10 ft Survival Rate
15 ft × 15 ft Survival Rate
Project Survival Benchmark 85.0%
Gap Management
10 ft × 10 ft Plot
15 ft × 15 ft Plot
Combined Average
What this proves
Local Spend to Date
PKR 6.37M
Salaries PKR 3.57M · labour PKR 0.93M · office & accommodation PKR 0.68M · pilot lease PKR 0.64M
Recurring Payroll
Local field roles established
Permanent MRV & field positions paid monthly
Land Economics
Lease payments started
Pilot landowner cashflow tested and operating
Execution Capacity
Local labour engaged
Plantation execution capability proven on-site
Ground Presence
Field office active
Permanent local presence with accommodation
Social Licence
Community channels open
Health, school and village engagement underway
Baghbaan has already moved money, jobs, lease payments, labour activity and field presence into the project area. These are early signals that the project is not arriving cold at scale — it is building the local operating base required for a long-duration carbon asset. Headline total includes additional locally incurred project and support expenditure that is not individually displayed in this investor summary.
What this proves
Baghbaan is creating the local operating footprint required for permanence, land access and field execution. Local spend to date is PKR 6,367,899, reflecting early payroll, lease payments, labour activity and permanent local presence. This should be presented as project-delivery infrastructure, not as a collection of CSR claims.
Canola Meal — Sold
PKR 6,000
75 kg at PKR 80/kg · realised June proceeds
Vegetable Activity
Germination and crop condition under monitoring
Watermelon, melon, pumpkin, cucumber and capsicum in the field
Chickpea & Vegetable Harvest Watch
Chickpea sale planned: 23 bags of 100 kg
Vegetable harvesting planned during the next reporting period
What this proves
Intercrop activity is early-stage supporting economics, not carbon value. The July workbook reports no new intercrop transactions, so the figures shown remain the last reported position: PKR 6,000 of realised canola-meal proceeds, with chickpea sales and vegetable harvesting still forward activity rather than booked revenue.
The drip-irrigation system is being monitored regularly to confirm proper operation. Daily checks and tensiometer-based soil-moisture monitoring remain important during harsh summer conditions.
Water stewardship — recorded
9.685 million litres of site water use recorded across nine months, supported by 460 daily field monitoring records and periodic water-level measurements across four bores.
Baghbaan is building a monitored, evidence-led operating model in which irrigation use, field conditions and groundwater levels are tracked together to support responsible scale-up decisions.
Monitoring system active Preliminary pilot evidence
What this proves
Water use, field condition and groundwater level are being recorded continuously rather than estimated retrospectively. This is a monitoring and operational-learning record at pilot level — it does not, on its own, establish groundwater recharge or sustainable abstraction.
No new water consumption, daily monitoring or bore-level records were supplied with the July 2026 update. This tab remains current to June 2026.
Recorded Site Water Consumption (million litres per month)
Lowest Recorded Month
0.255 million L
November 2025 · manual calculation, pre-flow-meter
Highest Recorded Month
1.977 million L
May 2026 · onset of summer conditions
Largest Month-on-Month Rise
+0.616 million L
Jan → Feb 2026 (+70.8%) · onion irrigation build-up
Recorded water use increased during the hotter months. Part of the increase reflects the addition of approximately 8,000 onion pits; therefore, the current totals should not be interpreted as tree-only water demand. October and November 2025 were recorded by manual calculation; a flow meter has been in use from December 2025 onward, so the two periods are not measured on an identical basis.
Not yet measurable
Tree and crop water use are not yet recorded separately. Current site totals therefore cannot be used as a tree-only water-intensity measure.
Consumption is metered at site level on a single flow meter. Trees, the approximately 8,000-pit onion crop, other intercrops, nursery beds and general site use share the same drip and abstraction system, and abstraction is not recorded per bore. No allocation between these uses has been created.
Tree Water Use
Not yet measurable
Requires separate tree-line metering
Onion & Intercrop Use
Not yet measurable
Shares the site drip network
Nursery & Other Site Use
Not yet measurable
Not separately recorded
A Litres per Tree field exists in the daily monitoring workbook but entries stop after January 2026 and cannot be reconciled against concurrent crop use. It is therefore not published as a water-intensity indicator.
Irrigation vs Non-Irrigation Records by Month
Recorded Maximum Temperature & Days at or above 40°C
Daily field monitoring connects water application with soil conditions, weather stress and management action, helping the team refine irrigation practices during the pilot. Recorded soil moisture is Moist on 448 of 460 records and little moist on 8, with 4 blank — a narrow range that limits its current diagnostic value. Temperature entries for November 2025 average 41.1°C against a December average of 27.0°C; these November values are treated as suspected entry errors and are flagged in the data-quality table rather than read as heat stress.
Technical detail — monthly monitoring summary
Aggregated from the consolidated daily monitoring workbook. Individual daily records, staff names and free-text field notes are held in the source workbook and are not published in the stakeholder layer.
MonthRecordsIrrigation daysNo irrigationWater logged (L)Meter reading (L)Reconciliation
Water Level, Depth Below Ground Level (ft) — axis inverted so downward movement means water is farther from the surface
Read the axis as depth below ground level: a greater depth (lower on the chart) means water is farther from the surface; a shallower depth (higher on the chart) means water is closer to the surface. All four bores are drilled to 91 ft. The 4th bore has been out of use since March 2026 and has no readings for the last two dates.
BoreBore depthJun 2025Nov 2025Mar 2026Jul 2026Change, Jun 25 → Jul 26
The available observations do not show a clear, uniform decline across all monitored bores. However, four measurement dates are insufficient to establish recharge rates, sustainable abstraction or long-term groundwater security. Groundwater response is being monitored. The recorded changes are not attributed to Baghbaan's abstraction: seasonal variation, regional abstraction and rainfall are unmeasured at this site, and no causal relationship can be drawn from four readings.
Data Confidence
RecordedDirectly available from field records — monthly meter readings, daily monitoring entries, periodic bore measurements.
DerivedCalculated from recorded values — totals, monthly change, irrigation-day counts, averages, completeness rates.
Not yet establishedRequires additional monitoring or technical analysis — tree-only water intensity, per-bore abstraction, recharge rate, sustainable yield.
Known Limitations — Explicitly Flagged
GapApril 2026 site water use is recorded at 1.182 million litres in the monthly workbook but no April daily monitoring records are present in the consolidated daily workbook.
ConsistencySome daily records contain non-standard date text, missing start and end times, blank fields and inconsistent case or category wording; 4 date entries are non-numeric text.
AttributionWater use for trees and crops is not consistently separated, and abstraction is not recorded per bore.
InsufficientGroundwater monitoring frequency — four measurement dates in 13 months — is too low to support any sustainability conclusion.
DatasetReporting periodRecordsCompletenessKnown limitationConfidence
Completeness basis. For the daily monitoring dataset, completeness is calculated over the eight fields expected on every record — date, plot, data-collection officer, irrigation done, soil moisture, weeding, pest/stress observation and damage/grazing — giving 3,669 of 3,680 expected entries completed (99.7%). Conditional fields are reported separately and are materially less complete: total water used 63.5%, irrigation duration 42.4%, temperature 48.9%, humidity 50.0%. For the monthly water dataset, completeness is the proportion of months in the stated period carrying a reading (9 of 9). For groundwater, completeness is the proportion of bore-by-date cells carrying a reading (14 of 16; the 4th bore is out of use). No field has been estimated or back-filled to raise a completeness figure.
What this proves
The limitations above are already driving changes to the monitoring design. Separating water use by planting system, recording abstraction per bore and increasing groundwater measurement frequency are the specific steps required before any water-availability or water-intensity claim can be made — and they are being built into the pilot rather than deferred to scale-up.
Source Records
01Monthly water consumption data — Katimar pilot. October 2025 to June 2026 · 9 monthly readings · manual calculation for October–November 2025, flow meter from December 2025.
02Consolidated daily monitoring. October 2025 to June 2026 · 460 records across 230 dates and both plots · consolidated from 8 monthly field workbooks; April 2026 absent.
03Periodic water level measurement — Katimar pilot. June 2025 to July 2026 · 4 bores × 4 measurement dates · depth below ground level in feet and inches.
These records demonstrate active monitoring and operational learning at pilot level. They do not, by themselves, establish groundwater recharge, sustainable abstraction or long-term water availability. Those conclusions require hydrogeological assessment and continued monitoring.
Path to Full Scale-up
What this proves
Action Owner Target Date Priority
Field follow-through for the next reporting period includes post-harvest weed control by ploughing and manual removal, continued irrigation review of the weak-health cohort, nursery establishment for scale-up and compilation of the MRV data package.
Risk Signal Current Status Management Action Level
Resolved items carried in the July register: termite attack (both plots), winter growth slowdown (spring flush confirmed), species establishment lag (all nine species growing) and slow diameter growth (increment improving) — no resurgence observed.
What this proves
Note: The values shown are the reported July 2026 species-wise growth increments supplied in the dedicated species workbook. The source describes growth increment as relating to increases in height and basal diameter but does not provide a common calculation formula or unit. The figures are therefore shown as interim field observations and should not be interpreted as a final ranking of carbon performance, survival, suitability or long-term biomass.
What this proves
Rangelands Surveyed
6 Rakhs
With Forest Department support (DFO Rangeland Bhakkar)
Total Surveyed Area
19,198 ha
Screened for scale-up potential
Barren Land Identified
11,902 ha
Of surveyed rangeland
What this proves
The Rakh survey creates a stronger diligence base for scale-up discussions. It should be presented as potential land screening with government participation.
Tweaks