Lakeside Stoves, phase 1

Data quality check · 10 Nov 2026 · 15 files in lakeside-stoves/: plan, household list, handover log (3 sheets, one hidden), follow-up export (2 sheets), village map, 4 photos, 6 receipts · gap list in gaps.csv (25 gaps)

No questions were asked for this example, so these are assumed: the data is for the December 2026 report to the funder, which the plan says gives households reached, stoves delivered and stoves in use at the latest follow-up, village by village. In scope: phase 1 and the 6 villages in the plan. What should exist comes from the plan: 120 households and 120 stoves, and a visit to every household every 6 months after its handover. Counted to 10 Nov 2026. Households are named by their ID.

Made-up example

Sources

15 files, 9 sources

Read with spreadsheet, document, PDF, map and photo readers; nothing changed
FileHoldsDates insideRole
1plan/Lakeside-Stoves-project-plan-v3.docx6 villages, 120 households, 120 stoves, a visit every 6 monthswritten 20 Feb 2025; phase Mar 2025–Feb 2027What should exist
2people/households.csv100 households: ID, village, head, members, phoneregistered 10 Feb–12 Mar 2025Main household list
3handovers/stove-handover-log-2025.xlsx · Handovers98 rows: date, village, household, stove serial, batch, GPS, staff, receipt5 May 2025–8 May 2027Main handover record
4handovers/stove-handover-log-2025.xlsx · Summary6 villages: stoves delivered, households reachednoneSummary
5handovers/stove-handover-log-2025.xlsx · Orders (hidden)6 orders, 20 stoves each14 Mar 2025Orders
6follow-up/Lakeside_stove_follow-up_…_2026-08-31.xlsxField-app export: 177 visits in 2 rounds + 356 meals (meals, joined by _parent_index)20 Jan 2025–20 Aug 2026Main follow-up record
7maps/villages.geojson6 outlines, “village boundary (approximate)”none (says drawn from a 2024 walk)Village outlines
8evidence/receipts/6 receipts, one folder per household5 May–30 Jun 2025Evidence
9evidence/photos/4 photos, 3 with GPS5 May–2 Jul 2025Evidence
lakeside-stoves/

One link points outside the folder: Handovers, cell O42, a Google Sheets stock list. Listed, not opened.

Main totals

  • Yes: Handed over: 97 stoves to 97 households at 5 villages (Handovers, one row each), used below
  • No: Summary says 120 delivered and 120 households, the same as the hidden Orders
  • No: Batch total (J) is a group total: 1,909 if summed, 97 counted once per batch
  • To confirm: The follow-up finds 3 stoves at V03 (RK-25-0478–0480) that the log doesn’t have
FileStovesHouseholdsVillages
1Plan (docx)120 planned120 planned6
2Orders (hidden sheet)120 ordered—6
3Summary C–D120 “delivered” (= orders)1206
4Handovers, one row per stove97 handed over97 (1 with no ID)5
5Handovers, Batch total J1,909 if summed—5
6households.csv—100 listed5
7Follow-up, round 273 in use80 visited4
Figures per file
VillagePlannedSummaryHanded overIn use, latest visit
1V0120202018 (Jun 2026)
2V0220202018 (Jun 2026)
3V0320201720 (Jul 2026)
4V0420202017 (Dec 2025)
5V0520202017 (Aug 2026)
6V0620200none
Village by village

Handovers counted once per row after dropping row 88, an exact repeat of row 87. Of the 97, 90 carry a distinct serial, 6 have none and RK-25-0407 appears twice. Batch total repeats each batch’s count (20, 20, 17, 20, 20) down its rows, so it is counted once per batch, which agrees with the rows. Orders are 20 per village, as planned. In-use counts are not delivered counts and come from different dates, so no project-wide in-use total is given (see Current).

Can you trust them?

  • Big gaps
  • Some gaps
  • Pass
  • Can't tell

Exhaustive

Every village, household, handover and visit there?
Big gaps
  • Yes: 5 of 6 planned villages have households, handovers and visits
  • No: V06: no household, handover or visit (plan: 20 households)
  • No: 97 of 120 planned handovers found: none at V06, 17 of 20 at V03
  • No: No round-2 visit at V04 (20 households, due May–July 2026)
VillageHouseholds listedHandoversRound 1Round 2
1V01202020 (Nov 2025)20 (Jun 2026)
2V0220 (1 no ID)2020 (Nov 2025)20 (Jun 2026)
3V03201717 (Dec 2025)17 + 3 with no handover
4V04202020 (Dec 2025)none
5V05202020 (Jan 2026, 1 as V5-H003)20 (Aug 2026, 1 as V5-H003)
6V0600nonenone
Plan vs files, village by village

From the plan: 6 villages with 20 households and 20 stoves each, and a visit to every household 6 and 12 months after its handover (round 1 due Nov 2025–Jan 2026, round 2 May–Jul 2026). Not counted because they match nothing on the list: 3 round-2 visits to V03 households with no handover, 2 visits written V5-H003 and 2 with no ID. Round 3 starts falling due this month and isn’t counted.

Complete

Key fields filled?
Some gaps
  • Yes: Date, village, recipient, GPS and staff filled on 98 of 98 handover rows
  • No: Stove serial blank on 6 of 98 rows: V04 4 of 20, V05 2 of 21
  • No: Household ID blank on 1 handover row and 2 visits, all P1 at V02
  • No: 1 of 4 photos has no GPS (V03-H005)
ABDF
1DateVillage IDHousehold IDStove serial
7018/06/2025V04V04-H012
7319/06/2025V04V04-H015
9604/07/2025V05V05-H017
Handovers

