Skip to main content
Records Authority
Category: Digital Preservation

Designated Community

Simply put

A designated community is an identified group of people who are expected to be able to understand a particular set of preserved information. Defining this group helps those responsible for keeping records over the long term decide what supporting context and explanation must be preserved alongside the information itself so it remains usable.

Formal definition

In digital preservation practice, a designated community is an explicitly identified group of potential consumers who should be able to understand a particular set of information. Identifying the designated community is foundational to preservation planning because it establishes the assumed knowledge base of the intended users, against which a preserving repository determines what representation information, metadata, and contextual documentation must be retained to keep the information independently understandable over time. The concept concerns understandability for a defined audience rather than access rights or general availability, and its practical application depends on organizational policy and the nature of the material preserved. Note that the same phrase is used with entirely different meanings in unrelated domains such as tax and community-development law; those senses fall outside the recordkeeping and preservation scope defined here.

Why it matters

The designated community concept addresses a problem that is easy to overlook in the short term but decisive over the long term: information that is perfectly understandable to its creators today may become unintelligible to future users who lack the same background knowledge, technical tools, or contextual assumptions. By explicitly identifying the group expected to understand a body of preserved information, a repository establishes a benchmark for how much supporting context, explanation, and documentation must be retained. Without a defined designated community, decisions about what to preserve alongside the information itself tend to be arbitrary, and preserved records may degrade into data that no one can meaningfully interpret.

Defining the designated community is what allows preservation to be planned rather than assumed. It shifts the question from the vague aspiration of keeping information forever to the practical one of keeping information understandable for a specific audience. This framing helps those responsible for long-term retention make defensible, documented choices about representation information and contextual metadata, and it gives them a criterion against which preservation adequacy can be assessed over time.

Professionals should also be careful with the phrase itself. In recordkeeping and digital preservation, a designated community concerns understandability for a defined audience, not who is permitted to access material or how widely it is made available. The same phrase carries entirely unrelated meanings in other domains, such as certain tax and community-development contexts where it refers to residents of particular geographic areas; those senses fall outside the preservation scope defined here.

Who it's relevant to

Digital preservation specialists
Those responsible for keeping digital information usable over the long term use the designated community as the foundation for preservation planning, determining what representation information and contextual documentation must be retained so the material remains understandable to its intended audience.
Archivists and repository managers
Staff operating preserving repositories rely on an explicitly identified designated community to make defensible, documented choices about what supporting context to keep alongside preserved records, and to assess whether preservation remains adequate over time.
Records managers overseeing long-term retention
Records professionals managing information that must survive over extended periods benefit from defining the designated community to move from a general goal of long-term retention toward concrete decisions about the contextual material needed to keep records understandable.
Information governance leads
Those setting policy for the long-term stewardship of information can use the designated community concept to frame accountable, criterion-based decisions about preservation, while keeping the concept distinct from access rights and general availability.

Inside Designated Community

Identified user group
The Designated Community is the specific group of potential consumers or users for whom preserved information is intended to remain understandable over time. It is defined by the preserving repository rather than being an open-ended or universal audience.
Knowledge Base assumption
The concept assumes the Designated Community possesses a particular level of background knowledge, or Knowledge Base, that allows members to interpret the preserved information without additional explanation. Preservation planning typically depends on defining this assumed knowledge explicitly.
Basis for Representation Information
Because understandability is judged against the Designated Community, the concept drives decisions about what Representation Information (such as structure, semantics, and context) must be preserved alongside the content so that it remains usable by that community.
Evolving definition over time
A Designated Community is not necessarily fixed; its composition and assumed knowledge may shift over long preservation timeframes, which may require periodic review and, in some cases, additional Representation Information to maintain understandability.
Repository accountability
Defining and documenting the Designated Community is generally the responsibility of the preserving organization, and it provides a defensible reference point against which preservation adequacy and long-term usability can be assessed.

Common questions

Answers to the questions practitioners most commonly ask about Designated Community.

