Lecture 2-1: Collect Less, and Say Why
목차 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
Every church form begins as a small kindness. Someone wants to welcome a family, to register children for a camp, to send a card on a birthday, to know whom to call if a child is ill. A line is added to the form for each of these good purposes. Years later the form has twenty-five lines, nobody remembers why half of them are there, and a drawer or a folder holds hundreds of copies.
This week follows information through its life. It is collected for a reason, kept by the people who need it, used only for that reason, and let go when the reason ends. This first lecture is about the beginning of that life: the moment we ask. The question is not "what could be useful?" but "what do we need, and have we told the person why?"
The claim of the whole course stands behind every lecture, and this week's piece of it is plain: a church collects only what it needs, and says why. Two things need saying at the start. First, this course is not legal advice, and it does not tell you what any country requires you to collect or to avoid collecting. Rules differ from place to place. Learn the rule where you serve, ask a lawyer or the competent authority, and follow your community's written rules. Second, the habit taught here works on paper and on a screen alike. A paper card in a drawer is as much a record as a row in a program.
이 33분으로 얻는 것
- Explain why holding less information protects the person and the church.
- Describe the "we might need it someday" trap and say why it is a trap.
- Audit a form field by field, asking what the church will do with each field and who will see it.
- Identify the fields that carry more risk and decide whether to ask for them at all.
- Write a short statement of purpose that tells a person why a form asks what it asks.
Therefore whatever you desire for men to do to you, you shall also do to them; for this is the law and the prophets." — Matthew 7:12
World English Bible
doing nothing through rivalry or through conceit, but in humility, each counting others better than himself; each of you not just looking to his own things, but each of you also to the things of others." — Philippians 2:3-4
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
Jesus gives the question to ask of every form: would I want to be asked this, and to have my answer kept this way? Paul asks us to look at "the things of others", which here means looking at a form from the side of the person who must fill it in, not only from the side of the person who will read it. The builder in Luke 14 sits down first and counts the cost. A line on a form has a cost, which is the care it must receive for as long as it is held. Count it before you add it.
1. A piece of information has a life
Think of a phone number written on a card. It is given on a certain day, for a certain reason: so that the youth leader can reach a parent about a trip. From that day it has a life. It is collected (asked for and written down). It is kept (put in a drawer, a folder or a phone). It is used (called, texted, copied onto a list). And at some point it should be let go (shredded, deleted, returned), because the trip is over and the reason has ended.
Most churches are careful about one of these stages and careless about the others. They are careful about collecting, because the form is printed and looks official. They are careless about letting go, because nobody has a day on which it happens. This week takes the four stages in order. Lecture 2-1 is about collecting. Lecture 2-2 is about asking a person's agreement. Lecture 2-3 is about keeping. Lecture 2-4 is about using, sharing and letting go. Lecture 2-5 is a lab in which you repair one form.
Collecting comes first because it fixes the size of everything that follows. What was never asked for does not need a lock, a backup, a rule about access, a reply to a request, or a plan for the day it is lost. What was asked for must be cared for until it is let go.
2. The trap of "we might need it someday"
The commonest reason a form is long is a sentence nobody says aloud: we might need it someday. It sounds like prudence. A church-office volunteer thinks, "If I ask for the date of birth now, I will not have to chase the family later." A pastor thinks, "If we know the whole family tree, we will be able to care for them better." A camp organiser thinks, "Let us ask about every illness in case."
There are two difficulties with this reasoning. The first is that "someday" has no end. Any item can be justified by some imagined future, so the test can never exclude anything. The second is that the cost is paid now, by someone else. The person who fills in the form gives up a piece of their life today, and the church keeps it with no planned moment of use. If a use does arrive, it can ask again, and by then the person can answer for the actual purpose.
An honest rule for the trap is this: ask for what you will use within a defined purpose, and ask again if a new purpose arrives. A small church may find this inconvenient. The inconvenience is a fair price for not holding a person's life in a drawer on a guess.
Notice that this is not a rule against ever collecting anything. A church that organises a trip must know whom to call if a child is hurt. A church that pays a staff member must hold the details needed to pay. The rule asks for a reason, and does not forbid the information.
3. The field-by-field question
The simplest tool in this course is a pair of questions asked of every line on a form:
- What will we do with this, and when?
- Who will see it?
If you cannot answer the first question in a sentence, the field has no purpose yet. If the honest answer to the second is "everyone who opens the folder", you have found a second problem: the field will be seen by more people than the purpose needs. (Lecture 2-3 returns to that.)
Take the line "Marital status" on a newcomer card. What will we do with it, and when? One answer: "We want to know whether to invite them to the marriage group or the singles group." That is a purpose, but a weak one, because the person can say so themselves when they come to a group, and the card does not need to guess. Another answer: "We want to know whom to send the birthday card to." That is not a purpose for marital status at all. A third answer is silence. After the audit, the line is either removed, or rewritten as an open invitation: "Is there anything you would like us to know about your family, so that we can welcome you well? (optional)". The person decides what, if anything, to put there.
Now take "Phone number" on the same card. What will we do with it? "Call or message the person to welcome them, once." Who will see it? "The welcome team, three people." Now the field has a purpose, a user and an end. The audit does not make every field vanish. It makes every surviving field answerable.
4. The forms a church actually uses
It helps to walk through the ordinary forms, because the same questions reveal different things in each.
The membership card or register. This is usually the longest-lived form. A church needs to know who belongs, and how to reach them. It rarely needs more than a name, a way to reach the person, and the date they joined or were received. Many registers also carry a date of birth, address, spouse, children, occupation, previous church and baptism details. Each of those can be argued for, and each carries a different weight. Ask for each: is this the register's job, or is it someone else's job (the baptism record, the pastoral file, the youth list)?
The camp or trip registration. This form has the strongest case for sensitive information, because a child far from home needs an adult who knows about an allergy or a medicine. The purposes are real and urgent. The risk is in what happens afterwards. The form is filled in for one week, and the medical details can sit in the folder for years. The purpose ends when the camp ends, and so should the holding.
The baptism or first-communion record. Many traditions keep sacramental registers as part of the church's long memory. They usually record the name, the date, the place, the minister, and sometimes the names of parents and sponsors. That is a different kind of record from a pastoral file, and Lecture 2-4 returns to why such registers are kept. Here the question is only whether the register has crept into holding more than its job needs.
The volunteer application. A church that asks someone to work with children or with money may need to check who the person is, and may be required to do so by rules where it serves. Those checks sit in other courses and in local rules. The point here is that an application form can drift into asking about a person's marriage, finances, health and past, and that each of these needs its own reason. Screening records are among the most sensitive a church holds, since they may mention past offences, and Lecture 2-3 puts them in a separate place.
The newcomer card. This is the lightest form and the one most likely to be over-built. A visitor has come once. The purpose is to say thank you and to offer a next step. A name and one way of reaching them, if they wish, serves it.
The giving form. People give for many reasons and some give in a way meant to be unseen. A form that records who gave how much serves the giver (a receipt, where a receipt is wanted or required) and serves the treasurer. It should not serve curiosity. Jesus said that the left hand should not know what the right hand is doing (Matthew 6:3), and a church that keeps a tidy list of who gave what has to be especially careful about who may read that list. Where the person has asked for a receipt, the form needs what the receipt needs. Where they have not, it may need little.
5. Fields that carry more risk
Some fields deserve a pause before they are placed on any form. They are not forbidden. They are the ones where a mistake costs the most, so the reason for asking must be strongest.
- Date of birth. It is a common key for identifying a person, and in many places it is used to confirm identity. A full date is often more than a church needs: a year, or an age band, or a simple "child or adult", may serve the purpose.
- Home address. It tells a stranger where someone sleeps. It is needed for a visit or a postal letter. It is not needed for a prayer list.
- Health information. It can be vital at a camp and unnecessary almost everywhere else. Say what the church will do with it. "In case of emergency" is a real purpose; "so we can pray" is better served by asking the person what they would like prayed for, in their own words.
- Family status. Marriage, divorce, children, who lives with whom. It is the subject of many private griefs. Ask only where something follows from the answer, and make it optional.
- Nationality or immigration status. In some places this fact is harmless. In others, a record of who is in the country without permission is a danger to every person on it. A church seldom needs it at all. If a form seems to need it, stop, and ask what is truly being decided. Lecture 3-4 returns to the people for whom exposure can endanger.
- Church or denominational history. Where someone worshipped before can reveal a conversion, a quarrel or a faith they left. It is a sensitive fact in places where leaving a religion is dangerous.
- Past offences or conduct. This is among the most harmful things to expose and among the hardest to take back. If a role requires a check, the check belongs with a small, named group and under the written rules of the community. It does not belong on a general form.
A single practical test for these fields: if this card were left on a bus, who could be hurt, and how badly? The answer to that question tells you how much reason you need for asking.
6. Saying why, on the form itself
A field with a purpose is only half-way to being fair. The person filling it in must also be able to see the purpose. A short statement of purpose at the top or beside the field changes the relationship. The person is no longer handing over a piece of their life to an anonymous drawer. They are answering a stated request.
A good statement says four things in plain words: what we are asking, what for, who will see it, and how long we will hold it. It need not be long. For example:
"We ask for a phone number so that a member of the welcome team can contact you once to say thank you and tell you about this week's events. Three people on the welcome team will see it. We will remove it after the welcome has been made, unless you ask us to keep it for the weekly news."
Compare that with a form that simply has a line labelled "Phone". The first treats the person as someone owed an explanation. The second treats them as a source. Lecture 2-2 returns to what it takes for the person's agreement to mean something, and Lecture 2-5 gives you practice writing these statements. Notice that "how long" here is written in words, tied to the purpose ("after the welcome has been made"), and not in a number of months or years. Some kinds of record must be kept for a period set by local rules, and you will have to learn those where you serve.
7. Why less is safer
There is a simple fact behind this whole lecture: the less you hold, the less you can lose, and the less you can be forced to hand over.
The less you can lose. A drawer is forced open, a phone is dropped, a laptop is stolen, an account is guessed. If the card in the drawer holds a name and a phone number, the damage is limited. If it holds a name, address, date of birth, health history and family details, the damage is much larger. The harm of a loss grows with what was kept, and a church cannot undo a loss after it happens. It can only have held less.
The less you can be forced to hand over. In some places, authorities, a quarrelling family, or a court may demand records. In some places pressure comes from a dispute within the church itself. What a church does not hold, it cannot be made to give up. This is not a reason for secrecy or for dodging legitimate rules. It is a plain observation, and for communities that serve under hostile or watchful governments it is among the most important things in this course.
The less you have to look after. Every item requires a lock, a decision on who may see it, an answer when its owner asks about it, and a day on which it is let go. A small church with a handful of volunteers has limited attention. A short form can be cared for properly. A long one tends to be cared for badly.
8. Objections, fairly put
Three objections deserve to be heard at full strength.
"A shepherd knows the sheep." Many pastors and priests will say that the work of depends on knowing people deeply: their families, sorrows and histories. A church that asks only for a name and a phone number may seem to treat its members as strangers. The point is fair. Deep knowledge is part of ministry in nearly every tradition. But there is a difference between knowing a person, which happens through relationship and at the person's own pace, and holding a record, which stays when the relationship has ended and can be read by someone who never met them. A pastor can know a great deal and write down little. This is a point where readers will not agree. Some traditions place great weight on a pastor's thorough knowledge of each household and are comfortable with extensive visiting records. Others, especially those that emphasise memory and prayer over files, prefer that little be written. This course asks both to keep the same test: whatever is written must have a stated purpose and a short, named circle of readers.
"Our denomination, or the rules where we live, require us to hold this." This can be true, and where it is true the rule governs. The course cannot tell you what is required, since it differs from place to place. If someone tells you "the rules require it", ask them which rule, ask a person in your denomination's office or a qualified adviser to confirm, and write down the answer. Do not assume that a long form is required because it was always long.
"It is easier to ask everything once." Convenience is real. A church with two volunteers does not want to repeat itself. The answer is to ask in layers: a short form first, and a second, specific form for the few people who need it (the families going on the camp, the volunteers who will work with children). Most members never fill in the second form, and so most members never place that information with you.
9. A worked example
(An invented case.) A small assembly has used the same joining form for many years. A new volunteer, Naomi, has offered to put the register on a computer and, before typing, she goes through the form with the pastor, one line at a time, asking the two questions: what will we do with this, and who will see it?
The form asks for name, address, phone, email, date of birth, marital status, names and ages of children, occupation, employer, previous church, date of baptism, and "any special needs". They sort the lines in about an hour.
Name, phone, email. Kept. Purpose: to reach the person; seen by the church office and the pastor.
Address. Kept, but marked "for visits and letters". Seen by the pastor and the visiting team.
Date of birth. Changed to "year of birth, optional". The only use anyone could name was to know which members are children and to send a greeting on a birthday, and a year and a day-and-month the person chooses to give can do that.
Marital status, children, occupation, employer. Removed from the form. Nobody could name what they were for. The pastor says, with some surprise, that he has never once opened that part of the register. Members who want to share their family situation will say so.
Previous church. Removed. In this community, several members had left another faith to join, and one of them had once asked quietly that it not be recorded.
Date of baptism. Kept, but moved to the baptism register, which has its own rules and its own keeper.
"Any special needs." Rewritten as: "Is there anything we should know so that you can take part fully (for example, access, hearing, or language)? You do not have to answer." Purpose stated, optional, and the answer goes only to the person who arranges the building and services.
When they finish, the form is a third of its former length and carries a short statement of purpose at the top. Naomi notes that the sorting was uncomfortable only for a moment: it turned out that no part of the church's care had depended on the lines they removed. If something later does require a removed line, the church can ask the person for it then, and say why.
10. Where this lecture stops
This lecture teaches a habit of asking. It does not decide what is required where you live, and it does not teach you to design every kind of form. It does not settle how a person's agreement is obtained, which is the subject of Lecture 2-2. It does not say how to keep what you do collect, which is the subject of Lecture 2-3. It also does not tell you what to do with the old forms already in your drawer. Lecture 2-4 deals with letting go, and this lecture says only that the habit of asking why can be applied to old forms too, one at a time and without hurry.
If you are already holding more than you need, you have nothing to be ashamed of. Almost every church does. The habit starts from here.
Diagram 1. The two questions at every field
Diagram 2. Fields that deserve a second thought
| Field | Why it is risky | A smaller way to ask |
|---|---|---|
| Date of birth | Often used to confirm identity | Year only, or "child or adult" |
| Home address | Tells a stranger where someone sleeps | Ask only where a visit or letter is planned |
| Health | Exposure can shame or harm | Only for camps and trips, held only for the event |
| Family status | Touches private griefs | Optional open question, no tick boxes |
| Immigration status | May endanger in some places | Almost never ask; take local advice first |
| Previous church | May reveal a conversion or a quarrel | Leave out unless truly needed |
| Past offences | Hard to take back once seen | Only in a screening process with a small named circle |
핵심 요약
- 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. |
스스로 확인해 보세요
읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.
묵상 및 토론
- Think of the longest form your community uses. Which line could you remove tomorrow without any harm? What makes it hard to remove?
- The "we might need it someday" reasoning sounds careful. In what way is it careless, and in what way is it a real kindness?
- Philippians 2:4 asks us to look to the things of others. Read one of your own forms as the person filling it in. What would you feel on meeting each line?
- A pastor says, "I know my people; I do not need a form to tell me." Another says, "If it is not written down, it is not there." What would each have to give up to agree on a test for what is written?
- Which risky field in this lecture would be hardest for your community to give up, and what would you say to someone who asks why you hold it?
- Where you serve, which of your forms are asked for because a rule requires it, and which because they have always been asked for? How could you find out?