Information date: 12 November 2026 — On 5 June 2025 People’s Daily reported that the State Council had issued the Notice on Conducting the Fourth National Agricultural Census. The census takes 24:00 on 31 December 2026 as its reference date, with 2026 as the reference year for period data; enumeration and processing run through 2027. It covers farm households, agricultural operating entities and village-level units, collecting cultivated land area, sown area, output, livestock inventories and agricultural facilities. Results are published down to county level — which is the granularity a sourcing team can actually use, and exactly where the confidentiality boundary bites. If the goal is screening supplier capacity, use county aggregates plus site diligence plus the supplier’s own audited records. If the goal is siting a collection point or warehouse, county data alone is enough. If the goal is contract negotiation, treat statistics as context and do not let any aggregated figure substitute for a physical inspection of the fields and the weighbridge.
Verified facts and scope
On 5 June 2025 People’s Daily reported that the State Council had issued the Notice on Conducting the Fourth National Agricultural Census. The census takes 24:00 on 31 December 2026 as its reference date, with 2026 as the reference year for period data; enumeration and processing run through 2027. It covers farm households, agricultural operating entities and village-level units, collecting cultivated land area, sown area, output, livestock inventories and agricultural facilities. Results are published down to county level — which is the granularity a sourcing team can actually use, and exactly where the confidentiality boundary bites.
Scope has to be fixed before the numbers mean anything: Confirm before relying on anything: which county each supplier sits in, whether the county boundary matches the physical site, which indicator you need (cultivated area, sown area, or output), and whether that indicator will be published by crop and by season. Note that a supplier near a county border may be counted in a neighbouring county’s table. Anything outside that set is a separate question with its own evidence requirement, and mixing the two is the most common way a workable plan turns into an unusable one.
For a decision on “The Fourth National Agricultural Census Begins Field Work — How a Foreign Sourcing Team Can Read the County-Level Acreage and Output Data It Will Release, the Reference Date, and the Confidentiality Limits on What a Statistics Bureau Will Say About One Supplier’s District”, keep three layers apart: the published rule or statistic, the company’s own orders and process records, and the assumptions nobody has tested yet. The first layer defines the external conditions, the second proves what is true for this business, and the third is where the risk actually sits. Public material cannot substitute for a contract, a system log, a sample or a live test.
A practical way to test the scope is to ask which parts of “The Fourth National Agricultural Census Begins Field Work — How a Foreign Sourcing Team Can Read the County-Level Acreage and Output Data It Will Release, the Reference Date, and the Confidentiality Limits on What a Statistics Bureau Will Say About One Supplier’s District” would still be true if the company changed supplier, entity or product line tomorrow. Items that survive that change belong to the rule layer and can be taken from official publications; items that do not survive belong to the operating layer and have to be rebuilt from invoices, warehouse records, customs entries or platform statements. Where Confirm before relying on anything: which county each supplier sits in, whether the county boundary matches the physical site, which indicator you need (cultivated area, sown area, or output), and whether that indicator will be published by crop and by season. Note that a supplier near a county border may be counted in a neighbouring county’s table, the two layers are frequently mistaken for each other, and an action plan built on the wrong one either over-complies or misses a deadline it never saw coming.
How the effect reaches operations
Statistics law bars statistical agencies from supplying identifiable data about an individual reporting unit. Census results are released as aggregates under minimum-cell rules, so the county table is public while any single supplier’s figure is not. A bureau cannot confirm one factory’s output even if an official knows it. The consequence is that county-level data supports inference and benchmarking, never verification of a specific counterparty.
Typical misuse: applying a county average yield to a supplier’s contracted land and booking the inflated volume into a supply plan; blending census output with customs export totals and treating the difference as supplier capacity; asking a local bureau to confirm one company’s numbers and receiving a refusal plus an unhelpful flag. A fourth risk is reading the publication timetable as a forecast of next season’s availability.
Translated into an operating sequence, Statistics law bars statistical agencies from supplying identifiable data about an individual reporting unit. Census results are released as aggregates under minimum-cell rules, so the county table is public while any single supplier’s figure is not. A bureau cannot confirm one factory’s output even if an official knows it. The consequence is that county-level data supports inference and benchmarking, never verification of a specific counterparty. That ordering matters: check applicability first, then the transmission step, and only then the size of the gap in cost or timing. When an intermediate step cannot be confirmed, the honest response is to narrow the scope of the conclusion rather than to substitute an industry average for the company’s own figures.
The cost of getting the order wrong is asymmetric. A team that checks applicability too late usually discovers it at the point where the shipment, the filing or the invoice can no longer be changed without penalty, and by then the only remaining lever is price. A team that checks early spends a few hours on questions that turn out to be irrelevant, which is cheap by comparison. On “The Fourth National Agricultural Census Begins Field Work — How a Foreign Sourcing Team Can Read the County-Level Acreage and Output Data It Will Release, the Reference Date, and the Confidentiality Limits on What a Statistics Bureau Will Say About One Supplier’s District” the practical rule is therefore to spend the first hour on scope and the second on the numbers, never the other way round.
Decision
If the goal is screening supplier capacity, use county aggregates plus site diligence plus the supplier’s own audited records. If the goal is siting a collection point or warehouse, county data alone is enough. If the goal is contract negotiation, treat statistics as context and do not let any aggregated figure substitute for a physical inspection of the fields and the weighbridge.
The conditions should be written down so the decision can be re-run by someone else: Confirm before relying on anything: which county each supplier sits in, whether the county boundary matches the physical site, which indicator you need (cultivated area, sown area, or output), and whether that indicator will be published by crop and by season. Note that a supplier near a county border may be counted in a neighbouring county’s table. When those hold, proceed as described; when one is missing, close the gap first and decide afterwards. This is an explanatory news note, not statistical, legal or procurement advice. Census definitions, publication levels and release dates follow official notices; verify against the National Bureau of Statistics before relying on any figure.
Two workstreams usually have to move in parallel. The compliance workstream closes the document side of “The Fourth National Agricultural Census Begins Field Work — How a Foreign Sourcing Team Can Read the County-Level Acreage and Output Data It Will Release, the Reference Date, and the Confidentiality Limits on What a Statistics Bureau Will Say About One Supplier’s District” — registrations, confirmations, filings — while the commercial workstream protects the delivery date, the pricing already quoted and the customer commitments that were made on the earlier reading of the rules. Running them as one queue is how small documentation gaps become missed shipment dates: the commercial side waits for a certificate that could have been requested a week earlier. If the goal is screening supplier capacity, use county aggregates plus site diligence plus the supplier’s own audited records. If the goal is siting a collection point or warehouse, county data alone is enough. If the goal is contract negotiation, treat statistics as context and do not let any aggregated figure substitute for a physical inspection of the fields and the weighbridge. Set one owner per workstream and one shared status sheet, and treat a red item on either side as a reason to freeze only the affected order.
Implementation checklist
- Map each supplier to a county boundary before the data is released.
- Use county averages for screening only, never for a volume commitment.
- Request the supplier’s own sown-area records instead of a bureau confirmation.
- Name one decision owner, one execution owner and one review date.
- Keep the source page, access date, entity and internal evidence.
- On any change, reopen only the affected judgement.
Evidence and review
Start with the smallest test that can change the answer: Map each supplier to a county boundary before the data is released. Pick one real entity or one representative case, write down the continue, watch and stop conditions in advance, and record the input version, the owner, the start time and the actual result. The first pass should only look at facts that move the decision; formatting preferences are not risk.
The second pass is completed by “Use county averages for screening only, never for a volume commitment”, and someone who did not prepare the file should spot-check one piece of critical evidence. Typical misuse: applying a county average yield to a supplier’s contracted land and booking the inflated volume into a supply plan; blending census output with customs export totals and treating the difference as supplier capacity; asking a local bureau to confirm one company’s numbers and receiving a refusal plus an unhelpful flag. A fourth risk is reading the publication timetable as a forecast of next season’s availability. A single small deviation can be corrected in place; a repeated deviation, or one that touches a statutory duty or changes the economics, is what justifies pausing the affected part.
After “Request the supplier’s own sown-area records instead of a bureau confirmation”, compare the actual result with the baseline rather than with the impression of the team. If the goal is screening supplier capacity, use county aggregates plus site diligence plus the supplier’s own audited records. If the goal is siting a collection point or warehouse, county data alone is enough. If the goal is contract negotiation, treat statistics as context and do not let any aggregated figure substitute for a physical inspection of the fields and the weighbridge. When the arrangement is extended to more products, customers or processes, keep the same success test and one complete record per batch. If later information changes, update only the affected fields.
One last discipline keeps the file usable next quarter: write the closing note as if a colleague who has never spoken to the supplier has to act on it. That note states what was verified, on which date, against which source, and what remains open — on “The Fourth National Agricultural Census Begins Field Work — How a Foreign Sourcing Team Can Read the County-Level Acreage and Output Data It Will Release, the Reference Date, and the Confidentiality Limits on What a Statistics Bureau Will Say About One Supplier’s District” it also states which of the three actions was actually finished and which was only scheduled. Teams that skip the closing note re-litigate the same question every month, and each round costs more than the documentation would have. This is an explanatory news note, not statistical, legal or procurement advice. Census definitions, publication levels and release dates follow official notices; verify against the National Bureau of Statistics before relying on any figure.
Limits of the conclusion
This is an explanatory news note, not statistical, legal or procurement advice. Census definitions, publication levels and release dates follow official notices; verify against the National Bureau of Statistics before relying on any figure.
The limits are structural rather than cautious wording. Public sources describe rules and market conditions; they do not observe “The Fourth National Agricultural Census Begins Field Work — How a Foreign Sourcing Team Can Read the County-Level Acreage and Output Data It Will Release, the Reference Date, and the Confidentiality Limits on What a Statistics Bureau Will Say About One Supplier’s District” inside a specific company. Where the analysis quotes a second-hand interpretation, the original release has to remain reachable, and a figure that cannot be traced back does not enter the decision table. Where the point depends on Confirm before relying on anything: which county each supplier sits in, whether the county boundary matches the physical site, which indicator you need (cultivated area, sown area, or output), and whether that indicator will be published by crop and by season. Note that a supplier near a county border may be counted in a neighbouring county’s table, the conclusion is only as current as the last check of those conditions.
