DeshLoopThakurgaonWhat was approved, installed and paid for the reported Tk 499,400 pond-lighting work?
The ADP row reports Tk 499,400 expenditure and 100% progress. Item quantities, exact procurement identity, acceptance and executed payment remain unverified.
Different financial stages are not additive. Reported expenditure is not verified executed payment.
Different financial stages are not additive. Reported expenditure is not verified executed payment.
Different financial stages are not additive. Reported expenditure is not verified executed payment.
Different financial stages are not additive. Reported expenditure is not verified executed payment.
These amounts describe different stages. They are not added together, and reported expenditure is not automatically an executed payment.
THE HELD EVIDENCE
Each statement is attached to its source and location. An official claim and a finding from review are shown separately.
The row names “Supply of Around pond (Light) of upazila parishad”; estimate Tk 500,000, contract and expenditure Tk 499,400, financial and physical progress 100%.
Work-order date 5 May 2025, start 6 May 2025, end 5 June 2025; report 30 June 2025. These are reported dates, not inspection records.
Column 17 prints RFQ. It does not provide the quotation invitation, supplier selection, signed order or item schedule.
The 17 March 2025 engineering decision approves ADP demands by a referenced attachment. Its project list was not identifiable in the retained 15-page packet. Attendance appendixক is a different attachment. No exact link to this lighting scheme is established.
The 29 January 2025 packet contains a decision and an ADP scheme list. This review did not identify an exact pond-lighting entry. It does not rule out a later addition or a separate approval file.
FOLLOW THE REASONING
These checks apply to the stated evidence and scope. A flag identifies a question for further review; it does not by itself establish corruption.
Cannot determine: a general approval trail exists, but the exact lighting scheme is not linked to it.
General ADP resolutions or similar electrical work do not prove the exact scheme approval. Match the scheme list/order reference.
Cannot determine: the scheme’s certified bills and executed settlement records are not held.
A reported expenditure total alone cannot verify payment execution.
Cannot determine: neither the authorised item schedule nor matched acceptance evidence is held.
Compare authorised item quantities with itemised delivery and acceptance. A percentage cannot substitute for either.
These are possibilities, not established explanations or official replies.
Supporting approvals and acceptance may be held separately from the annual report.
The scheme file index, approval annex, work order and acceptance register.
THE NEXT EVIDENCE
The status below describes this collection. A record not held here may still exist at the institution.
Obtain the engineering project-demand attachment referenced by the 17 March 2025 decision, the exact lighting-scheme approval and any subsequent additions/changes. Match by scheme/order identity, not month or general electrical wording.
Identify procurement reference, selected supplier, quoted items and authorised price.
Establish the promised number, type and locations of lights and associated works.
Match delivery, installation and tests to the authorised items and locations.
Obtain bill references, gross/net amounts, deductions, settlement confirmation and reversals.
No submission or response is recorded for this request. Downloading a draft does not send it. Confirm the recipient, add the applicant’s details and use the official submission process.
No official reply to this case is held in the reviewed collection. This does not establish that the institution has never responded elsewhere.
A public case was assembled from retained official records; unresolved questions and missing inputs remain explicit.
Completed targeted screening of 27 retained PDFs/213 pages; narrowed the next request to the approval attachment and RFQ/order file. No verified payment or delivery was added.
Targeted visual screening covered all 213 pages of 27 retained meeting PDFs. This is a search for one scheme, not a full transcription,27 different meetings, or the council’s complete record universe. Key source passages are shown below; the full review inventory is downloadable.
The key sources are shown below. The full review inventory records which meeting documents and pages were checked and the limits of that review.
Download the full document review inventoryOne scheme in Pirganj Upazila Parishad’s FY 2024–25 ADP report; not its whole ADP account or district spending.
Reviewed pages: 2, 3
Method: Visual PDF review and retained-hash checks.
Selected claims above; no executed settlement or independent inspection verified.
Retained source SHA-256
7e5ae840217663444e6a49e0a67e24807fabc990af0586aa6401a4f3413cfd52Capture timestamp:
A matching hash identifies retained bytes; it does not independently authenticate the issuer or establish completeness.
General ADP approval context. The date shown is the printed meeting date; no exact pond-lighting scheme match is established.
Reviewed pages: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17
Method: Every retained PDF page visually screened for the target scheme; relevant approval pages reread.
Approval context found; no exact pond-lighting approval, quantity, acceptance or settlement match established.
Retained source SHA-256
adba0b094c0a51abba91febdd5524e1df49b2c489c1b4fade08f05d5f7b44defCapture timestamp:
A matching hash identifies retained bytes; it does not independently authenticate the issuer or establish completeness.
General ADP approval context. The date shown is the printed meeting date; no exact pond-lighting scheme match is established.
Reviewed pages: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15
Method: Every retained PDF page visually screened for the target scheme; relevant approval pages reread.
Approval context found; no exact pond-lighting approval, quantity, acceptance or settlement match established.
Retained source SHA-256
fefe70b477ab6be9b5eb95869860489f7eb87a4ac8d2bfd7f040107c7846b423Capture timestamp:
A matching hash identifies retained bytes; it does not independently authenticate the issuer or establish completeness.