Courts and justice
Protection orders
A protection order your court issues must be enforced by other states, tribes, and territories as if it were their own, and federal law conditions that on jurisdiction, notice, and an opportunity to be heard. All three are record facts, so the record is what makes the order enforceable.
Built with your court · deadlines from your code · every order provable
Under 18 U.S.C. 2265(a), a protection order issued by the court of one State, Indian tribe, or territory must be accorded full faith and credit by, and enforced by the court and law enforcement personnel of, another State, Indian tribe, or territory, as if it were the enforcing jurisdiction's own order. That is a federal command, and it runs in your favor.
It comes with conditions. Subsection (b) says the order qualifies only if the issuing court had jurisdiction over the parties and the matter under its own law, and only if the respondent was given reasonable notice and an opportunity to be heard sufficient to protect due-process rights. For an ex parte or emergency order, notice must be given within the time required by law and, in any event, within a reasonable time after issuance.
Read those conditions again and notice what they are made of. Jurisdiction, notice, timing, and opportunity to be heard are not legal theory. They are facts that either appear on the file or do not. The workflow runs on the same seven plain questions as every other matter in the court: summons, notice, change of notice, calendar, build, file, and the finished document.
The record is the enforceability
A protection order matters most in the moment a deputy two counties over is deciding whether to act on it. What that officer and that court are checking, whether they say it this way or not, is the 2265(b) list: did the issuing court have jurisdiction, and did the respondent get reasonable notice and an opportunity to be heard.
So the strongest protection order is the one whose file answers those questions immediately and provably. Not because the paperwork is tidy, but because federal law makes the paperwork the condition. A file that shows who was served, by what method, on what date, under which section of your code, and by whose authority is an order that travels.
This is the one place where a complete record stops being good practice and becomes the operative legal fact. Every date the system asserts shows the section of your code it came from, every service event is captured as it happens rather than reconstructed later, and every order is sealed and attributed at the moment it issues.
- Jurisdiction on the face of the file, tied to the section of your own law that gives your court the case.
- Service captured as an event, naming who was served, how, on what date, and with which document.
- The opportunity to be heard, on the record, so the due-process condition in 2265(b) is shown rather than assumed.
- The ex parte clock counted, because notice after an emergency order must come within the time your law requires and, in any event, within a reasonable time after issuance.
- Every date shows its section, so a question from the bench or from an enforcing jurisdiction has an immediate answer.
- Reproducible orders, so the copy produced for another jurisdiction next year is identical to the one issued today.
18 U.S.C. 2265 came in with VAWA 1994 (Pub. L. 103-322, sec. 40221(a)) and was most recently amended by VAWA 2022 (Pub. L. 117-103, sec. 106). The full-faith-and-credit command is federal and long-standing. What it asks of you is a record that can carry its own conditions.
Your civil jurisdiction here reaches any person
Subsection (e) is the provision tribal courts should know cold. A tribal court has full civil jurisdiction to issue and enforce protection orders involving any person, in matters arising anywhere in the Indian country of the tribe (as Indian country is defined at 18 U.S.C. 1151) or otherwise within the tribe's authority. Any person. The statute says so directly.
That civil authority includes enforcement, and Congress named mechanisms: civil contempt proceedings, exclusion of violators from Indian land, and other appropriate mechanisms. Exclusion is a live tool for a nation enforcing its own order on its own land, and like everything else it is only as good as the record showing the order, the notice, and the violation.
This is civil jurisdiction to issue and enforce protection orders. It is a separate question from criminal jurisdiction over non-Indians, which runs through 25 U.S.C. 1304 and is a choice your nation makes. Keeping the two straight is the difference between confident practice and an argument you did not need to have.
Protection orders, from each seat
Tribal IT
The file that has to hold up runs in-house.
Protection-order records sit on your hardware, reachable only by the people the court has cleared, and a certified copy can be produced for an enforcing jurisdiction without a request to an outside company.
Council
Your orders carry weight beyond your land.
Federal law requires other states, tribes, and territories to enforce an order your court issued when jurisdiction and notice are met. A provable record is what turns that entitlement into enforcement.
Staff
The service record builds itself as you work.
You answer plain questions and the notice, the method, the date, and the clock are captured as the matter runs. Nothing depends on reconstructing service from memory when it is challenged.
Where the code is yours
Federal law sets the recognition rule. It does not write your protection-order code. The grounds, the duration, the extension practice, the exclusion remedy, and the contempt procedure are your nation's law to enact, and 2265(b) points back at your own law for jurisdiction over the parties and the matter.
So we build your code in. We sit with the court, section by section, and the rules that come out are the ones your council actually enacted, with each computed date carrying the section it came from. The rules come from your published law, not from another jurisdiction's assumptions about how long an order should last or when a clock should start.
Where the court's practice differs from the written code, the system shows both and names the difference. Which one changes is a decision for the tribe.
Questions courts ask about protection orders
- Will a state enforce our protection order?
- Federal law requires it. Under 18 U.S.C. 2265(a), an order consistent with subsection (b) must be accorded full faith and credit and enforced by the courts and law enforcement of another State, Indian tribe, or territory as if it were their own. The conditions are that your court had jurisdiction over the parties and the matter under your own law, and that the respondent had reasonable notice and an opportunity to be heard sufficient to protect due process.
- Can we issue an order against a non-Indian?
- For protection orders, 2265(e) gives a tribal court full civil jurisdiction to issue and enforce orders involving any person, in matters arising anywhere in the Indian country of the tribe or otherwise within the tribe's authority, including through civil contempt and exclusion of violators from Indian land. Criminal jurisdiction over non-Indians is a separate question that runs through special Tribal criminal jurisdiction, which is opt-in.
- What about an emergency order issued without the respondent present?
- The statute addresses it directly. For an ex parte order, notice must be given within the time required by your law and, in any event, within a reasonable time after issuance. The system counts that clock from the event your code says it runs from and shows the section behind the date, so the notice that protects enforceability actually happens.
Sources
- 18 U.S.C. 2265, full faith and credit for protection orders · U.S. Code, Cornell LII. law.cornell.edu
- Rule
- Ch. 12.304
- Source
- your published code
- Enforced
- computed on the case
The system tracks the deadline and shows the exact section it comes from. When your practice differs from the written rule, it flags it instead of guessing.