무료

수료증 무료 발급 — 2027년 3월 31일까지.

PT738E Privacy and Confidentiality in Ministry › 요약으로 복습하기

요약으로 복습하기

PT738E 과목의 강의 31편을 요약만으로 훑어봅니다. 시험 전날에 쓰세요.

제 0 장 Introduction: Held in Trust

  • The central claim: what people entrust to a church is theirs; the church is its keeper and holds it faithfully.
  • The course follows information through its life: asking, keeping, using, letting go, and what to do if something goes wrong.
  • It is not legal advice or a security audit, and it names no law, product or company.
  • It does not rank traditions; where they differ, it marks the place and says who holds what.
  • Four things are asked of everyone: do not spread what was entrusted; hold only what you need; put safety before secrecy; do not hide a failure.
  • Every week ends with a Practice Lab on paper that needs no software and no real records.
Front Back
Topic The central claim of the course and what the course covers and leaves to others.
Remember What is entrusted is the person's; the church is the keeper. Hold little, share narrowly, protect safety, and never hide a failure.
Caution This course is not legal advice or a security audit. Learn the rules where you serve and ask a qualified person.
One line to carry into ministry Behind every record is a person who trusted us.

제 1 장 Week 1: Entrusted Words

  • Scripture holds two goods in tension: a community that knows and bears burdens, and a person's protection from being exposed. Neither cancels the other.
  • Proverbs treats passing on a confidence as a betrayal even when what is passed on is true; trust is the condition of pastoral work.
  • Matthew 18 widens the circle only when a smaller one fails, and only by as little as needed.
  • Confession is the confessor's own act; a culture of confession is only as safe as the listener's discretion.
  • "Sharing for the sake of prayer" is a common form of gossip. Ask the person first.
Front Back
Topic How scripture treats keeping and betraying a confidence, and how a community can both know its members and protect them.
Remember Two goods are held together: a community that bears burdens, and a person who is not exposed. The circle widens only as far as the purpose needs.
Caution "Sharing for the sake of prayer" is a common form of gossip. Hidden things coming to light is God's work, not a licence to expose.
One line to carry into ministry Before telling anyone what you were told, ask the person whose story it is.
  • Traditions understand confidence differently: a sacramental seal in Catholic and Orthodox churches, a duty of trust and church order in most Protestant ones, and custom in many house churches.
  • The seal and the pastoral promise are about what is said; a church also holds notes, files and messages, which need their own rules.
  • Never promise absolute secrecy before you have heard. State what you can promise, and the exception, at the start.
  • Danger to life and harm to a child or vulnerable adult come before confidentiality. Involve a leader, trained help and your local emergency number.
  • Reporting duties and legal protection of clergy differ from place to place. Learn the rule where you serve.
Front Back
Topic How traditions understand confidence, where it must stop, and why a confidence must be kept in records as well as in speech.
Remember Be honest about limits at the start. Safety comes before confidentiality. A secret kept in the mouth and published in a file is not kept.
Caution Rules about reporting and about the protection of clergy communications differ by place and role. Do not guess; ask where you serve.
One line to carry into ministry Promise only what you can keep, and keep it in every form the words take.
  • A community holds far more than it usually counts: registers, giving, notes, prayer requests, children's records, health and family history, legal status, images, device data.
  • Sort by one question: who could be hurt if this left the room, how badly, and could it be undone? Four layers help: open, internal, restricted, specially sensitive.
  • The same fact sits in different layers in different places and for different people; the sorting is done by someone who knows both.
  • In some communities a membership list is itself the most dangerous record.
  • Information belongs to the context where it was shared. Ask where it came from and what it was for.
Front Back
Topic What a community holds, and how to sort it into four layers by the harm that exposure could cause.
Remember Ask who could be hurt, how badly, and whether it could be undone. The layer depends on the place and the person, and information belongs to the context in which it was shared.
Caution In some places a membership list is itself dangerous. When unsure of the layer, treat the information as one layer higher until you have asked.
One line to carry into ministry You cannot keep well what you have not counted; draw the map first.
  • Separate what a congregation needs in order to act from what it merely wants to know. The detail often serves curiosity, not care.
  • Four questions test any disclosure: who asks and why; did the person agree; who could be hurt; is there a smaller circle that serves the purpose.
  • Financial transparency means showing how money is used, not showing each member what others gave.
  • Public confession and discipline can heal or shame, depending on whether it was chosen, the words are the person's own, and mercy follows.
  • Open and confined traditions each have a strong case and a real danger; both owe members care in what is told.
