A first look, and where it goes

What a first look is, and what it is not

The check on this page is short on purpose. It is not an assessment, it determines nothing, and it carries no authority. It is a note you write early, in the project record, saying what you noticed and handing the question to the people who lead this work while there is still room to act on the answer.

That modesty is the point. A project team that writes a confident finding about whether a matter has Tribal implications has stepped into a decision that is not its own, and a well-written wrong answer is harder to correct than an honest question. The most useful thing a team can produce is an accurate, specific, early question.

Two lines carry most of the weight. The first is the decision that is still open and the date it closes, because that tells the office receiving it whether early engagement is still possible or whether the project is asking for comment on something already settled. The second is what your team will not decide on its own, because writing that down is what keeps a helpful project team from quietly becoming the agency's answer.

A first-look check for Tribal implications in one project

Five lines you fill in yourself, early, so the offices that lead this work receive an accurate question while the decision is still open.

Project and the decision still open Redesign of the contracting route for a DSD-funded service. Open decision: which entities may hold the contract and how funds move. It closes when the solicitation language is approved.

Signals you noticed One funding route currently runs to Tribal governments; the eligibility language would change who may hold a contract; the reporting requirement attached to the contract would apply to programs operated by Tribal Nations.

Who leads from here Sent to the DHS office that leads tribal relations and consultation, addressed to the agency's designated Tribal liaison. Asking: does this require consultation, with which Nations, and by when must our schedule hold?

What this team will not decide on its own Whether the change has Tribal implications; whether consultation is required; which Nations are affected; who is contacted and how; any direct approach to a Tribal government or official.

Record, timing and the review point Date sent and date the open decision closes, both written in the project file. If no reply arrives before the closing date, raise it to our own leadership and ask to hold the date rather than proceed. Revisit this entry whenever the design changes.

Copy the five lines into your project record, fill them in from one live project, and send the first three to the DHS office that leads tribal relations before the open decision closes.

Browse and download only. Staff notes are not typed or saved on this page.

Where the signals usually hide

Eligibility language: who may hold a contract, run a program, be licensed, or count as a provider.
Funding routes: any line that moves money to or through a Tribal government, and the conditions attached.
Geography: anything that applies on Tribal lands, or that changes which office covers which area.
Data and reporting: whose records are used, how people are classified, who holds a data set, who may publish from it.
Authority: any change in who decides, who approves, who may appeal, or whose determination is final.
Timelines: any deadline too short for another government to respond within it, which is a signal about your schedule.

Four ways a good check still goes wrong

It arrives late

The signals were real and the note was accurate, and it was written the week before launch. Late notice turns a government-to-government question into a communications problem. Write the check when design work starts, not when it ends.

It is too vague to act on

“May have Tribal implications” gives the receiving office nothing to work with. Name the specific signal, the open decision and its closing date, and that office can usually tell you in one reply how urgent this is.

The team answers its own question

A project team that concludes there are no Tribal implications, and records that as a finding, has taken a determination that belongs elsewhere. Record what you noticed and why you read it that way, and let the answer come from the office that leads this work.

Someone goes around the route

A direct call to a Tribal official, an invitation sent from a project inbox, or a request that a Native colleague weigh in on behalf of a Nation. All three feel helpful, and all three cut across a relationship the agency holds as a whole. Send it through the route.

Be honest about the closing date

What you can change

You control how early the check is written and how accurately the open decision's closing date is stated.

What to watch for

Do not move a closing date on paper to make the routing look timely. The office receiving your note is planning real work against that date.

Your next step

Run the check on one live project this week, and put the reply, or the absence of one, back into the project record.

Which first-look entry can the receiving office actually act on?

“Project may affect Tribal Nations. Engagement planned.”

“Reporting rule would apply to Tribally operated programs. Open decision: the measure set, approved on the date in line five. Sent to the office that leads tribal relations on the date noted. This team will not decide whether consultation is required.”

“Reviewed for Tribal implications; none found; no action needed.”

“Tribal Nations will be included in the public comment period along with our other partners.”

Try a situation

A colleague sends you her first-look check for a contracting redesign. It reads, in full: “May have Tribal implications. Will reach out to the appropriate office at some point in the project.”

What do you send back?

Approve it. She has flagged the issue, which is the important part, and the detail can be filled in later.

Ask for four additions: the decision still open and when it closes, the specific signals she noticed, who she is sending it to and when, and what the team will not decide on its own.

Rewrite it yourself as a formal assessment of whether the redesign has Tribal implications, so the record is authoritative.

Carry this forward

A first look is not an assessment and not a determination. It records what you noticed, while the decision is still open, and hands the question to the office that leads the work.
A usable entry names the project, the decision still open and when it closes, the specific signals, who it went to and when, and what the team will not decide on its own.
Writing that you noticed nothing is a real answer, and it belongs in the record with your reasoning, so the next person can check the reasoning rather than repeat the work.
The route is the point. The DHS Office of Indian Policy and the DHS offices that handle tribal relations and consultation lead this work; the check exists to reach them early, not to replace them.

A completed first-look check, a scenario about an entry too vague to act on, and a knowledge check on what a usable entry contains.

Fill the check in for one live project this week and send it to the DHS office that leads tribal relations, with the open decision and its closing date in the first two lines.

What you’ll be able to do

What a first look is, and what it is not

A first-look check for Tribal implications in one project

Where the signals usually hide

Four ways a good check still goes wrong

Be honest about the closing date

What you can change

What to watch for

Your next step

Try a situation

Carry this forward

Your next step

A first look, and where it goes

What you’ll be able to do

What a first look is, and what it is not

A first-look check for Tribal implications in one project

Where the signals usually hide

Four ways a good check still goes wrong

Be honest about the closing date

What you can change

What to watch for

Your next step

Try a situation

Carry this forward

Your next step