Summary

  • Question 29 of the 2026 APNIC Survey required respondents to allocate a total of 100 points across eight activities, turning preference into a constrained strategic budget.
  • The main report labels the question Base n=1,039, but its segment table prints a total sample size of 1,038; the separately published official data-table appendix prints 1,037.
  • The main report’s eight displayed means add to 100.0. Appendix B changes organisational stability from 9.9 to 9.8, so its displayed totals add to 99.9. The documents do not explain either difference.
  • An average allocation cannot reveal whether individuals chose broadly balanced budgets or whether concentrated groups cancelled one another out. APNIC should publish a compact priority-allocation receipt connecting the questionnaire, accepted records, aggregation, versions and dispersion.

One question, three denominators

The cleanest way to read APNIC’s final strategic question is as a budget exercise. Respondents did not tick every activity they liked. The questionnaire gave them 100 points, eight boxes and a hard constraint: the total had to equal 100. A zero was allowed. The largest number was meant for the work APNIC should emphasise most over the next three to five years.

That design is valuable because it forces opportunity cost into the answer. Another point for registry services is one point unavailable for infrastructure deployment, community support or the Policy Development Process. An unconstrained importance scale can let every activity score highly. A fixed purse asks the respondent to expose relative preference.

The public output should therefore have an unusually simple denominator. It is one question, one submitted vector and one total of 100 for each accepted response. Yet APNIC’s official publication chain gives the item three bases.

Page 51 of the main report introduces the exercise and labels Question 29 Base n=1,039. Page 52 repeats that base beneath the chart. Page 53 presents the segmentation table. Its first numeric row says Sample Size 1,038, while the footer on the same page again says Base n=1,039. A reader can see both numbers without changing documents.

Appendix B creates a third count. Its Question 29 table says Sample size 1,037. The Member and Stakeholder columns are 689 and 348, which happen to add to 1,037. That arithmetic is observable, but it is not an explanation. It does not tell us whether 1,037 is a classified subset, the accepted universe, a later export or simply a different published version. The geographic and economy columns are not a mutually exclusive partition of the total, so they cannot safely be recruited to reverse-engineer the rule.

The member presentation returns to 1,039. Repetition makes 1,039 the most visible number, not necessarily the reconciled one. The source package never supplies a note saying why the narrative, the main table and the appendix differ. No responsible account can fill that silence with a guessed late exclusion, a missing classification, weighting, validation or transcription error.

The totals close, but the ledger does not

The main report gives the eight average allocations as 15.5, 15.1, 15.1, 12.3, 12.1, 10.5, 9.9 and 9.5. They sum to 100.0. That is satisfying, and it is consistent with a question designed around a 100-point purse. It does not reconcile the response base.

Arithmetic closure answers one question: the rounded category means shown in that chart exhaust the displayed total. It does not answer which records entered the calculation, whether every retained row already summed to 100, whether weights were used, how blanks were handled or why the adjacent table is short by one response. A result can close perfectly after one record has been added or removed because the vector is averaged and then rounded.

Appendix B introduces a smaller numerical seam. Seven of the eight total means match the main report. The value for organisational stability and financial sustainability is 9.8 rather than 9.9. The eight appendix figures therefore add to 99.9. That may be ordinary rounding from a different precision, a refresh from a different source table, a version difference or something else. The documents do not say. A difference of one tenth is not evidence of misconduct, but it is evidence that the two tables are not identical outputs.

The temptation is to solve the riddle from the visible sums. Resist it. Rounded means cannot yield exact point totals without knowing the accepted count, weighting and unrounded values. Multiplying 15.5 by 1,039 would create a pseudo-precise total that may correspond to no underlying record set. Doing the same with 1,037 does not make the comparison more legitimate. The correct fact is modest: three bases and two versions of one displayed mean coexist in the official bundle, without a reconciliation note.

APNIC’s release says the whole survey received 1,385 valid responses. That is important context, but it is not Question 29’s denominator. Respondents can skip an item, fail a constraint, fall outside an analytic subset or be treated differently by an unpublished validation rule. None of those possibilities is established here. The overall survey count must not be substituted for the item base merely because it is larger and clearly described.

A mean is a centre, not a portrait of respondents

APNIC’s main report draws a substantive conclusion from the chart. Because the allocation is relatively even, it says respondents see the activities as connected rather than competing or independent priorities. The report describes a registry whose effectiveness depends on infrastructure, registry services, community support, research, tools, advocacy, organisational stability and policy participation working together.

That interpretation is plausible. It is not proven by the mean vector alone.

Imagine ten respondents and two simplified activities. If every respondent divides 100 points as 50–50, the mean is 50–50. If five allocate 100–0 and five allocate 0–100, the mean is also 50–50. The first population expresses individual balance. The second expresses perfect aggregate balance produced by polarised individual choices. The centre is identical; the institutional meaning is not.

Eight activities allow many more hidden structures. Respondents may spread points among several complementary functions. Members may concentrate on operational services while stakeholders concentrate on policy participation. Regions may differ. A small group may assign zeros to an activity that remains near the middle because others place it first. The published segment averages offer useful comparisons, but averages within broad segments still do not expose the distribution inside each segment.

This is why a distribution is ordinarily described with more than location. NIST’s statistical handbook uses the triad of location, spread and shape. The mean is a measure of location. It does not reveal spread or shape. That general observation is not an APNIC-specific rule and it does not invalidate the survey. It explains the limit of the public evidence: readers have a centroid, not the topology of the preferences that produced it.

