1. Meaning of Failure to Log Unsuccessful Alert Deliveries

Failure to Log Unsuccessful Alert Deliveries refers to a situation in which an organisation, institution, company, government department, bank, regulatory authority or other entity uses an electronic communication system to send alerts, notifications, reminders, warnings, notices or other important communications but fails to maintain proper records when such communications are not successfully delivered to the intended recipients.

In simple terms, whenever an organisation sends an alert through email, SMS, WhatsApp, an automated notification system or any other electronic communication platform, it should maintain a proper record showing whether the communication was:

Successfully sent.

Successfully delivered.

Rejected by the recipient's server.

Bounced back due to an incorrect email address.

Undelivered due to network or technical problems.

Failed because of an inactive mobile number.

Blocked or rejected by the recipient's communication service provider.

Left pending without confirmation of delivery.

If an alert fails to reach the intended recipient, the system should generate and preserve an appropriate failure notification or error log.

When an organisation fails to record these unsuccessful delivery attempts, it creates a serious problem concerning transparency, accountability, compliance, record management and legal proof of communication.

2. Why Is Logging Unsuccessful Alert Deliveries Important?

Logging unsuccessful alert deliveries is important because merely generating or sending an electronic communication does not necessarily establish that the intended recipient received it.

For example:

Suppose a bank sends an important fraud alert to a customer's registered email address. However, the email address is incorrect, and the email delivery system generates a notification stating that the email could not be delivered.

If the bank does not preserve this failure notification, it may subsequently be unable to establish:

Whether the alert was actually delivered.

Whether the customer received information about the transaction.

Whether the communication system experienced a technical failure.

Whether the bank took appropriate steps after the unsuccessful delivery.

Whether the customer was given a reasonable opportunity to respond.

Whether the organisation complied with its applicable notification obligations.

Therefore, maintaining unsuccessful delivery logs is an important internal control mechanism.

3. Legal Implications of Failure to Log Unsuccessful Alert Deliveries

A. Failure to maintain reliable electronic records

Electronic records are important evidence in legal proceedings.

Where an organisation sends an electronic alert but does not maintain records of unsuccessful deliveries, the reliability and completeness of its electronic recordkeeping system may be questioned.

Under the Information Technology Act, 2000:

Section 4: Recognises electronic records and their legal validity, subject to the statutory requirements.

Section 5: Recognises electronic signatures.

Section 7: Deals with retention of electronic records.

Section 10A: Recognises the validity of contracts formed through electronic means.

Section 7 is particularly relevant because it addresses the retention of electronic records and requires that retained records remain accessible, accurately represent the information originally generated, sent or received, and contain relevant particulars concerning their origin, destination, date and time.

Failure to maintain delivery failure logs may weaken the organisation's ability to demonstrate the completeness and reliability of its communication records.

B. Failure to establish proper service of notice

An organisation cannot automatically claim that a notice or alert was successfully communicated merely because its system shows that an email or SMS was generated.

There is an important legal distinction between:

Generation of a communication.

Dispatch of a communication.

Delivery of a communication.

Acknowledgment or proof of receipt.

If the organisation cannot produce reliable delivery records, its claim that the recipient was duly informed may be challenged.

C. Failure of internal controls and accountability

The absence of unsuccessful delivery logs may indicate weaknesses in:

Information technology controls.

Electronic communication monitoring.

Audit trail maintenance.

Compliance monitoring.

Incident management.

Customer notification procedures.

Risk management systems.

An organisation should have a mechanism to identify unsuccessful deliveries and take corrective action.

D. Possibility of prejudice to the recipient

Failure to record unsuccessful deliveries may cause serious prejudice to an individual or organisation.

For example:

A customer may not receive a fraud alert.

A litigant may not receive information about legal proceedings.

An employee may not receive an important disciplinary notice.

A borrower may not receive an important payment reminder.

A regulatory entity may fail to communicate a statutory warning.

If such failure results in financial loss, denial of an opportunity to respond or other legal prejudice, the organisation may face legal consequences depending on the applicable law and facts.

4. Important Case Laws and Judicial Principles

The following Indian judicial decisions are relevant to electronic communication, proof of service, unsuccessful delivery and the evidentiary value of electronic records.

Case 1: M/s Shree Jee Sales Corporation v. M/s Nexgen Fluropolymers Pvt. Ltd. (2026)

