The IoD recently published a policy paper on a voluntary code of conduct for Directors. Currently, in the UK and the Crown Dependencies, private company directors have no Code of Conduct. Directors who provide their services through a company service business may be subject to codes of conduct for those regulated businesses, but that doesn’t apply to the many directors of private companies.
With so many recent corporate governance failures, including Carillion, P&O ferries, BHS, and other significant enterprises, it’s understandable that businesses should be more accountable to a broader group of stakeholders than just their shareholders.
As new corporate governance scandals arise, the government may wish to impose regulations to reduce the issues. The IoD feels that more rules will add complexity and won’t necessarily solve the problem. Instead, it recommends a more flexible, voluntary approach emphasising individual responsibility and the importance of a business-led solution.
We’ve spent years working in regulated financial services, as well as in private companies. Regulated businesses have heavy compliance requirements, which seem unduly burdensome for private companies. No conduct framework is insufficient, given the number of governance scandals over the past few years. As Directors, we must meet the Corporate Law requirements in our jurisdiction. We have additional requirements to meet if we are professionals in regulated industries, such as accountants, solicitors, auditors, and corporate governance specialists. But what about directors who aren’t regulated? The suggested Code of Conduct the IoD recommends seems like a sensible approach but needs to be driven by business leaders to ensure it gets the full buy-in of private Company Directors.
The draft Code of Conduct itself is short. Only three pages long, it’s not onerous and aligns with Director responsibilities in Corporate Law. It includes nine topics, each setting out several points a Director will agree to meet. It also gives practical, pragmatic ways that Directors can ensure they meet a standard Code of Conduct.
If you are a Director, consider adopting the draft Code of Conduct today. Then you can make suggestions on changes and be ready to support it should it get rolled out. If you are a business, we encourage you to consider supporting the IoD’s efforts on this voluntary code before more regulation lands on our desks.
For the full Consultation Paper Result, please see:
IoD-A-voluntary-code-of-conduct-for-directors.pdf
Please click on the button below to download the full article.
You can find more articles on our website, at Phundex Knowledge Hub, on LinkedIn at Phundex LinkedIn, or for other questions, please email us at: hello@phundex.com.
To book a demo or do a trial, you can either use the link on our website or email support@phundex.com, and they will be happy to set it up for you.
Get a one-to-one demo
Discover how Phundex can streamline your transactions and processes
Copyright Phundex 2024
PHUNDEX UK LIMITED
Registered Office :
128 City Road, London, UK, EC1V 2NX
Trading Office :
68 Summers Road, Godalming, Surrey, UK, GU7 3BE
Phundex Limited is registered in Jersey, Channel Islands, No 131447, Registered with the Information Commissioner’s Office in the UK in compliance with the Data Protection (Charges and Information) Regulations 2018 under registration ZA839762 and in Jersey in compliance with Regulation 4(1) of the Data Protection (Registration and Charges) (Jersey) Regulations 2018 under registration 68186
Phundex UK Ltd is registered in England & Wales No. 12207772, Registered with the Information Commissioner’s Office in the UK in compliance with the Data Protection (Charges and Information) Regulations 2018 under registration ZB285669
Cookie | Duration | Description |
---|---|---|
_GRECAPTCHA | 5 months 27 days | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
ajs_anonymous_id | 1 year | This cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before. |
ajs_user_id | never | This cookie is set by Segment to help track visitor usage, events, target marketing, and also measure application performance and stability. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
Cookie | Duration | Description |
---|---|---|
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
Cookie | Duration | Description |
---|---|---|
__tld__ | session | No description |