First Nations Management & Leadership · Arcus perspective
Building Institutional Memory in First Nation Governments
Institutional memory is the ability to use what the Nation knows
A government can retain thousands of documents and still struggle to continue a task when one employee is away. The missing knowledge may be which version was approved, why an exception was made, who must be consulted or how an annual process actually works. Storage preserves files; institutional memory enables responsible action.
Arcus’s central proposition is that institutional memory should be designed around consequential work. Start with the decisions, obligations and services that must continue, then identify the records, context, skills and relationships needed to carry them out. This makes the task manageable and avoids an expensive attempt to document everything equally.
This article addresses ongoing organizational knowledge across ordinary work, staffing changes and external assignments. Election orientation is one application, covered separately. The Nation determines how its knowledge is governed; an administrative knowledge program should not presume authority over cultural knowledge or make information broadly accessible merely because it has been recorded.
Evidence points to both usability and control
Tsawwassen First Nation’s September 2011 records policy describes records as evidence of activities, decisions and outcomes. It assigns responsibility for organized, secure and retrievable records and connects policy with supporting procedures and a records standard. This is a concrete institutional design example. It does not demonstrate measured performance gains or establish current requirements for another Nation.1
The First Nations Information Governance Centre explains OCAP® as ownership, control, access and possession, with expression shaped by each Nation’s worldview and protocols. Its guidance makes clear that control over information involves more than the location of a file. It informs the questions a Nation should ask about information stewardship; it is not a generic software certification.2
Arcus’s synthesis is that usable memory has two requirements: people with the appropriate authority must be able to find and understand information, and the Nation must retain meaningful control over its use. More documentation without those conditions can increase exposure and confusion instead of continuity.
Identify the knowledge that would be costly to lose
Begin with a small set of critical activities: an essential service, a recurring financial or reporting obligation, a major agreement, or an initiative approaching an important decision. Ask what would happen if the principal employee were unexpectedly unavailable. Would another authorized person know the current position, next action and source of authority?
Distinguish records from practical knowledge. An agreement may describe obligations while an experienced employee knows the working timetable, the dependencies and which counterpart can resolve a problem. Both can matter, but they require different preservation methods. A searchable repository helps with the agreement; supervised practice and a maintained contact history may help with the working process.
Prioritize according to the consequence of interruption, the difficulty of reconstructing the knowledge and the concentration of knowledge in one person. A rare task with serious consequences may deserve more attention than a frequently used form. Avoid treating file volume as a proxy for importance.
Diagnose why the knowledge is unavailable
There are several competing explanations for repeated reconstruction. Records may not have been created, may be stored in personal locations, may have unclear status, or may be technically accessible but difficult to interpret. Staff may also lack the time or confidence to use available guidance.
Each explanation suggests a different intervention. Missing records require a better capture process. Dispersed records require agreed custody and retrieval. Conflicting versions require a clear authoritative source and update responsibility. Knowledge that depends on judgment requires discussion, examples and practice rather than a longer procedure manual.
If the problem is excessive workload, adding documentation requirements without changing priorities may make continuity worse. Staff may produce superficial notes or postpone essential work. Identify the time needed to preserve critical knowledge and make an explicit choice about coverage, sequencing or additional support.
Preserve the reasoning behind consequential decisions
A decision record should allow a later authorized reader to understand what was decided, by whom, on what authority and with what conditions. For consequential choices, retain the relevant reasons, assumptions and alternatives alongside the official decision, according to the Nation’s records practices.
The purpose is not to create a second competing version of minutes or resolutions. It is to connect the authoritative decision with the information needed to interpret and implement it. Clearly distinguish approved direction from staff analysis, draft proposals and subsequent changes.
For a hypothetical service redesign, the useful record might explain why a phased approach was chosen, which resource assumptions supported it and when the arrangement should be reviewed. Without that context, a successor may mistake a temporary compromise for a permanent policy or repeat an option already rejected for a reason that still applies.
Transfer practical knowledge through work
Exit interviews can identify useful information, but they are a weak primary strategy when departure is sudden or the employee is already completing many other tasks. Build transfer into ordinary work through paired delivery of critical processes, cross-training and short reviews after significant activities.
Ask the person learning a process to perform an appropriate part of it with supervision and explain the next steps. This reveals gaps that a completed checklist may conceal. Record the points where judgment, approval or specialist support is needed, rather than implying that every situation can be reduced to a fixed instruction.
Relationship knowledge also needs continuity. Maintain institutional contact details, the purpose of the relationship and relevant commitments in an authorized location. Introduce a backup contact where appropriate. This does not require recording private conversations indiscriminately or treating personal relationships as organizational property. Preserve what the Nation needs to continue its legitimate work.
Choose an operating model for knowledge stewardship
A centralized records function can set standards, support retrieval and manage custody consistently. It needs enough capacity to help departments rather than becoming a distant compliance unit. A fully distributed model keeps knowledge close to the work but can produce inconsistent naming, access and maintenance.
A combined model may give a central steward responsibility for common rules and support, while departments maintain the accuracy and usefulness of their own working knowledge. Define who owns each critical process record, who updates it and who checks that a backup can use it. These responsibilities need to remain clear when positions change.
External support can help organize a backlog or establish a system, but the continuing responsibility must be assigned inside the Nation or through an explicitly governed arrangement. Include the handover of usable deliverables, supporting records and agreed access arrangements in external assignments. A final presentation alone may leave the working knowledge with the provider.
Assess technology by the continuity it enables
A new platform may help when existing tools cannot provide reliable access, version management or retrieval. It will not resolve an unclear record owner or determine who has authority to use information. Establish those requirements before selecting or expanding a system.
Compare improving current practices, adding targeted support and adopting new technology. Include the costs of organizing existing information, migration, access configuration, staff learning, ongoing administration and eventual export or transition. Low purchase cost can conceal substantial internal work.
Test a proposed arrangement with a real task. Can an authorized colleague locate the current record, understand its status and complete the appropriate next step? Can access be limited and changed when roles change? Can the Nation obtain its information in a usable form if a service relationship ends? These questions are more informative than a demonstration of search features alone.
Maintain memory without preserving everything indefinitely
Institutional memory requires deliberate maintenance. Outdated procedures can be more misleading than missing ones because they appear authoritative. Assign review triggers such as a changed policy, revised agreement, system change or significant learning from delivery. Mark obsolete guidance clearly through the approved records process.
Retention, access and disposal must follow the Nation’s applicable requirements, including any preservation obligations. Do not use a knowledge-cleanup project as a reason to destroy records without authorization. Equally, keeping unnecessary duplicate sensitive material in many locations can make control more difficult.
Keep cultural knowledge, personal records and confidential advice within their appropriate protocols and access arrangements. The objective is not a universal repository open to everyone. It is dependable access for authorized purposes, with clear stewardship and respect for the Nation’s decisions about its information.
Measure whether another person can continue the work
Useful checks include the time spent reconstructing a current position, the number of critical processes without a capable backup, and errors caused by using obsolete instructions. Interpret results in context: complex work will not always be transferable immediately, and some responsibilities appropriately require specialized authority.
Use a small set of continuity exercises rather than counting uploaded documents. Ask an authorized colleague to locate the current agreement, explain the next deadline or demonstrate a routine task using the available guidance. Record the gap and improve that part of the process.
The strongest sign of progress is that knowledge remains usable when circumstances change. That may mean faster orientation, fewer conflicting versions or less dependence on a single employee. Establish local evidence of those improvements before claiming savings or wider service impacts.
The Arcus usable-memory framework
This original Arcus decision framework is a management aid for local adaptation. It is not a validated assessment instrument or a substitute for the Nation’s authority and relevant professional requirements.
Critical work
Question: What must continue if a key person is unavailable?
Decision evidence: Prioritized services, obligations and decisions, assessed for interruption consequences.
Authoritative record
Question: What information can the next person rely on?
Decision evidence: A current source, status, decision context and traceable changes.
Practical capability
Question: Can someone else perform the necessary work?
Decision evidence: Supervised practice, backup capability and identified points requiring judgment or approval.
Control
Question: Who may hold, use and share the knowledge?
Decision evidence: Nation-defined stewardship, access, provider arrangements and applicable protections.
Renewal
Question: Who keeps it useful as circumstances change?
Decision evidence: Named maintenance ownership, review triggers and periodic continuity exercises.
Turn the design into an operating commitment
Select one critical process with a clear continuity risk. The responsible manager and information steward should identify the authoritative records, necessary context and people who need access. Confirm the relevant protections and responsibilities before collecting or moving information.
Allocate time for the current process holder and a suitable backup to work through the task. Capture only the guidance needed to make the process understandable and repeatable, with clear points for approval or specialist advice. Resolve conflicting versions and name the person responsible for future updates.
Test whether the backup can complete the appropriate next step using the available information. Fix the gaps, then extend the approach to the next priority. Resource stewardship as ongoing work so the Nation retains usable knowledge rather than a one-time documentation project.
Sources and limits of the evidence
- Tsawwassen First Nation, Policy for Records and Information Management, September 28, 2011. Policy statement and structure reviewed as a historical primary example; not a claim about current implementation, legal requirements elsewhere or measured outcomes.
- First Nations Information Governance Centre, The First Nations Principles of OCAP®. OCAP® is a registered trademark of the First Nations Information Governance Centre (FNIGC). Primary principles guidance; no certification or endorsement of this article or framework is implied.
Research reviewed October 18, 2026. Decision frameworks, options and hypothetical illustrations are Arcus management synthesis. No client outcomes or universal savings or impact benchmarks are claimed.
Governance & Leadership collection · Governance continuity after elections · Organization design services · Arcus consultant directory