Front Back
Topic What a congregation must know and must not, and how to decide in the hard middle.
Remember Ask four questions: who asks and why; did the person agree; who could be hurt; is there a smaller circle. Share the need, not the detail.
Caution Public confession and discipline can shame as easily as heal. Reporting duties for crime or harm to a child differ by place and are not replaced by church discipline.
One line to carry into ministry Before you tell the congregation, ask whether the smaller circle would do.
  • An information map lists kinds of information, who holds each, where it lives, who can see it, its layer, and who could be hurt.
  • Use roles and categories only. Never bring or write a real name, entry, account or password.
  • "Don't know" is a useful answer, often the most important one. When unsure of a layer, choose the higher one.
  • Asking a partner "who could be hurt if this left the room?" is harder to wave away than asking yourself.
  • The four promises hold the room: nobody reads your sheet, nothing is marked, you may pass, the leader writes too.
Front Back
Topic An information map: kinds, holders, places, viewers, layers and who could be hurt, drawn by hand in a lab.
Remember Use categories only. Write "don't know" where you do not know. When unsure of a layer, choose the higher one.
Caution Never bring a real list, record, note or password. If someone in danger is mentioned, stop the lab and follow the rule that safety comes first.
One line to carry into ministry The first thing I will ask about is the row where I wrote "don't know".

제 2 장 Week 2: Collecting, Keeping, Using, Letting Go

  • Information has a life: it is collected, kept, used and let go. What is never asked for needs no care, and what is asked for must be cared for until it is let go.
  • "We might need it someday" has no end. Ask for what a stated purpose needs, and ask again if a new purpose arrives.
  • Ask of every field: what will we do with this, and who will see it? A field with no answer has no purpose.
  • Fields such as health, address, family status and past conduct need the strongest reason; some almost never belong on a general form.
  • Say on the form what is asked, what for, who sees it, and how long it is held, in words.
  • The less you hold, the less you can lose and the less you can be forced to hand over.
Front Back
Topic Collecting less and saying why: asking only for what a stated purpose needs.
Remember Two questions for every field: what will we do with this, and who will see it? No clear answer means the field goes or becomes optional.
Caution A shepherd's deep knowing of people is not forbidden; the test is that anything written has a purpose and a short, named circle of readers. Local rules may require some records, so learn them.
One line to carry into ministry Do not ask for what you cannot explain to the person who must give it.
  • Consent is how a person stays the owner of what they entrust. A signature without real agreement protects no one.
  • Real consent is told what for, free to refuse, able to be withdrawn, understandable and not bundled.
  • A request from someone who decides about baptism, marriage, membership or help makes refusal feel disloyal, however kind the asker.
  • Lower the cost of "no": separate asker from decider, give time, offer a smaller circle, and say aloud that no is welcome.
  • Take extra care with the sick, grieving, dependent, newcomers and children. For children, ask the guardian and, as they grow, the child too.
  • Consent cannot fix a request that should not be made. A need is a notice, and a harmful use is not cured by a signature.
Front Back
Topic Consent when the asker holds authority: what makes a member's "yes" real.
Remember Five marks: told what for, free to refuse, able to withdraw, understandable, not bundled. A plain sentence says what, for what, who sees it, until when, and how to say no.
Caution Consent does not repair a request that should not be made. What counts as valid consent in law differs by place, so ask a qualified person where you serve.
One line to carry into ministry Make it easy for a person to say no, and then believe their yes.
  • A person sees a record because a task requires it, not because of their title, and not because of concern or curiosity.
  • Paper needs a lock, a named key holder, records put away when no one is there, and safe destruction. Screens need folder-by-folder access, individual ways in and checked copies.
  • Copies spread through attachments, private phones and backups. Each copy needs the same care as the original, and each must be let go too.
  • Counselling notes, safeguarding records, discipline files and screening records are kept apart, with a short written list of named people.
  • Where one person holds everything, add a second trusted holder, a sealed note of where things are, and a written rule.
  • Review who can open each store once a year and whenever someone leaves a role.
