30 Calendar Day Tribal Consultation Process for U.S. Officials
The tribal consultation process is a nation-to-nation, two-way exchange in which agencies identify affected Tribes early, give timely notice, ensure decision-makers show up at the table, and document how Tribal input shaped the outcome. Skipping any one of these elements turns consultation into a formality rather than a genuine dialogue. The applicable rules start with Executive Order 13175 and are made operational through agency-specific policies at DOI, EPA, ACHP, and NPS.
TL;DR:
Agencies should identify tribes with interests beyond reservation boundaries by reviewing treaty rights, cultural resources, and consulting directly with tribal officials.
Consultation must follow a four-phase process: identification, notification, meaningful input, and follow-up, with clear documentation at each step.
Notices should be plain-language, specify a 30-day response window, and be sent via multiple channels to ensure proper tribal awareness.
Tribal input must be considered seriously and documented, even if the final decision diverges from the tribes’ requests or concerns.
Coordinating across multiple agencies and including tribal preferences in meeting formats enhances consultation effectiveness and legal defensibility.
Table of Contents
The legal and policy framework behind consultation
No single statute lays out a universal federal consultation procedure. Instead, Executive Order 13175 and agency-specific policies establish the applicable process and determine when an action or policy has enough Tribal implications to trigger consultation. This structure gives agencies room to tailor procedures to their mission, but it also means officials must check the specific policy governing their agency rather than assume a one-size-fits-all standard exists.
The Department of the Interior offers the clearest procedural template in 18 IAM 6, the Indian Affairs Manual’s Tribal Consultation Process, which sets a 30 calendar day advance notice standard, requires federal decision-maker participation, mandates formal records, and calls for a consultation summary report posted publicly on BIA.gov. DOI’s companion directive, 512 DM 5, reinforces these expectations at the departmental level and applies them across DOI bureaus.
EPA’s approach, articulated in its 2023 Policy on Consultation with Indian Tribes, organizes the work into four phases: Identification, Notification, Input, and Follow-up. The policy pushes for early notice built on plain-language materials, names practical notification channels such as email and the Tribal Consultation Opportunity Tracking System, and instructs staff to honor Tribal scheduling preferences rather than impose federal convenience on the timeline.
The National Park Service applies a parallel structure through Director’s Order #71C, which stresses that consultation windows must accommodate Tribal governmental review cycles, not just agency deadlines. Across these frameworks, a few baseline principles repeat:
Consultation is government-to-government, meaning it occurs between agency officials and Tribal leadership, not between agency staff and individual Tribal members.
Early identification of Tribal implications is a prerequisite, not an afterthought layered on once a decision is nearly final.
Written records, including a summary of Tribal input and the agency’s response, are required across DOI, EPA, and NPS policies.
Consultation does not automatically require Tribal consent, though certain actions on Tribal lands carry separate consent requirements under specific statutes.
That last point matters for officials who sometimes treat consultation as either meaningless or as an implicit veto. It is neither. Agencies must give Tribal input meaningful consideration and explain how it factored into the decision, even when the final outcome differs from what a Tribe requested.
Running the four-phase consultation process step by step
Agencies that get consultation right tend to follow the same operational rhythm, whether or not their governing policy uses these exact labels: identification, notification, input, and follow-up. Each phase has specific, checkable requirements.
Identification. Determine whether the action, policy, or project has Tribal implications by screening for effects on Tribal lands, treaty rights, cultural resources, or federal trust responsibilities; document the screening decision even when the answer is no.
Notification. Send written notice that states the subject matter, decision timeline, points of contact, and how to request additional time; use plain language and distribute through multiple channels, including direct mail, email, and phone outreach to known Tribal contacts.
Input. Hold consultation sessions, whether in person, virtual, or written, that give Tribal representatives a real chance to shape the decision before it is finalized, not after a draft is already locked in.
Follow-up. Produce a consultation summary report describing what was heard, how it influenced the decision, and where it did not, then share that report with the Tribes involved and, where required, post it publicly.
The 30-day advance notice standard set in 18 IAM 6 is echoed in the White House memorandum on uniform standards for tribal consultation, which also calls for a 30-day post-consultation comment period, with exceptions permitted when the agency explains its reasoning. Treat these figures as defaults, not ceilings: a Tribe facing a council schedule or a ceremonial calendar may need more time, and agencies should build that flexibility into their internal timelines from the start rather than negotiating it under pressure near a deadline.
Pro Tip: Build your internal project schedule around the Tribe’s decision cycle, not the other way around; a consultation invitation that lands two weeks before a tribal council’s quarterly meeting will almost always produce a stronger, more authoritative response than one that demands an answer within days.
Notification content deserves particular attention. A notice that buries the actual decision point in technical jargon, or that fails to name a specific contact who can answer questions, invites the kind of confusion that later gets read as inadequate consultation. Officials should treat the notice itself as a working document, not boilerplate copied from the last project.
Identifying which Tribes belong at the table
Getting the invitation list right is often the single hardest part of consultation, and getting it wrong is one of the most common reasons consultation efforts draw legal or political challenges later. Tribal implications rarely stop at a reservation boundary. Treaty rights, off-reservation trust lands, and ancestral homelands can extend a Tribe’s interest in a project well beyond its current jurisdictional footprint, and cultural resources tied to specific places do not respect modern property lines.
A defensible identification process usually includes:
Mapping treaty-reserved rights, such as hunting, fishing, or gathering rights, that may extend into the project area even when no Tribal land is directly affected.
Reviewing known cultural-resource indicators, including previously identified traditional cultural properties, sacred sites, and archaeological records.
Contacting Tribal Historic Preservation Officers directly, since THPOs often hold institutional knowledge that does not appear in any public database.
Notifying tribal leadership and any tribal designees named for consultation purposes, since a THPO contact does not always substitute for government-to-government notice to elected leadership.
Coordinating across multiple Tribes with overlapping interests in the same geography, rather than running parallel, disconnected consultations that produce conflicting commitments.
When several Tribes have a plausible interest in the same project, agencies face a choice between joint sessions and Tribe-specific meetings. Joint sessions save time and can surface shared concerns efficiently, but some Tribes prefer separate, confidential consultation given differing histories, governance structures, or sensitivities about sharing cultural information in front of other Tribes. The safest default is to ask each Tribe its preference rather than assume a joint format will work for everyone.
Recordkeeping during outreach itself matters as much as the consultation sessions that follow. Agencies should log every notification attempt, including dates, methods, and responses, since gaps in that record are exactly what surface when a consultation decision gets challenged months or years later.
Making consultation sessions genuinely two-way
A meeting that only delivers information is not consultation, even when an agency calls it that. The distinguishing feature of meaningful consultation is that the decision is still open when the conversation happens, and the people in the room have the authority to change course based on what they hear.
Format matters more than agencies often assume. A site visit lets Tribal representatives point directly to features a desk review would miss; a virtual session can lower the burden on Tribes with limited travel budgets or distant offices; a confidential session may be the only appropriate format when the subject involves sensitive cultural information. Ask which format the Tribe prefers rather than defaulting to whatever is easiest for agency staff.
Preparation determines whether the actual meeting time gets used well. Read-ahead materials, written in plain language rather than agency jargon, give Tribal representatives time to consult internally before the session and arrive ready to engage substantively rather than spend the meeting decoding acronyms.
Send technical briefing materials at least as far ahead as the notice period allows, not the day before the meeting.
Confirm that the agency official with actual decision authority, not just a project liaison, will attend and can discuss real outcomes.
State any hard constraints on the decision up front, since a Tribe cannot meaningfully weigh in on options the agency has already ruled out without saying so.
Avoid scheduling consultation only after a preferred alternative has been selected internally, even informally.
Pro Tip: If the person attending the consultation session cannot explain why an option was ruled out or commit to carrying a concern back to the decision-maker, that session is information sharing, not consultation, and should be labeled honestly as such internally.
Agencies sometimes worry that acknowledging constraints up front will shrink the conversation. In practice, the opposite tends to happen: Tribal representatives can direct their input toward the choices that remain genuinely open, which produces sharper, more usable feedback than a broad conversation with no stated boundaries.
Documentation, confidentiality, and FOIA exposure
Every consultation should leave behind a written record that would let a new staff member, or a court, reconstruct exactly what happened and why. That record typically includes the notification sent, attendance at each session, meeting summaries or transcripts, written comments received, any commitments the agency made, and the agency’s documented response to Tribal input.
DOI’s consultation summary report requirement, described in 18 IAM 6, is a useful model regardless of which agency is running the process: a short document naming what was heard, how it affected the decision, and where it did not, shared with the Tribes involved and posted where policy requires. That single document does more to defend a consultation record than pages of raw meeting notes ever will.
Confidentiality requires its own handling, particularly around cultural information. Tribes often share details about sacred sites or traditional practices only on the understanding that the information stays protected. Agencies should:
Ask explicitly whether information shared is intended to remain confidential before recording or summarizing it.
Document any agreed limits on how sensitive information will be used or described in public materials.
Explain, honestly and in advance, that records held by a federal agency may be subject to Freedom of Information Act requests, and that some protections exist for culturally sensitive material but are not absolute.
Keep sensitive cultural details out of public-facing summary reports when a Tribe has requested that treatment, while still documenting internally that consultation occurred.
Being upfront about FOIA exposure before a Tribe shares sensitive information is far better than discovering the gap after a request arrives. Written consent language, agreed at the start of a relationship, protects both the agency and the Tribe later.
How Section 106 consultation fits with government-to-government duties
Section 106 of the National Historic Preservation Act creates a separate, overlapping consultation duty focused specifically on historic properties, including those of religious and cultural significance to Tribes. Under ACHP’s Consultation with Indian Tribes Handbook, this obligation applies even when the project sits entirely off Tribal land, because a historic property’s significance to a Tribe is not bounded by jurisdiction.
Section 106 and government-to-government consultation are related but distinct. Section 106 focuses narrowly on identifying and resolving effects to historic properties through a defined regulatory process that can produce a Memorandum of Agreement. Government-to-government consultation is broader, covering any policy or action with Tribal implications, and remains the agency’s responsibility even when it overlaps with Section 106 steps.
An applicant or contractor may conduct early coordination on cultural resource surveys, but the agency itself remains responsible for the government-to-government consultation duty and cannot delegate it without the Tribe’s agreement.
THPOs should be brought in as early as possible, since their role in identifying historic properties often surfaces concerns that reshape a project’s design before options narrow.
A Memorandum of Agreement should document not just resolution but any unresolved objections, since a clean record of disagreement protects everyone if the project is later challenged.
Agencies should track Section 106 concurrence separately from broader consultation sign-off, since the two processes can conclude on different timelines.
Practical experience documenting Section 106 coordination, including how SHPO’s 30-day response window interacts with agency decisions, offers a useful companion reference for Section 106 consultation procedures for federal staff.
Coordinating across state, local, and federal roles
State and local agencies should not assume federal consultation rules apply to them automatically. Federal policies like 18 IAM 6 and the EPA’s consultation policy govern federal actions; a state department of transportation or a county planning office operates under whatever consultation commitments it has separately adopted, whether through state law, tribal-state agreements, or its own policy.
That gap is an opportunity, not just a risk. Agencies operating in the same geography can reduce duplicated effort and Tribal fatigue through coordination:
Hold joint consultation sessions when multiple agencies need input on related aspects of the same project, rather than sending a Tribe through three separate meetings.
Maintain a shared calendar and contact list across agencies working in the same region, so notification does not depend on one office’s institutional memory.
Draft a written, mutually agreed consultation protocol with each Tribe that specifies notice methods, timelines, and points of contact, adapting the ACHP’s guidance on state and local coordination where it fits.
Loop in DOI or ACHP early when a project touches federal land, federal funding, or a federal permit, since that often triggers federal consultation duties layered on top of any state process.
Building a consultation protocol you can actually use
A written protocol turns consultation from an improvised effort into a repeatable, defensible process. The strongest protocols share a common structure, whether the agency is federal, state, or a project team supporting either.
Define scope and triggers. Specify what kinds of actions require consultation and what screening criteria determine Tribal implications.
Set default notice language and timelines. Draft standard notice text, name the default 30-day notice window, and state the process for requesting extensions.
Name points of contact. Designate a specific Tribal Consultation Official for the agency and request a corresponding tribal point of contact.
Include a confidentiality clause. State how sensitive cultural information will be handled and what FOIA exposure exists.
Attach a record template. Standardize what gets logged: notifications sent, attendance, comments received, commitments made.
Commit to a response timeline. State how long after consultation closes the agency will issue its summary report and response.
Before, during, and after each session, a short checklist keeps the process consistent: before the meeting, confirm decision-maker attendance and send read-ahead materials; during the meeting, document attendance and capture commitments in writing; after the meeting, draft the summary report and send it back to the Tribe for review before finalizing.
Protocol component | What it should specify |
Notice timeline | Default 30 calendar days, with documented process for extensions |
Decision-maker requirement | Named official with authority to discuss outcomes attends every session |
Record template | Invitations, attendance, comments, commitments, and agency response |
Confidentiality clause | How sensitive cultural information is handled and FOIA limits explained |
Response timeline | Deadline for issuing the consultation summary report after input closes |
Performance follow-through matters as much as the template itself. Agencies that designate a Tribal Consultation Official, require annual staff training consistent with the White House memorandum’s uniform standards, and report annually on consultation activity tend to catch process gaps before they become legal exposure. A protocol left in a drawer protects no one; one reviewed and updated after each major consultation earns its place in the process.
Practitioner notes on bridging policy and practice
Turning a written protocol into a consultation that actually lands well with Tribal partners takes more than a template. Read-ahead materials work only when they are genuinely plain-language, tested against someone outside the project team before they go out. Facilitation should keep the room decision-focused: a skilled neutral facilitator can surface Tribal priorities early in the session rather than letting technical staff dominate the agenda with background briefings.
Draft technical summaries in plain language first, then layer in agency terminology only where precision requires it.
Use a neutral facilitator to keep sessions focused on decisions still open, not just information already decided.
Build a standing record template before the first session, so documentation stays consistent across a multi-year project.
Route sensitive cultural information through a confidentiality review before it appears in any public-facing summary.
Why meaningful consultation is worth the extra time
The strongest argument for genuine consultation is not just legal risk reduction, though that risk is real when agencies treat consultation as a formality. It is that Tribes often hold the clearest, earliest signal about which options will work and which will generate years of conflict. Projects that build in real consultation time tend to reach decisions that hold up, both legally and in the community’s eyes, because the record shows Tribal input actually shaped the outcome rather than arriving after the fact.
— Ignacio
How AMAUTA Public Affairs supports consultation implementation
Agencies and project teams running consultation alongside permitting, environmental review, and public outreach often find the coordination burden outpaces in-house capacity. AMAUTA Public Affairs supports that work through permitting support and stakeholder relations built around the same principle this guide describes: early, well-documented engagement produces better outcomes than last-minute outreach. Our services extend to facilitation and community-engagement planning that can run alongside formal Tribal consultation without duplicating it.
When a project’s timeline, geography, or number of interested parties makes in-house coordination difficult, an outside team can keep notification, scheduling, and documentation on track while agency staff focus on the substance of the decision. Get connected with AMAUTA Public Affairs to talk through what support your project needs.
Primary sources worth bookmarking
Executive Order 13175: the foundational directive requiring federal consultation with Tribes.
18 IAM 6: DOI’s detailed procedural standard.
EPA’s 2023 consultation policy: the clearest phase-by-phase model.
ACHP’s Consultation with Indian Tribes Handbook: Section 106 coordination guidance.
NPS Director’s Order #71C: timelines built around Tribal governmental cycles.
Sources
FAQ
What is the tribal consultation period?
Most federal policies default to a 30 calendar day advance notice period before a scheduled consultation, as set out in 18 IAM 6 and echoed in the White House’s uniform standards memorandum, which also calls for a 30-day post-consultation comment window. Agencies can extend either period when a Tribe’s internal review schedule requires more time, and they should document the reason for any exception.
When to consult with Tribes checklist?
Consultation should begin as soon as an agency identifies that a proposed action, policy, or project may affect Tribal lands, treaty rights, or cultural resources, well before any decision is finalized. A practical checklist includes screening for Tribal implications early, sending plain-language notice with a clear timeline, confirming decision-maker attendance, and documenting the agency’s response to Tribal input.
What is FEMA’s policy on tribal consultation?
This guide focuses on the consultation frameworks published by DOI, EPA, ACHP, and NPS, which is not publicly listed here for FEMA specifically. Officials seeking FEMA’s own consultation procedures should check FEMA’s published policy directly rather than assume the DOI or EPA models apply without modification.
What is consultation in tribal government?
From a Tribal government’s perspective, consultation means direct, government-to-government dialogue with federal or state officials before a decision affecting Tribal interests is made, not a briefing delivered after the fact. It requires that the Tribe’s input have a genuine chance to change the outcome and that the agency explain in writing how that input was considered.
What is the difference between Section 106 consultation and government-to-government consultation?
Section 106 consultation is a narrower legal duty focused on identifying and resolving effects to historic properties, including those with religious or cultural significance, under the National Historic Preservation Act. Government-to-government consultation is broader, covering any agency action or policy with Tribal implications, and the agency retains that responsibility even where the two processes overlap.
Recommended
Comments