Lecture 6-2: A Community's Policy
Contents 31
- Lecture 1-1: What the Word "AI" Points To
- Lecture 1-2: How a Language Model Makes Words
- Lecture 1-3: Sounding Right Is Not Knowing
- Lecture 1-4: Reading a Conversation Closely
- Lecture 1-5: Practice Lab, Read an AI Answer
- Lecture 2-1: Invented Facts
- Lecture 2-2: Old Knowledge, Missing Sources, Uneven Coverage
- Lecture 2-3: Scripture and Theology, Where to Be Most Careful
- Lecture 2-4: Building a Checking Plan
- Lecture 2-5: Practice Lab, Find the Errors
- Lecture 3-1: Asking Well
- Lecture 3-2: Checking What You Are Given
- Lecture 3-3: What Must Never Be Typed In
- Lecture 3-4: Keeping Notes and Giving Credit
- Lecture 3-5: Practice Lab, Mend the Prompts, Mark the Secrets
- Lecture 4-1: Hand It Over, Help With It, Keep It
- Lecture 4-2: Office Work and Communication
- Lecture 4-3: Teaching and Study Materials
- Lecture 4-4: Where Teachers and Leaders Draw the Line
- Lecture 4-5: Practice Lab: Hand Over, Help, or Keep
- Lecture 5-1: Preaching and AI: A Theological Question
- Lecture 5-2: Care and Counselling
- Lecture 5-3: When Members and Young People Use AI
- Lecture 5-4: The Minister's Own Life
- Lecture 5-5: Practice Lab: Judge the Scene, Write a Position Paragraph
Up to now this course has asked what you, one person, should do. But ministry is seldom one person alone. A parish office has a secretary and a priest and volunteers. A youth group has leaders and parents. A small church has a treasurer, a newsletter editor and a woman who runs the online meeting. When these people each decide for themselves what to do with a chat assistant, three things tend to happen. Some use it in ways the others would not accept. Nobody knows who is responsible when something goes wrong. And the first mistake is handled in a panic, because nobody ever talked about it.
A written policy is the plain answer. It need not be long or technical. One page, agreed by the people who must live with it, can settle most of these questions before they hurt anyone.
This lecture is about what such a page contains and how a community might make it. It does not give you a policy to adopt, and it does not claim to know the rules of your community, your denomination, your school or your country. Those are for the people responsible to decide. The lecture gives a frame, so that what they decide is clear.
What these 17 minutes give you
- Name the seven parts of a one-page policy for the use of AI tools in a community.
- Explain why a policy should say who answers, and when it will be reviewed.
- Describe the extra care that volunteers and work with children and young people call for, at the level of principle.
- Describe a calm, fair way to respond when someone has made a mistake.
- State fairly why communities differ about how permissive a policy should be.
Where there is no wise guidance, the nation falls, but in the multitude of counselors there is victory." — Proverbs 11:14
World English Bible
Let all things be done decently and in order." — 1 Corinthians 14:40
WEB
Proverbs praises shared counsel over one person's guess. Paul asks for order, which in his setting meant that a gathering should be understandable to the people in it and well ordered. A written policy is a modest form of both.
1. Why write it down
An unwritten rule is only as strong as the memory of the people who know it, and it is invisible to the newcomer. A written page does four things.
It lets a new volunteer know what is expected on the first day. It gives a leader something to point to that is not a personal opinion. It moves the hard conversation from "what you did" to "what we agreed." And it can be corrected, because a page that is wrong can be crossed out in a way that a habit cannot.
A policy is not a way of showing that a community is up to date, and it is not a way of finding someone to blame. If it is used for either, people will hide what they do. It is a way of keeping a few commitments in view: do not deceive, keep confidences, and let a person be responsible.
2. The seven parts of a one-page policy
The following seven parts fit most communities. A community may leave one out or add one. What matters is that the people who write it have thought about each part.
1. What is allowed. Name the kinds of work for which a tool may help. Name them as kinds of work, not as brands or features, because the tools will change. For example (an invented example): "A tool may help with first drafts of notices and minutes, with plain-language rewrites of study material, and with lists of questions for discussion."
2. What is not allowed. Name the work that stays with people. For example (an invented example): "A tool is not used to write words of comfort, condolence or congratulation to a person; to give counselling or advice to a member; or to decide who receives help."
3. What must be checked. Say what must be checked before anything leaves the building, and by whom. For example (an invented example): "Every quotation, verse, date and name is checked against the source by the person who sends it. Teaching material is checked against our own community's sources before it is used."
4. What must be disclosed. Say whether and how readers are told that a tool helped. Communities answer this in different ways (see "Where readers will not agree" below). Whatever the answer, it should be written, so that nobody has to guess.
5. What is never typed in. State plainly that personal, congregational and counselling information, and anything unpublished that was given in trust, is never typed into a tool. This echoes lecture 3-3. Say also that the service's terms and the community's rules are checked before any new tool is used, and that following local law is the community's duty. The details of data law and records belong to PT738E; the policy only needs to say who will look into it.
6. Who answers. Name a person, or a small group, who answers questions, approves new uses, and receives reports of mistakes. A policy without a named person leaves everyone unsure whom to ask. Pick a role, not just a name, so the policy survives when people change.
7. When it will be reviewed. Set a date or a rhythm: for example, once a year and whenever a serious mistake or a new kind of tool makes it necessary. Tools change, communities change, and a page that is never reread becomes a page nobody trusts.
3. Making the page
How the page is made matters nearly as much as what is in it.
Start with the people who do the work, not with a template. Ask the secretary what she already does. Ask the youth leader what worries him. Ask a volunteer who is not confident with technology what she needs to know. Ask a member who dislikes the whole idea what he fears. Their answers will show where the page is needed.
Write it in plain words. Many in your community will read it in a second language. Avoid technical terms; where one is needed, explain it in the sentence where it appears.
Keep it to a page. A policy that runs to twelve pages will not be read, and the long parts will be the ones that were hardest to agree on, so the community has lost its clearest decisions in a heap of detail.
Let those with authority approve it. In many communities, that means a board, a council, a pastor, a bishop or a parish leadership team. If your community has such a body, the policy is theirs to approve; yours is to prepare a draft. Do not write a policy and present it as if it carried an authority you were not given.
4. Volunteers and young people
Volunteers deserve a clear page, because they are often the ones with the least training and the most access. A volunteer who helps with the online gathering may hold a list of names and addresses. A volunteer who prepares the newsletter may be tempted to paste the whole prayer-request list into a tool "to tidy it up." The policy should say, in a sentence they cannot miss, that this is never done. Orientation for new volunteers should include the page and the name of the person who answers.
Work with children and young people calls for extra care. At the level of principle: follow your community's written rules and local law about children's safety and privacy. Never put a child's name, photo, voice or writing into a tool without the specific permission that those rules require, and where in doubt do not. Do not let a chat assistant take the place of a trusted adult in a young person's conversation about faith or about trouble. And if a young person says something that suggests harm to them or to someone else, that is never handed to a tool; it goes to the responsible person named in your safeguarding rules, and if there is danger now, to the local emergency number.
5. When someone makes a mistake
Sooner or later someone will do something the page does not allow, or something the page did not foresee. A newsletter will go out with a verse that does not exist. A leader will paste something private into a tool. A volunteer will use a tool to answer a member's message and the answer will be wrong.
A calm, fair response has five steps.
- Stop and secure. If something private has been entered into a tool, tell the responsible person at once; time may matter. Do not try to fix it quietly.
- Tell the people affected, in plain words and in the way your rules and local law require. The responsible person decides how and what.
- Correct the record. Withdraw the notice, send the correction, repair the page.
- Ask what the page could not see. Was the rule unclear? Was the person untrained? Did the pressure of time make a shortcut look reasonable?
- Change the page or the training, not only the person.
Distinguish a mistake from a deception. A person who made an honest error and reported it is to be treated differently from one who hid it. A community that punishes the first will soon get more of the second.
6. Where readers will not agree
This is a point where readers will not agree. Communities differ about how permissive a policy should be. Some hold that the safest and most faithful course is a short list of what is allowed and a firm "no" to the rest: they say that in a community of trust, a small doubt about a tool should be settled against using it, and that a ban is easier to keep than a nuance. Others hold that prohibition is unrealistic, since people already use these tools at home, and that a community does better to teach careful use and to agree on a few firm lines than to drive the use out of sight. Others hold that no general policy can fit every ministry, so each task should be judged by the person responsible, with an agreed frame like the one in lecture 4-1. Each has a real strength and a real danger: the first can leave people to use tools in secret, the second can drift toward what is convenient, and the third can leave volunteers without clear guidance.
This course does not choose. It asks for something smaller than any of the three: whatever a community decides, it should be written, known, and kept to; it should never allow deceiving the people it serves; it should keep confidences; and it should name the person who answers.
Diagram 1. The one-page policy: seven parts
In short
- A written policy tells newcomers what is expected, lets leaders point to an agreement, and can be corrected.
- Seven parts: allowed, not allowed, check, disclose, never type in, who answers, and review date.
- Write it with the people who do the work, in plain words, on one page, and let those with authority approve it.
- Volunteers need the page and a named person to ask; work with children needs extra care and the responsible person named in safeguarding rules.
- After a mistake: stop and secure, tell those affected, correct the record, ask what the page could not see, change the page.
- Communities differ on how permissive to be; the minimum is written, known, honest, confidential, with a named person.
| Front | Back |
|---|---|
| The seven parts of a one-page policy | Allowed; not allowed; check; disclose; never type in; who answers; review date. |
| Why name a person who answers | So that everyone knows whom to ask and whom to tell when something goes wrong. |
| Steps after a mistake | Stop and secure; tell those affected; correct the record; ask what the page could not see; change the page or the training. |
| What the course asks of any community policy | Written, known and kept; no deceiving those it serves; confidences kept; a named person who answers. |
One sentence to remember A good policy is short, written with the people who do the work, and clear about who answers.
This week's action Write one sentence for each of the seven parts as your own community might put it, and mark the part you are least sure of.
Check yourself
Not "did you read it" but "can you explain it". Ticks are kept on this device only.
Reflection and discussion
- Of the seven parts, which would be hardest for your community to agree on? Why?
- Who in your community could be "the person who answers"? What would that person need to know?
- Who should be asked before a draft policy is written, and whose voice is easiest to forget?
- State the strongest case for a short list of firm prohibitions, and the strongest case for teaching careful use. What does each risk?
- Think of a mistake of any kind that your community has handled well or badly. What would the five steps have changed?