무료

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

FS102E Ministry Ethics and Boundaries: Power, Money, Relationships, Accountability

Lecture 5-3: Codes of Conduct and Personal Covenants

목차 31
FS102E Ministry Ethics and Boundaries: Power, Money, Relationships, Accountability
제 0 장 · Introduction: Power Given to Build Up
  1. Lecture 0: Introduction: Power Given to Build Up
제 1 장 · Week 1: Power and Spiritual Authority
  1. Lecture 1-1: What Authority Is For
  2. Lecture 1-2: How Authority Is Misused
  3. Lecture 1-3: Unequal Power and Why Consent Is Not Enough
  4. Lecture 1-4: Authority and Accountability in Different Traditions
  5. Lecture 1-5: Practice Lab, My Map of Power
제 2 장 · Week 2: Money and Gifts
  1. Lecture 2-1: Scripture and the Minister's Money
  2. Lecture 2-2: Pay, Gifts and Conflicts of Interest
  3. Lecture 2-3: Openness and Shared Control
  4. Lecture 2-4: Honest Reports and Honest Appeals
  5. Lecture 2-5: Practice Lab: A Checklist for My Money
제 3 장 · Week 3: Relationships and Sexual Boundaries
  1. Lecture 3-1: Dual Relationships
  2. Lecture 3-2: Sexual and Romantic Boundaries
  3. Lecture 3-3: Meeting, Messaging and Online
  4. Lecture 3-4: Family, Favourites and Friends in Ministry
  5. Lecture 3-5: Practice Lab: My Boundary Statement
제 4 장 · Week 4: Confidence, Information and Honesty
  1. Lecture 4-1: What Is Told to You, and Where Silence Ends
  2. Lecture 4-2: Records, Data and Gossip
  3. Lecture 4-3: Honesty About Yourself and Your Work
  4. Lecture 4-4: When Silence Becomes Concealment
  5. Lecture 4-5: Practice Lab, An Honesty Check
제 5 장 · Week 5: Structures of Accountability
  1. Lecture 5-1: Not Standing Alone
  2. Lecture 5-2: Shared Oversight
  3. Lecture 5-3: Codes of Conduct and Personal Covenants
  4. Lecture 5-4: Tired, Lonely and Hurt: When Ethics Gives Way
  5. Lecture 5-5: Practice Lab: My Web of Accountability
제 6 장 · Week 6: When Wrong Comes to Light
  1. Lecture 6-1: Mistake, Violation, Abuse
  2. Lecture 6-2: Taking Responsibility
  3. Lecture 6-3: The Harmed Person First
  4. Lecture 6-4: Forgiveness, Restoration and Return
  5. Lecture 6-5: Practice Lab, A Plan for the Day It Comes

핵심만 먼저 보기 ↓

25분

Many ministers belong to a body that has a written code: a statement of how its ministers must behave. It may be called a code of conduct, a code of ethics, standards of ministry, a rule of life, a set of regulations or a discipline. Some ministers have signed one without reading it closely. Some have never been given one. Some serve where nobody has written anything.

A written code is a structure, and this course has said that structures are what keep ethics in place when resolve is weak. But a code is also easy to misuse. It can be read as a list of what one may do, until the point of it is lost. It can be written to protect an organisation's name more than the people it serves. It can be treated as a substitute for character. This lecture teaches two skills: how to read a code, and how to write a short covenant of your own. Both turn on one test, which is the central claim of the course in small: does this promise limit my power for the sake of people who trusted me, and can someone hold me to it?

This lecture names no real code. It gives the questions to ask of any.

이 25분으로 얻는 것

  • Say what a code of conduct can do and what it cannot do.
  • Read a code with eight questions, noting what it promises and what it leaves open.
  • Explain why a code is neither the same as character nor a substitute for it, and why local law stands above any code.
  • State fairly why some communities favour written codes and some distrust them, and what this course requires of both.
  • Write a short personal covenant that is specific, checkable and shared with someone who can ask about it.

Yahweh, who shall dwell in your sanctuary? Who shall live on your holy hill? He who walks blamelessly does what is right, and speaks truth in his heart; He who doesn’t slander with his tongue, nor does evil to his friend, nor casts slurs against his fellow man; In whose eyes a vile man is despised, but who honors those who fear Yahweh; he who keeps an oath even when it hurts, and doesn’t change; he who doesn’t lend out his money for usury, nor take a bribe against the innocent. He who does these things shall never be shaken." — Psalm 15:1-5

