1. Meaning and concept

A waiver approval hierarchy is a formal organisational framework that specifies who has the authority to approve, reject, modify, or escalate a request to waive a legal requirement, contractual term, internal policy, procedural rule, service condition, financial charge, or employment-related obligation.

A waiver permits an authorised exception to an otherwise applicable rule. The hierarchy ensures that the exception is approved by the appropriate person, supported by legitimate reasons, properly documented, and consistent with applicable law.

For example, an organisation may permit a department manager to waive a minor administrative deadline, while a waiver involving a substantial financial amount, contractual liability, employee entitlement, or statutory requirement may require approval from senior management, legal counsel, the finance head, or the board.

The essential distinction is that internal authority to approve a waiver does not automatically create legal authority to waive a statutory obligation or a third party's rights.

2. Objectives of waiver approval hierarchies

The principal objectives are:

Accountability: Identify the person responsible for approving each exception.

Risk management: Ensure that higher-risk waivers receive more rigorous scrutiny.

Legal compliance: Prevent unlawful waivers of mandatory statutory rights or obligations.

Consistency and fairness: Ensure comparable cases are assessed according to consistent criteria.

Financial control: Prevent unauthorised discounts, fee concessions, debt write-offs, or contractual variations.

Prevention of conflicts of interest: Stop employees from approving exceptions that personally benefit them or their associates.

Auditability: Maintain an adequate record of the reasons, approvals, conditions, and implementation of each waiver.

Protection against arbitrary decisions: Reduce favouritism, discrimination, retaliation, and inconsistent treatment.

3. Common levels of a waiver approval hierarchy

The following is an illustrative structure, not a legally prescribed universal hierarchy.

Legal, HR, finance, compliance, and procurement functions may operate as parallel approval routes rather than strictly sequential levels. The appropriate route depends on the nature of the waiver.

4. Legal principles governing waiver approvals in India

Waiver approval hierarchies are generally governed by a combination of contract law, statutory requirements, employment law, corporate governance, delegated authority, and principles of fairness.

A. Authority and delegation

An approval is valid only if the approving person possesses the relevant authority under the applicable law, contract, board resolution, delegation-of-powers schedule, or organisational policy.

A manager cannot validly approve a waiver merely because the matter falls within the manager's department. The organisation must verify whether the manager has authority over the particular subject, financial value, and type of risk involved.

B. Voluntary and informed waiver

Where a waiver involves the relinquishment of a legal right, the circumstances must establish that the right-holder knowingly and intentionally relinquished that right, where the law permits it.

Silence, delay, routine conduct, or an employee's failure to object immediately should not automatically be treated as a waiver.

C. Statutory restrictions

An internal policy cannot authorise an exception prohibited by legislation. For example, an employer cannot rely on a senior manager's approval to eliminate a mandatory minimum wage or other non-waivable statutory employment protection.

D. Consistency and non-arbitrariness

Waiver decisions should be supported by objective criteria. Decisions involving public authorities or exercises of statutory discretion may also be subject to constitutional requirements of equality, reasonableness, and non-arbitrariness.

E. Proper documentation

The organisation should record the original rule, the requested exception, the applicant's reasons, the approving authority, the legal or financial assessment, the duration of the waiver, and any conditions imposed.

5. Important case laws — at least six

The following Indian judicial decisions establish relevant principles concerning waiver, authority, statutory rights, contractual obligations, and discretionary decision-making. They are not all cases specifically about corporate approval hierarchies; their relevance lies in the legal principles that a properly designed hierarchy must respect.

1. Basheshar Nath v. Commissioner of Income Tax (1959)

Court: Supreme Court of India.

Principle: Fundamental rights under Part III of the Constitution cannot be waived by an individual to excuse unconstitutional State action.

Explanation: The case concerned a settlement under tax legislation and the argument that the affected person had waived the right to challenge the proceedings. The Supreme Court rejected the proposition that the relevant fundamental right could be waived in that manner.