Court: Delhi High Court Case: FAO 203/2024 Decision: 28 February 2026.

Facts:

The dispute concerned whether summons had been properly served upon a defendant through electronic communication, including email and WhatsApp.

The defendant disputed having received the summons.

The court examined the material produced to establish electronic service.

Judicial observations:

The Court emphasised that the mere assertion that an email or WhatsApp message was sent does not establish successful service.

There was no sufficient material demonstrating successful email delivery or receipt. The record also lacked an adequate delivery report, acknowledgment or server confirmation.

Legal principle:

The validity of electronic communication as a mode of service does not eliminate the requirement to establish that service was actually effected.

Relevance to failure to log unsuccessful deliveries:

This judgment is particularly important because it demonstrates that an organisation or litigant should preserve:

Email delivery reports.

Server confirmation.

Bounce-back notifications.

Electronic acknowledgments.

Relevant communication records.

Where no delivery evidence is maintained, the claim of successful service may be challenged.

Case 2: Electricity Regulatory Commission v. National Hydroelectric Power Corporation Ltd. (2010)

Citation: (2010) 10 SCC 280 Court: Supreme Court of India.

Legal issue:

Whether notices and communications could be served through electronic mail in commercial proceedings.

Legal principle:

The Supreme Court recognised the permissibility of electronic communication for service of notices in the relevant commercial context.

However, recognising email as a permissible mode of communication does not mean that every email generated by a sender must automatically be treated as successfully delivered.

Relevance:

An organisation must distinguish between the legal validity of electronic communication and proof that the particular communication was successfully delivered.

This distinction is essential when examining unsuccessful alert delivery logs.

Case 3: C.C. Alavi Haji v. Palapetty Muhammed (2007)

Citation: (2007) 6 SCC 555 Court: Supreme Court of India.

Facts:

The case concerned service of a statutory demand notice under Section 138 of the Negotiable Instruments Act, 1881.

The Court considered the legal presumption relating to service of notices sent through registered post to the correct address.

Legal principle:

The Supreme Court explained the circumstances in which service may be presumed when a notice is properly addressed, prepaid and dispatched through registered post.

The decision also discussed the opportunity available to an accused to rebut the presumption of service.

Relevance:

This decision is useful for understanding the distinction between:

Dispatch of a communication.

Presumed service under an applicable legal provision.

Actual receipt.

Evidence rebutting the presumption of service.

Importantly, the statutory presumption applicable to properly dispatched postal notices cannot automatically be extended to every electronic alert.

Case 4: State of Madhya Pradesh v. Hiralal (1996)

Citation: (1996) 7 SCC 523 Court: Supreme Court of India.

Legal principle:

The Supreme Court considered the presumption of service arising from postal communications and the circumstances in which a party may be treated as having received a notice despite an endorsement indicating refusal.

Relevance:

The case illustrates that the law may recognise presumptions of service in specific circumstances.

However, such presumptions depend upon the applicable statutory framework and supporting evidence.

It does not mean that an organisation can disregard failed electronic delivery notifications or treat every unsuccessful communication as successfully delivered.

Case 5: Shree Jee Sales Corporation v. Nexgen Fluropolymers Pvt. Ltd. – Electronic Service and Proof of Delivery

The significance of this decision deserves particular attention because it directly addresses the evidentiary weakness arising when electronic delivery records are absent.

The Court considered the absence of adequate proof that an email had reached the intended recipient.

The important principle is:

Sending an electronic communication and establishing successful delivery are two different matters.

A party relying on electronic service should produce credible evidence supporting its assertion.

This principle is directly relevant to situations where organisations fail to preserve unsuccessful delivery logs.

5. Legal Framework Under the Bharatiya Sakshya Adhiniyam, 2023

The Bharatiya Sakshya Adhiniyam, 2023 (BSA), which came into force on 1 July 2024, governs the admissibility and proof of electronic and digital records in proceedings to which it applies.

Some important provisions are:

Accordingly, delivery reports, system-generated notifications, email bounce-back messages and other electronic audit records may be relevant evidence, subject to the applicable requirements of admissibility and proof.

An organisation should ensure that such records are properly preserved and capable of being produced when required.

6. What Records Should an Organisation Maintain?

An effective electronic alert delivery monitoring system should maintain the following information:

These records help establish an accurate and complete communication history.

