flowchart TD
A["<b>Code of conduct</b>"] --> B["<b>Content</b><br>the situations people<br>actually face"]
A --> C["<b>Tone</b><br>compliance rules,<br>values, or both"]
A --> D["<b>Access</b><br>found when needed,<br>not filed at induction"]
B --> E["<b>Supporting system</b>"]
C --> E
D --> E
E --> F["Training on real cases"]
E --> G["A route to ask<br>before acting"]
E --> H["A route to report,<br>per Chapter 41"]
E --> I["Consistent consequence"]
I --> J["<b>Belief</b><br>what people conclude<br>the standard actually is"]
F --> J
G --> J
H --> J
style A fill:#ede7f6,stroke:#7E57C2
style J fill:#e8f5e9,stroke:#388E3C
39 Designing a Code of Conduct
ImportantLearning Objectives
You will be able to:
- Explain what a code of conduct is for and what it cannot do.
- Distinguish a compliance-based code from a values-based code and explain when each is appropriate.
- Describe the content a workable code requires and the drafting choices that determine whether it is used.
- Identify the statutory codes an Indian company must maintain and how they relate to a general code.
- Evaluate an organisation’s code and supporting system and recommend the changes that would make it operative.
39.1 Introduction
Chapters 35 to 38 examined a failure. This chapter and the two that follow examine the machinery that prevents one, beginning with the document every organisation has and few use.
A code of conduct states the standards an organisation expects of the people who act for it, and the conduct it will not accept. Almost every company of size has one. In most, it is a document circulated at induction, acknowledged electronically, and never consulted again by anyone (Manuel G. Velasquez, 2018).
That failure is worth understanding rather than lamenting, because its causes are in the design. Codes fail when they are written for the wrong reader, when they answer questions nobody asks and are silent on the ones people actually face, when they conflict with what the organisation rewards, and when nothing follows from breaching them. Chapter 18 made the point in general terms: an organisation teaches character through what it rewards, and a code that contradicts the reward system loses.
39.2 What a Code Is For
A code serves four purposes, and confusing them produces a document that serves none.
NoteThe Four Purposes
| Purpose | What it means | Consequence for drafting |
|---|---|---|
| Guidance | Helping a person decide what to do in a situation they face | Content must address real situations, in the language of the people who face them |
| Commitment | Stating publicly what the organisation stands for, to employees, customers, suppliers and regulators | Requires a document that can be shown outside without embarrassment |
| Authority | Providing the basis on which conduct can be required and breach acted upon | Requires clarity about what is mandatory, and integration with employment terms |
| Signal | Telling everyone inside what actually matters here | Requires consistency with what the organisation rewards, or the signal is reversed |
A code also cannot do certain things, and expecting them of it produces disappointment and, worse, a false sense of protection. It cannot substitute for judgement, because no document anticipates every situation. It cannot make people honest, since it addresses those who want to know the standard rather than those who have decided to breach it. And it cannot override incentives: where a code says one thing and the bonus plan another, the bonus plan wins, which is why Chapters 23 and 26 belong to this subject.
39.3 Two Approaches
| Compliance-based | Values-based | |
|---|---|---|
| Organising idea | These are the rules; follow them | These are our standards; apply them |
| Content | Prohibitions, thresholds, procedures, mandatory approvals | Principles, expectations, illustrative situations, questions to ask |
| Strength | Clear, enforceable, defensible, and effective for bright-line matters such as bribery, insider dealing and safety | Extends to situations not anticipated, engages judgement, and travels better across cultures and functions |
| Weakness | Cannot anticipate everything, invites the search for what is not prohibited, and teaches that unlisted conduct is permitted | Can be too abstract to guide anyone, and difficult to enforce against |
| Best used for | Legal obligations and matters where any deviation is unacceptable | The large space of ordinary decisions where the right answer depends on circumstances |
Most workable codes combine the two, and the combination should be deliberate rather than accidental. Bright-line rules are stated as rules, without qualification: no facilitation payments, no dealing during a closed window, no acceptance of a gift from a party under evaluation. Everything else is stated as a standard with worked illustrations and a route to ask.
WarningCommon Misconception: A Longer Code Covers More
Length is inversely related to use. A forty-page code is not read, and a code that is not read provides no guidance, however comprehensive.
Three specific harms follow from length. It buries the bright lines, so the three rules that must never be broken sit among two hundred paragraphs of equal typographical weight. It invites the boundary search, because a detailed rule set teaches readers to look for what is not covered, which is exactly the disposition a code should discourage. And it cannot be maintained, so within three years parts of it are inconsistent with current policy and everyone who notices learns that the document is not authoritative.
The alternative is a short code carrying the standards, the bright lines and the routes, supported by separate detailed policies that specialists consult. The code is what everyone reads; the policies are what particular people need. Merging the two produces a document nobody uses for either purpose.
39.4 Content That Works
A code should be organised around the situations people actually encounter, in the order they encounter them, rather than around legal categories.
NoteThe Situations a Code Must Address
| Area | The questions people actually have |
|---|---|
| Gifts and hospitality | May I accept this, from whom, at what point in a relationship, and what do I do if refusing causes offence? |
| Conflicts of interest | My relative works for a supplier, I have been offered outside work, I am recruiting someone I know. What must I declare and to whom? |
| Payments and intermediaries | An agent says a payment will speed up a clearance. What do I do, and what do I do if the shipment is stuck? |
| Confidential information | What may I take when I leave, what may I share with a customer, what may I discuss at home? |
| Insider dealing | May I buy shares, when, and does this apply to my family? |
| Accuracy of records | I have been asked to date an invoice differently, or to record a test I did not run |
| Safety and product integrity | I have found something that may be a problem and I am not certain |
| Fair treatment | What is harassment, what is discrimination, and what happens if I report it? |
| Competitors | I meet them at an association. What may I discuss and what must I do if the conversation moves? |
| Use of company resources | Which personal use is acceptable, and what about data and systems? |
| Speaking publicly | May I post about my employer, and what if I am asked about a company matter? |
| Suppliers and their workers | What am I responsible for in the conduct of people who are not our employees? |
Two drafting choices determine whether this content is usable.
Write it as situations, not as prohibitions. A section headed conflicts of interest that defines the term is less useful than one that begins with three short examples and says what to do in each. People recognise situations; they do not classify them.
Answer the hard question, not the easy one. Every area above has an obvious case and a difficult one, and a code that addresses only the obvious case teaches its readers that it has nothing to say about their actual problem. The difficult cases are: refusing a gift when refusal is an insult, the payment demanded when a shipment is already stuck, the concern that is not certain, and the relative who is genuinely the best candidate.
TipPractitioner Insight: Build the Code From the Questions the Helpline Received
The most reliable method of writing a code that gets used is to stop writing and start collecting. Gather every question the compliance function, human resources, legal and the finance team received last year, plus every disciplinary matter and every issue raised through the reporting channel.
That list is the syllabus. It shows what people are actually uncertain about, in their own words, which is almost never what a code drafted from a template addresses. It also shows where the same question recurs, which identifies a policy that is unclear or a practice that is widespread.
Write the code to answer those questions. Then test it: give the draft to twenty people across functions and levels, present them with five real situations from the collected list, and ask them to find the answer. What matters is not whether they agree with the answer but whether they can locate it in under two minutes. A code that fails that test will fail in use, and no amount of communication afterwards repairs it.
39.5 The Statutory Codes
An Indian company maintains several codes required by law, and their relationship to a general code must be deliberate.
| Code | Required of | Content |
|---|---|---|
| Code for directors and senior management | Listed entities | Conduct standards, with annual affirmation of compliance and a declaration in the annual report (Securities and Exchange Board of India, 2015a) |
| Code for independent directors | Companies with independent directors | The professional conduct, roles and duties described in Chapter 25 (Government of India, 2013a) |
| Code of conduct on insider trading | Listed entities | The machinery described in Chapter 27, covering designated persons, windows and pre-clearance (Securities and Exchange Board of India, 2015b) |
| Policy on sexual harassment | Every workplace above the prescribed size | The internal committee, complaint procedure, timelines and protections under its own statute (Government of India, 2013b) |
| Vigil mechanism and whistle-blower policy | Prescribed and listed companies | The channel and protections described in Chapters 21 and 41 |
| Code of conduct for the board on related party transactions and interests | Companies generally | Disclosure of interest and abstention, per Chapter 12 |
These are distinct instruments with distinct legal effects, and folding them all into one document creates problems: the sexual harassment framework has statutory timelines and a defined committee that a general code cannot alter, and the insider trading code binds a defined population that is not everyone. The general code should reference each and state where it applies, rather than restating it.
39.6 Making a Code Operate
A code is one component. Four others determine whether it means anything.
Training on real cases. Not the code recited, but situations from the collected list, discussed in small groups by function, with a right answer that is defended rather than announced. Training that consists of reading slides and answering a quiz teaches only that the organisation regards the subject as an administrative task.
A route to ask before acting. Most people who are about to do something wrong would prefer not to and do not know who to ask, particularly when their own manager is the person creating the pressure. A named, reachable, low-consequence route to ask a question is worth more than any amount of prohibition, and its usage volume is a better measure of a programme’s health than the number of reports it receives.
A route to report. Chapter 41 takes this in full.
Consistent consequence. This is the component that determines what everyone believes the standard is. A code enforced against junior employees and not against a high performer has communicated the real rule with complete clarity, and every subsequent statement about values is heard against that evidence.
39.7 Case Studies
39.7.1 Case Study 1: The Code That Answered the Easy Question
The following situation is constructed rather than reported.
A company’s code contains a clear section on gifts, prohibiting acceptance of anything above a stated value and requiring registration above a nominal amount. A regional manager is offered, by a long-standing distributor at a family wedding, a gift well above the threshold, in front of the distributor’s relatives. Refusing publicly would cause visible offence and damage a twenty-year relationship. The code addresses acceptance and says nothing about refusal. He accepts and does not register it.
Discussion questions
- Identify what the code got right and what it omitted, and explain why the omission matters more than the rule.
- Draft the two additional sentences the code needed, addressing the difficult case rather than the easy one.
- What should the company do now about the manager, and what does each option teach the organisation?
39.7.2 Case Study 2: The Code and the Bonus Plan
The following situation is constructed rather than reported.
A company’s code states that accuracy of records is fundamental and that no employee may record a transaction other than in the period in which it occurred. Its sales incentive plan pays a stepped bonus on achievement of an annual target, with a large increment at one hundred per cent. In each of the past four years, revenue in the final week of March has been between three and four times the weekly average, and the first week of April correspondingly low. The pattern is visible in the management accounts. No disciplinary matter has ever arisen under the records provision.
Discussion questions
- Which document is the operative code in this company? Justify your answer from the evidence.
- Chapter 18 argued that organisations form character through what they reward. Apply that argument to these facts.
- Recommend what must change, and state whether changing the code would be part of it.
39.7.3 Case Study 3: Testing the Draft
The following situation is constructed rather than reported.
A company has redrafted its code. It runs to thirty-four pages, is well written, was reviewed by external counsel and approved by the board. Applying the two-minute test, twenty employees are given five real situations. On the gift question, twelve find an answer and eight of those find a different provision from the other four. On the question of what to do about an uncertain safety concern, three find anything at all. On the competitor conversation question, none finds a provision within two minutes; four say they would ask their manager, and two say the manager is the person who would be at the meeting.
Discussion questions
- Diagnose each of the three results. What does each reveal about the draft?
- The last result is the most serious. Explain why, connecting it to Chapters 21 and 41.
- Recommend what to do with this draft, and describe the version that would pass the test.
39.8 Applying the Chapter
ImportantExercise: Designing a Code for Suvarna Foods
Return to Suvarna Foods after the crisis of Chapters 35 to 38. The company had a code of conduct: twenty-six pages, acknowledged at induction, last revised six years ago, containing sections on integrity, gifts, conflicts, confidentiality and use of company property. It contained nothing about raising a safety concern, nothing about supplier conduct, and nothing about what to do when a concern is not acted upon. The analyst’s note fourteen months before the alert was a good-faith act for which the code provided no framework and no protection.
Working in a group, design the replacement. CO-6 requires evaluation of a corporate episode and recommendation of ethical, governance, compliance and ESG improvements, so the code must be designed against this company’s demonstrated failures.
- Derive the syllabus. From the events of Chapters 35 to 38, list the specific situations this company’s code must address. Add the situations you would expect from the collected-questions method and say what sources you would collect from.
- Choose the approach. Decide what is stated as a bright-line rule and what as a standard with illustrations. Justify each bright line, and keep them to no more than six.
- Draft three sections in full. Write the sections on raising a safety or quality concern, on supplier and raw material integrity, and on gifts and hospitality. Each must address the difficult case, not only the obvious one, and each must say what to do and whom to tell.
- Design the escalation provision. Draft the provision covering what an employee does when a concern has been raised and not acted upon, which is the provision that would have changed this company’s history. State who it names.
- Map the statutory codes. List the separate codes this listed company must maintain, and specify how the general code references each without restating it.
- Design the supporting system. Specify the training, the route to ask before acting, the route to report, and the consequence framework. For each, name the owner and the measure that would show it working.
- Test the design. Set out five situations from the case and state where in your code an employee would find the answer, and how quickly.
- Address the incentive conflict. Identify anything in this company’s targets or rewards that would contradict the code you have written, and recommend what must change alongside it. Name the board committee responsible.
Present the code syllabus, the three drafted sections and the escalation provision in full, a statutory code map, and a two-page implementation plan.
39.9 Summary
NoteChapter Summary
A code of conduct states the standards an organisation expects and the conduct it will not accept (Manuel G. Velasquez, 2018). Almost every company has one and in most it is acknowledged at induction and never consulted, which is a design failure rather than an inevitability. Codes fail when written for the wrong reader, when they answer questions nobody asks, when they conflict with what the organisation rewards, and when nothing follows from breach.
A code serves guidance, commitment, authority and signal, and each has a drafting consequence. It cannot substitute for judgement, cannot make dishonest people honest since it addresses those who want to know the standard, and cannot override incentives, because where the code and the bonus plan disagree the bonus plan wins.
Compliance-based codes are clear, enforceable and right for bright-line matters, but cannot anticipate everything and teach that unlisted conduct is permitted. Values-based codes extend to unanticipated situations and engage judgement, but can be too abstract to guide. Workable codes combine them deliberately: bright lines stated without qualification and kept few, everything else stated as a standard with worked illustrations and a route to ask. Length is inversely related to use, because it buries the bright lines, invites the boundary search, and cannot be maintained; the alternative is a short code supported by separate detailed policies.
Content should follow the situations people encounter rather than legal categories, and two drafting choices decide whether it is usable: write situations rather than definitions, since people recognise situations and do not classify them, and answer the hard question rather than the easy one, since a code addressing only the obvious case teaches readers it has nothing for their actual problem. The reliable method is to build the code from the questions the compliance, human resources, legal and finance functions actually received, then test the draft by asking twenty people across functions to locate answers to five real situations in under two minutes.
Indian companies maintain several statutory codes with distinct legal effects, covering directors and senior management (Securities and Exchange Board of India, 2015a), independent directors (Government of India, 2013a), insider trading (Securities and Exchange Board of India, 2015b), sexual harassment with its own committee and timelines (Government of India, 2013b), and the vigil mechanism. The general code should reference rather than restate them.
Four components determine whether a code operates: training on real cases rather than recited text, a named low-consequence route to ask before acting whose usage is a better health measure than report volume, a route to report, and consistent consequence, which is what everyone believes the standard is.
TipKey Terms
Code of conduct · Guidance · Commitment · Authority · Signal · What a code cannot do · Incentives override codes · Compliance-based code · Values-based code · Bright line · Boundary search · Length and use · Supporting policies · Situations not definitions · The hard question · The collected-questions method · The two-minute test · Statutory codes · Code for directors and senior management · Insider trading code · Sexual harassment framework · Training on real cases · Route to ask before acting · Route to report · Consistent consequence · The escalation provision
Summary
| Concept | Description |
|---|---|
| What a Code Is For | |
| Code of conduct | A statement of the standards expected and the conduct that will not be accepted |
| Guidance | The purpose of helping a person decide in a situation they actually face |
| Commitment | The purpose of stating publicly what the organisation stands for |
| Authority | The purpose of providing the basis on which conduct is required and breach acted upon |
| Signal | The purpose of telling everyone inside what actually matters, which incentives can reverse |
| Not a substitute for judgement | The limit that no document anticipates every situation |
| Addresses those who want to know | The limit that a code speaks to the uncertain rather than the determined |
| Incentives override codes | The limit that decides the contest whenever a code and a reward plan disagree |
| Two Approaches | |
| Compliance-based code | The approach stating rules to be followed, clear and enforceable but unable to anticipate |
| Values-based code | The approach stating standards to be applied, extending further but harder to enforce |
| Bright line | A rule stated without qualification, which should be kept few so that it is visible |
| Boundary search | The disposition a detailed rule set teaches: looking for what is not covered |
| Length and use | The inverse relationship that makes a long code a guidance failure |
| Burying the bright lines | The specific harm of giving the rules that must never be broken equal typographical weight |
| Supporting policies | The detailed documents specialists consult, kept separate so the code stays readable |
| Content That Works | |
| Situations not definitions | The drafting choice recognising that people encounter situations and do not classify them |
| The hard question | The choice to address refusal that offends, the stuck shipment and the uncertain concern |
| The collected-questions method | Building the code from questions the compliance, legal, finance and people functions received |
| The two-minute test | The test of whether twenty people across functions can find five answers in two minutes each |
| Statutory Codes | |
| Statutory codes | The separate codes Indian law requires, with distinct populations and legal effects |
| Code for directors and senior management | The listed entity code with annual affirmation and a declaration in the annual report |
| Code for independent directors | The professional conduct and duties attaching to the independent role |
| Insider trading code | The machinery of designated persons, windows and pre-clearance binding a defined population |
| Sexual harassment framework | The statutory regime with its own committee, timelines and protections |
| Reference rather than restate | The relationship a general code should have with each statutory instrument |
| Making It Operate | |
| Training on real cases | Discussion of real situations by function, with an answer defended rather than announced |
| Route to ask before acting | A named, reachable, low-consequence way to ask before doing something |
| Usage as a health measure | The measure of programme health better than the number of reports received |
| Route to report | The channel described in Chapters 21 and 41 |
| Consistent consequence | The component that determines what everyone believes the real standard is |
| Enforcement against high performers | The test of consistency, whose failure communicates the real rule with complete clarity |
| The escalation provision | The provision covering what to do when a concern has been raised and not acted upon |