FOR INSTITUTIONS, SEMINARIES AND NETWORKS
Your institution needs more than an AI policy. It needs a way to respond together.
Across departments, campuses and affiliated organizations, people are already making decisions about AI.
Movemental helps institutional leaders establish shared commitments, respect local authority, organize trusted knowledge, form their people, and develop systems that can evolve as the technology changes.
Want to know what is actually happening first? Take the Reality Assessment
One institution. Many different responses.
- A faculty member permits AI-assisted writing; another prohibits it.
- Administrative teams use incompatible AI services.
- Academic leadership establishes general principles, but departments lack implementation guidance.
- A denominational network tries to support churches operating in very different contexts.
The central issue is not merely inconsistent technology. It is the relationship between institutional authority and local responsibility.
An institution that answers once, for everyone, will be ignored where it doesn’t fit. One that leaves every unit alone will fragment. The work is deciding what must be shared and what must stay local.
What must be shared? What must remain local?
These are the questions your leaders will have to decide. The page doesn’t answer them. The Map is where you do.
- 01Who has authority to establish institution-wide AI commitments?
- 02What decisions belong to faculty, department leaders, congregations or local affiliates?
- 03How should assessment and education change when AI can produce competent academic work?
- 04What knowledge may an institutional system responsibly access?
- 05What should an institution refuse to standardize?
- 06How can institutional memory remain available as people and technologies change?
Two ways to begin
Individual conviction
Students, faculty, staff and leaders can each write a Resolution about what they believe the institution should do. Writing one carries no institutional authority, whatever your position.
Institutional reality
Authorized leaders use the Reality Assessment to see the difference between official expectations and what people actually do. Participation is voluntary, answers are anonymous, and nothing appears until at least five people have answered.
A Resolution is a person’s conviction, not institutional policy. Results are counted only for the people an institution invites, and only as totals.
The Map at institutional scale
The same five stages, carried out at two levels: commitments the whole institution shares, and decisions that stay with each department, campus or affiliate.
- 1Decide what you will stand for
Develop institution-wide principles with explicit local decision rights, so every unit knows what it may decide for itself.
- 2Gather what should ground the work
Identify source repositories, rights, permissions and workflows, and which knowledge is shared and which is local.
- 3Practice the judgment your people will need
Provide role-specific formation for leaders, faculty, staff and affiliates, led by people inside each unit.
- 4Build only what belongs
Choose shared infrastructure and local applications according to actual needs, not one deployment for everyone.
PursuePursue carefullySolve simplyDeferRefuseAn example refusal, written into the charter
We will not standardize how individual faculty assess student work. Each department sets its own rules within the institution’s principles.
- 5Review what changes
Revisit institution-wide rules, local exceptions, incidents and emerging capabilities on a set rhythm.
Shared commitments
The institution’s statement on AI
What may never enter any AI system
Shared infrastructure and security
How incidents are reported and reviewed
Local decisions
How each department teaches and assesses
Which tools a unit adopts
What local context a unit gathers
Exceptions, recorded with their reasons
Both sides connect through named responsibility and a written record, so a local decision can always be traced to the shared commitment it works within.
THE NETWORK MODEL
One foundation. Many responsible organizations.
A network can offer the response to every member at once, without turning shared infrastructure into shared data.
- Shared onboarding and common resources.
- Local governance and organization-specific context.
- Shared technical infrastructure where it fits.
- Separate permissions and approved data boundaries for every member.
- Optional specialized tools for particular affiliates.
- Central support without unrestricted central access to any member’s private information.
A conceptual demonstration, not specific technical or contractual terms. How the network offer is structured is still being decided.
What a managed institutional environment could provide
When your institution decides a system belongs, this is the kind of environment it could become, built on your sources and your permissions.
Institutional knowledge
Source-grounded access to approved materials and organizational history.
Role-specific applications
Different staff and departments working with tools suited to their responsibilities.
Governance and review
Visible decision history, approved policies, recorded exceptions and ongoing review.
Network support
A repeatable configuration and training approach for affiliated organizations.
Possible applications, shown as concepts. Not features every organization receives, and only ever built after your organization decides they belong.
Leaders who have built networks and institutions
All movement leaders
A lasting response requires continuing stewardship.
An institutional engagement is a continuing relationship, not a single installation: discovery, the charter, context reconstruction, formation, purpose-built implementation, managed operations and review, and, where it fits, expansion to your affiliates.