Tribal digital literacy: data to collect before starting

A household may sit inside an area reported as served, yet share one ageing phone among several people, ration mobile data until the end of the month, lose signal in bad weather, or avoid online services because no one has shown them how to use them safely. Availability is not adoption. Adoption is not confidence. And confidence is not the same thing as agency.

This distinction matters particularly in rural tribal outreach. In 2021, 71% of American Indian and Alaska Native households on tribal land had a broadband subscription, compared with 84% of households in tribal areas and 90% nationally. Those figures describe a real improvement over the previous decade, but they do not tell us what one particular village, settlement, school catchment, or tribal housing cluster needs. Nor do they explain who is being left to manage the practical gaps within a connected household: the elder asked to navigate a benefits portal, the parent trying to download schoolwork, the young person carrying everyone’s passwords in their head.

When our rider volunteers arrive with laptops, refurbished devices, or plans for a classroom connectivity drive, I have learned to begin with conversation rather than inventory. The devices are visible; the relationships around them are not. A sound tribal digital literacy project planning checklist must therefore gather information about service, cost, equipment, skills, accessibility, safety, and community authority over the information being collected.

Digital inclusion begins not when a signal reaches a settlement, but when people can use that signal on their own terms.

Beyond the FCC map: what it can tell you, and what it cannot

The FCC National Broadband Map is useful as a starting point. For a home, public facility, or community anchor site, it can show the providers that report service, the network technologies they report, and the maximum advertised download and upload speeds. Its tribal-area tools can also help a planning team form an early picture of reported availability across a larger geography.

That is a valuable desk-research layer. It is not a community assessment.

Provider information is filed through the FCC Broadband Data Collection twice a year. It records where providers say service is available; it does not establish whether a family can pay for it, whether the installation was ever completed, whether the service performs at the advertised level, or whether anyone in the home feels able to use it. The map can also be challenged when local information shows that reported availability is inaccurate. For that reason, every map extract used in a proposal or baseline should be date-stamped and retained alongside the local verification that either supports or complicates it.

In practice, I would take the map to the field as a set of questions, not answers. When speaking with households and local leaders, ask:

1. Is service actually installed and active at this location? Reported availability may mean a provider could potentially serve an address, not that the household has a working subscription.

2. What type of connection is in use? A household relying on a mobile data plan, satellite service, fixed wireless connection, or shared neighbour’s Wi-Fi faces a different learning environment from one with a stable home broadband line.

3. What does the household pay, including hidden costs? Installation, deposits, equipment rental, data limits, reconnection fees, and travel to recharge a device can turn nominal access into an unreliable arrangement.

4. When does the connection fail? Ask about rain, wind, seasonal changes, power interruptions, network congestion, and the hours when children and working adults are most likely to need access.

5. Who is able to use the connection without assistance? A connection controlled by one technically confident family member is not the same as access shared with dignity across generations.

The Census Bureau’s computer-and-internet-use questions offer three sensible minimum fields for a household form: device type, whether internet access is available, and the type of internet access. Those fields are a clean beginning. They should not become the whole survey.

Build the baseline around five connected realities

The National Telecommunications and Information Administration identifies five areas for digital-equity planning: broadband availability and affordability; accessible and inclusive online resources and services; digital literacy; privacy and cybersecurity awareness; and devices with related technical support. I find this framework useful because it prevents a common intervention error: treating a training class as though it exists separately from the material conditions that allow people to practise after the trainer leaves.

For a tribal internet connectivity survey, collect each area separately. Do not fold them into a single “digitally connected” score, because that neat number tends to conceal precisely the barrier that needs funding.

A good indigenous technology access assessment does not ask only, “Do you have a device?” It asks, “Can you use it privately, regularly, safely, and for the things your household considers important?”

That phrasing changes the social dynamic. It recognises a family’s existing improvisation and stewardship instead of defining them by what they lack. In many communities, a device is already serving several roles: school tool, communication line, camera, government-services portal, entertainment screen, family archive, and informal help desk. If the programme assumes that device belongs to one individual, it may accidentally create tension in a household that has developed its own sharing arrangements.

Put community authority before data collection

Before a survey is printed, an app is loaded, or a volunteer begins recording responses, establish who has the authority to approve the work and to set its boundaries. This is not a procedural detail to be dealt with after the grant application. It is part of the intervention itself.

The CARE framework for Indigenous data governance gives a practical language for that conversation: Collective Benefit, Authority to Control, Responsibility, and Ethics. It is not a one-size-fits-all legal rule, and it does not replace the specific protocols of a tribal government or authorised data-governance body. Its value lies in the questions it insists we ask.

With elders, tribal representatives, school leaders, youth workers, and other locally authorised partners, agree on the following before collecting a single response:

• Purpose: What decision will the data support? A community should never be asked for detailed household information merely because a funder likes a baseline spreadsheet.
• Authority: Who has approved collection, and who can amend or stop it if concerns emerge?
• Access: Who will see raw household responses? Will volunteers, partner organisations, contractors, or funders have access?
• Storage: Where will records be held, for how long, and in what form? Identify whether names, phone numbers, addresses, or precise location details are genuinely necessary.
• Secondary use: May the information later be used in a report, a funding bid, academic work, a promotional campaign, or a different programme? If the answer is not clearly authorised, the answer is no.
• Return of findings: How will the community receive the results in a useful form—not merely a polished report circulated outside the community?
• Benefit: What tangible improvement will follow from participation, and how will residents be kept informed if the timetable shifts?

