What this page covers
This article explains how the word may is used and understood in planning, law, policy, contracts, and everyday communication. It clarifies common interpretations, limits, and risks, and helps you recognize when may indicates permission, possibility, discretion, or mere aspiration. The guidance is practical and oriented toward reducing ambiguity in both written and spoken contexts.
The core meaning of may
At its most basic level, may signals that something is possible, allowed, or within scope. Unlike must or shall, it does not compel action; unlike can, it is often used to express formal or legal permission rather than pure ability. In contracts and policy documents, may commonly grants discretion rather than imposing an obligation. Understanding this nuance helps prevent confusion between what is permissible and what is required.
Permission vs possibility
In everyday usage, may can mean either permission or possibility, and context determines which reading applies. For example, “You may enter the building” focuses on permission, while “The project may finish next month” focuses on possibility. In formal documents, courts often interpret may as permissive when the text refers to actions a party is entitled to take, but the surrounding terms and purpose can shift that reading. Clear context and consistent terminology reduce the chance of disagreement.
Non‑mandatory language
Because may is non‑mandatory, it rarely creates a binding duty. In contract language, “Party A may deliver the goods” describes a right or option, not a promise to act. In policy and internal guidance, it signals that a course of action is allowed, not required. This differs from “shall” or “must," which typically impose obligations. Treating may statements as discretionary helps set accurate expectations.
How may appears in contracts and legal text
In contracts, the choice between may, shall, and can affects rights and responsibilities. Courts generally treat may as permissive, but poorly drafted clauses can still lead to disputes. Ambiguous cross‑references, inconsistent headings, or shifting definitions can cloud whether a party has a mere option or an implied obligation. Below is a concise comparison of these terms in common contractual contexts.
Contract language quick reference
| Term | Typical legal effect | Common use case |
|---|---|---|
| may | Permission or discretion; non‑mandatory | Granting a right or option, e.g., “The tenant may renew.” |
| shall | Obligation; mandatory | Imposing duties, e.g., “The tenant shall pay rent.” |
| can | Ability or practical possibility | Describing capacity, not necessarily right or duty |
May in policy, procedure, and public communication
In policy documents and public guidance, may often communicates what is authorized rather than what is expected. For example, “Staff may work remotely” indicates that remote work is permitted, not required. This can be useful for flexibility, but it may also leave room for inconsistent implementation. When clarity is essential, writers sometimes replace may with “may, but are encouraged to” or add explicit expectations to align practice with intent.
Practical drafting tips
- Use may when you intend to grant permission or describe a genuine option.
- Prefer shall or must when an action is required.
- Avoid mixing may with mandatory language in the same clause.
- Define key terms if the same word could be read differently in context.
- Review surrounding text to ensure the intended meaning is clear.
Common misinterpretations and risks
Treating may as mandatory can lead to unnecessary pressure or noncompliance claims, while reading it as purely optional can undermine intended rights. In regulations, “may” often limits agency discretion or defines permissible conduct, not aspirational goals. In negotiations, ambiguous “may” clauses can obscure who controls key decisions. Documenting intent and testing clauses in real scenarios reduces these risks.
How context shapes interpretation
The meaning of may depends heavily on audience, document type, and surrounding language. In a customer agreement, “Services may be suspended” likely describes a permitted contingency. In an internal operations manual, the same phrase could prompt questions about consistency and escalation. Considering the reader’s perspective and potential scenarios helps writers choose language that matches their true intent.
When to replace may with stronger language
If discretion is not the goal, consider clearer alternatives. Use shall or must for obligations, and will for firm commitments. For emphasis without compulsion, “is encouraged to” can signal expectation while preserving flexibility. Choose wording that aligns with accountability, auditability, and the expectations of all parties.
Quick guidance at a glance
| Goal | Recommended wording | Effect |
|---|---|---|
| Grant option or permission | may | Non‑mandatory; allowed but not required |
| Impose duty | shall or must | Creates obligation |
| Describe ability | can | Describes capacity, not policy |
| Encourage without mandating | is encouraged to | Signals preference, not requirement |
Final notes
May is a versatile word, but in formal and legal contexts its flexibility can be both useful and risky. Understanding how courts, policies, and teams typically interpret it allows you to use more precise language and avoid misunderstandings. Review documents for ambiguous uses of may, align wording with intent, and when in doubt, replace vague language with terms that clearly reflect whether an action is required, permitted, or optional.
References and further reading
- Plain Language Association International, “Legal drafting and defined terms.”
- Bryan A. Garner, “Black’s Law Dictionary” (standard definitions of “may” and “shall”).
- American Bar Association, “Contract drafting best practices.”
- ISO recommendations for clarity in procedural documents.
Related topics
Explore related guidance on contract language, policy drafting, plain language, and obligations vs. permissions to refine how you communicate conditions and choices.