Relevance to waiver approval hierarchies: An internal approval cannot legitimise an act that the Constitution prohibits. Where a proposed waiver affects constitutional protections, equality, or the legality of State action, decision-makers must examine the underlying legal restriction rather than rely on consent or seniority alone.

2. Motilal Padampat Sugar Mills Co. Ltd. v. State of Uttar Pradesh (1979)

Court: Supreme Court of India.

Principle: Promissory estoppel may prevent a party from departing from a clear promise on which another party has relied, subject to recognised legal limitations.

Explanation: The Supreme Court considered a promise concerning sales-tax exemption and the consequences of reliance on that promise. The decision is an important authority on governmental promises and the circumstances in which they may be enforced.

Relevance to waiver approval hierarchies: Organisations should establish who may make binding promises concerning concessions, exemptions, and contractual benefits. An unauthorised representation can create disputes over reliance, authority, and enforceability. Approval procedures should therefore be clear before commitments are communicated.

3. Mademsetty Satyanarayana v. G. Yelloji Rao (1965)

Court: Supreme Court of India.

Principle: The legal consequences of waiver, acquiescence, and estoppel depend on the relevant facts and applicable legal requirements; these concepts are not interchangeable.

Explanation: The case considered equitable principles in the context of contractual rights and relief. It illustrates why a party's conduct must be assessed in its legal and factual context rather than automatically treated as a relinquishment of rights.

Relevance to waiver approval hierarchies: An organisation should not infer that a policy has been waived simply because a manager previously tolerated a departure from it. The record should identify the actual decision, the authority behind it, and the intended scope of the exception.

4. Associated Hotels of India Ltd. v. S.B. Sardar Ranjit Singh (1968)

Court: Supreme Court of India.

Principle: Waiver involves the intentional relinquishment of a known right; whether it occurred depends on the circumstances and the conduct of the parties.

Explanation: The case is commonly cited in discussions of waiver and the need to distinguish a genuine relinquishment of rights from conduct that does not establish such an intention.

Relevance to waiver approval hierarchies: A waiver record should identify the precise requirement being relaxed and demonstrate that the relevant party and authorised decision-maker understood the consequences. General statements such as "approved as an exception" may be insufficiently precise where important rights or contractual obligations are involved.

5. P. Dasa Muni Reddy v. P. Appa Rao (1974)

Court: Supreme Court of India.

Principle: Waiver and estoppel are distinct legal concepts and must be applied according to their respective requirements.

Explanation: The Supreme Court examined these doctrines in a property-related dispute. The decision is relevant to the distinction between voluntarily giving up a right and being prevented, by the operation of estoppel, from asserting a position.

Relevance to waiver approval hierarchies: An approval system should distinguish between an authorised exception, an alleged relinquishment of a right, and a situation in which previous representations or conduct may have legal consequences. These categories should not be collapsed into a single administrative label.

6. Krishna Bahadur v. Purna Theatre (2004)

Court: Supreme Court of India.

Principle: Whether a statutory right can be waived depends on the nature and purpose of the provision; not every statutory protection is freely waivable.

Explanation: The Court considered waiver in a dispute involving statutory protections. The judgment supports examining whether the right exists primarily for an individual's benefit or whether the relevant provision serves a broader public purpose or imposes a mandatory legal requirement.

Relevance to waiver approval hierarchies: Before approving an exception, legal or compliance personnel should classify the requirement as a contractual condition, internal policy, waivable individual entitlement, or mandatory statutory obligation. This classification determines whether approval is legally permissible at all.

7. State of Punjab v. Davinder Pal Singh Bhullar (2011)

Court: Supreme Court of India.

Principle: Waiver requires conscious abandonment of an existing legal right by a person who knows and understands that right.

Explanation: The judgment discusses waiver as an intentional relinquishment of a legal right, benefit, claim, or privilege. Mere conduct cannot establish waiver unless the necessary legal and factual requirements are satisfied.

Relevance to waiver approval hierarchies: The approving authority should be able to demonstrate that the waiver was consciously granted, the relevant rights and consequences were understood, and the decision was not merely inferred from informal conduct or silence.