Is the designated community simply everyone who might access the archive?
No. The designated community is not the same as the general public or the total set of possible users. It is the specific group, or set of groups, that a repository identifies as the intended users of its preserved information, and whose knowledge base the repository commits to supporting. Others may access the holdings, but the repository defines its preservation obligations against the designated community rather than against any possible user. This distinction matters because scoping too broadly can make preservation commitments impractical.
Does defining a designated community mean fixing who the users are permanently?
Not in the sense of a permanent, unchangeable roster of named individuals. A designated community is defined by its characteristics and assumed knowledge base rather than by a fixed membership. Because the knowledge, expertise, and expectations of intended users can shift over time, repositories typically revisit and, where appropriate, revise their definition. What is fixed is the repository's responsibility to keep information understandable and usable for whichever community it currently designates.
How does an organization go about defining its designated community?
Defining a designated community generally involves identifying who the intended users are, what they already know, and what they will need in order to understand and use the preserved information independently. This often draws on consultation with stakeholders, analysis of anticipated use, and consideration of the domain knowledge users can reasonably be assumed to hold. The definition is typically documented so that preservation and access decisions can be tested against it. The specifics depend on organizational context, sector, and the nature of the holdings.
How does the designated community influence what representation information or metadata must be preserved?
The assumed knowledge base of the designated community typically determines how much supporting information must accompany the preserved content for it to remain understandable. Where the community can be assumed to hold relevant expertise, less explanatory material may be required; where that assumption is weaker, more representation information may need to be captured and maintained. Decisions about descriptive, technical, and contextual metadata are, in many approaches, made by reference to what this community would need, so the definition directly shapes the scope of what is retained alongside the records.
When should a repository review or revise its designated community definition?
Review is commonly prompted by changes that could affect whether preserved information remains understandable to intended users, such as shifts in the knowledge base of the community, changes in mandate or user profile, technological change, or new access requirements. Many repositories treat this as a periodic activity rather than a one-off exercise. If a review indicates that the current definition no longer reflects actual intended users, the repository may need to reassess its preservation and representation commitments accordingly. Timing and triggers depend on organizational policy.
What are the practical consequences of scoping a designated community too broadly or too narrowly?
Scoping too broadly can make the repository's preservation obligations difficult to meet, because supporting a very wide or highly varied knowledge base may require extensive representation information and ongoing effort. Scoping too narrowly may leave some intended users unable to understand or use the holdings, undermining the purpose of preservation. The workable position typically lies in a defensible middle ground that reflects the users the repository genuinely intends to serve, documented clearly enough to guide consistent decisions. The appropriate balance depends on the repository's mandate and resources.

Common misconceptions

The Designated Community means anyone who might ever access the material.
The concept typically refers to a defined, identified group with an assumed level of background knowledge, not a universal or unbounded audience. Preservation decisions are calibrated to that defined group rather than to every conceivable future user.
Once set, a Designated Community remains valid indefinitely.
Because assumed knowledge can change over long timeframes, the definition often warrants periodic review. What is understandable to the community today may require additional Representation Information to remain usable for a comparable community in the future.
Defining a Designated Community is only about identifying users, not about preservation content.
The definition directly shapes what Representation Information must be preserved. It is closely tied to decisions about the structure, semantics, and context needed to keep content understandable, so it is a preservation planning concept rather than merely an audience label.

Best practices

Define the Designated Community explicitly and in writing, describing the assumed Knowledge Base rather than leaving the intended audience implicit or open-ended.
Use the documented Designated Community as the reference point for deciding what Representation Information must accompany preserved content to keep it understandable.
Review the Designated Community definition periodically, since assumed background knowledge may shift over long preservation timeframes.
When the assumed knowledge of the community appears to be eroding, consider capturing additional Representation Information to maintain long-term understandability.
Assign clear organizational responsibility for defining, documenting, and maintaining the Designated Community, treating it as a repository accountability rather than an informal assumption.
Retain the Designated Community definition as a defensible basis for assessing whether preservation measures are adequate for continued usability.