Board resolutions document company decisions and prove authority. They are used for officer appointments, bank accounts, equity issuances, major contracts, financings, acquisitions, compensation, option grants, related-party transactions, policy approvals, and delegations. A good resolution identifies the decision, authority, approvals, materials reviewed, conflicts, signatures, and implementation owner.
This article is part of the Corporate Law pillar. Use the pillar page to explore the full topic cluster and related Kurums Law guides.
A board resolution can look like paperwork until someone asks whether a company action was actually authorized. Banks, investors, buyers, auditors, regulators, counterparties, and courts may all ask for proof. A resolution is the company speaking through its governing body.
This guide supports the Corporate Law pillar by explaining how board approvals should be drafted and maintained.
Key Takeaways
Resolutions prove authority
They show that the board or required decision-makers approved the action.
Context matters
Minutes or consents should reflect materials reviewed, conflicts disclosed, and approval basis.
Templates need customization
The approval language should match the company documents, statute, and transaction.
Implementation should be assigned
A resolution should authorize officers or managers to execute documents and take follow-up actions.
What is a board resolution?
A board resolution is a formal written record of a decision approved by a board of directors or similar governing body. It may be adopted at a meeting or by written consent, depending on the governing documents and applicable law.
The resolution should identify the company, date, approving body, action approved, authority granted, documents reviewed, officers authorized, and any special conditions. For important matters, the surrounding minutes should record discussion, conflicts, and materials considered.
When are board resolutions needed?
Common uses include appointing officers, opening bank accounts, entering material contracts, borrowing money, issuing equity, approving option grants, adopting policies, approving budgets, acquiring or selling assets, approving mergers, authorizing litigation, and approving related-party transactions.
Not every operational act needs a board resolution. The point is to document matters that require board authority, exceed delegated authority, affect ownership, create significant obligations, involve conflicts, or are likely to be requested by third parties.
What should a resolution include?
A resolution should include background recitals where useful, the specific approved action, the documents approved, the officers authorized to sign, power to make non-material changes, authority to take related actions, and a record of voting or unanimous consent.
For transactions, attach or identify the final agreement. For equity, include number and class of shares, price, recipient, vesting if relevant, securities law basis, and cap table update. For debt, include lender, principal amount, maturity, collateral, guarantees, and signing authority.
How should conflicts be handled?
If a director, officer, founder, investor, or affiliate has a personal interest in the transaction, the record should show disclosure and appropriate process. Depending on law and documents, conflicted persons may abstain, independent directors may approve, shareholders may ratify, or fairness evidence may be gathered.
A conflict does not always prohibit action, but undocumented conflicts create avoidable risk. Good minutes should show that the board knew the relevant facts and followed the required approval path.
How should resolutions be stored?
Resolutions should be kept with minutes, written consents, attachments, signature pages, notices, waivers, and evidence of delivery where relevant. A searchable minute book is much better than scattered PDF files in email.
The company should also update related records after approval. Equity approvals should update the ledger and cap table. Officer appointments should update signing authority. Bank resolutions should match bank mandates. Contract approvals should match final signed agreements.
Practical governance checklist
A practical corporate law file should show who made the decision, what authority they had, which documents were reviewed, which approvals were required, which conflicts were considered, and how the decision was recorded. This is not only useful for disputes. It helps investors, lenders, auditors, tax advisers, acquirers, and future directors understand what the company actually did.
For this topic, the main control areas are Vague approval, Wrong approving body, Missing conflict record, No implementation authority, Poor storage. Each should have an owner, evidence standard, escalation trigger, and document location. If the company cannot quickly locate its charter documents, ownership ledger, board approvals, shareholder consents, material contracts, option records, and conflict disclosures, the legal structure is weaker than it looks.
Corporate governance also needs a rhythm. Annual approvals, periodic cap table review, officer appointments, delegated authority updates, related-party transaction checks, insurance review, subsidiary records, and contract authority policies should not wait until a financing, dispute, tax audit, or sale process. The quiet periods are when cleanup is cheapest.
Common mistakes companies make
The first mistake is treating entity formation as the finish line. Formation creates the legal container, but governance keeps the container reliable. Missing minutes, outdated registers, unsigned consents, inconsistent ownership records, informal side promises, and undocumented approvals can create avoidable risk when the company raises capital, sells equity, borrows money, hires executives, issues options, or enters a dispute.
The second mistake is copying documents from another company without matching economics, tax, control, investor expectations, exit strategy, or jurisdiction. A startup corporation, family-owned LLC, professional services firm, joint venture, acquisition vehicle, and holding company need different governance controls. The documents should match the business model, not a template search result.
The third mistake is ignoring conflicts. Director, officer, founder, manager, investor, and affiliate conflicts do not always make a transaction invalid, but they require process discipline. Disclosure, abstention, independent approval, fairness review, and clean minutes can turn a risky decision into a defensible one.
Decision questions before approval
Before signing or approving a corporate action, ask who has authority, whether approval thresholds are met, whether anyone has a conflict, whether notices are required, whether tax or securities rules are implicated, whether third-party consent is needed, whether the action affects ownership or control, and whether the record will make sense six months later.
The workflow should follow this path: Identify action -> Prepare materials -> Approve -> Record -> Implement. A person outside the transaction should be able to open the file and understand the facts, the legal authority, the approval path, the decision, and the follow-up owner. If that cannot be done, the file is not ready for a financing, diligence request, shareholder dispute, or board review.
Good governance protects speed. When authority matrices, consent templates, board calendars, capitalization records, and document repositories are clean, ordinary matters move faster because teams do not need to reconstruct basic facts. Legal attention can then focus on strategic matters rather than housekeeping.
Investor, lender, and buyer diligence expectations
Corporate records are often judged by people who were not present when the business was built. Investors want to know whether the cap table is real. Lenders want to know whether debt was authorized. Buyers want to know whether equity, contracts, intellectual property, employees, taxes, and approvals are clean. Auditors want evidence, not explanations. The company should prepare records for that audience before pressure appears.
A diligence-ready file usually includes formation documents, bylaws or operating agreement, amendments, ownership ledger, securities issuances, option or incentive records, board and shareholder approvals, investor rights, debt documents, major contracts, IP assignments, employment and contractor agreements, tax registrations, licenses, litigation records, insurance, and compliance policies. Each document should be final, signed where required, dated, and stored in a stable location.
The most common diligence friction is not a dramatic legal violation. It is inconsistency. A board consent says one number of shares, the cap table says another, the option platform shows a third, and the finance model assumes something else. A founder assignment is missing. A customer contract was signed before officer authority was documented. A related-party transaction was approved informally. These issues consume deal time and reduce trust.
Documents to keep current
The company should maintain a small group of living documents. The cap table should reflect issued equity, convertible instruments, options, warrants, vesting, repurchases, transfers, and cancellations. The authority matrix should show who can sign which contracts, hire employees, approve spending, open bank accounts, borrow money, issue equity, and settle disputes. The minute book should show approvals for major actions.
The contract register should identify agreements that require consent for assignment, change of control, debt, exclusivity, non-compete, most-favored customer terms, data processing, audit rights, or termination. The IP register should track inventions, assignments, licenses, open source use, trademarks, domains, and contractor contributions. The subsidiary register should track local directors, registered agents, annual filings, licenses, and intercompany agreements.
Keeping these documents current reduces legal cost. Lawyers spend less time reconstructing history and more time advising on the actual decision. It also improves management quality because leadership can see ownership, authority, obligations, and restrictions in one place.
Red flags that require legal review
Certain events should automatically trigger legal review: issuing or transferring equity, changing voting rights, hiring a senior executive, entering a related-party transaction, borrowing money, granting security, approving unusual compensation, selling major assets, changing tax classification, entering a joint venture, acquiring a company, receiving an investor term sheet, or discovering a cap table error.
Other red flags are quieter. A shareholder asks for company records. A departing founder claims promised equity. A director has a personal interest in a vendor. A customer asks for change-of-control consent. A bank asks for certified resolutions. A buyer asks for all board minutes. A regulator asks who controls the company. These are signals that governance records need to be accurate before the response is sent.
The response should be measured. Not every red flag means the company is in trouble, but it does mean the file should be reviewed. A clean corrective approval, ratification, amendment, waiver, disclosure, or updated record may solve the issue if handled early. Waiting until a dispute or closing deadline usually makes the same issue more expensive.
As a final check, every material corporate action should answer four questions in writing: who had authority, what exactly was approved, what evidence supports the decision, and who is responsible for implementation. This small discipline makes the file easier to trust.
It also reduces avoidable rework during financing, lending, acquisition, audit, and shareholder review processes.
That consistency is valuable even when no dispute ever happens.
Board resolution quality table
Board approval workflow
Identify action
Determine whether board, shareholder, member, or manager approval is required.
Prepare materials
Collect agreements, summaries, financials, conflict disclosures, and recommendations.
Approve
Hold meeting or written consent under governing documents and law.
Record
Finalize minutes, resolutions, signatures, attachments, and voting record.
Implement
Sign documents, update ledgers, notify parties, and store records.
Related Kurums Law guides
- Kurums Law department – the main legal hub for business-focused legal guides.
- Corporate Law pillar – for governance architecture.
- Director Duties – for fiduciary decision process.
- Mergers and Acquisitions Law – for transaction approvals.
Official reference points
- Delaware General Corporation Law board provisions – official Delaware code subchapter on directors and officers.
- Delaware corporate law business judgment overview – official discussion of board management and business judgment.
FAQ
Discover more from Kurums | Business Intelligence
Subscribe to get the latest posts sent to your email.


