Independent technology governance for sovereign nations operating programs across justice, health, education, gaming, and economic development on the nation’s terms.
Tribal nations run technology programs at the intersection of federal program coordination and sovereign authority. BIA. IHS. DOJ. HUD. The work has to respect sovereignty in writing, every contract, every configuration, every record.
federally recognized sovereign nations
federally recognized reservations across more than 35 states
people served by tribal government technology programs on or near reservations
tribal justice systems operating with their own case management, records, and evidence integrity requirements
Most consultancies and vendors approach tribal governments as a smaller version of state or local government. Sovereign nations are not. The procurement record is a sovereignty record. The configuration authority is a sovereignty authority. Every cross-agency federal interaction has to land without compromising the nation's standing as a peer government.
That is the work Sentinel does for tribal nations. We govern the program. We never sell the platforms.
Independent. Practitioner-led. Vendor-neutral.
Sovereign program decisions do not fail in the vendor demonstration. They fail in the data-sharing default that no one read carefully, in the federal reauthorization cycle that arrives without the documentation it requires, and in the cross-jurisdictional case where the data residency assumption was never written down. Sentinel sits on the nation’s side of every vendor decision, every federal coordination touchpoint, and every council briefing. And we produce the documentation that proves the sovereignty discipline is real, in writing.
These are the structural pressures we hear from tribal CIOs, program directors, and council leadership in nearly every conversation. Sentinel’s role is to help you navigate them with documentation and evidence on the nation’s side.
BIA, IHS, DOJ COPS, HUD ICDBG, and USDA Rural Development each carry their own reauthorization, reporting, and audit cadence. Tribal programs run multiple federal programs simultaneously. The documentation requirements arrive on each program’s schedule, not on a unified cycle.
Most cloud and SaaS vendor agreements were written for state, local, or commercial customers. Tribal data sovereignty rarely appears as an enforceable term. The default data-sharing posture, the audit-log access, and the e-discovery clauses all assume a non-tribal customer. The first contract review surfaces it. The second one fixes it.
Tribal CAD, RMS, and JMS deployments routinely overlay federal, state, and tribal jurisdictions on the same case. Cross-deputization adds federal data sharing into the mix. The technology has to model jurisdictional boundaries the vendor demos rarely address. The configuration discipline that gets it right is rare and explicitly tribal.
Gaming compacts now routinely include technology, surveillance, audit, and reporting requirements that touch the broader tribal IT environment. The boundary between gaming and non-gaming systems is sometimes fuzzy, and the regulatory consequences of getting it wrong fall on the nation, not on the vendor.
Tribal nations have governed themselves for centuries. The institutional knowledge of why a program is structured the way it is, why a system is configured the way it is, and why a particular data category is handled the way it is, lives with people whose authority precedes any consulting framework. Sentinel respects that. We document it.
Sovereign program technology is not a product purchase. It is a multi-decade discipline built on tribal authority, gaming compact terms, federal program coordination, and the contracts a nation signs with every vendor that touches its citizens, its services, and its data. Most consultancies treat tribal governments as a niche version of state or local government. They are not. The legal frame is different. The institutional knowledge is older. The data-sovereignty bar is rising. We change that.
Sentinel reads the actual contract language through a sovereignty-first lens. We map it against the gaming compact, the federal program rules, the IT-986 compliance posture, and the council direction that authorized the work. We document the decisions before the next federal reauthorization cycle, before the next compact review, and before the next cross-jurisdictional case. The artifacts we produce are structured under the assumption that they will be read by tribal counsel, by federal program officers, by the council, and by the citizens whose services depend on the system staying operational on the nation’s terms.
Our work is independent. We sell no platforms. We collect no referral fees. Every recommendation is auditable, defensible, and built to survive the year-five conversation when the original vendor has been acquired and the nation still owns the consequences.
While the phases move, Sentinel stays.
What We Do Here
Forged in public safety. Trusted across sovereign nations. From council authorization to year-five outcome, Sentinel’s signature practices govern every phase of the nation’s technology program on the nation’s terms.
For nations that need a defensible artifact this quarter, not a six-month conversation. Each engagement is fixed-scope, independently delivered, and structured to survive scrutiny on the nation’s terms.
Reading the contract through a sovereignty lens
Vendor evaluation that puts tribal data sovereignty, IT-986 compliance, gaming compact alignment, and federal coordination ahead of vendor convenience. Sentinel reads the contract, the data-sharing default, the audit-log access, and the e-discovery clauses through a sovereignty lens, and produces a scorecard that holds up before the council and the gaming commission.
Output: a sovereignty-defensible vendor scorecard for the procurement file.
For the reauthorization cycle that is always coming
Documentation package for BIA, IHS, DOJ COPS, HUD ICDBG, USDA Rural Development, or other federal program reauthorization cycles. Sentinel reconstructs the decision history, maps it to the program rules and the tribal authority that governs it, and produces an audit-ready record of the federal program work.
Output: an audit-ready federal program documentation package.
For tribal CAD, RMS, JMS deployments
For tribal CAD, RMS, JMS, and public safety deployments where federal, state, and tribal jurisdictions overlay on the same case. Sentinel maps the jurisdictional boundaries, the data-sharing rules, the cross-deputization framework, and the dispatch-to-court information chain in a form that respects the nation’s authority and the operational reality at the same time.
Output: a coordination posture document for tribal public safety operations.
Every engagement draws on the practices below. Each has its own discipline, its own training pedigree, and its own boundary. None of them are platforms.
Public-sector program management. Used on every deployment.
Sovereign program delivery means coordinating procurement, federal compliance, vendor management, and cross-program operation in one documented motion. SDF is the program management discipline Sentinel runs on every tribal engagement, with sovereignty-first defaults built into every checkpoint. Every decision is documented to survive a federal audit and a council briefing in equal measure. Every record is captured in a form the next program director can pick up.
Public-sector organizational change management. Used on every rollout.
A new system for a sovereign program is a community readiness problem before it is a technology problem. SRM coordinates the readiness work across the council, the program staff, and the citizens who use the services. The discipline manages stakeholder alignment, training cadence, communication architecture, and the council communication. Go-live becomes an operational event, not a community surprise.
Configuration authority on the nation’s side of the table. Practitioner-delivered only.
When the vendor builds the platform, someone has to govern the configuration choices through a sovereignty lens. Council direction, compact terms, and federal program rules become platform behavior through a thousand small decisions. SDB is Sentinel’s configuration authority discipline, deployed on strategic tribal engagements where the configuration decisions need an independent custodian on the nation’s side. Never offered as training. Practitioner-delivered, on the nation’s side of the table.
Post-deployment outcome governance. Advisory and non-binding by design.
A go-live is not an outcome. SVA is Sentinel’s post-deployment governance discipline, designed for the multi-cycle horizon when the original vendor has been acquired, the federal program staff have rotated, and the system is still expected to deliver service to the citizens of the nation. Findings are advisory and non-binding by design. Sentinel documents. We do not litigate.
Sentinel’s tribal governance bench leans on cross-domain pedigree. The disciplines that show up on day one of a sovereign engagement.
Vendor contracts written for state, local, or commercial customers default to terms that do not contemplate tribal data sovereignty. Sentinel reads the terms through a sovereignty lens, identifies the assumptions buried in the data-sharing default, and writes the corrections into the contract before signature. The result is a posture the council can defend and the gaming commission can audit.
BIA, IHS, DOJ COPS, HUD ICDBG, and USDA Rural Development each carry their own program rules, reauthorization cycle, and reporting cadence. Sentinel reads the active program rules, maps the nation’s posture against them, and produces the documentation in the language a federal program officer accepts and a tribal council can review.
Tribal CAD, RMS, and JMS deployments routinely overlay federal, state, and tribal jurisdictions. Sentinel brings the public-safety practitioner pedigree that respects all three, with the configuration discipline that gets the cross-deputization framework, the data-sharing rules, and the dispatch-to-court chain right on the nation’s terms.
Sentinel’s tribal governance bench is named, deep, and growing. Where additional sovereign-domain specialists are needed for a specific engagement (gaming compact technology, IHS-specific health data, federal grant compliance), we say so up front, name the bench-in-flight specialist, and bring them in under the engagement governance the nation already trusts. We do not invent expertise we do not have.
The tribal vendor playbook is patterned. Once you have read enough contracts and reviewed enough sovereignty defaults, the moves become obvious. These are five Sentinel sees most often.
A cloud or SaaS vendor markets itself as sovereignty-friendly without addressing the actual contract terms. The data-sharing default is unchanged. The audit-log access is unchanged. The e-discovery clauses still assume a non-tribal customer. The marketing is real. The contract is not. We require the actual sovereignty terms, in writing, in the contract, before the procurement file accepts the claim.
A vendor implies federal endorsement by referencing past work with a single BIA program or a single tribal customer. The reference is real. The endorsement is not. BIA does not approve technology vendors for tribal customers. The nation makes that decision. We require the citation to the specific contract vehicle, the specific program rule, and the specific tribal customer reference, before the recommendation goes to council.
A vendor proposes data-sharing defaults that match a state or commercial customer’s federal coordination posture. The default does not contemplate tribal sovereignty, the gaming compact, or the cross-deputization framework. The first sovereignty review surfaces it. The procurement file documents the corrections. We do that review before the contract, not during the dispute.
A vendor invokes gaming compact alignment without naming the specific compact, the specific section, or the specific surveillance, audit, or reporting requirement the platform is intended to satisfy. The claim is reassuring. It is also unenforceable. We require the citation, in writing, in the procurement file, before the platform touches a gaming-adjacent system.
A vendor provides a list of other tribal customers as an implicit endorsement. The list is real. The reference is not always meaningful. Tribes are not interchangeable, and what works for one nation’s programs, gaming compact, and federal coordination posture may not fit another’s. We require specific reference calls with specific outcome questions, before the procurement file treats the list as endorsement.
The people on the other side of every Sentinel tribal engagement have run government technology programs from inside, with the procurement, contract, and configuration discipline that respects sovereignty in writing. Not consultants who treat sovereign nations as smaller-scale state or local clients.
Co-Founders · Sentinel Solutions Group
Twenty years inside the largest and most-watched public safety and government technology programs in the country. LAPD Records modernization. LA County Sheriff. LAFD. DC Metro CAD/RMS. The configuration-authority and program-governance discipline they ran at LAPD became the foundation of the Sentinel Delivery Framework and Sentinel Readiness Method. Both methodologies remain in active use at LAPD and Motorola today.
On every Sentinel tribal engagement, Justin owns the operations and change management arc. Jason owns the engineering and technical posture. Together they hold the engagement accountable to the council and to the long horizon the nation operates against.
Independent. Practitioner-led. Vendor-neutral.
Advisor · Procurement, Contracts, Sovereignty Discipline
Brings the procurement, contracts, and compliance discipline that turns a vendor pitch into a sovereignty-defensible procurement file. Hands-on local-and-state government project experience, federal grant compliance fluency, and the contract-language judgment that protects a nation's standing across every cross-agency interaction.
The bench Sentinel built specifically for sovereign program work.
The right engagement depends on where the nation is in the program lifecycle. Each tier has its own scope discipline and its own deliverable cadence.
Managed Technology Subscription
End-to-end managed operations for the platforms Sentinel helped you stand up. Sustainment, on-site systems administration, vendor coordination, version-upgrade discipline, and 24/7 incident response. The system is still delivering services on the nation’s terms because someone is still accountable for it.
Retained Governance & Advisory
Ongoing retainer with quarterly governance reviews, pre-decision advisory, and an open line for council briefings, federal program response, and vendor escalations. The nation has independent counsel on the technology side of the table, every cycle.
Anchored to one of the four signature practices
Anchored to one of SDF, SRM, SDB, or SVA. Best when the nation knows which discipline is needed: program delivery, council and community readiness, sovereignty-aware configuration authority, or post-deployment outcome governance. Fixed scope, named practice, defined deliverables.
Specialized Services + Practice + Institute
A specialized service plus a signature practice plus Sentinel Institute training, packaged as a single integrated engagement. For nations standing up a major program from scratch and building the institutional capacity to operate it themselves.
Related
Tribal programs rarely live in isolation. These adjacent disciplines and capabilities are commonly stitched together in the same engagement.
Sibling Discipline
Many tribal services share regional infrastructure with neighboring cities and counties.
Explore →Sibling Discipline
Pass-through funding and shared platforms link state programs to tribal operations.
Explore →Sibling Discipline
Water, power, and tribal utility authorities run inside or alongside the nation.
Explore →Sibling Discipline
Tribal courts and CMS integration with federal and state court systems.
Explore →Service Offering
Sustainment and managed IT for the platforms we help your nation stand up.
Explore →Training
Practitioner training in SDF and SRM for tribal IT and program staff.
Explore →Tell us where you are in the program lifecycle, and we will tell you honestly whether Sentinel is the right fit, or recommend someone better if we are not.
Schedule a Conversation →