Summary

  • LACNIC’s own documents identify contributors, listening channels, a previous-plan assessment, situational analysis, collaborative SWOT work and a final strategic map. They do not, in the checked public record, expose an issue-level path connecting those stages.

  • “Collective” is a provenance claim. It does not mean every view prevailed, that participants authorised the result, or that consultation created consensus. The Board and management remain responsible for decisions.

  • A compact public trace can preserve source class, channel, issue, analytical treatment, disposition, reason, authority and final-text location without disclosing identities, confidential interviews or raw personal survey answers.

  • The principal loss from an absent trace is auditability and institutional memory. It is not automatic proof that the strategy is unsound or that LACNIC failed to consult.

The documentary mismatch is narrow. LACNIC’s six-page 2026–2029 Strategy says the plan was not developed internally and names members, NIRs, the technical community, the Board of Directors, staff and other ecosystem actors.

The CEO’s account of the process adds regional NIR and global RIR colleagues. It also names satisfaction surveys, member support and visits, event meetings, other dialogue spaces and accumulated experience among the inputs.

The strategy says work began with an assessment of the previous plan. It then gathered expectations, combined internal and external situational analysis, and moved into a SWOT analysis developed collaboratively by the LACNIC team and Board.

The result is presented as a map towards 2029. It integrates identity, mission, vision and internal capabilities, while the public strategic-plans page supplies the institution’s publication context.

Those documents describe a route. They do not themselves let a reader take one input, issue or dissent and follow it through neutral synthesis, SWOT or other analysis, disposition, decision authority and a precise location in the final strategy.

That is a boundary of the checked public evidence. It is not proof that LACNIC kept no internal records, used no further instruments, or failed to consider the contributions it received.

Primary-source context, not independent validation

The three LACNIC documents are primary-source context. They establish what the institution says about its process, contributors, channels, analysis and final map. They do not independently validate mandate, legitimacy, representativeness or consensus.

That distinction is especially important because the strategy describes the process as one of continuous improvement, participation and transparency. Those are institutional claims about design and provenance, not independent findings about how authority was conferred.

What “collective” can properly mean

Calling the strategy collective is a provenance claim. It says that defined constituencies and organisational bodies contributed to the process, rather than that the final text emerged solely from internal drafting.

It does not mean every view prevailed. It does not establish that participants authorised the result, that the process reached consensus, or that consultation displaced the Board’s responsibility.

Heng Lu’s doctrine essay supplies a useful caution: attendance, participation and listening can be evidence of engagement, but they do not by themselves create authorisation, mandate or consensus.

The essay is a doctrinal lens, not evidence about LACNIC’s conduct. Applied narrowly, it does not support an accusation of false or illegitimate consultation. It clarifies the evidentiary burden created when an institution calls a strategy collective while retaining Board and management authority.

The proper test is therefore not whether contributors controlled the result. It is whether the public account preserves enough of the path to show how inputs entered analysis, how they changed, and where authorised decision-makers made choices.

Five institutional states

Listening means that a channel existed and an input was received or discussed. Representation concerns who or what source classes were present relative to a relevant constituency.

Consensus denotes convergence and cannot be inferred from attendance. Synthesis is the analytical act of grouping, translating or combining inputs into issues. Decision is the exercise of authority to accept, modify, combine, defer, decline or leave an issue unresolved.

A credible trace keeps those states separate. It protects contributors from the assumption that being heard meant being accepted, and it protects LACNIC from the opposite assumption that a non-adopted input was ignored.

Different channels produce different evidence

Survey, visit, support, event, peer-registry, staff and Board inputs should remain analytically distinct. Their selection effects, units and institutional roles differ.

A satisfaction survey has an instrument, an invitation boundary, a response denominator and non-response limits. A member visit can produce deeper contextual evidence from a selected encounter, but it is not interchangeable with a survey response.

