FREE

Course certificates are free until March 31, 2027.

PT738E Privacy and Confidentiality in Ministry

Lecture 6-1: Writing a Plain Policy

Contents 31
PT738E Privacy and Confidentiality in Ministry
Chapter 0 · Introduction: Held in Trust
  1. Introduction: Held in Trust
Chapter 1 · Week 1: Entrusted Words
  1. Lecture 1-1: Secrets, Shame, Gossip and Trust in Scripture
  2. Lecture 1-2: Confidence in the Traditions, and Where It Stops
  3. Lecture 1-3: What a Church Holds, and What Can Hurt
  4. Lecture 1-4: When the Community Must Know, and When It Must Not
  5. Lecture 1-5: Practice Lab, Map What Your Community Holds
Chapter 2 · Week 2: Collecting, Keeping, Using, Letting Go
  1. Lecture 2-1: Collect Less, and Say Why
  2. Lecture 2-2: Consent When the Asker Holds Authority
  3. Lecture 2-3: Keeping It: Places, Keys and Who Needs to See
  4. Lecture 2-4: Using, Sharing, Letting Go
  5. Lecture 2-5: Practice Lab, Fix One Form
Chapter 3 · Week 3: Notes, Prayer Requests and People at Risk
  1. Lecture 3-1: Writing Notes About People, and Not Writing Them
  2. Lecture 3-2: Prayer Requests and the Circle Around a Person
  3. Lecture 3-3: Children, Young People and Vulnerable Adults
  4. Lecture 3-4: When Exposure Can Endanger
  5. Lecture 3-5: Practice Lab, Rewrite the Note and the Request
Chapter 4 · Week 4: Digital Safety
  1. Lecture 4-1: Accounts, Passwords and Devices
  2. Lecture 4-2: Group Chats, Social Media, Livestreams, Cameras and Photographs
  3. Lecture 4-3: Choosing Tools and Vendors, the Questions to Ask
  4. Lecture 4-4: Volunteers, Borrowed Devices and Handing Over Access
  5. Lecture 4-5: Practice Lab, Audit One Day of Access
Chapter 5 · Week 5: When It Goes Wrong, and When Hands Change
  1. Lecture 5-1: When Something Goes Wrong: The First Hours
  2. Lecture 5-2: Speaking to the People Who Were Hurt
  3. Lecture 5-3: Hands Changing: Pastors, Leaders, Splits and Closures
  4. Lecture 5-4: Leaving, Moving, Dying, Asking: Requests About a Person's Record
  5. Lecture 5-5: Practice Lab, The First Hour and the Handover List
Chapter 6 · Week 6: Policy and Culture
  1. Lecture 6-1: Writing a Plain Policy
  2. Lecture 6-2: Teaching and Culture: Making It Ordinary
  3. Lecture 6-3: Different Places, Different Rules: How to Ask
  4. Lecture 6-4: Known and Kept: A Theology of Being Held
  5. Lecture 6-5: Practice Lab, My Rule and Our One Page

Jump to the key points ↓

32 min

Five weeks of this course have built up to a simple question: what do you now do about it? A minister who has mapped the information a community holds, and has thought about forms, notes, prayer requests, devices, mistakes and handovers, can easily end up with a head full of good ideas and a community that has not changed. Ideas that live only in one person's head leave when that person leaves. A policy (a written statement of how a community will act) is the way a community writes its ideas down so that they can be shared, checked and kept.

By "policy" this lecture does not mean a thick binder or a legal document. It means a short, plain statement, ideally one page, of how this community treats the information it holds about people. Think of it as a promise written to the people the church holds: members, children, visitors, volunteers, those who come for help. The course's central claim applies directly. What people entrust to a church is theirs, and the church is its keeper. A policy is where the keeper says, in words the owners can read, how it intends to keep.

This lecture is not legal advice. The rules that bind a community differ from one country and one church body to another, and a policy of this kind states principles and names the local rule to follow; it does not try to be the rule. Part of the work, as you will see, is asking a qualified person to check it.