I have seen the difference this makes when a village council helps shape the questions. People do not become “respondents” being measured by an outside group; they become co-authors of a local account of what is working, what is difficult, and what should happen next. That is the beginning of agency.

Data gathered without community authority can describe a place while still failing the people who live there.

Design household conversations, not extraction exercises

A survey can be useful, but it should be short enough to respect people’s time and open enough to capture what a tick-box cannot. In our field preparation, I prefer a mixed approach: a consistent household form for comparable baseline data, followed by facilitated listening sessions with elders, parents, young people, educators, health workers, and local service providers.

The household form should include the Census-style core questions, then move into the realities that determine use. Questions might cover:

• devices in the home, including whether they are working, shared, borrowed, or dependent on costly repair;
• the internet source used most often and whether it is available at home, at work, at school, in a community facility, or only through a phone;
• recurring cost and whether the household has had to reduce, pause, or cancel service because of expense;
• practical reliability, described in local terms: times of day, weather conditions, power interruptions, or locations where signal disappears;
• activities people want or need to do online, such as school communication, telehealth appointments, job searches, benefit applications, language and cultural work, video calls, or small-enterprise tasks;
• tasks that feel difficult, including setting up email, filling out forms, downloading files, managing accounts, updating a device, or distinguishing trustworthy information from fraud;
• preferences for training time, location, group size, language, trainer identity, childcare arrangements, transport support, and whether participants would rather learn with family members or peers;
• accessibility needs involving vision, hearing, mobility, literacy, screen-reader use, captioning, font size, or alternative input tools;
• safety concerns, especially account sharing, online scams, unwanted contact, harassment, and the risks created by using a shared phone or computer.

Keep a clear separation between what is necessary to plan and what is merely interesting to know. A digital literacy project does not need to build a surveillance archive of a community in order to teach email, support online school access, or help residents navigate public services.

Listening sessions reveal patterns that individual questionnaires often miss. An elder may explain that people avoid a particular online system because its language is unfamiliar. Parents may describe why evening classes conflict with care responsibilities. Young people may show that the formal classroom has Wi-Fi, but the learning materials are unusable on the phones most families actually own. These are not side notes. They are the design brief.

Keep rural and urban tribal realities visible

A single average for a tribal population can create a comfortable but misleading picture. Census reporting shows that 45% of tribal households were rural, compared with 19% of nontribal households. In the 2021 data, rural tribal households had an 80% broadband-subscription rate, while urban tribal households had an 88% rate.

Those figures should not be used to presume the situation of any individual Tribe or community. They do, however, underline why geography belongs in the baseline. A programme operating across a tribal service area should record whether each household is rural, town-based, remote, or connected through a nearby urban centre, and then review the findings by geography rather than only as one combined total.

The differences are not limited to network reach. Rural community technology needs can include longer travel distances to repair a device, fewer places to print documents, inconsistent electricity, seasonal road conditions, limited private space for online appointments, and a much smaller pool of people who can offer informal technical support. A weekly training schedule designed around an urban library may have no practical relationship to a remote community’s routines.

For this reason, map the community anchors alongside household data:

• schools and their opening hours outside formal class time;
• libraries, tribal offices, clinics, youth centres, and other places where people may already seek help;
• reliable charging points and safe places to store shared equipment;
• locations with verified working connectivity, rather than merely reported coverage;
• local repair capacity, including trusted technicians and realistic turnaround times;
• existing cultural preservation programmes, language initiatives, or livelihood projects that could meaningfully use digital tools.

A classroom programme becomes more durable when it integrates with these local institutions. The rider crew may be able to bring equipment across difficult distances, and that practical contribution matters. But the programme belongs to the people who will explain it again next week, reopen the device cabinet, help someone reset a password, and decide which online tasks deserve trust.

Let the data change the project, not just justify it

The point of collecting this information is not to produce a more impressive proposal. It is to give the community and the programme team permission to alter the plan before money, equipment, and goodwill become locked into the wrong shape.

If affordability is the central barrier, more advanced classes will not resolve it. If the baseline shows that most residents use shared phones, training built around individual laptops will be poorly fitted. If participants are already online but uneasy about fraud and privacy, the first sessions should address account safety and shared-device practices, not introduce a browser as though no one has seen one before. If elders and tribal leadership request control over how findings are held and used, that governance must be budgeted for, respected, and revisited—not treated as an obstacle to efficiency.

There is no universal passing score for digital literacy, no training-hour total that guarantees confidence, and no single monthly price or broadband speed that can be declared appropriate for every tribal community. The honest route is slower at the beginning: verify local conditions, listen for the social arrangements around technology, and let authorised community voices determine what success looks like.

That is the form of stewardship a grassroots programme owes to the place it hopes to serve. Bring the devices, certainly. Bring the riders, the repair kits, and the patient trainers. But first bring the discipline to ask who needs what, who decides, and what must remain in community hands after the last motorbike has gone home.