Every small business eventually hears, "Can we make an exception this time?" The request may be reasonable. The danger is answering from loyalty, pressure, or convenience without deciding what the exception means for everyone who follows the normal process.
An exception should be handled as a documented decision, not as a favor that quietly rewrites the rules.
First identify the rule and who owns it
Write the exact rule the person wants to bypass. Then label it:
- company policy;
- legal, safety, or compliance requirement;
- team operating process; or
- personal preference.
You can’t grant an exception to a rule you don’t control. Company return terms, product-claim restrictions, privacy requirements, and compensation rules belong with the authorized source or decision maker.
If the request belongs to official support, route it there. Do not promise approval. Explain the verified process and when you’ll return with information.
Ask what problem the exception is solving
An exception request often points to one of three conditions:
- The rule works, but this situation genuinely falls outside its assumptions.
- The rule is sound, but the team failed to explain or apply it.
- The rule itself makes the work unnecessarily difficult and may need revision.
Do not decide which one is true from the person's urgency alone. Gather the minimum facts: what happened, what the normal process would do, who would be affected, and what risk changes if you depart from it.
Use the repeatability question
Before approving a team-level exception, ask: would I make the same decision for another person in the same conditions?
If the honest answer is no, the decision may be favoritism rather than judgment. If the answer is yes, write the conditions clearly enough that another leader could reach the same result.
Repeatability does not require rigid treatment of different situations. It requires a reason that survives the person's identity, rank, friendship, or sales volume.
That standard belongs beside the test in Can a New Teammate Repeat the System Without You?. Another leader can’t follow the process if every difficult case requires a private conversation with the person who created it.
Record the decision without creating a secret rule
For a team-controlled process, record:
- the rule;
- the condition that justified review;
- the decision and owner;
- the customer or operational risk considered;
- whether the process changes for the future; and
- the date for review.
Protect personal and customer information. The decision log needs the reason for the decision, not a collection of private details.
Tell the affected person what was decided, what remains unchanged, and whether this is a one-time response or a new process. Ambiguity invites the story, "They did it for someone else," to become the next team's unofficial policy.
Decide whether the process needs repair
One rare exception may reveal nothing beyond a rare case. Repeated exceptions around the same step mean the process deserves review.
Do not keep praising flexibility while forcing people to request special treatment every week. Change the process if a clearer, fairer method can handle the recurring condition without violating a controlling rule.
Use the business asset inventory as a related check: if exceptions live only in one leader's memory, the business has not built a usable system.
The right answer is not always yes or always no. It is a decision whose authority, reason, risk, and future effect are visible. That is how flexibility serves people without turning the operating method into a collection of private favors.