What these 32 minutes give you

  • Explain why a short, plain policy serves a community better than a long copied one.
  • List the eleven parts of a one-page policy and say what question each part answers.
  • Describe a way of drafting a policy that involves the people who will have to live by it.
  • Identify what to ask a qualified person to check, and write a policy so that it names the local rule instead of pretending to be it.
  • Mark an annotated sample policy for words that promise too much, too little, or nothing at all.

Where there is no counsel, plans fail; but in a multitude of counselors they are established. — Proverbs 15:22

World English Bible

Now in those days, when the number of the disciples was multiplying, a complaint arose from the Hellenists against the Hebrews, because their widows were neglected in the daily service. The twelve summoned the multitude of the disciples and said, “It is not appropriate for us to forsake the word of God and serve tables. Therefore select from among you, brothers, seven men of good report, full of the Holy Spirit and of wisdom, whom we may appoint over this business. But we will continue steadfastly in prayer and in the ministry of the word.” These words pleased the whole multitude. They chose Stephen, a man full of faith and of the Holy Spirit, Philip, Prochorus, Nicanor, Timon, Parmenas, and Nicolaus, a proselyte of Antioch; whom they set before the apostles. When they had prayed, they laid their hands on them. — Acts 6:1-6

WEB

For which of you, desiring to build a tower, doesn’t first sit down and count the cost, to see if he has enough to complete it? Or perhaps, when he has laid a foundation, and is not able to finish, everyone who sees begins to mock him, saying, ‘This man began to build, and wasn’t able to finish.’ — Luke 14:28-30

WEB

Plans fail without counsel and stand with many counsellors. A policy written by one person in an evening is a plan without counsel. This verse is the reason the drafting method below involves more than one voice.

A community discovers that some of its widows are being overlooked in the daily distribution. The apostles do not scold and do not fix it alone. They state the problem, ask the whole company to choose people of good reputation, and then pray over the choice. A structure is created, with named people and a defined task, so that the work does not depend on the memory or the goodwill of one leader. That is the shape of a good policy: a shared problem, a shared choice, named people.

Jesus speaks of counting the cost before building. A policy that no one can afford to follow, because it asks for a locked room the church does not have or a monthly audit nobody will do, ends as the half-built tower: the community looks foolish and, worse, trusts the paper more than the practice. Count what you can truly keep, then promise that.

1. Why a policy at all

A small church may say, "We have never had a policy, and we have never had a problem." That may be true, and it may also mean that no one has yet noticed the problem. A policy is not mainly there for the day of crisis, though it helps then. It is there for three ordinary reasons.

The first is memory. Habits that live in one person (the secretary who always locks the drawer, the pastor who never writes down what was said in a hospital room) disappear when the person moves, falls ill or is replaced. Writing the habit down lets the next person inherit it.

The second is fairness. Without a written rule, each case is decided by whoever happens to be asked, on the day, and two members in the same situation may be treated very differently. People who are treated differently, and cannot see why, lose trust.

The third is honesty with the people held. Members cannot ask whether their information is treated well if they do not know how it is treated. A written policy lets a member read a promise and, later, hold the community to it. This is uncomfortable for a leader and good for a community.

There is an objection worth stating in its strongest form. Some leaders, in house churches and in small congregations built on personal trust, say that a written policy is a step toward the cold institution; that the relationships are the protection; that paper invites lawyers, suspicion and a "rights" attitude among brothers and sisters. This is a serious point, and it is true that a policy can be misused as a replacement for love. The reply is not that love is insufficient but that love is not always present, and not always present in the next leader. A short statement of what we do is a way of making care outlast the person who first had it. If the paper becomes a weapon, it was written wrongly or used wrongly; the remedy is better paper, not no paper.

2. One page, eleven questions

A useful policy answers eleven questions, in this order. The order matters: it moves from why, through what, to how, to what if, and ends with who and when.

1. Why do we hold information about people at all? One or two sentences of purpose. For example: "We hold information about people so that we can care for them, teach them, serve with them and be accountable for what has been given to us." If a use is not covered by the purpose, the church has no business holding the information for it. This sentence is the test that everything below is measured against.