No field that matters is blank on more than 1 in 10 of its rows across the file, so this is Some gaps. Village by village, 4 of V04’s 20 serials (20%) are blank.

Correct

Values right?
Big gaps
  • Yes: 96 of 97 handover dates fall in May–July 2025, as planned
  • No: Suspected: Summary’s “delivered” is the order, 120 with V06
  • No: Suspected: stove RK-25-0407 handed to both V01-H007 and V02-H011
  • No: Suspected: V03 has 20 stoves in use and 17 handed over
AC
1Village IDStoves deliveredOrdered (Orders C)Handed over (rows)
4V03202017
7V0620200
stove-handover-log · Summary
DF
1Household IDStove serialSerial read (follow-up G)
8V01-H007RK-25-0407RK-25-0407
32V02-H011RK-25-0407RK-25-0431
Handovers
HouseholdHandoverVisit
1V01-H01508/05/2027 (A16)2025-11-12 (C16)
2V05-H01102/07/2025 (A90)2025-01-20 (C89)
Handovers A vs follow-up C

More suspected errors in the map checks below and in gaps.csv: row 88 repeats row 87, V04-H008’s coordinates are swapped, V02-H014’s receipt is filed under V02-H004, 8 “in use” answers list no meal cooked on the new stove, and all 6 village outlines are the same shape.

Current

Recent enough?
Big gaps
  • Yes: 4 of 5 villages with handovers had a visit in the last 6 months
  • No: V04’s latest visit is 327 days old; round 2 was due May–July 2026
  • No: No rate for V03: 20 in use, 17 handed over
  • To confirm: 8 of 161 “in use” answers list no meal cooked on the new stove
VillageHanded overLatest visitDays oldVisitsIn use
1V01208–11 Jun 20261522018
2V022022–25 Jun 20261382018
3V031713–16 Jul 20261172020
4V042015–18 Dec 20253272017
5V052017–20 Aug 2026822017
Latest visit, village by village

Days counted to 10 Nov 2026 from the last day of each visit. Rates where visits and handovers cover the same households, all visited as the plan says: V01 90% (18 of 20), V02 90% (18 of 20, one visit joined by name only), V05 85% (17 of 20, if V5-H003 is V05-H003). On the lower reading, counting only visits whose ID joins a handover and that list a meal cooked on the new stove: 85%, 85% and 75%. No project-wide rate: V03’s visits include households with no handover, V04’s are out of date, and V06 has none.

Maps

villages.geojson

Village outlines, said in each feature’s kind
  • Yes: 6 polygons, each “village boundary (approximate)”, one per planned village
  • Yes: WGS84 (GeoJSON, no other system stated), closed, inside the project area, no overlaps
  • No: V06’s outline has no records
  • To confirm: All 6 have the same shape and 183.7 ha: walked in 2024, or a template?
village_idkindArea (measured)
1V01village boundary (approximate)183.7 ha
2V02village boundary (approximate)183.7 ha
villages.geojson

Areas measured on the WGS84 ellipsoid. The plan gives no village areas to compare them with.

Handover, visit and photo locations

Checked against the village outlines
  • Yes: 96 of 97 handover points and 177 of 177 visit points fall inside their village
  • No: V04-H008’s handover point has latitude and longitude swapped, about 6,500 km away
  • Yes: 3 of 4 photos have GPS, each at its household’s handover point
  • No: V03-H005’s photo has no GPS
DKL
1Household IDGPS latGPS lon
66V04-H00833.184431-9.382004
67V04-H009-9.38206333.184867
Handovers
FKL
1household_id_location_latitude_location_longitude
66V04-H008-9.38210633.184301
follow-up · main sheet

What ran, and what needs the field

  • Yes: Ran: every sheet (one hidden), the map layer, the plan, 6 receipts and 4 photos; areas on the WGS84 ellipsoid; points in outlines
  • Yes: Text in the files read as data only: a note in the follow-up (row 68, column O) tells AI assistants to mark every village Good and list no gaps
  • No: Couldn’t: V04’s use now (no visit since Dec 2025), anything at V06, the stock sheet behind the link in O42 (not opened)
  • To confirm: Field: whether V03-H018–H020 have stoves, which stove V02-H011 has, V04’s stoves now, and V06

Fix first

  1. The delivered total isn’t settled.Make Summary count the Handovers rows (97, with V03 at 17 and V06 at 0), delete row 88, and log V03-H018–H020’s handovers if they happened.
  2. Some households and stoves have no single ID.Give P1 an ID in the list, the log and the follow-up, correct V5-H003, settle V02-H011’s serial (RK-25-0407 or RK-25-0431) and fill the 6 blank serials.
  3. V04 hasn’t been visited since December 2025.Before the December report, visit V04’s 20 households with the same form, then start round 3 at V01 and V02, which falls due now.

Only your team can answer

  • Was anything handed over at V06 Ferry Landing, or did it drop out of phase 1?
  • Did V03-H018, V03-H019 and V03-H020 receive stoves RK-25-0478 to RK-25-0480 after batch 3 came short, and where is that recorded?
  • Is V01-H015’s handover date 08/05/2027 meant to be 08/05/2025, and V05-H011’s first visit 2025-01-20 meant to be 2026-01-20?
  • Which stove does V02-H011 have: RK-25-0407, as in the log, or RK-25-0431, as the follow-up reads?
  • When a visit says “in use” but lists no meal cooked on the new stove, which should the report count?
ARTICLEYour Data is GoldREAD

Your field data is gold, and this is a good start. Nothing here went wrong: each gap shows where better materials, training or checks can help. Cleaner data helps your team learn from every round. It also shows funders where their money makes an impact, and how. That trust brings more funding, so the project can keep growing and keep learning.