Four ledgers the Chair must reconcile
The financial ledger records revenue, cost, assets, provisions and cash. The delivery ledger records what has actually been implemented, accepted, stabilised and supported. The technology ledger records systems, debt, access, vulnerabilities and recovery. The stakeholder ledger records promises, disputes, grievances and trust. The central purpose of this chairship is to make sure these four do not tell incompatible stories.
The financial ledger
The Chair will set expectations for contract-level assurance over fixed-price work, implementation milestones, licence or subscription elements, unbilled revenue, change control and loss-making engagements. Estimate revisions should be visible by cause and owner. Large aged receivables, customer dependencies and credits require commercial explanation as well as accounting treatment.
Capitalised development, software assets, acquired intangibles, restructuring costs and cloud commitments must be reviewed against evidence of continuing economic benefit. The committee should know what was originally assumed, what has changed and how management has treated unsuccessful investment.
The delivery and technology ledgers
Internal audit will be expected to follow high-risk services end to end. Scope should include sales-to-contract controls, transition, access, configuration, subcontractors, service credits, customer acceptance and cash. Project status reporting must expose the small number of assumptions capable of changing margin or obligation.
For cyber and resilience, the Board needs tested restoration evidence for critical services, including identity, backups, client interfaces, vendors and manual workarounds. The Chair will ask whether recovery objectives are consistent with contractual commitments and whether repeated exceptions are symptoms of design rather than execution.
AI-supported development and operations require inventory, data boundaries, permitted tools, human review, evaluation and incident escalation. Productivity benefits should be measured after quality, rework and security consequences—not inferred from adoption.
The stakeholder ledger
As a Stakeholders Relationship Committee member, the director will look beyond closure metrics to recurring investor confusion, disclosure quality, significant customer disputes and the way corrective information is communicated. The Risk Committee should then absorb those signals into appetite and scenario work. The NRC should ask whether leadership, skills and reward explain persistent control behaviour.
Candidate proof
The strongest applicants will have chaired an Audit Committee or held senior responsibility as a technology-company CFO, audit partner, global delivery leader, CIO/CISO, chief risk officer or transformation executive. They must demonstrate decisions in which they connected operating evidence to accounting or risk, especially where the initial management position was plausible. Experience of restructuring, platform migration or service recovery is useful. Independent-director databank status, independence and capacity will be verified. The role entails quarterly cycles, private auditor sessions, technology-risk deep-dives and incident availability.
When a material incident occurs, the Chair will protect a disciplined decision sequence: establish known facts and uncertainties; preserve evidence and legal privilege; determine customer, regulatory and market-disclosure duties; validate service-continuity options; and schedule independent review after stabilisation. The committee should not direct technical containment, but it must make sure commercial urgency does not outrun truthful reporting, customer protection or the conditions for a safe restoration.
Registration on the IICA Independent Directors Databank is required before appointment. A DIN is not needed to apply: where an appointee does not yet hold one, it is obtained through the appointing company at the point of appointment.