A community technology review board runs on paper before it runs on people. To run one well you write down what the board can decide, who sits on it, how proposals get scored, and what happens after a vote — then you hold meetings the public can actually follow. Boards rarely fail on the technology side; they fail because nobody defined decision rights, and six months in, nobody can say who was consulted or why.
If you need to know how to run a community technology review board, the sequence below is the one that works. It is built for a city, county, school district, library, housing authority, or nonprofit that spends money on technology affecting real people. Cities such as Seattle, Austin, and Sedgwick County all run versions of it, though none of them run it exactly the same way.
Table of Contents
- What You Need
- How to Run a Community Technology Review Board: Step-by-Step
- How to run a community technology review board: set a clear charter
- How to run a community technology review board: choose representative members
- How to run a community technology review board: create a consistent review process
- How to run a community technology review board: prepare and run productive meetings
- How to run a community technology review board: record decisions and explain them
- How to run a community technology review board: improve the board over time
- Common Mistakes
- Frequently Asked Questions
- Do members of a community technology review board get paid?
- What does a community technology review board do?
- What happens at an advisory board meeting?
- How do I join a city technology advisory board?
- Can a technology review board actually block a purchase?
- How many members should a community technology review board have?
- Conclusion
What You Need
Everything below has to exist in writing before the first review meeting. If it only exists in someone’s head, the board cannot be held to it.
- A one-page mandate. The board’s purpose, the body with spending authority, and the deadline by which that body must respond to a recommendation.
- A charter and bylaws. Scope, membership composition, terms of service, quorum, voting rules, conflict-of-interest policy, meeting cadence, and a sunset or review clause.
- A membership model. How many seats, which stakeholder groups they represent, how people apply, who appoints, and whether resident members get a stipend or honorarium.
- A meeting format. Length, frequency, location or video platform, whether meetings are open to the public under your state’s open meetings law, and how public comment is collected.
- Evaluation materials. A standard proposal form, a scoring rubric with weighted criteria, and a plain-language summary the board votes on rather than a vendor deck it cannot question.
- A decision record template. Evidence reviewed, criteria scores, recusals, votes, dissent, conditions attached, and the date the recommendation went to the decision-maker.
- Transparency safeguards. Published agendas, minutes, recordings, the roster with terms, and a stated list of what the board can and cannot approve.
One thing worth adding before anything else: a training budget for members. Boards routinely get steamrolled on technical proposals simply because no one paid for orientation on procurement, privacy, and information security.
How to Run a Community Technology Review Board: Step-by-Step
How to run a community technology review board: set a clear charter
Write the mandate before you recruit anyone. The charter should answer, in plain language: what technology decisions this body reviews, what it may recommend, what it may consent to, what it may approve, and what it may never touch. Oakland’s Privacy Advisory Commission works because OPD has to obtain policy approval from it before adopting certain technology use policies — that line was written down, not negotiated meeting by meeting.
Also write the escalation path. Where does the recommendation go, who responds, and by when? Without that, a passed vote becomes a filing cabinet. Set a default deadline — 60 days is common — and publish the answer either way.
You know the charter worked when an applicant can read it and predict the outcome before submitting anything.
How to run a community technology review board: choose representative members
Recruit across knowledge types rather than across head counts. A working board mixes technical expertise, community and lived experience, accessibility, privacy and data governance, education, and operations — the person who has to actually use the thing at 7 a.m. People tend to recruit people like themselves, so the membership model has to force the mix. Sedgwick County’s charter sets a minimum seven members drawn from named roles rather than open seats.
Guard against capture from a single organization or viewpoint. Cap how many seats any one employer, agency, or vendor-affiliated group can hold, and publish who appointed each member.
Compensation is the practice most boards get wrong. Engagement practitioners consistently point to paid participation as the single biggest lever on who shows up — unpaid-only boards tend to attract whoever can afford to give time away, which quietly filters out residents from disinvested communities. Even a modest stipend, plus childcare or a transit pass, changes the room.
How to run a community technology review board: create a consistent review process
Applicants should be able to follow the same track every time. A workable pipeline runs: intake and completeness screening, staff briefing, conflict disclosure, committee or workgroup review, full-board discussion, vote, recorded recommendation, response from the decision-maker, then a public status update. Fixed intake windows — monthly or quarterly — beat rolling submissions, because they give applicants a date to plan around.
Publish the form and the rubric so people can see the bar before they write a proposal. Most complaints about boards being a rubber stamp come down to applicants genuinely not knowing what evidence was expected.
How to run a community technology review board: prepare and run productive meetings
Run meetings in a fixed order: call to order and approvals, review of prior minutes, conflicts and recusals, the agenda item, public comment, member discussion, vote, next steps. Agenda control is the real friction point in most rooms. In Seattle Public Schools, parents pushed back hard on a meeting where a large share of the time went to the committee’s internal funding rather than the item on the agenda — a fair complaint from anyone who showed up to watch.
Send pre-reading at least seven days ahead and say plainly what a member is expected to have read. Give the chair a hard time limit per item and a clear decision rule, so the discussion ends in a vote instead of trailing off. Record recusals in the minutes with the reason.
Seat around nine to fifteen members. Below about seven, one absence can kill quorum and the board stops. Above roughly fifteen, discussion gets thin and the chair spends the meeting managing.
How to run a community technology review board: record decisions and explain them
A vote without a written reason is the single most common trust failure. Every recommendation should state the evidence the board relied on, the criteria and scores, who recused and why, the vote including any dissent, any conditions the board attached, and the date it went to council or the purchasing department.
Send the applicant a short letter within a week, in plain language, naming what would have changed the outcome. Then tell the public what happened. Austin’s technology commission publishes an annual internal review, which is the habit worth copying: a short self-assessment of what the board got right, what it missed, and what it is changing.
If the recommendation is rejected or ignored, publish that too, with the response. Boards that hide the misses get read as theater.
How to run a community technology review board: improve the board over time
Review the process twice a year against a handful of honest measures: days from submission to vote, share of recommendations getting a written response, number of recusals, attendance and whether the meeting time works for working residents, proportion of recommendations implemented, and any cases where residents challenged a decision on process grounds.
Then change one or two things at a time and say what you changed. Also revisit membership and scope on a schedule — the US State Department’s technology review board operates inside an agency manual, which makes review obligations explicit and repeatable rather than optional.
Keep the sunset clause. Boards without one tend to coast on the original membership long after the city has changed.
Common Mistakes
Advisory in name, decisive in practice — nothing. If the board cannot influence anything, say so honestly or give it real decision rights. Residents quickly learn to tell the difference between a board with authority and a talking shop.
Advice with no destination. A recommendation that goes nowhere tells residents the process was a box-checking exercise. Fix the escalation path before the first vote.
Volunteer-only participation. This filters out the people the board most needs to hear from. Budget a stipend line.
Agenda control by staff or a chair. If members cannot move an item, add one, or request time, the meeting is a briefing, not a review.
No conflict rules. Unpaid members face vendor gifts and employer pressure constantly. State the disclosure duty and the recusal procedure up front, and record them.
Closed or quasi-closed meetings. Most states have open meetings laws that reach advisory bodies too, and residents notice when session doors close.
Recruitment by word of mouth. If openings are only public after they are filled, the board will look identical to itself every year. Advertise broadly and publish the roster.
Never measuring anything. Without numbers in the annual report, nobody can tell whether the board is working or just meeting.
Frequently Asked Questions
Do members of a community technology review board get paid?
Often yes, and the stipend is the part most boards skip. Cities and counties variously pay an hourly honorarium, a flat per-meeting stipend, or a modest gift card for resident members, with staff and elected officials typically unpaid. Even a small hourly rate plus childcare or transit support changes who can realistically serve, because unpaid seats tend to fill with people who can afford to give the time away. Put the money line in the charter and in the budget before you start recruiting.
What does a community technology review board do?
It reviews proposed technology purchases, pilots, policies, and data-sharing arrangements on behalf of the community, then sends a written recommendation to the body with spending authority. In practice the board checks a proposal against published criteria, asks questions in an open meeting, votes, and records the evidence and any dissent. Depending on the charter it may recommend, give consent, or approve outright, and it should publish clearly what it cannot approve.
What happens at an advisory board meeting?
Most meetings follow the same sequence: approve the prior minutes, take conflicts and recusals, work through each agenda item with pre-reading already sent, hear public comment, discuss, and vote on a motion. The chair usually runs a timer per item and the secretary records the vote, recusals, and any conditions in the minutes. If your board publishes the agenda a week ahead with the supporting documents attached, you will know you are running a real review process.
How do I join a city technology advisory board?
Look for your city clerk or board-and-commissions office rather than the IT department, since appointments usually sit with council or the city manager. Applications open on a public cycle with posted deadlines, and outreach often goes through library branches, neighborhood groups, and community organizations rather than the city’s own channels. Watch for open-seat announcements months in advance, and check whether the board pays a stipend or covers childcare, because that changes who realistically applies.
Can a technology review board actually block a purchase?
Only if its charter says so. Most boards are advisory and can recommend against a proposal without stopping it, while a few hold consent or approval authority over specific categories. Oakland’s privacy advisory commission is a useful model, because a written policy-approval requirement gives the body a genuine veto point on certain technology use policies. Read the scope section of any charter you are evaluating, and look for whether the escalation path names a deadline for the decision-maker’s response.
How many members should a community technology review board have?
Nine to fifteen is the working range. Below about seven, one absence can drop you under quorum and the board stalls on scheduling, which is why Sedgwick County’s charter sets a minimum of seven named positions. Above roughly fifteen, discussion gets thin and the chair ends up managing the meeting instead of the substance. Pick a number that your meeting calendar can support and that mixes technical, community, accessibility, privacy, and operational knowledge.
Conclusion
Your first move is small and unglamorous: write a one-page charter that names the board’s purpose, its decision rights, and the deadline any recommendation must be answered by. Publish the review process next, then recruit members against it — the order matters, because a charter written after recruitment becomes a description of whoever happened to show up. Everything else in this guide is downstream of those two documents.
Written for 2026. Rules on open meetings, public records, and compensation vary by state and city, so check your local code before you commit to anything.