2. What do we hold? A plain list of the kinds of information: registers, giving records, visiting notes, children's forms, photographs, contact lists, and so on. This is the map from the first week of the course. The policy does not contain the information, only the categories, and it says which are especially sensitive.

3. How do we collect it? We ask only for what we need, we say why, and we tell people when they may decline. Where a form exists, it states the reason for each question.

4. Who may see it? Access by task, not by rank or curiosity. The policy says, for each kind of information, which roles may see it (for example, "children's allergy information: the children's team leader and the helpers in the room on the day"). It is the shortest section and often the hardest to write, because it forces choices.

5. How do we keep it? Where the paper lives and who holds the key; where the digital copies live; that personal phones and private accounts are not the place for sensitive records; that special records (notes of pastoral conversations, safeguarding concerns, discipline) are kept apart.

6. How long do we keep it, and how does it end? In words, not numbers: "while we need it for the reason it was given, and as long as the rules where we serve require for certain records; then we destroy it." The policy names the way of destruction, such as shredding paper and deleting every copy.

7. What do we do with outside tools? Any service that holds our information (a storage service, a form tool, a messaging app) is chosen by a named person, after asking the questions of Chapter 4, and is not adopted because a volunteer likes it.

8. What do we do if something goes wrong? The first-hour order of Chapter 5 in a few lines: say so at once, tell the named person, care first for those affected. The policy gives a name and a way to reach that person.

9. How may a person ask about their own record? Any person may ask what we hold about them, ask us to correct it, and ask us to remove it. The policy says to whom the request goes, that we answer kindly and promptly, and that where we must keep something, we say so and why.

10. Who is responsible? A named role, not just "the church". One person, with a deputy, who holds this policy and answers questions. In a very small community this may be the pastor and one other trusted person. In a large one, it may be an administrator under the board.

11. When do we look at this again? A stated rhythm of review (for instance, once a year, and whenever something changes, such as a new tool or a new ministry), and a note of who attends.

There is a twelfth item that is not one of the questions but is just as important: a version for members. The policy that the board reads and the paragraph that a new member or a parent of a child in the youth group reads need not be the same length. The members' version is a half page in the plainest language, saying what is promised and whom to ask. It sits where people can see it: on a noticeboard, with the membership information, on the church's website if it has one.

3. How to write it: order, people and words

Start from the map. Do not begin by looking at another church's policy. Begin with what your community holds, from the Chapter 1 map, and the habits it already has. The first draft is often a description of what the church already does well, with two or three gaps marked.

Consult the people who will carry it. The secretary who files, the children's leader, the treasurer, the person who runs the sound desk and the live stream, a youth worker, an or and, where possible, a member who is not in leadership. The reason is practical and also theological. A policy written by the leader for others will be quietly ignored by those others. A policy that the volunteers helped to shape is one they recognise as their own. In the language of the reading from Acts, let the people choose, and give the task to named hands. Ask each of them one question: "What is the hardest thing for you to keep to, in this area?" The answers tell you where the policy needs to be realistic.

Write for the person who will read it once. Short sentences. No words that need a dictionary. "We keep the key to the cabinet; two people hold one" is better than "access to physical repositories is restricted." For every sentence, ask: could the least experienced volunteer, reading it alone, know what to do? A reader in a second language needs this even more.

Say what you will do, not what you will never do. "We never lose data" is a promise no one can keep. "We lock the cabinet, we tell the named person at once if something goes missing, and we tell those affected" is a promise that can be kept and checked. Be modest. A policy full of "never" and "always" teaches people that the paper is not true.

Name the rule to follow locally; do not copy it. This course cannot say what the rules are where you serve, and the policy should not pretend to. A sentence such as "We follow the rules that apply where we serve about keeping records, telling people about a loss of data, and reporting suspected harm, and we ask a qualified person to tell us what those rules are" keeps the policy honest. The detail of the rule lives with the person who knows it, and the policy points to that person.

Small and large. A house church of fifteen can have a policy of a third of a page, known to everyone who meets, and held by two people. A cathedral parish, a large congregation or a denomination with several sites will have a fuller structure: a short policy at the top, and below it separate short procedures for the children's ministry, the office, the finance team and the media team. Even then, the top page should still fit on one sheet. The common failure of a large community is to write many pages that say nothing; the common failure of a small one is to write nothing because "we all know."