Front Back
Topic Keeping records: where they are, who holds the key, and who needs to see them.
Remember Access by task, not by title or curiosity. Keep the most sensitive records apart, with two named people. Check copies and backups. Review the list each year.
Caution Traditions differ on how far a board may see a minister's private records. Keep finance and decisions open to oversight and private words with the minister, and learn any local rule on storage.
One line to carry into ministry Faithful keeping is small and unseen: a lock checked, a list shortened, a key accounted for.
  • Information is used for the reason it was given. A new use is a new question for the person, not a favour the church grants itself.
  • The test of surprise asks whether the person would say "of course" or "I did not expect that".
  • Before sharing outside, settle and write down why, the least that serves, who receives it, and who decided. Do not hand records to authorities on a call alone.
  • A person who asks about their own record is the owner speaking: take it seriously, answer kindly and promptly, and check the local rule.
  • Write "keep until" in words tied to an event. Let go by shredding, deleting every copy and backup, and wiping devices.
  • Sacramental registers and the church's history may be kept for long; private records of pain lean towards letting go.
Front Back
Topic Using, sharing and letting go: the later life of a record.
Remember Use only for the reason given; ask "would they be surprised?". Write sharing decisions down. Write "keep until" in words. Let go means every copy gone.
Caution How long records must be kept, and what a person may demand, differ by place. Traditions also differ on whether a sacramental entry may ever be removed.
One line to carry into ministry When the reason ends, let the record end, and keep only what the church's memory and the law truly require.
  • A form is a promise in small print. Test each line with two questions: what will we do with this, and who will see it?
  • A line with no answer is removed, or turned into an optional, open question the person answers as they choose.
  • A consent sentence names a specific use and circle, says how long, and tells the person how to say no.
  • A "keep until" rule is tied to an event and written in words, with no number.
  • The lab works on paper by hand with an invented form, a partner, or only the fields of a form from your own community.
  • The four promises: nobody reads your sheet, nothing is marked, you may pass, and the leader writes too.
Front Back
Topic Practice lab: repairing one form with a purpose for each field, a consent sentence and a "keep until" rule.
Remember Two questions per field. Remove or soften what has no answer. State the use, the readers, the end and the way to say no. Write the end in words.
Caution Never bring a real list, record, note or credential. Use the invented form or only the fields of your own. Local rules may require some lines and some records.
One line to carry into ministry A form is a promise: make sure each line can be explained to the person who must fill it in.

제 3 장 Week 3: Notes, Prayer Requests and People at Risk

  • A note is useful for continuity, accountability and protection, and risky because it outlives the relationship and is easy to copy.
  • Write every note as though the person described, and a stranger, might read it one day.
  • A minimal note holds the date, who was present, what was agreed and the next step.
  • Leave out diagnoses, labels, guesses about motives, third parties' stories and the details of a confession.
  • Keep ordinary notes apart from closely held records, with a short named list of readers and a rule for letting them go.
  • Decide in advance, in writing, what happens to notes when the writer leaves, falls ill or dies.
Front Back
Topic Pastoral notes: what to write, what to leave out, where they live and what becomes of them.
Remember A note records date, who was present, what was agreed and the next step; it keeps fact apart from interpretation.
Caution A note outlives the relationship; labels, motives, third parties' stories and confessed details do harm when a stranger reads them.
One line to carry into ministry Write nothing about a person that you would be ashamed for them to read, and say to them what you write.
  • A prayer request is a story about a person told by someone else, and it is one of the commonest ways a church passes on private life.
  • The story belongs to the person it is about. Ask what may be shared, with whom, where and until when.
  • The more permanent and public the place (bulletin, chat, board, recording), the more general the words and the clearer the permission should be.
  • Use the lowest rung of the ladder that serves the purpose: the person, the pastor, a promised team, a small group without names, the congregation in general terms.
  • General language lets a community pray without exposing anyone; a person who cannot speak is served by the least that meets the need.
  • Where someone may be in danger, a prayer request is not enough: safety comes first.
