AI policy, governance and training
An AI policy for local government, with a governance roadmap your leadership can approve
We help agencies decide where AI should and should not be used, write the policy that governs it, configure Microsoft 365 to enforce it, and train staff before anything is deployed.
Free · about one week · view-only · no obligation
View-only access your IT administrator approves and removes. Nothing in your systems changes.
On this page
Short answer
Our AI policy, governance and training engagement gives a public agency an AI use policy, a use-case inventory scored for value and risk, a roadmap aligned to the NIST AI Risk Management Framework, the Microsoft 365 controls that enforce the policy, and role-based staff training. A first sprint takes 8 to 12 weeks and typically costs $30K to $60K.
Starting points
Where most agencies start
The cost of waiting
Without an AI policy for local government, AI use happens anyway
Rules are arriving state by state.
A policy written to the NIST AI RMF now is easier to adapt than one written in a hurry after a state mandate or an incident.
What it really is
A policy on a shelf is not governance. Governance is a policy your systems enforce.
Most AI policies list good intentions. Ours map each rule to a Microsoft 365 control or a named owner who reviews it.
Your options
Policy template, consultancy, or policy plus controls
Agencies usually choose between adapting a template, hiring a consulting firm, or a partner that also configures Microsoft 365.
| Policy template | Consulting firm | Policy plus controls (us) | |
|---|---|---|---|
| Fits your agency | Generic | Tailored | Tailored, from what is actually open in your Microsoft 365 |
| Enforced in Microsoft 365 | No | Recommendations | Labels, DLP and access controls configured |
| NIST AI RMF | Sometimes referenced | Mapped | Mapped, with owners and review dates |
| Staff training | No | Optional | Role-based and recorded |
| Next step | Up to you | A separate procurement | First pilot scoped and priced |
What is included
What the engagement covers
AI use policy
Acceptable use, approved tools, data rules, human review and procurement terms for AI vendors, written for public-records obligations.
Use-case inventory
Department sessions to list candidate uses, each scored for value, risk and readiness, plus a register of AI already in use.
NIST AI RMF alignment
Govern, map, measure and manage controls for each approved use, with named owners and review dates.
Tenant controls
Sensitivity labels, DLP and access policies in Microsoft 365 that enforce what the policy says.
Staff training
Role-based sessions for leaders, staff and IT, including what must never go into an AI tool.
Roadmap
A phased 12 to 18 month plan, with the first pilot scoped and ready to procure.
Our approach
Four steps from policy to practice
Discover what is happening, decide what should, enforce it, and enable staff.
- DiscoverInventory AI already in use and review what is open in your Microsoft 365.
- DecideDraft the policy and score each use for value and risk.
- EnforceConfigure labels, DLP and access controls in Microsoft 365.
- EnableTrain staff, brief leadership and scope the first pilot.
Our promise: every rule in your policy maps to a control we configure or a named owner who reviews it. Nothing sits on a shelf.
Governance, security and data handling
Where your data goes, and who stays in control
- Inside your own Microsoft 365. We build in your Microsoft 365 and Azure environment, using the identity and permissions you already govern.
- Exposure fixed first. An AI assistant sees whatever its user can see, so oversharing and unlabeled sensitive content are dealt with before anything is switched on.
- Hosted in Microsoft Foundry on Azure. We use the model that fits the job: OpenAI, Anthropic or open-source models, deployed in Microsoft Foundry on Azure. Your data is never used to train them (see Microsoft’s data terms for Foundry). Anthropic operates its Claude models on Azure under its own commercial terms, and we show you which model and which terms apply before work starts.
- People decide. Approval rules, audit trails and human review wherever an output affects a resident, a record or a decision.
What it runs on
Built on Microsoft security
Identity protection, sensitivity labels and data loss prevention are what turn an AI policy into rules your systems enforce.
Proof
Government work this builds on
Governance before automation is how we have delivered Microsoft work for agencies for years.
The offer
One week, read-only, and a plan you keep
The AI readiness assessment shows what an AI assistant could find in your Microsoft 365 today, which uses are ready, and what each one needs before it goes live. The report is yours whether or not you build with us.
Exposure map
What an assistant could reach today: oversharing, permission sprawl and unlabeled sensitive data, ranked by risk.
Use-case shortlist
Three to five uses your agency could start with, scored for value, risk and readiness.
Plan and fixed price
The controls each use needs and a fixed-price estimate for the first build, ready for your procurement process.
- Free, with no obligation
- About one week
- View-only: nothing in your systems changes
- The report is yours to keep
Why free? It is how we scope a fixed price we can stand behind, and it shows you what to fix whether or not you hire us.
How it runs
Day 030-minute scoping call with the architect who would run the work.
Days 1–2Your administrator grants read-only consent. About an hour of your team’s time.
Days 2–4We review your Microsoft 365 and talk to the use-case owners you choose.
Day 5Findings session: exposure map, shortlist and fixed-price plan.
We reply within one business day.
Read-only Microsoft Graph permissions only, consented by your administrator and revoked at the end. No content leaves your Microsoft 365. NDA and data processing terms before any access.
Why agencies choose us
A Microsoft partner that builds and runs it

Transparent investment
The assessment is free. Here is what the work costs.
Every agency is different, and the assessment gives you the firm number. You deserve a real range first.
| Engagement | Typical timeline | Typical investment |
|---|---|---|
| AI policy sprint: policy, use-case list, roadmap | 8–12 weeks | $30K–$60K |
| Governance program: controls, training, first pilots | About 6 months | $80K–$150K |
| Enterprise or multi-department program | 12 months | $150K–$250K |
Want a figure for your organization? Get an estimate in 2 minutes with our pricing calculator.
Tenant configuration and training are in the estimate, not a change order.
Questions buyers ask
Before you decide
We already have an IT acceptable-use policy. Why a separate AI policy?
AI raises questions an IT policy does not answer: which data can go into a prompt, who reviews an AI output before it reaches a resident, and how prompts are kept as records. We usually add an AI section to your existing policy framework rather than starting over.
Should we block ChatGPT and other public AI tools?
Blocking alone tends to push use onto personal devices. Most agencies do better with an approved tool inside their own Microsoft 365, clear rules on data, and DLP that stops sensitive content leaving. We help you decide what to allow and enforce it.
How soon can staff start using AI?
Interim guidance is usually ready in the first weeks. Approved uses follow as their controls are in place, often within the first sprint.
Will this keep up with state rules?
We map the policy to the NIST AI RMF and to rules in your state, such as Texas HB 3512 training, and the managed service keeps it current as they change.
Start with a policy you can stand behind
The free assessment shows what is open in your Microsoft 365 today and which uses are ready, so the policy is built on facts rather than guesses.