The missing information need not be raw microdata. APNIC could report medians and quartiles, the share assigning zero, the share putting more than a stated threshold on one activity, or a respondent-level concentration measure. It could show how often activities rise together within a budget and where trade-offs actually appear. Those summaries would distinguish complementarity from cancellation without disclosing any person’s response.

Without them, “balanced priorities” can slide between two different claims. One is safe: the aggregate means are distributed relatively evenly across eight activities. The other is stronger: respondents themselves generally constructed balanced portfolios. The published chart establishes the first. It cannot by itself establish the second.

Why the denominator matters to governance

This would be a minor editorial defect if the chart were decorative. APNIC presents the survey as input on performance, priorities and future direction. The questionnaire says the Executive Council is interested in Members’ views on prioritisation. APNIC’s governance page says the EC is its governing board, establishes the basis for the activity plan and budget, publishes the proposed plan and budget for Member feedback, and adopts the final budget after receiving that feedback.

Question 29 is not a vote and its percentages are not budget instructions. But the question has been designed to resemble resource allocation, and its results can frame which activities appear to deserve marginal attention. A clear count and distribution matter because strategic authority can attach itself to an apparently precise average.

Consider the difference between consensus and coalition. If most respondents gave every activity a non-trivial allocation, the EC could reasonably read the result as broad support for a portfolio. If the same mean emerged from sharply different camps, the management problem would be different. It might require sequencing, explicit trade-offs or engagement with groups facing distinct operating conditions. A centroid conceals that choice.

The three bases create a second governance ambiguity. A denominator is not merely a footnote to a survey. It defines whose responses were counted for the claim being made. When three counts appear for one item, a Member cannot tell whether the narrative and table describe the same analytic population. The difference is small—two responses between the widest endpoints—but the missing rule is larger than the numerical gap. It is the rule that turns submissions into evidence.

The issue is therefore not whether one or two respondents could overturn the ranking. The published values are too rounded to answer that, and the article does not claim it. The issue is whether the public can reproduce the provenance of a chart used to describe collective priorities. Institutional legitimacy is strengthened when the path from question to decision input can be inspected without asking readers to trust whichever denominator appears most often.

The questionnaire is only the start of the chain

The questionnaire page is admirably concrete. It shows the eight activities, says the options are randomised, permits allocations from zero to 100 and requires the total to equal 100. That is the collection contract presented to a respondent.

A publication contract needs additional stages. It should say what happened if the form contained a blank, a total of 99 or 101, a duplicated submission, an out-of-range entry or an incomplete classification. It should distinguish validation performed by the survey interface from exclusions applied during analysis. It should identify whether weights altered the contribution of accepted records. It should say whether charts and appendices were built from one frozen extract.

None of these conditions should be assumed to have occurred. They are the ordinary questions raised by the unexplained count difference. A valid answer may be simple: perhaps one artifact covers a classified subset and another covers all accepted vectors. If so, a one-line note and a stable label would settle the matter. If the files came from different revisions, a version identifier and correction history would do the work. The current package asks readers to infer both.

The survey index makes the lineage problem visible because it places the main report, questionnaire, appendix and presentation together as the 2026 package. That is good publication practice. It also makes cross-document agreement a reasonable expectation. A bundle is more than a shelf of related PDFs; it is a claim that the artifacts describe the same research object.

An immutable crosswalk would connect the item number and option order in the questionnaire to the chart, report table, appendix table and presentation. Each output would carry its accepted count, extract version, calculation precision and publication date. If an artifact is corrected, the earlier file would remain available with a correction note rather than silently changing the historical evidence.

A priority-allocation receipt

APNIC does not need to publish respondent identities or a giant methodological appendix. A compact receipt beside Question 29 would be enough.

First, name the response universe. State how many records reached the item, how many were valid under the 100-point rule and how many entered each published output. If a segment table requires classification fields that reduce the base, label that subset explicitly. Do not let Base, Sample Size and Total stand in for different definitions without saying so.

Second, publish the validation and exclusion sequence. A short ledger could report blanks, incomplete totals, duplicates, out-of-range entries and any other exclusion as separate counts. Where no such case occurred, zero is useful information. Missingness should remain visible instead of being absorbed into a denominator.

Third, identify weighting and precision. Say whether the figures are unweighted respondent means or weighted estimates. Give the rounding rule and retain an unrounded calculation artifact internally. The main report and Appendix B should point to the same source version or explain why they do not.

Fourth, add safe distribution summaries. For each activity, report a median and an interquartile range or another suitable spread measure. Show the proportion of zero allocations and the proportion above a high-concentration threshold selected in advance. A respondent-level concentration statistic would make the aggregate balance claim testable without revealing individual vectors.

Fifth, publish the crosswalk and revision history. The questionnaire, main chart, segment table, appendix and presentation should carry one immutable item identifier and one data-version identifier. A correction note should reconcile 1,039, 1,038 and 1,037, and the 9.9/9.8 difference, without erasing the documents in which readers encountered them.

This receipt would not decide APNIC’s priorities. It would separate three layers that the current presentation compresses: what respondents were asked, which records were counted and what aggregate structure the accepted responses support. That separation protects the survey from over-interpretation as much as it holds the institution to account.

The right conclusion today is bounded. APNIC has published a useful forced-choice signal. The main report’s displayed allocation closes at 100 and shows no single activity dominating. The official files also disclose three bases and omit the distribution required to know whether balance belongs to individual portfolios or only to their average. Those are repairable evidence gaps, not permission to invent a scandal.

Source trail