Board Resolution Approving the Award of a Contract Template

In plain language: States whether the resolution was passed at a duly convened board meeting or by written consent in lieu of meeting, records the date, and confirms quorum or unanimous agreement.

Common mistake: Failing to confirm quorum in the preamble. If the resolution is later challenged, the absence of a quorum statement can render the resolution voidable under most corporate statutes.

In plain language: Provides factual background — what contract is being approved, who the counterparty is, why the board is being asked to act, and any prior actions or recommendations that led to this resolution.

Common mistake: Using vague recitals that do not identify the specific contract or counterparty. If a dispute arises about which agreement was approved, an undescriptive recitals block provides no guidance.

In plain language: The core 'RESOLVED THAT' statement formally authorizing the corporation to enter into and execute the specified contract — the sentence that creates the legal authority.

Common mistake: Drafting the operative clause without referencing the attached contract or a description specific enough to identify it. A generic 'any contract with Counterparty' clause may authorize far more than the board intended.

In plain language: Identifies by name and title the specific officer or officers empowered to sign the contract and any ancillary documents on the corporation's behalf.

Common mistake: Naming only a title without a name, or naming only a name without a title. Counterparties and their lawyers need to verify the signatory's authority, and an ambiguous designation creates friction at closing.

In plain language: Clarifies the extent of the authorized signatory's powers — whether they can negotiate final terms, approve amendments, and execute ancillary documents, or only sign the contract as presented.

Common mistake: Granting unlimited authority without any qualification. An open-ended scope clause can expose the corporation to liability for side agreements or amendments the board never reviewed.

In plain language: Specifies the contract subject matter, the counterparty, the total contract value or budget authorization, and the term or delivery timeline so the resolution is self-contained as a record.

Common mistake: Omitting the contract value or cap. A board resolution that approves a contract without stating the financial commitment provides no financial-control record and may not satisfy audit or lender requirements.

In plain language: States the date on which the resolution and the authority it grants take effect — which may be the date of the meeting, the date of signing, or another specified date.

Common mistake: Leaving the effective date blank or stating it as 'immediately.' Counterparties and auditors need a specific date for their records, and an undated resolution can complicate enforceability analysis.

In plain language: A statement, typically signed by the corporate secretary or chair, certifying that the resolution was duly adopted, that the signatures are genuine, and that it is a true extract from the minute book.

Common mistake: Omitting the certification entirely when the resolution is sent to a counterparty or lender. Without a certification, the recipient has no assurance that the resolution was actually adopted or that it has not been superseded.

In plain language: Signature blocks for the required number of directors — or all directors in the case of a written consent — confirming their vote or written approval of the resolution.

Common mistake: Collecting only one director's signature when the bylaws or applicable statute require a majority or specific quorum. A single signature does not constitute a board resolution in most jurisdictions.

A board resolution approving the award of a contract is a formal written decision by a company's board of directors authorizing the organization to enter into and execute a specific contract with a named counterparty. It identifies the contract, designates the officer authorized to sign, and becomes part of the corporate minute book as permanent evidence of the board's decision. Most corporate bylaws and many counterparties require one before a major contract can be validly executed.

A board resolution is typically required when the company's bylaws set a monetary or strategic threshold above which board approval is mandatory — commonly $50,000–$250,000 for mid-sized companies. It is also required when a counterparty, lender, or government agency demands evidence of corporate authorization, when the contract involves real property or intellectual property, or when corporate statutes in the applicable jurisdiction mandate it for specific transaction types.

In most jurisdictions, an officer with apparent or actual authority — typically a CEO or president — can bind the corporation to routine contracts without a board resolution. However, for material contracts, most bylaws require board approval above a defined threshold. Even where not strictly required, a counterparty who requests evidence of authority will expect a board resolution, and signing without one creates enforceability risk if the officer's authority is later disputed.

A board resolution is typically adopted at a duly convened meeting of the board where directors vote in person, by phone, or by video. A written consent — sometimes called an action by unanimous written consent — achieves the same result without a meeting, provided all directors (or, in some jurisdictions, a majority) sign the consent document. Both have the same legal effect; the written consent is faster but requires every director's signature rather than just a quorum.

Notarization is not required in most jurisdictions for a standard board resolution to be valid. The certification by the corporate secretary typically provides sufficient authentication for counterparties and lenders. However, certain government contracts, real property transactions, and cross-border filings may require a notarized or apostilled resolution — confirm the counterparty's requirements before finalizing the document.

A post-execution resolution functions as a ratification, not an authorization, and ratification is subject to additional legal requirements in some jurisdictions — including that the board had the power to approve the act at the time it was taken. Some counterparties and most lenders will not accept a retroactive resolution as equivalent to a pre-execution authorization. The correct practice is to adopt the resolution before the contract is signed.

Board resolutions should be retained permanently as part of the corporate minute book. There is no statute of limitations that allows corporate governance records to be destroyed — lenders, acquirers, and regulators routinely request resolutions going back five to ten years or more during due diligence or audits. Store certified copies with the executed contract they authorized.

No — many companies adopt a standing delegation-of-authority policy that authorizes specific officers to execute contracts within defined parameters (e.g., up to $100,000, for terms not exceeding two years, with approved vendors) without requiring a separate resolution each time. A specific board resolution is needed for contracts that exceed those delegated thresholds, involve new counterparties not covered by the policy, or are otherwise flagged as requiring board review.

A contract executed without required board approval may be voidable by the corporation on the grounds that the signatory lacked authority. Whether the corporation can actually void it depends on whether the counterparty had knowledge of the authority limitation and whether the doctrine of apparent authority applies. Courts in most jurisdictions protect good-faith counterparties who relied on reasonable indications of authority — meaning the corporation may be bound regardless, while the officer who exceeded their authority faces internal liability.