Under Provision 29, boards are required to include a genuine declaration in their annual report, confirming whether material controls operated effectively throughout the year.
That evidence sits with the company. The board's role isn't necessarily producing it, it's reviewing what management and risk functions present, challenging it properly, and being satisfied it's genuinely adequate before putting their name to a declaration.
Nothing can make that judgement for a board. The material controls, the adequacy of the evidence, the decision to declare, all of that remains the board's own responsibility, and rightly so.
What MyDirector-OS can do is lighten the burden of getting there. In practice, the evidence a director needs is often scattered rather than assembled in one place when any declaration falls due.
BoardLens reviews board packs and any other document through the lens of the specific regulatory framework governing each appointment. It tracks activity across successive versions, packs and meetings, flagging where an item raised previously hasn't moved or where a gap appears to be forming, so nothing stalls quietly in the background. That review gives a director something concrete and genuinely useful to weigh when material controls come up for judgement.
The Director's Assistant goes further than most governance tools are willing to. Every answer is grounded in the verified regulatory framework for that specific board, and where a question needs something current beyond the library itself, it searches and checks the answer against the source before it ever reaches you. Thorough, honest, and built to actually be relied upon, not just consulted.
Given the Code's comply-or-explain basis, the real exposure isn't choosing not to comply with a specific control. It's reaching the declaration with no proper explanation ready either way.
If your board's next declaration were due tomorrow, could you say plainly which controls it would rely on?