This principle supports requiring a reasoned approval record and a clear description of the scope and effect of the exception.

6. Practical implementation of a waiver approval policy

A well-designed policy should establish the following controls.

A. Define the categories of waivers

Organisations should separately classify:

Operational waivers: Exceptions to routine processes, deadlines, or administrative requirements.

Financial waivers: Discounts, penalties, fees, receivables, or payment terms.

Contractual waivers: Changes to rights and obligations under agreements.

Employment waivers: Exceptions concerning internal HR policies, benefits, procedures, or employment terms.

Compliance waivers: Exceptions to internal control requirements, subject to legal restrictions.

Statutory waivers: Requests affecting legislation or mandatory legal requirements, which must undergo legal review and may be impermissible.

B. Establish approval thresholds

For financial waivers, the policy can use monetary limits. For non-financial waivers, it should assess the nature of the risk, affected parties, legal implications, and operational consequences.

For example, a low-value administrative concession may be approved by a manager, whereas a substantial contractual concession may require finance, legal, and executive approval. These thresholds must be set by the organisation rather than assumed to be legally mandated.

C. Require independent review

A person requesting a waiver should not be the sole person approving it. Where the waiver creates a conflict of interest or benefits the approver, the request should be escalated to an independent authority.

D. Set conditions and expiry dates

Every waiver should specify:

The precise requirement being waived.

The reasons for granting the exception.

Its effective date and expiry date.

Any financial, legal, or operational conditions.

Whether renewal is permitted.

Whether the waiver applies only to one transaction or to a continuing arrangement.

E. Maintain an audit trail

The organisation should maintain a central waiver register containing the request, supporting documents, risk assessment, approval history, conditions, expiry date, and any subsequent review.

Periodic audits should identify repeated waivers, unexplained deviations, approval-limit breaches, and attempts to avoid mandatory controls by splitting transactions.

7. Common risks and legal consequences

8. Recommended approval workflow

Step 1: Request submitted

Identify the rule, reason, benefit, and supporting evidence.

Step 2: Initial assessment

Check eligibility, delegated authority, conflicts, and completeness.

Step 3: Legal and risk screening

Determine whether the waiver is legally permissible and assess the consequences.

Step 4: Authorised decision

Approve, reject, request modifications, or escalate to the correct authority.

Step 5: Record and communicate

Document the decision, conditions, responsible owner, and expiry date.

Step 6: Monitor and audit

Track implementation, renewals, recurring exceptions, and compliance.

9. Illustrative example

Suppose an employee requests an exception to a company travel policy because of an urgent client requirement.

The immediate manager verifies the business justification. If the cost exceeds the manager's delegated limit, the request is escalated to the relevant senior authority. Finance assesses the additional expense, and compliance or legal personnel review any applicable restrictions. The authorised decision-maker then approves or rejects the waiver in writing.

If the request instead seeks permission to disregard a mandatory statutory requirement, the hierarchy cannot make that requirement optional simply by escalating the request to the CEO or board.

This illustrates the fundamental distinction between escalating a waiver for approval and establishing that the waiver is legally permissible.

10. Conclusion

An effective waiver approval hierarchy combines delegated authority, risk-based escalation, informed decision-making, documentation, independence, and periodic monitoring. The cited Supreme Court decisions demonstrate why waiver must be analysed carefully, why statutory and constitutional protections cannot automatically be waived, and why authority and intention matter.

The most defensible approach is to ensure that every waiver is:

Permitted by applicable law.

Approved by the correct authority.

Supported by a legitimate and documented reason.

Consistent with objective criteria and relevant rights.

Limited in scope and duration where appropriate.

Subject to audit and accountability.

Legal qualification: These principles are framed primarily with reference to Indian law. The legal effect of a particular waiver depends on the applicable statute, contract, facts, and jurisdiction. The case summaries above are intended for general legal and governance education, not as a substitute for reviewing the full judgments in a specific dispute.