Annual Board Policy Acknowledgments: Who Received What, and Who Still Owes

Target keyword: board policy acknowledgment
Intent: Informational / How-to
Last updated: 2026-10-05
Reading time: ~9 minutes

---

Who this guide is for

Chairs, corporate secretaries, governance counsel, and investor directors who need to answer one plain question each year: did every director receive the current version of each board policy, and who still owes an acknowledgment?

This is practice guidance, not legal advice. Which policies your board must adopt, and whether a signature, an acknowledgment, or a certification is required, depends on your charter, bylaws, regulators, listing status, and counsel. Nothing here is a compliance determination.

---

Why the annual acknowledgment matters

Adopting a policy is a board decision. Knowing that each director actually received it is a separate fact, and it is the one people ask about later:

• An investor's diligence list asks whether directors acknowledged the code of conduct and insider trading policy this year.
• An auditor or regulator asks when the board last circulated the whistleblower or anti-corruption policy.
• A nonprofit's Form 990 preparer asks whether the conflict and whistleblower policies are in place and monitored.
• A new director asks which policies they are expected to have read.

Most boards answer from memory, a reply-all email thread, or a spreadsheet the secretary keeps. Those break the same way: the version is unclear, the date is unclear, and nobody can say who is still missing without chasing everyone again.

---

A five-step annual cycle

1. Decide the set. List the policies the board has actually adopted. Common ones: code of conduct / ethics, whistleblower / speak-up, gift and hospitality, insider trading / MNPI, anti-bribery / anti-corruption, information security, data privacy / confidentiality, and conflict of interest (often collected in the annual questionnaire instead).
2. Attach the current version. Each acknowledgment should point at a specific document in the board book, not "the policy on the shared drive."
3. Set one due date per policy. Stagger them if the board is small, or align them to the annual meeting. Write the year on the cycle so last year's acknowledgment never counts for this year.
4. Ask for receipt in plain words. "I received the current policy" is a receipt, not a signature. Keep it that way unless counsel says you need a wet or electronic signature.
5. Chase only who owes, then report. The secretary should see who has not acknowledged, send a short reminder, and put a one-line status in the board report or diligence response.

What to leave out: scoring directors, ranking "compliance," or treating a missing acknowledgment as a breach. An unacknowledged policy is a follow-up item, not a finding.

---

Where the record should live

Keep each acknowledgment next to the board record, not in a separate HR system the board cannot see. That way the same place that shows decisions, recusals, and minutes can also show that directors received the policies those decisions rely on — and an investor or auditor gets one answer instead of five forwarded emails.

---

How Prepared Board records it today

Prepared Board has one acknowledgment tracker per policy, each at its own page and Settings anchor:

Each works the same way. A Chair, Admin, or Owner enables a board-declared year, a due date, a short title, an optional link to the policy document in the same board's book, and optionally includes observers (labeled when included). Active directors show Not acknowledged or Acknowledged with an in-app timestamp, and acknowledging requires a short honesty confirmation that this is a receipt. Chair, Secretary, Admin, and Owner see who owes; each director sees their own status. Every page has Copy for your agent so a director or secretary can paste the status into their own assistant.

When someone still owes and the due date has passed or is within 14 days, a soft cue appears in Board Go. Status strips also appear on Board decision quality proof and the Diligence snapshot, which is where investors usually look.

Honest limits:

• In-app record only. It is not eSign, not DocuSign, and not a legal signature.
• Not a compliance determination. Prepared does not decide whether your policies satisfy any statute, regulator, or listing rule — not an FCPA or UK Bribery Act determination, not a trading-window determination, not a security assessment, and not a GDPR or CCPA determination.
• Prepared does not run a hotline, blackout calendar, or broker pre-clearance. It records that a director received the policy.
• Reminders are copyable text. Prepared does not send the chase email for you.
• No scores. Nobody gets a compliance grade.

Check every product claim on this page against Facts or the machine-readable /agent-facts.json.

---

Try it: Northlight Robotics

Northlight Robotics is a seeded venture-backed demo board (not a real company). Its 2026 cycle has all seven trackers enabled with due dates between 2026-10-11 and 2026-10-17, and a different director still owes on each one, so the chase view has something real to show.

The shared demo password is an evaluation login, not SSO. Seeded names and dates are demo data.

---

Board-type guides

• Venture-Backed Board Governance
• Public & Pre-IPO Board Governance
• Private Company Board Governance

Related guides

• Whistleblower Policy for Boards
• Conflict of Interest Policy for Boards
• Board Director Onboarding Checklist
• Board Observer Rights and Roles

---

Conclusion

Run policy acknowledgments as a short, dated annual cycle: the current document, one due date, a plain receipt, and a chase list of only the people who still owe. Keep it beside the board record so the answer to "did every director receive it?" is one page, not an email hunt. Try Northlight above, then verify every claim on Facts.

Try a board → Northlight