Front Back
Topic Prayer requests and the circle around a person: how a request becomes gossip and how to ask first.
Remember Ask what may be shared, with whom, where and until when; choose the lowest rung of the ladder that serves the purpose.
Caution Bulletins, chats, boards and recordings keep a request long after the need has passed; a prayer request is no answer to danger.
One line to carry into ministry Before you say "please pray for her," ask her what you may say.
  • Children and vulnerable adults cannot easily consent, refuse or complain, and leaks can follow them, so their records need more care.
  • Decide in writing who may see each kind of record; most people need to see very little.
  • Write a concern as what was seen and said, with the time and what you did, not as a conclusion or a label.
  • Keep concerns apart from ordinary files, and do not discuss them in corridors or group chats.
  • If you suspect harm, safety comes first: tell the responsible leader, involve trained help, and use your local emergency number in danger.
  • Never promise absolute secrecy to a child, and do not investigate yourself.
Front Back
Topic Keeping records about children, young people and vulnerable adults.
Remember Write what was seen and said, keep concerns apart with a short named list of readers, and pass worries to the responsible leader at once.
Caution A conclusion or a label in a record can harm the child; a corridor conversation can leak a concern as surely as a lost file.
One line to carry into ministry Let the children come close, and keep what you hold about them small, plain and safe.
  • For some people, one wrong disclosure can cost safety, liberty or life, and what is dangerous depends on context, place and person.
  • The strongest defence is to hold less: ask whether a thing is needed at all, and whether it needs to be written.
  • Where something must be held, keep the list small, locked, offline where possible, uncopied and with one or two named holders.
  • Speak in generalities, and never confirm to an outsider who attends.
  • Ask the person before each disclosure, and make it easy to say no.
  • Do not give legal advice; send people to qualified local help.
Front Back
Topic Information that can endanger: holding less, keeping lists small, speaking in generalities and asking first.
Remember Ask whether you need it at all, keep the list small and locked, and check with the person before any disclosure.
Caution A well-meant welcome, a testimony or a convenient list can expose someone; this lecture is not legal advice.
One line to carry into ministry What you do not hold, you cannot lose or be forced to give up; and nothing about a person at risk is shared without asking them.
  • Mark each line of a note as keep, remove or rewrite, and give a reason for removing.
  • A note should serve the next step; labels, guesses, third parties' stories and confessed details do not.
  • A request without a name can still identify a person; check what others could do with it.
  • Choose the lowest rung of the circle that serves, and ask the person first.
  • A lab uses invented cases or categories only; nobody reads your sheet, nothing is marked, you may pass, and the leader writes too.
Front Back
Topic Practice lab: marking a pastoral note and rewriting prayer requests for a wider circle.
Remember Keep what serves the next step; ask "what could someone do with this?"; choose the lowest rung and ask the person.
Caution Leaving out a name is not the same as being anonymous; if someone in the lab speaks of danger, safety comes before confidentiality.
One line to carry into ministry When someone asks "may we pray for this?", say "yes, and tell me what I may say."

제 4 장 Week 4: Digital Safety

  • Many harms to the people a church holds information about come from ordinary lapses: reused passwords, lost phones, old access, a message that was not what it seemed.
  • Each important account needs its own long password. A manager or a locked paper notebook can hold them.
  • A second step at sign-in means a stolen password alone does not open the door. Check where recovery really points.
  • When a device is lost, say so quickly, change the passwords of what was on it, lock it remotely if you can, and write down what it held.
  • Signs of a deceptive message are pressure to hurry, a request for money or codes, and changed details. Confirm by another route.
  • When a person leaves, remove their access the same week with a written checklist.
Front Back
Topic The doors to a church's information: accounts, passwords and devices, and who holds the keys.
Remember One password per account, a second step on the important ones, recovery pointing to a role, and the leaving checklist done the same week.
Caution A shared account hides who did what, and a lost phone reported late cannot be protected. A message that presses you to hurry is a sign to stop and confirm.
One line to carry into ministry Keep the doors well: the people whose stories are behind them did not choose to depend on our habits.
  • Group chats, posts, streams, cameras and photographs are records, even if nobody planned them as such. The questions are where they are kept, who can reach them and how they end.
  • Know who administers a chat, who can add people, and who still holds the history after leaving. Give each group one purpose and a short rule.
  • Ask before posting a person's image or name. Make refusal easy, and make removal afterwards simple and prompt.
  • For streams, recordings and cameras, decide who is in frame, who sees the data, and how long it is kept, in words, before starting.
  • Keep event photographs in one church-controlled place with a named holder, labelled by event, with a stated rule for what is kept.