Do not copy a long document. It is tempting to take a long policy from a larger body, change the name at the top and file it. Then there is a document that nobody in your community wrote, nobody has read and nobody could follow. It may promise things you do not do, and a promise on paper that is not kept is worse than silence, because members rely on it. If you borrow, borrow ideas and sentences, one at a time, and test each against your real habits.

4. What to ask a qualified person to check

Nobody expects a minister to be a lawyer. But a policy that touches what must be kept, what must be reported, and what must be told to people needs a second look by someone who knows the local position. Ask a lawyer experienced with charities or religious bodies, a competent authority that advises such bodies, or the office of your denomination or association, if it has one. Take them the one-page draft and ask:

  • Is anything in this policy contrary to a rule that applies to us?
  • Are there rules about records, consent, children, reporting suspected harm, or telling people about a loss of data that we have not mentioned and should?
  • Is there anything we promise that we are not allowed to promise (for example, a promise of secrecy that the rules where we serve do not allow us to give)?
  • Is there anything we must say that we have left out?

Write down what you asked, who answered and when. Lecture 6-3 returns to this. The point here is that the policy is written by the community and checked by the expert, not the other way round. A policy written wholly by an outsider is hard to own; a policy that nobody checked may be wrong in ways the community cannot see.

5. An invented sample, annotated

(An invented case.) A small congregation, which we will call the Fellowship of the Green Door, meets in a rented hall. It has about sixty members, a Sunday children's class, a prayer team, a part-time administrator named Marta and an elder named Tobias who has agreed to be the policy's keeper. After a discussion over several evenings with Marta, the children's leader, the treasurer and two members, they produce the following. The notes in square brackets are the teacher's, not part of the policy.

How the Fellowship of the Green Door holds information about people

Why. We hold information about people so that we can care for them, teach them, serve alongside them and give an honest account of what has been given to us. We do not hold it for any other reason. [Purpose is one sentence and doubles as the test: if a use does not fit, it is not allowed.]

What. We hold a membership list, a record of gifts, notes of pastoral visits, forms for children's activities, photographs from events, and the phone numbers and addresses people have given us. Some of this is sensitive, and we treat pastoral notes and children's health forms most carefully. [The categories are named. No one is listed.]

How we ask. We ask for only what we need and tell people why. A person may say no to anything that is not needed for the thing they have joined, and saying no will not count against them. [The second sentence is the one that matters most when the asker is the pastor.]

Who sees it. Each kind of record is seen by the people whose task needs it, and by no one else. The membership list: Marta, the pastor and the elders. Gift records: the treasurer and one other person. Children's forms: the children's leader and the helpers on duty. Pastoral notes: the pastor only; and we write only what is needed. [Roles, not names, so that the sentence survives a change of people.]

How we keep it. Paper records are in a locked cabinet; two people hold keys. We do not keep sensitive records on private phones or in private email accounts. Where we use an outside service, Tobias decides, after asking the questions we agreed, and records why. [A promise the church can keep: it names an action, not a result.]

How long. We keep a record while we need it for the reason it was given, and for as long as the rules where we serve say that we must; then we shred or delete it, including copies. [Words, not numbers, as agreed. The local rule is named, not copied.]

If something goes wrong. Anyone who notices a lost record, a wrongly sent message or a stolen device tells Tobias at once, without fear of blame. We will tell the people affected promptly and plainly, say what we are doing, and care for them first. [Note "without fear of blame": it invites the report.]

Your own record. You may ask us what we hold about you, ask us to correct it, or ask us to remove it. Ask Tobias or Marta. We will answer kindly and promptly. If we must keep something, we will tell you what and why. [Two named people, so that the member is not stuck if one is away.]

Who is responsible. Tobias, with Marta as his deputy. [A person and a deputy.]

Review. The elders and the people who work with records look at this page each year and when we adopt a new tool or begin a new ministry. We have asked a qualified person to check that it fits the rules where we serve. [The date of the last check is written under the policy.]

