Documentation Standards for Exceptions

Documentation standards for exceptions refer to the rules and practices used by an organisation to record, justify, approve, review, and preserve instances where a normal policy, procedure, control, contractual requirement, or established practice is not followed. An exception may arise because of an emergency, special employee circumstance, operational necessity, management decision, statutory requirement, or other legitimate reason.

Proper exception documentation is important because it creates an audit trail showing what happened, why the ordinary rule was not followed, who authorised the departure, what risks were considered, and what corrective or preventive action was taken.

1. Meaning of an Exception

An exception is a departure from an established rule or standard. In an employment context, examples may include:

• permitting an employee to work outside the normal attendance policy;
• approving leave outside ordinary limits;
• making an exception to recruitment criteria;
• allowing a different performance target for a particular employee;
• deviating from a disciplinary procedure because of urgent circumstances;
• making an exception to an internal financial or procurement control;
• permitting remote work despite a general office-attendance requirement.

An exception should not ordinarily be treated as an informal or undocumented managerial decision. Where the decision may affect an employee's rights, benefits, duties, evaluation, or disciplinary position, adequate documentation becomes particularly important.

2. Identification of the Rule From Which an Exception Is Made

The record should clearly identify the ordinary rule or policy that would otherwise apply.

For example, an exception record may state:

• name of the policy;
• relevant policy clause;
• normal requirement;
• date on which the exception arose;
• person or department affected.

This prevents later uncertainty about whether an exception actually occurred.

3. Written Reasons for the Exception

The most important element is the reason for granting the exception.

The documentation should explain the factual circumstances rather than merely stating that management "approved an exception."

Relevant reasons may include:

• emergency circumstances;
• operational necessity;
• employee-specific circumstances;
• business continuity;
• statutory or regulatory requirements;
• technical difficulties;
• unavoidable delay;
• safety considerations.

The reasons should be supported by available records wherever appropriate.

4. Authority and Approval

The document should identify who authorised the exception and whether that person had authority under the applicable policy.

An effective exception record normally contains:

1. person requesting the exception;
2. person recommending it;
3. person approving it;
4. date of approval;
5. duration of the exception;
6. conditions attached to the approval.

This is particularly important where an employee later challenges the decision or alleges unequal treatment.

5. Objective and Consistent Criteria

Exceptions should not be granted arbitrarily. Organisations should establish objective criteria for deciding when an exception can be made.

For example, if an organisation permits exceptions to a performance target, it should identify circumstances that may justify such treatment and apply those criteria consistently.

Otherwise, inconsistent exceptions may create allegations of:

• discrimination;
• favouritism;
• arbitrariness;
• victimisation;
• unequal treatment;
• breach of contractual or statutory obligations.

6. Supporting Evidence

Where an exception is based on specific facts, relevant evidence should be preserved.

Depending on the circumstances, this may include:

• emails;
• attendance records;
• medical or leave-related records where lawfully relevant;
• performance records;
• meeting minutes;
• written employee explanations;
• management approvals;
• investigation reports;
• photographs or inspection records;
• system logs.

Documentation should be limited to information that is genuinely necessary and should be handled in accordance with applicable privacy and employment requirements.

7. Duration and Scope

An exception should normally specify whether it is:

• one-time;
• temporary;
• recurring;
• permanent;
• limited to a particular employee;
• applicable to a particular department;
• applicable only to a specific transaction or event.

A temporary exception should preferably contain an expiry or review date.

8. Conditions Attached to the Exception

Management may impose conditions to reduce the risks created by departing from the normal procedure.

For example:

"The employee may work remotely for two weeks, subject to daily reporting and submission of the required work records."

Such conditions should be recorded along with the approval.

9. Risk Assessment

Where the exception could create legal, financial, operational, or employment risk, the organisation should record the risks considered and the measures adopted to control them.

This is especially important for exceptions involving:

• statutory compliance;
• employee safety;
• disciplinary proceedings;
• financial controls;
• recruitment;
• confidential information;
• working hours;
• health and safety.

10. Review and Closure

Exception documentation should not end with approval. The organisation should record whether the exception was later reviewed and whether it should:

• continue;
• expire;
• be modified;
• be withdrawn;
• become part of the regular policy.

A closure record creates a complete audit trail.

Legal Importance of Exception Documentation

Indian courts have repeatedly emphasised the importance of fairness, non-arbitrariness, natural justice, proper procedure, and evidence-based decision-making. Although these cases do not all concern an "exception documentation policy" in the narrow sense, their principles are highly relevant to situations where an employer or public authority departs from an established rule.