Front Back
Topic The storage, access and deletion of what group chats, social posts, streams, cameras and photographs hold about people.
Remember Know the admin, give each group one purpose, ask before posting, make removal easy, and keep photographs in one place with a named holder.
Caution A member's number, face or caption can reveal a story they did not choose to tell. Removal reaches only what the church holds.
One line to carry into ministry Let people be seen only as they agreed to be seen, and let them change their mind.
  • A church often adopts a tool because a volunteer likes it. The church stays the keeper of the information and cannot hand that duty to the vendor.
  • Ask where the data is kept, who at the vendor can see it, and what the vendor may do with it, in plain words and in writing.
  • Check that you can export and delete everything, what happens when payment stops, whether access can be limited and logged, and whether you will be told of a breach.
  • Name a person or small group to own the decision, tell members where their information is kept, and ask someone qualified to look at any tool that will hold sensitive material.
  • Do not type names, health, family trouble or counselling content into AI, translation or document tools. Describe the task with an invented case.
Front Back
Topic The questions to put to any outside tool or vendor before it holds information about people.
Remember Where is the data, who can see it, can we export and delete it all, can we limit and log access, will we be told of a breach, and who owns the decision.
Caution A free or cheerful tool may hold what it should not, and a story without a name can still identify a person. Never type sensitive content into an AI or translation tool.
One line to carry into ministry Count the cost of leaving before you enter, and keep the people's information as theirs.
  • Churches rely on volunteers' own phones, laptops and accounts. The aim is simple rules, applied first to leaders and without suspicion, for devices and accounts the church does not fully control.
  • Write a short plain understanding: what you may see, what you may use it for, what you must not do, and whom to tell, with a promise of thanks.
  • Keep church work and private use apart where possible; where it is not, lock the device and limit what is on it.
  • Give access by task and for a season, keep a list of who has what, and end access in the same week a person leaves.
  • Share a single window, not a screen. Show a board only what its task needs. Make reporting a slip easy.
Front Back
Topic Volunteers, borrowed devices and handing over access: simple rules, given and taken back without suspicion.
Remember A short understanding, access by task and season, a list of who holds what, and the leaving steps done the same week, with thanks.
Caution A volunteer who fears blame will hide a slip, and a leader who does not keep the rules teaches that they are only for others.
One line to carry into ministry Make it easy to say "I made a mistake", and make ending access a way of saying thank you.
  • The lab is done by hand with categories and roles. No real list, record, account or password is brought.
  • A map of accounts shows who can enter each one, whether there is a second step, and where recovery points.
  • Starred items, the ones marked "do not know", are the first thing to find out.
  • The leaving checklist works best as a thank-you, done calmly in the same week.
  • The four promises hold: nobody reads the sheet, nothing is marked, you may pass, the leader writes too.
Front Back
Topic A paper audit of one day of access: accounts, devices, keys and the people who can reach them.
Remember Draw the map in categories and roles, star what you do not know, and write five small actions in order.
Caution Never bring a real list, name, address or password to the lab. If something private is shared, ask the room to keep it, and put safety first if someone may be at risk.
One line to carry into ministry Find the old key in the pocket before anyone else does, and do it kindly.

제 5 장 Week 5: When It Goes Wrong, and When Hands Change

  • An incident is any event in which information about people may have reached the wrong hands or been lost. Small ones count, and handling them well prepares a church for the large one.
  • A sensible order is: notice and say so, stop the spread, keep a record, tell the responsible person, find who is affected, get qualified help, check what you must tell others.
  • Hiding, deleting evidence, solving it alone and blaming the volunteer each make an incident worse.
  • Speed of reporting depends on how the last report was received.
  • A one-page plan, made in a quiet week, names roles, order of calls and who may speak.
  • What you must report, to whom and by when differs from place to place: ask early, follow local advice, and write down the answer.
