Lecture 5-1: When Something Goes Wrong: The First Hours
목차 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
Sooner or later, something will go wrong with the information a church holds. An email goes out to the whole list with a private attachment. A phone with the children's contact details is left on a bus. A folder of visiting notes is taken from a car. A link to a shared document, meant for three people, turns out to be open to anyone who has the address. A treasurer receives a message that looks like it comes from the pastor, asks for a change of payment details, and acts on it. None of this requires a bad person. Almost all of it comes from tiredness, haste, kindness and ordinary mistakes.
The first four chapters of this course were about keeping things from going wrong: knowing what you hold, collecting less, keeping it with care, and using good habits with accounts, messages and tools. This week begins from the other side. The care has failed, or may have failed. What now?
The course returns to one claim in every chapter, and this week it takes a particular form:
A failure is a chance to be honest; a handover is a chance to be careful; in both, the person whose information it is comes first.
This lecture is about the first hours after you notice. It is not about blame, and it is not a lesson for people who never make mistakes, because there are none. It gives an order to follow when your head is full of alarm and you cannot think what comes first. It is not legal advice. What you must report, to whom and by when depends on where you serve and what role you hold, and the lecture says so once more near the end.
이 30분으로 얻는 것
- Recognise the common kinds of incident in a church, and say what they have in common.
- Put the first steps of a response in a sensible order, and explain why each step is where it is.
- Name the actions that make an incident worse: hiding it, deleting evidence, trying to solve it alone, and blaming the volunteer.
- Draft a short "who is called, in what order" plan for your own community, in categories rather than names.
- Explain why the question "what must we tell others?" is asked early but answered with local advice.
But there is nothing covered up, that will not be revealed, nor hidden, that will not be known. Therefore whatever you have said in the darkness will be heard in the light. What you have spoken in the ear in the inner rooms will be proclaimed on the housetops." — Luke 12:2-3
World English Bible
He who conceals his sins doesn’t prosper, but whoever confesses and renounces them finds mercy." — Proverbs 28:13
WEB
Therefore putting away falsehood, speak truth each one with his neighbor. For we are members of one another." — Ephesians 4:25
WEB
In its setting, Luke 12:2-3 warns against hypocrisy, so we use it here by analogy and not as a rule about data. What it still teaches is practical: a thing hidden tends to come out, and it usually comes out worse when it comes out late. Proverbs 28:13 sets concealment beside confession and says which one finds mercy. Ephesians 4:25 gives the reason that matters most for a church: we are members of one another, so the person whose address was shown to a list is not a customer to be managed but a member of the same body.
1. A way of looking: not a courtroom
Begin with the person who has made the mistake, because the person is often the first obstacle to a good response. Someone who has just seen a wrong attachment go out feels sick. The urge is to hope nobody notices, to fix it quietly, and to say nothing. That urge is human and it is the most dangerous thing in the first hour, because time is what the harm feeds on.
So the first thing a church needs is a culture in which saying "I think I have made a mistake" costs little. A leader who reacts to a reported slip with anger will teach every volunteer to stay quiet next time. A leader who thanks the volunteer for the quick report, and then gets to work, will hear about the next slip within minutes. Chapter 6 comes back to this as a matter of culture. For now, hold on to a plain fact: the speed of the report decides much of what can still be saved, and the speed of the report depends on how the last report was received.
This lecture does not ask you to be a technician. It asks you to be calm, honest and orderly. A with a printed page of steps and a phone is better prepared than a church with an expensive tool and no plan.
2. What counts as an incident
An incident here means any event in which information about people may have reached someone who should not have it, or may have been lost, altered or made unavailable. Some common kinds:
- A wrongly addressed message. An email or a message goes to the wrong person, or to a whole list with every address visible, or with a private attachment.
- A lost or stolen device or folder. A phone, laptop, memory stick or paper register is left behind, taken or damaged.
- The wrong person has access. A former volunteer can still open the shared drive. A new helper was given the whole folder when she needed one page.
- A link left open. A shared document or photo album was set so that anyone with the address can open it, and the address has travelled further than intended.
- A message to everyone by mistake. A private note meant for the pastor was posted to the whole congregation's group. A message that was meant to be general named a family.
- A deceived person. The treasurer, the office worker or a volunteer was tricked by a message that looked genuine into handing over money, a code or access.
- Loss without theft. A device fails, a service closes, and the register for the last ten years is simply gone.
These look different, but they share three features. Something about people has moved to where it should not be, or has been lost. Some of those people may be hurt, and you do not yet know how many or how badly. And there is a short period in which the response matters most.
Notice what is not on this list: only the dramatic cases. A wrongly addressed email that reaches one trusted member is an incident too, though a small one. The habit of treating small incidents seriously and quickly is what prepares a church for the big one.
3. The first hours: an order
Here is an order that fits most incidents. It is a general pattern, not a legal procedure. Some steps may be done in minutes, others need a day. Where more than one step can be done at once, ask someone to help.
Notice, and say so at once. The first step is to admit to yourself that this may be an incident. The second is to tell someone, quickly. You do not need to know how bad it is, or whose fault it is. A sentence is enough: "I think the wrong file went out in the newsletter this morning." Say it to the person responsible for the church's information, or if that is unclear, to the leader you would ordinarily report to.
Stop the spread. Ask: can anything still be done to keep this from going further? Some examples, in general terms. If a document has a link anyone can open, change it so that it is closed. If a message was sent to a group, ask the group, plainly and without long explanation, not to forward it and to delete it. If a former helper still has access, remove it today. If a device is lost, tell the person responsible so that its accounts can be locked and passwords changed, and use any remote-locking feature the device offers. Stopping the spread rarely undoes the harm already done, but it limits the number of people who can be hurt.
A caution here: stopping the spread is not the same as erasing the evidence. See the section below on what not to do.
Keep a record of what you know. Take a plain sheet of paper, or a plain note, and write down, in order, with the time: what happened, when you noticed, who noticed, what was affected, what you have done so far. Write what you know and mark separately what you suspect. Do not write guesses as if they were facts, and do not write opinions about whose fault it was. This record helps in three ways: it keeps your memory straight when you are tired, it lets a helper join without asking you everything again, and it allows a later review to learn from what happened.
Tell the responsible person. If you have not already done so, make sure that the person who carries responsibility for the church's information, and the leader above them, know. In a small church this may be the same person, and it may be you. In that case, tell a second person you trust, such as another , a bishop's office, a regional leader or a colleague in another church, so that you are not carrying this alone and someone else can check your thinking.
Find who and what is affected. Work out, as carefully as you can, whose information was involved and what kind it was. This matters because the layers from Chapter 1 now decide how urgent things are. A wrong attachment containing a hymn list is not the same as a wrong attachment containing the names of people in counselling. If the information was in the specially sensitive layer, or if the people involved are children, vulnerable adults or people at risk (see lectures 3-3 and 3-4), treat the matter as urgent and bring in help at once. Write down the list of people, but keep that list as small and as closely held as the information it describes.
Get qualified help. Some incidents a church can handle on its own. Others need someone with skills the church lacks: a person who can check whether an account has really been taken over, a person who can advise on a loss of money, a lawyer experienced with charities or religious bodies, a denominational office, or an adviser on information security. Do not wait until you are sure you need them. The question to ask is not "can we manage?" but "what would it cost us if we were wrong?"
Check what you must tell others. Many places have rules about telling the people affected, or an authority, when information is lost or exposed, and about who must do so and by when. Other places have no such rule, and a church there still has a duty of honesty to its people. These rules differ from place to place and from role to role, and some apply to some organisations and not to others. Learn the rule where you serve, ask a lawyer or the competent authority, and follow your community's written rules. The point for the first hours is only this: put the question on the list early, because if there is a deadline, you do not want to discover it late. The next lecture is about how to speak to the people who were hurt, whether or not a rule requires it.
4. What not to do
Four reactions turn a manageable incident into a worse one.
Hiding. It is tempting to hope that a wrongly addressed message will go unremarked. But the person who received it knows. The members who were visible on a list know. People talk. When the matter comes out later, the harm of the original slip is joined by the harm of the silence, and trust is damaged twice. Proverbs 28:13 is blunt about this, and Luke 12:2-3 says the same in a different register. Hiding also deprives the people affected of the chance to protect themselves, and that is the worst of it.
Deleting evidence. Deleting the wrong message from your own outbox, wiping a device, tidying the shared folder or throwing away a notebook can feel like repair. It is not. You may need to see exactly what was sent, to whom and when, in order to know who was affected and what to tell them. Stop the spread, yes; but before you delete, write down what is there, and ask the responsible person or an adviser before you remove anything you may need.
Trying to solve it alone. A volunteer who made a mistake often tries to fix it before telling anyone, so that nobody will know. A leader who is the only person with the skills often tries to carry the whole matter privately. Both are understandable. Both lose the benefit of a second mind, and both delay the people who ought to be told. An incident is not the moment for pride, and not the moment for heroism either.
Blaming the volunteer. A volunteer who attached the wrong file did one thing wrong. The church that set up a system in which one wrong click could expose a private list did something wrong too, and often did it long before. If the response begins with finding someone to blame, three things follow: the person hides future slips, the other volunteers learn to stay silent, and the real weakness (an unlocked list, an open link, a shared account) goes unfixed. This is not to say that no one is ever responsible. Chapter 6 speaks of what to do when a volunteer breaks trust deliberately. The point here is that the first hours are not the time to sort out responsibility, and that a mistake and a betrayal are different things.
5. A plan made before the day
A short plan, made in a quiet week, is worth more than a clever plan made during the incident. It does not need to be long. A single page can say:
- who a volunteer tells first, and who after that, with a phone number for each on paper as well as in a phone;
- who decides whether outside help is needed, and who is called;
- who may speak to the people affected, and who may speak to the congregation (see the next lecture);
- who records what happened, and where that record is kept;
- who is the second person if the first is the person who made the mistake, or is away, or is the one involved;
- where the page itself is kept so that it can be found when a computer is not working.
The page should name roles first and people second, because people change. It should be known to every volunteer who handles information, and it should be read aloud once a year. In a house church, the plan may be three lines and a phone number for a trusted leader elsewhere. In a large church, it may be longer. What matters is that the order of calls is decided when nobody is frightened.
6. Two invented cases
(An invented case.) Marta volunteers in the parish office on Mondays. She sends the weekly newsletter to the parish list. This week, she attached the draft of the pastoral-care list, which includes the names of people in hospital and a short note beside some of them, instead of the notices page. The newsletter went to about the whole parish. Twenty minutes later, she saw the attachment's name in her sent folder and felt her stomach drop.
What does a good response look like? Marta does not delete the sent message. She does not wait to see whether anyone replies. She phones the parish administrator, whose number is on the one-page plan, and says, "I attached the wrong file to the newsletter. It has the pastoral-care list. I have not told anyone else." The administrator tells the priest, and between them they write a short message asking recipients to delete the attachment unopened and not to forward it. Marta writes down the time of sending, the attachment's name and what the list contained, marking separately what she knows and what she does not. The priest asks the administrator to work out which people on the list were named with notes, and whether any of them are in the specially sensitive layer. They decide to visit or phone each person named, before anything is said to the parish. The administrator asks the diocesan office whether any rule about informing people applies, and writes down the reply. Nobody blames Marta. On Wednesday the team looks at why the attachment was so easy to confuse, and changes the folder where attachments are kept.
(An invented case.) Samuel, the treasurer of a small assembly, received a message that seemed to be from the elder, written in the elder's usual tone, saying that the supplier had changed bank and asking him to pay the next invoice to a new account that day, because the elder was travelling. Samuel paid. A day later, the supplier asked why the invoice had not been paid. Samuel realised that the message had not come from the elder.
Samuel sat for an hour before he told anyone, because he was ashamed. In the first hour, the damage was already done, and the shame was now adding to it. What helps here? The church's earlier habit: a plan that says anyone who finds they have been deceived tells the second elder at once, and nobody is thought a fool for it. Samuel tells the second elder. They ask the bank at once whether the payment can be stopped, which sometimes works if asked early. They write down the message, the time and the account details, and they do not delete anything. They check whether the elder's email account was itself taken over, because that would change what else could be exposed, including the members' list in the same account. They ask someone qualified to look at it, and they put the question about telling others on the list. And they ask, as a lesson and not a punishment, what habit would have caught this: a rule that a change of payment details is always confirmed by phone, by a number already known, and never by the message that announced the change. That is the habit of confirming by another route that Chapter 4 taught, and Samuel's case shows its value.
Neither of these cases ends in disaster, and neither ends with perfect repair. The aim of a first-hour response is not to make everything as though it had never happened. It is to reduce the harm, to find out who needs to be told, and to behave honestly.
7. What this lecture cannot tell you
This lecture does not say what the rules in your place require. It does not say whether you must tell an authority, whether you must tell the people affected, what the deadline is or what penalty may follow. It cannot, because the answer differs from one country, one denomination and one role to another. It does say that these questions exist, that someone should ask them early, and that a church should write down what it asked and what it was told. Doing so protects the church and also the people whose information it was.
It also does not say that every incident needs a lawyer. Many are small, and common sense and kindness settle them. The test is this: if the information was sensitive, if children or people at risk are involved, if money is lost, or if you are unsure, bring someone qualified in early.
And where the incident touches a danger to a person (for example, an address exposed to someone from whom a person is hiding, or a message that suggests someone may harm themselves or another), safety comes before everything else in this lecture. Involve a responsible leader, a trained professional and your local emergency number without delay. Nothing in the list above should slow that down.
Diagram 1. The first hours, in order
Diagram 2. Who is called, in what order: a one-page plan
| Question the page answers | Written as a role, then a name |
|---|---|
| Who does a volunteer tell first? | The person responsible for information |
| Who is next if that person is away or involved? | A second trusted leader |
| Who decides about outside help? | A named leader, with a phone number on paper |
| Who may speak to the people affected? | One person, not many |
| Who may speak to the congregation? | The leader, after the people affected have been told |
| Who keeps the record of what happened? | One person, in a closed place |
핵심 요약
- 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. |
스스로 확인해 보세요
읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.
묵상 및 토론
- Think of the last time someone in a community you know made a small mistake with information. How was it received? What did that teach the next person?
- Why might deleting a wrongly sent message from your own outbox be a mistake, even though it feels like repair?
- In the invented case of Samuel, he waited an hour because he was ashamed. What could a church do, before any incident, so that the hour is shorter?
- In your community, who would a volunteer tell first? Who would be second if the first were away or involved? If you cannot answer, what does that tell you?
- Why does the lecture ask you to put "what must we tell others?" on the list early, and also say that you cannot answer it from this course? What is the sensible way through?
- Luke 12:2-3 is about hypocrisy, and the lecture used it by analogy. What are the strengths and the limits of using a verse that way?