World English Bible

He has shown you, O man, what is good. What does Yahweh require of you, but to act justly, to love mercy, and to walk humbly with your God?" — Micah 6:8

WEB

When you vow a vow to God, don’t defer to pay it; for he has no pleasure in fools. Pay that which you vow. It is better that you should not vow, than that you should vow and not pay." — Ecclesiastes 5:4-5

WEB

Psalm 15 asks who may live in God's presence and answers with conduct: truthful speech, no slander, keeping an oath "even when it hurts", no bribe taken. Micah says in one verse what the Lord requires. Ecclesiastes warns against making a promise and not keeping it. Together they say that a promise matters, and that what matters most in it is whether it is kept.

1. What a code is

A code of conduct is a set of written promises. Behind it stands a body: a denomination, a diocese, an association of churches, a religious order, a mission, a school or a charity. The body says: those who serve under our name will behave in these ways, and here is what happens if they do not.

Codes differ in length and in kind. Some are one page. Some are long and detailed. Some are mostly lists of forbidden acts. Some are mostly statements of purpose. In many religious orders, the "rule" is not first a list of prohibitions but a pattern of life and vows, kept in a community, under a superior. In some communities there is no written code, and the elders' shared understanding does the work. This lecture speaks of written codes because they can be read, checked and compared, but what is said applies to any set of promises a community holds its ministers to.

A code can do five useful things.

  • It gives a shared language. Ministers and members can point to a sentence and say "this is what we agreed".
  • It sets a standard before trouble comes. A promise made when nobody is tempted is easier to keep than a rule invented in the middle of a crisis.
  • It protects the faithful. A minister who is pressed to do something doubtful can say, "Our rules do not allow me to," and the pressure falls on the rule, not on the person.
  • It gives a route. A good code says where a concern goes and what follows, so that a person who has been harmed does not have to guess.
  • It supports training. New ministers can be shown, with cases, what is expected.

(An invented example.) A rule used as relief. A young minister is asked by a member's teenage son to be driven home alone after a late meeting. The minister's association has a written rule that adults do not drive young people alone. He says, "My association has a rule for this, so I will call your father and we will find another way." The rule did not insult the boy and cost the minister nothing. He did not have to decide in the moment whether he was being too careful. A rule did the deciding, for the benefit of everyone.

2. How to read a code: eight questions

A code that is not read carefully gives a false sense of security. These eight questions work for any.

  1. Who wrote it, and who is it for? A code written by an association for its ministers is different from one written by an employer for its staff, or one that a congregation wrote for itself. Whom does it bind: ordained ministers, paid staff, volunteers, children's workers?
  2. What does it say it protects? Read the opening. Does it speak of the people the ministers serve, of the body's name, or of both? A code that speaks mostly of reputation is a warning sign. This is not a reason to throw it away; it is a reason to read what it requires with care.
  3. What does it require and what does it forbid, and how specific is it? "Ministers shall behave with integrity" can mean anything. "Ministers shall not borrow money from those they counsel" can be kept or broken. The more a promise can be checked, the more it protects.
  4. Where do concerns go? Is there a named person or office, with a way to reach it that does not pass through the minister or the minister's friends? Can a person who is not a member of the body use it? Can a child or a parent?
  5. What follows? Does the code describe a process, who decides, how long it takes, what the outcomes can be, and whether the person who raised the concern is told what happens? A code with rules but no process is a code with no teeth.
  6. What does it say about the person harmed? Does it speak of care, safety and support for the person who was harmed, as well as of the minister's rights? A code that is silent on this one point has forgotten the reason it exists.
  7. What does it say about law? A good code says that it does not replace the law of the country, and that duties to report certain matters to public authorities come from local law and must be kept. Where a code and local law differ, follow local law and ask a qualified person. Reporting duties, and what they cover, are different in different countries and regions.
  8. What does it leave open? Every code is silent about something. Common silences are online messages, the handling of gifts and loans, relationships between ministers, the conduct of ministers outside work, and what happens when a minister leaves the body. Name the silences, and decide how you will act in them.