Support interactions arise from operational needs and may reveal recurring friction. Event meetings are bounded by attendance, agenda and setting. Other dialogue spaces may have different entry conditions again.

NIR and RIR inputs are institutional and comparative. Staff contributions carry implementation knowledge. Board contributions combine governance responsibility with strategic judgement. Technical-community contributions may reflect sustained process experience or an occasional participant’s narrower encounter.

Each source can be valuable without serving as a proxy for another. Counts of respondents, meetings, organisations, support cases and contributors cannot be added into one participation total without qualification.

A compact input-to-strategy trace

The remedy is not publication of identities, confidential interviews or raw personal survey answers. It is a compact, privacy-safe record that separates evidence of participation from evidence of substantive treatment.

Trace field Minimum public content Evidentiary purpose
Input-round identifier Stable label for each exercise or collection period Ties later summaries to a bounded round
Source class Member, NIR, RIR, technical community, Board, staff or other stated class Shows institutional perspective without naming people
Channel and dates Survey, visit, support, event, peer exchange or other channel, with dates Preserves collection conditions
Invitation or session boundary Who was invited, eligible or present, at a non-identifying level Defines the relevant population or session
Participation count and limits Non-identifying count, unit and material qualifications Prevents unlike counts being combined
Stable issue identifier Persistent label for each distinct issue Allows tracking after consolidation or wording changes
Neutral synthesis Concise statement of the issue, separated from advocacy language Makes analytical transformation visible
Evidence and confidence note Source breadth, corroboration and relevant limits Distinguishes repeated patterns from isolated observations
SWOT or analysis join SWOT item or other analytical state affected by the issue Connects listening to analysis
Disposition Accepted, modified, combined, deferred, not carried or unresolved Distinguishes omission, rejection and pending judgement
Reason and decision authority Brief rationale and responsible body or role Separates contributor preference from authorised choice
Final strategy pointer Axis, capability statement or other precise location Shows where a carried issue landed
Version and correction history Release date, corrections and preserved prior versions Makes later changes reviewable
Privacy or redaction basis Category withheld and reason Protects participants without breaking the chain

This trace does not require false precision. Several contributions may combine into one issue, one issue may affect several passages, and a SWOT item may be reframed before decision.

Those transformations should be recorded rather than hidden. “Combined”, “modified” and “not carried” are legitimate dispositions when the reason and decision authority are visible at an appropriate level.

An evidence note should not turn heterogeneous sources into an invented vote. Repetition across support interactions and a single RIR observation may carry different weight while both remain relevant.

The impact mechanism

Without stable identifiers, management can describe a priority as community-derived without exposing the source path. The description may be sincere and accurate, yet an outside reviewer cannot reproduce the connection.

A contributor can make the opposite mistake. Knowing that an issue was voiced, the contributor may infer that being heard meant being accepted or that non-appearance in the map proves neglect.

A later reviewer then cannot distinguish a missing input from a rejected one, a minority warning from a common concern, or a management choice from a member request.

An absent issue may have been missed, combined, deferred, judged outside scope or deliberately not carried. A final sentence may reflect member evidence, NIR coordination, RIR comparison, staff analysis or Board judgement.

The loss is traceability and institutional memory. It is not automatic proof of a bad strategy, defective consultation or unsound strategic axes.

What the trace must not become

The trace should use minimisation. Source classes can replace names, small counts can be suppressed where disclosure risk is material, and survey answers can be synthesised without releasing personal responses.

Confidential interviews can contribute to an issue while the public record states only the source class, analytical limit and redaction basis. The objective is a reviewable join, not exposure of participants.

The Board’s authority remains intact. Consultation supplies evidence, concerns, options and constraints. It does not transfer strategic responsibility or turn frequency into command.

The checked evidence stops at the strategic map, and so does this audit. It does not test annual plans, budgets, implementation or results.

On the public record supplied, contributors and channels are named, the analytical route is described, and the final map is visible. The issue-level join between them is not.

Sources