1. E.P. Royappa v. State of Tamil Nadu, (1974) 4 SCC 3

The Supreme Court established that arbitrariness is fundamentally inconsistent with equality under Article 14.

The principle is relevant to exception management because an employer or public authority should be able to demonstrate why one person received treatment different from the normal rule. Proper documentation helps establish that the exception was based on rational and relevant considerations rather than personal preference.

2. Maneka Gandhi v. Union of India, (1978) 1 SCC 248

The Supreme Court significantly expanded the requirement of fairness and reasonableness in administrative action.

Where a decision affects rights or interests, the procedure adopted cannot be arbitrary or unfair. Documentation of the circumstances, reasons, and decision-making process therefore becomes important when an exception affects an employee or another individual.

3. Mohinder Singh Gill v. Chief Election Commissioner, (1978) 1 SCC 405

The Supreme Court stressed that when an authority makes a decision, the validity of the decision must generally be assessed on the basis of the reasons reflected in the decision itself rather than unsupported explanations supplied later.

This principle demonstrates why the reasons for an exception should be recorded at the time the decision is made. Creating reasons retrospectively can seriously weaken an organisation's position in litigation.

4. S.L. Kapoor v. Jagmohan, (1980) 4 SCC 379

The Supreme Court recognised the importance of natural justice, particularly where a decision has serious adverse consequences.

Where an exception involves an employee's rights, disciplinary status, employment conditions, or other adverse consequences, documentation should show whether the affected person was given an appropriate opportunity to respond.

5. Union of India v. Tulsiram Patel, (1985) 3 SCC 398

The Supreme Court considered circumstances in which the ordinary requirements of natural justice may legitimately be excluded in disciplinary matters.

The case is relevant because it demonstrates that departure from an ordinary procedure may sometimes be legally permissible, but the circumstances justifying that departure matter. An organisation should therefore document the exceptional circumstances and the legal or policy basis for departing from the ordinary process.

6. Shrilekha Vidyarthi v. State of U.P., (1991) 1 SCC 212

The Supreme Court emphasised that State action, including actions involving contractual relationships, cannot simply be arbitrary.

For organisations subject to public-law standards, this reinforces the importance of maintaining objective records when making decisions that depart from established practices.

7. Kranti Associates Pvt. Ltd. v. Masood Ahmed Khan, (2010) 9 SCC 496

The Supreme Court strongly emphasised the importance of recording reasons in judicial and administrative decision-making.

The Court explained that reasons promote transparency, accountability, and meaningful judicial review. This principle is particularly useful for exception documentation because the record should explain why the ordinary rule was not followed.

8. Siemens Engineering & Manufacturing Co. of India Ltd. v. Union of India, (1976) 2 SCC 981

The Supreme Court stressed the importance of reasoned orders in administrative decision-making.

A documented exception should therefore not merely say "approved." It should identify the factual basis and reasons supporting the departure from the normal requirement.

Essential Elements of an Exception Record

A practical exception form can contain the following fields:

Importance in Employment Disputes

Exception documentation can become important evidence in disputes concerning:

• termination;
• disciplinary action;
• poor performance;
• promotion;
• recruitment;
• salary and benefits;
• attendance;
• leave;
• workplace accommodations;
• discrimination or unequal treatment;
• contractual obligations;
• internal investigations.

For example, if an employer normally requires a particular performance target but permits an employee to operate under a different target, the employer should record why the deviation was permitted and whether similar circumstances received similar treatment.

Conversely, if an employee is denied an exception that was previously granted to similarly situated employees, the organisation may need to explain the distinction.

Conclusion

Documentation standards for exceptions provide a structured method for recording departures from ordinary rules and procedures. A sound system should identify the normal rule, explain the reason for the departure, record supporting evidence, obtain approval from an authorised person, specify the scope and duration, assess risks, and provide for review and closure.

The principles reflected in E.P. Royappa, Maneka Gandhi, Mohinder Singh Gill, S.L. Kapoor, Tulsiram Patel, Shrilekha Vidyarthi, Kranti Associates, and Siemens Engineering demonstrate why decisions affecting rights or interests should be fair, reasoned, non-arbitrary, procedurally appropriate, and capable of being justified from contemporaneous records. Proper documentation therefore serves not merely an administrative function but also an important evidentiary, compliance, governance, and litigation-management function.