The last point needs a word. A code binds only those who are inside the body it belongs to. A minister who resigns from the body, or moves to another, leaves the code behind. Some codes say that the body will tell other bodies about serious findings; some do not; and local law differs. This is a limit of what a code can do, and a reason why personal commitment and shared structures among communities matter as well.

If a code is not in a language you read well, ask for a copy that you can. A promise you cannot read is not one you can keep or hold others to.

3. What a code cannot do

A code is not the same as character. A person who keeps the rules because of fear of being caught is a different sort of person from one who keeps them because he or she does not want to harm anyone. The two behave alike while the rule is enforced and differently when it is not. Micah's three requirements are "to act justly, to love mercy, and to walk humbly with your God." None of the three can be fully written as a rule.

A code is not a substitute for judgement. No code covers every case. A minister who thinks "it is not forbidden, so it is fine" has turned a floor into a ceiling. A good question after reading any rule is: what was this rule trying to protect, and does my plan protect it?

A code is not a shield. "I broke no rule" is a sentence heard after many a failure. It may be true. It does not answer the question of whether someone was harmed. A rule that was kept to the letter and defeated in its purpose has not been kept.

(An invented example.) Within the letter. A minister's association forbids ministers from lending money to members they counsel. A minister arranges, instead, for a member's small business to be paid in advance for work the church does not need, so that the member has cash. He tells himself that no loan was made. The member, who had been grateful, now feels bound to support the minister in a dispute with the board. The code was not broken. The purpose of the rule, to keep the minister's power from being bought with money or bought by it, was broken entirely. A better path: ask, before acting, "What was the rule trying to prevent?" and, "Would I be willing to tell my overseer exactly what I am doing?"

A code does not stand above the law. Where local law requires something of a minister (for example, to report certain things to public authorities) or forbids something, the minister follows the law. Where it is unclear, the minister asks a qualified person and, if need be, the body that has the code.

4. Written codes: a point on which readers differ

This is a point where readers will not agree: whether ministers should be bound by written codes at all.

Some hold that written codes are necessary. Their reason is practical and serious: good intentions are not enough, memory fails, and a promise nobody has written down is easy to forget or reinterpret. People who have been harmed have often found that nothing was written to which they could point. A written code gives them something to hold, and gives ministers something to be held to.

Others distrust codes. They fear a faith that becomes a list of rules, a religion of compliance, or a replacement of Scripture and the Spirit with a committee's paper. Some of them also point out that codes have been used to silence people, to protect institutions, or to punish those who ask awkward questions. In some communities a signed document is felt as foreign and as a sign that trust has gone.

Both are describing real things. This course requires less than either side: some promise, in words, made to people who can ask about it. It need not be called a code, it need not be long, and it need not come from outside. It must be specific enough to be checked, and shown to someone with the standing to question it. A community that says "our elders hold each other to what Scripture says" is welcome to do so, if the elders can say what they hold each other to, and the members can find out.

5. A personal covenant

Whether or not a body has a code, a minister can write a personal : a short written statement of what he or she will and will not do with the power of the office. It does not replace a code. It fills the silences, and it is the minister's own.

A good covenant has these marks.

It is short. A page at most. Six to ten sentences. A long list is not kept.

It is specific enough to be checked. "I will be careful with money" cannot be tested. "I will not hold church money alone, and two people will count every offering" can.

It is written in the first person and the present tense. "I do not..." and "I will..." are plainer than "I should try to..."

It covers the areas of this course. Power (what I will not do with my authority), money, closeness (how I meet and message), information (what I will not repeat), truth, rest, and accountability (who sees this).

It is shown to someone who can ask about it. A covenant kept in a drawer is a wish. Give a copy to a companion, an overseer or an outside adviser (lectures 5-1 and 5-2), and agree when they will ask whether it is being kept. In some places it is also shared with the congregation.

It is reviewed once a year, and changed only in the open. Do not change a covenant in the moment of temptation, and do not alter it without telling the person who holds a copy. It may need to grow, but a loosening made in secret is the thing it exists to prevent.

It says what happens if I break it. "If I break any of these, I will tell my overseer within a week." This line is the one that makes the others real, because it decides in advance that wrongdoing will be spoken of and not hidden.

Here is an invented covenant, to show the form. It belongs to no one and should be rewritten by whoever uses it.