Front Back
Topic The first hours after information about people may have been exposed or lost: what to do, in what order, and what to avoid.
Remember Notice and say so at once; stop the spread; keep a record; tell the responsible person; find who is affected; get qualified help; check what you must tell others.
Caution Do not hide it, delete what you may need, try to solve it alone or blame the volunteer. What you must report differs by place and role, and safety of people comes first.
One line to carry into ministry When something goes wrong, say so at once, and let the person whose information it is come first.
  • The first duty after an incident is to the people whose information it was. They are told before the congregation, and promptly.
  • A person needs to hear what happened, what it means for them, what the church has done, what they can do, and whom to contact.
  • A plain apology names the act, says it was wrong, says "we are sorry" and says what will change. It does not excuse, minimise or use pious words to quiet a complaint.
  • Vulnerable and at-risk people are told in person and privately first, by a route that cannot put them in danger.
  • A congregation announcement says what happened and what the church has done, and leaves out names. Traditions differ on how much a congregation should be told.
  • The apology is kept by what follows: changed practice, a note saying so, and a calm review.
Front Back
Topic How to speak to the people hurt by a loss or exposure of their information, and to the congregation.
Remember Tell the person first, promptly and plainly: what happened, what it means for them, what has been done, what they can do, whom to contact. Apologise without excuse.
Caution Do not minimise, use pious phrases to hush a complaint, or send a message that could put an at-risk person in danger. Rules about whom you must tell differ by place.
One line to carry into ministry Say what happened in plain words, say you are sorry, and then change what you do.
  • A change of hands is the risky moment: the knowledge is in a person, access outlasts authority, and feelings run high.
  • A handover list sets out what is handed over, what is not, who holds what access, what is closed or deleted, and what is archived and where.
  • The leaver's access ends on the day they leave. This is the church's habit for everyone and says nothing against the person.
  • A member list is not a prize in a dispute. People are told neutrally of a change so that each can choose.
  • Traditions differ on who owns a pastor's private notes: the relationship or the church. A common minimum: no weapon, sealed or deleted by prior rule, no exposure, a trusted person above knows.
Front Back
Topic What happens to a church's records when a pastor or leader leaves, retires or dies, when churches divide or merge, and when a church closes.
Remember Make a handover list: what is handed over, what is not, who holds access, what is closed, what is archived. End the leaver's access the same day.
Caution Never use files as leverage in a conflict. Traditions disagree on who owns a pastor's private notes; the rules about records differ by place and church.
One line to carry into ministry When hands change, nothing is used as a weapon, sensitive records are sealed or ended by rule, and the people they concern are not exposed.
  • Receive a request about a person's record kindly, write it down, check who asks by a trusted route, say when you will reply, and do what can be done.
  • Explain what must be kept and why. Rules about access, correction and keeping differ by place: ask when unsure.
  • A request to leave a list or remove a photograph is met promptly, with an honest account of what cannot be undone.
  • Requests by a parent about a child, by a family after a death, or by an adult child need a responsible leader. A safeguarding record is not ordinary.
  • The dead can be hurt through the living. The family decides what is said of the cause of death, and a person's confidences do not end at death.
  • Registers are kept for the church's memory, held closed with a record of who opens them. Traditions differ on removing entries.
Front Back
Topic How a church meets requests about a person's record: a member leaving, a request to be removed, a family after a death, a parent or an adult child, and the keeping of registers.
Remember Receive kindly, write it down, check who asks by a trusted route, give a date, do what can be done and explain what must be kept.
Caution A safeguarding concern is not an ordinary record. The dead can still be hurt through the living. Rules about access, keeping and correction differ by place.
One line to carry into ministry Answer a request about a person's record as you would want to be answered, and keep only what you have good reason to keep.
  • The lab practises the first hour of an incident and the writing of a handover list, on paper, with invented material.
  • It has three ways in: the observer's way, the partner's way and the own-community way. Each is complete on its own.
  • The own-community way uses only categories and structures: no real names, entries, accounts or passwords.
  • The four promises hold: nobody reads the sheet, nothing is marked, you may pass, and the leader writes too.
  • No lab asks anyone to bring a real list, record, note or credential, and none needs software or the internet.
Front Back
Topic A paper practice lab for the first hour of an incident and for a handover list.
Remember Fill Sheet A in order, say first what happened and that you are sorry, and correct a handover list so that access ends and sensitive records are decided.
Caution Use categories only. Bring no real list, note or password. If someone is at risk, safety comes before the lab's promises.
One line to carry into ministry Rehearse the first hour and the handover while nothing is at stake, so that your hands know what to do when something is.

