Lecture 2-4: Using, Sharing, Letting Go
목차 31
- Lecture 1-1: Secrets, Shame, Gossip and Trust in Scripture
- Lecture 1-2: Confidence in the Traditions, and Where It Stops
- Lecture 1-3: What a Church Holds, and What Can Hurt
- Lecture 1-4: When the Community Must Know, and When It Must Not
- Lecture 1-5: Practice Lab, Map What Your Community Holds
- Lecture 2-1: Collect Less, and Say Why
- Lecture 2-2: Consent When the Asker Holds Authority
- Lecture 2-3: Keeping It: Places, Keys and Who Needs to See
- Lecture 2-4: Using, Sharing, Letting Go
- Lecture 2-5: Practice Lab, Fix One Form
- Lecture 3-1: Writing Notes About People, and Not Writing Them
- Lecture 3-2: Prayer Requests and the Circle Around a Person
- Lecture 3-3: Children, Young People and Vulnerable Adults
- Lecture 3-4: When Exposure Can Endanger
- Lecture 3-5: Practice Lab, Rewrite the Note and the Request
- Lecture 4-1: Accounts, Passwords and Devices
- Lecture 4-2: Group Chats, Social Media, Livestreams, Cameras and Photographs
- Lecture 4-3: Choosing Tools and Vendors, the Questions to Ask
- Lecture 4-4: Volunteers, Borrowed Devices and Handing Over Access
- Lecture 4-5: Practice Lab, Audit One Day of Access
- Lecture 5-1: When Something Goes Wrong: The First Hours
- Lecture 5-2: Speaking to the People Who Were Hurt
- Lecture 5-3: Hands Changing: Pastors, Leaders, Splits and Closures
- Lecture 5-4: Leaving, Moving, Dying, Asking: Requests About a Person's Record
- Lecture 5-5: Practice Lab, The First Hour and the Handover List
A church asks with care and keeps with care. Then, months or years later, someone has a good idea. The directory would make a fine mailing list for the building appeal. The prayer requests collected in the small group would be moving in the newsletter. The youth contact list would help a member who is starting a small business and wants customers. Each idea comes from a warm heart, and each takes information given for one reason and uses it for another.
This lecture covers the last two stages of a piece of information's life: its use and its end. The chapter's principle names both: information is used only for the reason it was given, and let go when that reason ends. We look at what a change of use looks like, at the questions to ask before sharing with anyone outside the church, at what to do when a person asks about their own record, and at the quiet work of disposal. Then we face the hardest case: the records a church has good reason to keep for a very long time, and how they can be kept without wounding the people named in them.
As in the whole course, nothing here is legal advice. The rules about how long particular records must be kept, about a person's right to see or correct what is held, and about handing records to authorities differ from place to place. Learn the rule where you serve, ask a qualified person or the competent authority, and follow your community's written rules. What this lecture offers is the habit of mind that sits inside those rules and goes a little beyond them.
이 32분으로 얻는 것
- Apply the test of surprise to a proposed new use of information.
- Describe what to settle, and to write down, before sharing a record with an outside body.
- Explain a kind and prompt way to answer a person who asks to see, correct or remove what is held about them.
- Write a "keep until" rule in words, tied to a purpose, without any number of years or months.
- Distinguish records a community has reason to keep for the long term from records it should let go, and describe safe disposal for paper, devices and copies.
a time to tear, and a time to sew; a time to keep silence, and a time to speak;" — Ecclesiastes 3:7
World English Bible
He who covers an offense promotes love; but he who repeats a matter separates best friends." — Proverbs 17:9
WEB
But when you do merciful deeds, don’t let your left hand know what your right hand does, so that your merciful deeds may be in secret, then your Father who sees in secret will reward you openly." — Matthew 6:3-4
WEB
Ecclesiastes gives the rhythm that a record-keeper needs: there is a time to keep silence and a time to speak, and wisdom is knowing which time it is. Proverbs names what is at stake when something told in one setting is repeated in another: a friendship is damaged. A record repeated in the wrong place does the same. Jesus teaches that some good is done best unseen. A church that helps someone in need should not turn that help into a story, a list or a display.
1. Use only for the reason it was given
Information comes with its reason attached, as a gift comes with the giver's intention. A parent who gives a phone number for the Sunday school has not given it for any other purpose. A person who tells a small group about an illness has told it to that group, for prayer and support, and has not told the church. A member who gives an address for a visit has not given a mailing address for appeals.
The pastoral rule is plain: use information for the reason it was given. When a good new use appears, it is a new question to be put to the person, and it is not a favour the church may grant itself. Here are four everyday temptations.
A directory is not a fundraising list. A printed or online directory is given for members to reach one another. To use it for an appeal, or to let the appeals committee write to everyone in it, changes its meaning. People who would gladly give may be unhappy to find their details used in this way.
A prayer list is not a newsletter. Requests shared in a prayer group were given to those who pray. Printing them in a weekly sheet that is left on seats and carried home widens the circle without the person's knowledge. (Chapter 3 gives prayer requests a lecture of their own.)
A youth contact list is not for anything else. The numbers of young people and their parents were given so that the leaders could reach the families. Using the list to recruit customers for a business, to promote a political cause, or even to advertise another church's event turns a trust into a market.
A membership list is not a weapon. In a dispute, the person who holds the list holds a power, and the temptation to use it to gather supporters or to contact members privately is real. The list was given for the community's life together, not as a prize in a quarrel. Lecture 5-3 returns to this when hands change.
2. The test of surprise
A simple question settles most cases: would the person be surprised? If a member found out that their number was used in this way, would they say "of course" or "I did not expect that"? If the answer is surprise, the new use is outside what was given.
The test is more reliable than a rule, because it asks the question from the side of the person. It also has a fair outcome: where the answer is "of course", you may proceed. A church that texts parents a reminder about the camp for which they registered their child has not surprised them. A church that texts the same parents an invitation to the congregation's annual dinner may or may not have. When in doubt, ask. A short message, "We would like to use the numbers you gave for the camp to tell you about the dinner too. Reply STOP if you would rather we did not," costs little and can be answered by a person who can say no. A request that has to be asked in this way is exactly one where the answer might be no.
3. Sharing with those outside
Sooner or later someone outside the congregation asks for something. A denominational office wants a list of members or of ministers. A company that provides a church-management program or a storage service will hold the data. Another church wants to know about a member who is moving. A school or a charity asks about a family. An authority asks for records.
The pastoral habit for each case is a short set of questions, answered in writing before anything is sent:
- Why do they need it? Name the purpose in a sentence. If no one can, wait.
- What is the least that serves it? A total number may do where a list was asked for. A name may do where a full record was asked for.
- Who exactly will receive it? A named person or office, not "the denomination".
- What will they do with it, and will they keep it? Ask. A responsible body can answer.
- Has the person agreed, or would they be surprised? If the sharing is not part of what the person understood, ask them.
- How will it be sent? Not by a route anyone can read on the way. A list sent to the wrong address cannot be recalled. If you are unsure of the route, ask a person who understands such things.
- Who decided, and where is it written? One line in a record: what was shared, with whom, when, for what, and who agreed.
These are not obstacles. A denominational office that has a legitimate need will not mind them, and most responsible bodies already have answers.
A vendor is a particular case: a program or a service that holds the church's records on the church's behalf. The questions for choosing one belong to Lecture 4-3. Here it is enough to say that handing records to a vendor is sharing, and the same questions apply.
Requests from authorities deserve special care, and the answer differs from place to place. Some requests are lawful and proper, and a church should co-operate. Some are not. In some places, a church may be under pressure that no honest request would produce, and a list of members may put people in danger. The wise habits are the same everywhere: do not hand over anything on the strength of a telephone call or a visit alone; ask who is asking, on what authority and for which records; ask for the request in writing; tell the responsible leader at once; and ask a qualified adviser, such as a lawyer familiar with religious bodies, before answering. Where the request concerns a person who may be at risk, the person's safety weighs heavily, and Lecture 3-4 returns to this. Where a rule requires a church to report something, such as a suspicion of harm to a child, the duty comes before ordinary confidentiality. Who must report, what and to whom differs from place to place. Find out where you serve before the day you need it.
Whatever the answer, a church that has chosen in advance the people who decide such matters, and has written down how, will answer better than one that decides in the hallway.
4. When a person asks about their own record
Sometimes the person whose information is held asks for it. A member wants to see what is written about them. A former member asks to be taken off a list. A parent asks what is kept about a child. Someone wants a wrong date corrected or their photograph taken from the website.
Treat these requests as a form of the owner speaking. The general approach is the same in every case: take it seriously, answer kindly and promptly, and check the rules where you serve.
- Take it seriously. The request is not an attack. A church that bristles teaches people that asking is unsafe.
- Be sure who is asking. Before giving a record to anyone, check that the person is who they say they are, by a route you trust, such as a person you know or a call to a number already on file. A stranger who writes "I am Maria's husband, please send her record" may not be. Lecture 5-4 returns to this.
- Answer promptly. A reply that says "we have received this, and we will answer by such a day" is better than silence.
- Do what can be done. Correct what is wrong. Remove what the church has no need to keep. Stop a use the person objects to.
- Explain what must stay, and why. Some records the church must or will keep: a sacramental entry, a financial record, a record that the rules of the place require. Say so in plain words, and say what you can do about it, such as restricting who may see it.
- Write down what was asked and what was done. So the next person knows.
- Check local rules. Whether a person has a right to see, correct or remove a record, and in what time, differs by place and by kind of record. Ask a qualified person where you serve. If a rule gives the person more than the church's habit does, the rule governs. If the church's habit gives more than the rule, love does not ask you to give less.
Some requests will be hard, such as a person who is angry and wants everything removed, or one who suspects the church of holding something shameful. These are the moments in which a plain, unhurried reply does most for trust. Offer to meet. Offer to show what is held, where the rules and the safety of others allow.
5. When the reason ends: letting go
A reason ends. The camp is over. The volunteer has left. The visitor has been welcomed. The member has moved away. Here is the moment that most churches miss, because nothing marks it. Nobody receives a message saying "the purpose of this record has ended".
A simple remedy is a "keep until" rule, written in words and tied to a purpose, set when the record is made. It need not be a number. It can be:
- "Until the camp has finished and any follow-up is complete."
- "While the person is serving as a volunteer in the children's work, and for as long afterwards as the rules of this place require us to keep a record of who served."
- "Until the person leaves the congregation or asks us to remove it, unless a rule requires otherwise."
- "While the case is open, and afterwards only as the written rules of the community say."
Notice what these have in common. Each ties the end to an event. Each admits that some kinds of record must be kept for a period set by local rules, which this course cannot state: when you read "as long as local rules require", find out what the rule is. And each makes a decision of the church, since a "keep until" rule written in the open is something people can ask about and the church can be held to.
Where there is no rule at all, the plain habit is to ask each year what has ended. A short review (Lecture 2-3 suggested one for access) can ask the same of content: which forms are for events that have passed? Which people have left? Which lists are no longer used?
6. Letting go safely
Letting go means that the information is no longer readable by anyone. Dropping a card in the bin does not do that.
- Paper. Shred, or tear into small pieces, or burn where that is safe and lawful. Do not put readable records in an ordinary bin, a recycling skip or a rubbish tip where strangers will find them.
- Digital files. Delete the file, and then delete it where it also lives: the "recently deleted" place, the sync copy on other devices, the copy attached to an old email. A file removed from one place may exist in five.
- Backups. A backup made before you deleted still holds the record. Either it is replaced in its normal cycle by newer copies, or the old one is itself destroyed. Ask the person who keeps backups how and when they expire.
- Devices. A phone, laptop, tablet or storage drive that is given away, sold, repaired or thrown out can carry church information with it. Before it leaves, the information is removed and the device is reset, following the instructions for that kind of device, and, if you are unsure, with the help of someone who knows. A device with sensitive records that is simply discarded is a record put in the street.
- Copies on private phones and accounts. If volunteers have kept copies, ask them to delete them, and give them a way to say that they have.
- A note that it was done. For records that matter, write one line: what was destroyed, when and by whom. Do not keep the content.
Letting go can feel like a loss. Some people keep everything for the reason that they have not decided. A rule decided in advance spares the volunteer who finds an old box from having to make that decision alone.
7. Records worth keeping, and how
Not everything should be let go. The church is a body with a history, and some records serve that history and the people named in them.
Sacramental and membership registers. Many traditions keep registers of baptisms, confirmations, first communions, marriages and funerals. They serve the person (who may need a certificate or proof of a years later, for a marriage, an ordination or a family search), the community (a memory of who belonged), and in some places the wider society. They are kept for a very long time, often by rule. Their contents are usually few: who, when, where, by whom.
Financial and legal records. The rules of the place may require these for a period. Keep them as the rule says, and let them go when it ends.
The church's history. Minutes, photographs of celebrations, records of building works, letters from founders. A church has a duty to its own memory, and these are among the things that later generations will be glad of.
Records of cases and care. These are different. They are about a person's pain, not about the church's life. The case for keeping them is weaker and the case for letting them go is stronger, with the exception of what rules require, such as some safeguarding records. If they are kept, they are kept apart and sealed from ordinary access, with a rule for when they are reviewed or closed.
A practical way to hold both goods is to sort by what the record is about. Records about the church (decisions, buildings, sacraments, finances) lean towards keeping. Records about a person's private life (counselling, discipline, health) lean towards letting go, unless a rule or a serious reason says otherwise. Between them is a layer that should be held more closely as it ages: a history that names living people should be read by researchers only with care, and a rule for who may read old records, and from when, protects the people in them. Such a rule can be written in words, such as "this register may be consulted by those with a proper reason, with the pastor's permission".
This is a point where readers will not agree. Consider the entry of a baptism in a register, when the baptised person later asks for it to be removed because they have left the faith. Many Catholic and Orthodox communities hold that baptism is a fact that happened, that the register records an event and not a membership, and that the entry cannot be erased, though a note may be added, and access to the register can be restricted. Many other communities, including those that understand baptism as a profession of the person's own faith, would be more ready to remove or close an entry on request, since they see the register as a record of a relationship that the person has ended. Each view has an argument. The first protects the truth of what happened and the integrity of the church's memory. The second protects the person from a record that no longer says what they are. Where local rules speak to the matter, they govern. This course asks both to deal with the person kindly and plainly, to explain what the church can and cannot do, and to limit who may read the entry.
8. A worked example
(An invented case.) A congregation is preparing for a move to a new building. Rosa, who has been its secretary for many years, is asked to clear the old office. She finds: three boxes of forms from camps and trips going back many years; the visitors' cards of every Sunday since the church began; a bundle of letters from members about a dispute that ended long ago; the baptism register; the accounts for each year; a folder of newsletters; and a laptop that was replaced and is going to be given to a family in the congregation.
She asks the pastor and an to meet her, and they agree a plan, written on one sheet. The camp forms are for events that have ended, and they decide to destroy those with medical details by shredding, keeping a single sheet listing which camps took place and when. The visitors' cards are shredded, except for those that a visitor later became a member, whose details are in the register. The dispute letters are put in a sealed envelope, with the names of the two people who may open it, and a note that the church will review in a stated period whether to destroy them. The baptism register stays, in a locked cabinet, with a note on who may consult it. The accounts stay as the rules of the place require. The newsletters go to a small archive. The laptop is wiped and reset by a member who understands how, and is checked by Rosa, before it goes to the family.
Rosa writes at the bottom of the sheet: "Destroyed as agreed, on this date, by me and the pastor." She keeps the sheet, and nothing else of the destroyed material.
The pastor says that he had assumed the church needed all of it, and that it was a relief to find that it did not. The elder points out that it would not have been done had the move not forced the question. So they add a line to the church's calendar: each year, one evening in which the question is asked.
9. Where this lecture stops
This lecture does not name any period for which a record must be kept, or any right a person has in your place. It does not describe sharing with an authority in a way that fits every country, and it does not give legal advice. It teaches a habit: ask why before using, ask who and why before sharing, answer the owner kindly, and end what has ended. Where a rule is stricter, follow it. Where it is silent, the habit is your guide.
Diagram 1. The life of a piece of information
Diagram 2. Use and misuse
| Given for | Tempting new use | Why it is a new question |
|---|---|---|
| Members reaching one another (directory) | A fundraising appeal | The person did not expect to be asked for money |
| Prayer in a small group | A printed weekly sheet | The circle grows beyond those who were told |
| Contacting families about youth events | A member's business or a cause | Trust becomes a market |
| Community life together (membership list) | Gathering supporters in a dispute | A shared trust becomes a weapon |
| One event (camp forms) | Keeping for "just in case" | The reason has ended |
핵심 요약
- 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. |
스스로 확인해 보세요
읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.
묵상 및 토론
- Think of a list your community holds. For what reason was it first made? Has it ever been used for something else?
- Apply the test of surprise to a use you have seen or imagined. Would the person have said "of course" or "I did not expect that"?
- Proverbs 17:9 says that repeating a matter separates close friends. How does repeating a record in a new setting do the same?
- A person writes to ask what the church holds about them. Who in your community would answer, how, and by when? What would you want the reply to feel like?
- Write a "keep until" rule in words for one record your community holds, with no number. What event ends it?
- Some hold that a baptism entry records an event and cannot be erased. Others hold that it records a relationship that the person may end. State each at its strongest. What common minimum could both keep?