(An invented example.) A one-page covenant.

  • I will not use my office to ask for favours, gifts or loans from those I serve.
  • Two people will count and record every offering, and I will not hold church money alone.
  • I will not decide my own pay, housing or allowances.
  • I will not be alone behind a closed door with a child or a young person, and I will tell their parents where I am meeting them.
  • I will not send private messages at night to those I counsel, except in an emergency, and then I will tell my overseer the next day.
  • What I hear in private I will not use in a sermon or repeat, except where someone's safety requires me to speak, and then I will speak to the right person.
  • I will take one day of rest each week and two weeks of rest in the year.
  • I give a copy of this to my overseer and my companion, and we will read it together each January.
  • If I break any of these, I will tell my overseer within a week.

Some of these lines will not fit every community. In some places two adults counting money is not possible, or a closed door is not a thing. The point is not the lines but that each is something a person could check.

The covenant is not a performance. Do not write it in order to seem trustworthy, or put into it a promise that you do not mean to be asked about. Ecclesiastes says it is better not to vow than to vow and not pay. A short covenant that is kept is better than a long one that is admired.


Diagram 1. Eight questions for reading a code

Reading a Code of Conduct Eight questions to ask of any written promise 1. Who wrote it, and whom does it bind? 2. Does it protect people, or a name? 3. How specific is it? Can it be checked? 4. Where do concerns go, apart from the minister and his or her friends? 5. What follows: who decides, how long? 6. What does it say of the harmed person? 7. Does it say that local law stands above it, and that reporting duties are kept? 8. What does it leave open? online messages - gifts and loans ministers' conduct outside work what happens when a minister leaves A code binds only those inside the body. What a code cannot do It is not character. It is not a substitute for judgement. It is not a shield: "I broke no rule." It does not stand above local law. A personal covenant Short - checkable - first person Covers power, money, closeness, truth Shown to someone who can ask Says what I do if I break it

Diagram 2. Code and covenant compared

A body's code A personal covenant
Who writes it The body The minister
Strength Shared, with a process behind it Fills the silences; the minister's own
Weakness Silent in places; binds only those inside Only as strong as the person who holds a copy
Needs To be read with the eight questions To be shown to someone who can ask

핵심 요약

  • A code gives a shared language, a standard set before trouble, protection for the faithful, a route for concerns, and a basis for training.
  • Read any code with eight questions, including what it says it protects, where concerns go, what it says of the person harmed, and what it leaves open.
  • A code binds only those inside the body, does not stand above local law, and is not a substitute for character or judgement.
  • "I broke no rule" does not answer whether someone was harmed; ask what the rule was trying to protect.
  • A personal covenant is short, checkable, first person, shown to someone who can ask, reviewed yearly, and says what the minister will do if it is broken.
  • Where readers differ about written codes, this course requires some promise, in words, made to people who can ask.
Front Back
Three things a code is not Character, a substitute for judgement, a shield against the question of harm.
Two silences to look for in a code Any of: online messages, gifts and loans, ministers' conduct outside work, what happens when a minister leaves the body.
What a good covenant is Short, checkable, first person, shown to someone who can ask, reviewed yearly, with a line for what I do if I break it.
What the course requires where readers differ about codes Some promise, in words, made to people who can ask about it.

One sentence to remember A promise protects people only when it is specific enough to be checked and shown to someone who can ask.

This week's action Write a covenant of six to nine lines, including the last line about what you will do if you break it, and give a copy to one person who can ask.

이 과목 요약 전체 보기 →

스스로 확인해 보세요

읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.

묵상 및 토론

  • If you belong to a body with a written code, which of the eight questions can you answer from the text, and which can you not? If you belong to none, which promises does your community hold ministers to, and who knows them?
  • Think of an invented case in which a rule is kept to the letter and its purpose is lost. What was the rule trying to protect?
  • State fairly the strongest case for written codes, and the strongest case against them. What does the course require of both?
  • Which area of your work is least covered by any written promise you know? What line would you write for it?
  • Who could hold your covenant, and how often would you want them to ask whether it is being kept?

로그인하시면 여기에 답을 적고 보관하실 수 있습니다

다음 단계

여기까지가 강의입니다. 아래는 읽은 사람들이 남긴 글입니다.