7. Consequences of Failure to Log Unsuccessful Alert Deliveries

The consequences depend on the nature of the organisation, applicable regulatory requirements and the harm caused.

The possible consequences include:

1. Weakness in evidentiary support: The organisation may be unable to prove that an important alert was successfully delivered.

2. Regulatory non-compliance: Where applicable rules require communication monitoring or preservation of records, inadequate logging may constitute a compliance deficiency.

3. Audit observations: Internal auditors and statutory auditors may identify the absence of delivery failure logs as a weakness in information technology general controls and operational controls.

4. Customer disputes: Customers may dispute claims that they were informed about important transactions, warnings or obligations.

5. Legal liability: Where negligence, breach of statutory duty, contractual obligations or other actionable wrongdoing is established, the organisation may face legal consequences.

6. Loss of accountability: Without failure logs, it becomes difficult to identify whether the problem arose from incorrect recipient details, system malfunction, network disruption or inadequate monitoring.

8. Recommended Corrective and Preventive Measures

An organisation should implement the following controls:

Configure automated logging of every unsuccessful alert delivery.

Maintain complete records of email bounce-back messages and SMS delivery failures.

Generate alerts for repeated delivery failures.

Establish an escalation mechanism for critical notifications.

Verify and periodically update recipient contact details.

Implement automated retry mechanisms where appropriate.

Maintain tamper-evident audit trails.

Preserve relevant logs in accordance with applicable retention requirements.

Conduct periodic reviews of unsuccessful delivery reports.

Ensure that important statutory communications are sent through an alternative legally recognised mode wherever required.

9. Overall Legal Position

The central legal principle is that the mere generation or dispatch of an electronic alert does not invariably establish successful delivery or valid service upon the intended recipient.

Where an organisation fails to log unsuccessful alert deliveries, it may become difficult to establish whether the recipient was actually informed, whether the communication system functioned correctly and whether the organisation fulfilled its legal or contractual obligations.

The judgments in M/s Shree Jee Sales Corporation v. M/s Nexgen Fluropolymers Pvt. Ltd. (Delhi High Court, 2026), Electricity Regulatory Commission v. NHPC (2010) and C.C. Alavi Haji v. Palapetty Muhammed (2007) help explain the legal distinction between permissible modes of communication, proof of service and presumptions of receipt.

However, failure to maintain such logs is not automatically a statutory offence in every situation. Its legal significance depends upon the particular regulatory requirement, contractual obligation, applicable record-retention rules and resulting prejudice.

10. Suggested Audit Observation / Compliance Finding

The following language can be used in an internal audit report, compliance report or risk assessment.

Observation: Failure to Log Unsuccessful Alert Deliveries

It was observed that the organisation has not established an adequate mechanism for recording, monitoring and retaining details of unsuccessful electronic alert deliveries. In particular, appropriate records relating to failed email notifications, undelivered SMS alerts, system-generated delivery errors and unsuccessful communication attempts were not adequately maintained.

The absence of such records creates a risk that the organisation may be unable to demonstrate whether critical alerts and notifications were successfully communicated to the intended recipients. It may also adversely affect the organisation's ability to establish compliance with applicable statutory, regulatory and contractual communication requirements.

Further, the absence of reliable delivery and failure logs may weaken the evidentiary value of electronic communication records in the event of customer disputes, regulatory inspections, audits or judicial proceedings.

Risk: Inadequate communication monitoring, potential regulatory non-compliance, weak audit trails, inability to establish proof of service and possible legal disputes.

Recommendation: Management should implement an automated alert delivery monitoring mechanism that captures successful and unsuccessful delivery attempts, records relevant error messages, generates exception reports and ensures timely escalation and corrective action for critical communication failures.

11. Conclusion

Failure to Log Unsuccessful Alert Deliveries is not merely an IT or operational issue. It can also become a legal, evidentiary, compliance and governance issue.

An organisation must be able to demonstrate not only that an alert was generated or dispatched but also what happened to that alert after dispatch.

Proper documentation of unsuccessful deliveries is therefore essential for transparency, accountability, effective internal controls and establishing the reliability of electronic communications.

Important legal distinction: The absence of a failure notification is not, by itself, conclusive proof that an electronic communication was successfully delivered. Equally, an unsuccessful delivery does not automatically establish negligence or legal liability. Both questions must be decided on the available evidence and applicable law.