Zeenat Qavlerni · Chief Information Officer · India
What must be true before the digital promise holds?
My contribution to a board
I could help a board examine the operating promise inside an enterprise-system recommendation. A calendar may show a free interval while necessary turnover work has disappeared, and a cancelled booking may leave inspection or agreement questions unresolved. Those are business assumptions expressed through software, not merely implementation details. My own release error would make me ask what management’s acceptance evidence actually establishes and whose account has been left outside it. Directors should understand the consequence and the assurance route without designing workflows or approving individual premises. I would first learn the company’s services, agreements and professional responsibilities so my experience is applied to the right question. The contribution would be a more complete basis for the technology decision: which physical condition, commercial permission or remaining obligation must be preserved before the application’s answer becomes a promise the business can responsibly make.
Judgement in practice
01
A calendar could pass while the service sequence still failed
The selected twenty-four bookings contained seven conflicts once the required turnover interval was included. I would ask directors whether a technology acceptance account tests the full operating sequence or only the periods represented in the application. The ninety-minute value belonged to that arrangement and its qualified owners; it was not a universal prescription. A board should understand who establishes such assumptions and how management knows the software preserves them. My initial acceptance is part of the example because the failure was not simply a vendor defect discovered by an attentive customer. I had approved an incomplete account. Useful oversight should make that conclusion revisable before a clean-looking system result becomes a commitment that operating colleagues must somehow repair afterwards.
02
A supported room description needed evidence specific to that room
Forty-four of sixty reviewed amenity rows were initially confirmed, with sixteen unsupported. Facilities-led examination increased the supported count to fifty-six and left four withheld. I would ask a board whether a platform’s commercial descriptions remain tied to evidence at the level where the customer relies on them. A common brand or similar room does not establish identical equipment or conditions. Directors need an assurance account for those statements, including the unresolved rows, while qualified owners retain technical and suitability decisions. The increase in confirmed descriptions was a bounded review outcome, not certification of every possible use. Oversight should preserve that boundary when management presents the platform as ready to support a broader commercial offer.
03
Ending one booking did not settle the next commitment
The forty-eight cancelled bookings divided into thirty-two cleared spaces, ten inspection cases and six requiring contractual clearance. I would ask whether a board report distinguishes the event that ends a customer arrangement from the decisions needed to offer the resource again. A single positive status can obscure unresolved responsibilities even when the cancellation itself is undisputed. Directors should know the owners and consequences of the outstanding groups without choosing a refund or interpreting each agreement. The application’s role is to represent an authorised transition, not create permission through a default. That distinction matters when an apparent efficiency improvement merely removes the intermediate state in which the business still needs to do real work.
My first year on a board
I would begin by tracing one material digital promise from its board recommendation through the operating and contractual evidence supporting it. With the chair’s agreement, I would meet the responsible technology, facilities and commercial owners to understand how assumptions are established and who can change them. I would examine an unresolved case and a withdrawn release alongside a successful implementation, because those accounts reveal how the company handles contradiction. The proposed twenty-two days need to accommodate induction, preparation, meetings and exceptional demands before they become an agreed commitment. I would seek feedback on whether my questions clarify the decision or draw directors into executive workflow design. A useful first year could make one consequential systems proposal clearer about the conditions it assumes, the professional decisions it represents and the route for reporting when later evidence changes the basis of the original approval.
Conflicts and their management
My role gives access to property agreements, workspace-use patterns, supplier arrangements and systems plans that may be commercially sensitive to another operator. I would disclose employer, property-investor, premises-owner, software-supplier and commercial-user connections before receiving restricted material from a prospective board. The appointment would need the company’s eligibility and independence assessment together with employer agreement and a workable calendar. Recusal can address a specific matter, but repeated exclusion from the main property or technology agenda could defeat the purpose of the seat. I would not offer another enterprise private booking patterns or privileged supplier access as part of my contribution. I would also decline a role expecting a non-executive director to certify premises suitability, settle individual agreements or act as a shadow CIO. Collective oversight depends on management and qualified advisers retaining their own decisions and being able to explain the evidence supporting them.
My independence statement
Property investors, premises owners, software suppliers and commercial users require relationship checks for the proposed seat. No personal equity is held; independence is not established by that alone.
Board and committee exposure
Presented to the Board or a committee
Drevqazni Kitchen Properties
Board technology and property-service discussions
April 2022–present
Presents system assumptions and unresolved premises-workflow conditions through the CEO; no director appointment.
Reported to a committee
Drevqazni Kitchen Properties
Application release review through the CIO
April 2016–March 2022
Reported the withdrawal and reconstruction of the booking release; executive evidence rather than statutory voting responsibility.
Governance learning and readiness
IICA Independent Directors’ Databank: Not yet registered
Governance learning and any appointment-specific registration remain to be completed. There is no claimed proficiency result, exemption or previous statutory director service.
Preparing to assess technology recommendations through collective director responsibility
Learning how premises and contractual assurance should inform board scrutiny of digital commitments