Notice what the page does not contain. It has no reference to the law of any country. It has no number of years. It does not name a product. It does not promise secrecy; it promises a circle. And it fits on one side of a sheet. A page like this is not perfect, and the next section shows how to look for its weaknesses.

6. Three ways a policy fails

A policy fails in three recognisable ways, and the lab at the end of the chapter asks you to find each of them in an invented page.

It promises too much. "All information is strictly confidential and is never shared with anyone." No community can keep that sentence: there are people who must be told (a leader responsible for safety, a person the local rules name), and there will be days when a form is misplaced. A sentence the church cannot keep damages trust the first time it fails.

It promises too little, or nothing. "The church will make reasonable efforts to protect information in accordance with appropriate standards." Nobody could say, after reading, what the church will do on Monday. This kind of sentence is written to protect the writer, not the person held, and it is easy to recognise by the fact that no one is named and no action is described.

It cannot be followed. "All records are reviewed quarterly by an audit committee." If there is no audit committee and no one with the time, the sentence is a fiction. A policy nobody follows teaches people that policies are decoration. Count the cost, as the reading from Luke says, before building the tower.

There is a fourth failure, which is not on the page: the policy is written and then put in a drawer. It must be read aloud at the volunteers' first meeting (Lecture 6-2), kept where people can find it, and brought out at the review. A policy kept but never used is a form of the same silence.

7. A word for those who feel behind

Some readers will recognise that their community has done none of this. Do not be ashamed; write one page this month. A first draft with five of the eleven parts and three honest gaps is more useful than a perfect policy planned for next year. The rest of this chapter is about what makes a policy matter at all, which is the way people live with it. But a short page, written together, is a good start.


Diagram 1. The one-page policy: eleven questions and a members' version

The one-page policy Eleven questions in this order, then a short version for members Why we hold information at all What kinds held, no names How we collect only what we need Who may see it by task, not rank How we keep it places, keys, tools How long, how it ends in words Outside tools who decides, why If something goes wrong who is told Your own record ask, correct, remove Who is responsible person and deputy When we review and who is there A version for members half a page, plain

Diagram 2. From idea to policy: who is in the room

Drafting together Counsel, then a draft, then a check, then a shared page Start from the map what we really hold Ask the carriers what is hardest? Write one page short, plain, modest Qualified check local rule named Then read it aloud, post the members' version, and set a date to review it.

In short

  • A policy is a short, plain written promise to the people a community holds. Its first use is to carry good habits past the person who started them.
  • A one-page policy answers eleven questions, from why the community holds information at all to when the page will be reviewed.
  • Draft it with the people who will carry it out. Start from your own map of what you hold, not from another body's long document.
  • Promise only what you can keep. Describe actions, not guarantees; use words for time, not numbers.
  • Name the local rule and ask a qualified person to check the page. A policy states principles; it is not the law of any place.
Front Back
Topic Writing a short, plain policy that states how a community holds information about people.
Remember One page, eleven questions in order, drafted with those who carry it, checked by a qualified person, with a plain version for members.
Caution A policy fails when it promises too much, says nothing, or cannot be followed; copying a long document produces all three.
One line to carry into ministry Write down what you truly do, promise only that, and ask someone qualified to check it.
Review every summary in this course →

Check yourself

Not "did you read it" but "can you explain it". Ticks are kept on this device only.

Reflection and discussion

  • Think of a habit in your community that protects people's information but exists only in one person's head. What would be lost if that person left tomorrow, and how would you write the habit down?
  • The objection says that a written policy can replace love with paper. Where have you seen paper used this way? What would make a policy serve love rather than replace it?
  • Which of the eleven parts of the policy would be hardest for your community to write honestly? What does the difficulty tell you about what the community actually does?
  • Who should be in the room when you draft? Name the roles of the people who would carry the policy out, and the one member who is not in leadership whose view you would want.
  • Look again at the three ways a policy fails (promising too much, too little, or what cannot be followed). Which is your community most likely to fall into, and why?
  • What exactly would you ask a qualified person to check, and whom would you ask where you serve?

Sign in to write and keep your answers

What next

The lecture ends here. What follows was written by its readers.