제 6 장 Week 6: Policy and Culture

  • 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.
  • Culture is how a community behaves when no one is checking. It is built by a short first meeting, regular reminders, example and the way slips are received.
  • A written pledge and a spoken promise each have honest reasons behind them. Whichever is used should say what the volunteer will do, bind the leader too, and be remembered.
  • People ask first and report slips when asking is welcomed and reporting is thanked. The leader who admits a slip first teaches the room that slips can be survived.
  • A slip calls for care and learning, a pattern for gentle correction, and a deliberate misuse for stopping access and protecting those hurt. Safety comes first where anyone is in danger.
  • Access limits are care for the people held and for the volunteer. A church that watches its own people has turned care into suspicion.
Front Back
Topic Teaching volunteers, forming a culture of care, and responding when trust is broken.
Remember Explain why, say what they will see and may not share, make asking and reporting safe, and respond to a slip, a pattern and a misuse differently.
Caution Do not let care for information become surveillance, and do not use a pledge as a weapon or reproof in public as a first step.
One line to carry into ministry Thank the person who tells you of a slip, and go first yourself.
  • No course can teach the rules where you serve. A minister's duty is to find out: ask a church body, a qualified lawyer, a competent authority or a trusted colleague, and ask more than one.
  • Ten categories cover most of what to ask: records, consent and notice, children, reporting harm, loss of data, clergy communications, cameras, gifts, staff and volunteers, and registration or church-body rules.
  • An answer is a floor. A rule says the least that is asked; love may ask more, and rules change and may conflict.
  • Traditions differ on whether a church should hold itself above the law's standard and whether the state's rules reach the church's inner life. Safety of a person is never given up by either view.
  • Keep a short written note of what you asked, whom, what they said, what was decided, and when you will ask again.
Front Back
Topic Finding out which rules apply where you serve, and deciding how to relate your community to them.
Remember Ask more than one qualified person across ten categories, treat the answer as a floor, and write down the question, answer and decision.
Caution Do not assume a legal protection exists or does not exist, and where asking is dangerous, hold less and ask someone outside the reach of those who would misuse the list.
One line to carry into ministry Learn the floor, then decide what love asks above it, and write it down.
  • Scripture holds two pictures together: a community of mutual knowledge and burden-bearing, and a community that covers and does not expose. Confession is something a person gives; exposure is done to a person.
  • Only God knows fully and safely. Human knowledge, and any record of it, is partial and can be misused, so ministers hold what they know with humility.
  • Traditions differ on how many should know, from a confessor alone to the whole assembly. Each has reasons and costs, and the course does not rank them.
  • Every community is asked for three commitments: no story used without the person's knowledge, no exposure by carelessness, and the person hurt cared for first.
  • No policy or record can make a church trustworthy. Faithful people can, and a good system makes their faithfulness easier and failure visible sooner.
Front Back
Topic How a community that confesses and bears burdens together can also protect its members from exposure.
Remember Known by God fully, by a few in part, by many only with reason. Every tradition is asked for three things: no story used unknown, no exposure by carelessness, the hurt cared for first.
Caution Do not choose one scriptural picture and drop the other, and do not take a good system for a trustworthy people.
One line to carry into ministry Hold what you know of people as God holds us: truly, gently and without show.
  • A personal rule names the kinds of information you hold, how you keep each, who else may see it and when you let it go. Write only what you can keep.
  • A badly written policy is missing something, says nothing anyone can do, or describes a practice that does not exist.
  • A one-page outline can be made by headings alone, using categories and structures and never names, entries, accounts or passwords.
  • The lab is run on four promises: nobody reads your sheet, nothing is marked, you may pass, and the leader writes too.
  • No lab asks anyone to bring a real list, record, note or credential, and none needs software or the internet.
Front Back
Topic Practice lab: writing a personal rule and outlining a community's one-page policy by hand.
Remember Three ways in: mark an invented policy, read your rule to a partner who asks one question, or outline your community's page by headings only.
Caution Never bring or write a real name, entry, account or password, and never promise absolute secrecy if someone shares something that suggests danger.
One line to carry into ministry A modest rule that is kept is worth more than a fine one that is not.