A contract approval process is a short, written answer to four questions. Who approves the business terms? When does an agreement need a second read from a lawyer or another specialist? Who is allowed to sign it? And who keeps the signed copy and tracks the dates buried inside it?
That is the whole thing. Four answers, written down, so your own team knows them.
When they are not written down, the person closest to the deal makes all four calls alone, usually against a deadline. Your company can end up owing money nobody else discussed, and there is no record of who said yes. Everyone else may not find out until the invoice or the renewal shows up.
Four answers do not require four people. In a ten-person company, the same founder can approve the terms, decide nobody else needs to read it, sign it, and save the file. That works fine. The trouble starts when nobody can tell which of the four got skipped.
The four answers on one page
| Question | Who answers it | What gets written down |
|---|---|---|
| Are these business terms ones we want? | The person responsible for the budget or the revenue this deal touches | What we owe, what we get paid, how long it runs, how we get out |
| Does this one need a second read? | Decided by a short list you agree on in advance, not deal by deal | Why it needed a read, and who read it |
| Who signs? | Named roles, checked against your own governing documents | Who signed, and the date |
| Who keeps it and watches the dates? | Whoever owns the shared file | Final signed copy, amendments, renewal and notice dates |
The same name can go in every row. What matters is that each row has an answer. If you do nothing else today, put a name and a one-line answer in each row, then read on to see which of your answers are thin.
What goes wrong without a process?
Here is a hypothetical. It is not an account of any real company.
An operations manager needs a software tool and signs the vendor's order form. The form runs for one year. It renews for another year unless the customer cancels at least 90 days before the renewal date, the price goes up 10 percent on each renewal, and the cancellation notice has to go to one specific address. Nobody writes down the renewal date. Nobody saves the address.
If those stated terms apply as written, the cancellation window closes before anyone looks at it, and the company is into a second year at 10 percent more than the first. Nothing went wrong in the negotiation. A capable person did their job. The commitment just never passed anyone who would have asked a second question or put a date on the calendar.
Whether any particular email or order form legally binds a company, and whether a renewal or notice clause like this one holds up, depends on the facts and on the law that governs it, including notice and auto-renewal rules that can vary by state. That is a question for counsel on the actual documents, not something to assume in either direction. What you can control is whether your own side knew the commitment was being made.
What should the team check before approving business terms?
Business approval answers one question: are these obligations ones we want and can keep? It is not a legal review, and the person doing it does not need to be a lawyer.
The terms worth slowing down for are usually the ones that outlive the signature:
- What exactly are we on the hook to deliver, by when, and what happens if we are late?
- What are we actually getting paid, after discounts, credits, and anything we promised to throw in for free?
- How long does this run, and does it renew on its own?
- If this goes badly, how do we get out, and what does getting out cost?
That last one is the easiest to leave unanswered, and it is the one the hypothetical above turns on. An automatic renewal plus a notice window means a date makes the decision, not a person, unless somebody owns that date.
When should an agreement get a second read?
Not every contract needs a lawyer. Treat every purchase order as a legal matter and the process gets quietly abandoned by month two. So sit down with whoever will do the reading and agree on a short list of situations that call for it. Write the list down. Everything that is not on the list moves without a specialist read, under that agreed rule.
Things a growing company can usually spot in its own numbers and paperwork:
- the deal is large next to your revenue
- the term runs long, or renews on its own
- the agreement touches customer data or personal information
- it assigns or licenses your intellectual property
- it caps the other side's responsibility and leaves yours open
- it includes an indemnity, meaning a promise to cover someone else's losses
- it is governed by the law of a state you have never dealt with
- the counterparty handed you a form and said it cannot be changed
The reader is not always a lawyer. A security questionnaire may belong with whoever runs your systems. A revenue-recognition question belongs with your accountant. Sending everything to a lawyer by default slows the deal and often does not answer the question that was actually asked.
Then decide what happens when one of these situations comes up and the reviewer is unavailable. Either the deal waits, or someone you name in advance can say it goes ahead without that second read. Naming that person settles who answers for the holdup on the business side. It does not by itself give them legal authority to sign, which is a separate question and the subject of the next section.
Pick your own thresholds. There is no universal dollar figure here, and any number in an article would be a guess about your business. A $50,000 commitment is routine for one company and a serious risk to the quarter for another. Whether the reading comes from inside the company or from outside is a separate decision, worked through in when to hire your first general counsel and fractional GC versus law firm versus in-house. Recurring contract work of this kind is the ordinary subject matter of outside general counsel support.
How do you know who can sign for the company?
Signing authority is the third answer, and it looks obvious until someone actually asks who gets to sign.
Start in two places: your own governing documents, and the law of the state where the company was formed. Other law can matter too, depending on the facts, which is a question for counsel rather than something this general illustration can resolve for every entity type and every state.
What follows is narrow on purpose. Both points are about limited liability companies and their members only, not about managers, officers, employees, or corporations, and only in two specific places. For any other entity type, any other state, or any other role inside the company, the question belongs with counsel reading your actual documents.
Under Maryland Corporations and Associations Section 4A-401, each member of an LLC is by default an agent of the company for the purpose of its business. That default can be displaced by the operating agreement, which is the contract among the owners about how the company runs.
The default can also be narrowed if the articles of organization, the formation document filed with the state, contain a statement that a member has no authority solely by virtue of being a member. Even where that statement is in place, the law leaves room for someone dealing with the company to argue that a member in fact had authority, or that the company should not be allowed to deny it after the fact.
D.C. Code Section 29-803.01 starts from the opposite default. A member of a DC LLC is not an agent of the company solely by reason of being a member. That does not shield the company from liability. Other law can still hold the company responsible for what a member did.
Two jurisdictions a few miles apart, one entity type, two different starting points. Which is the practical reason to write down who may sign instead of assuming everyone already knows.
One thing a written policy cannot do is decide whether a contract is binding. Your internal rule does not by itself void an agreement someone signed outside the rule, and it does not guarantee that an agreement signed inside the rule is enforceable. What it does is make your own side predictable, which is the part you actually control.
What should you keep and track after signing?
Signed agreements have a way of living in the inbox of whoever closed the deal. Then that person leaves.
Pick one shared place where the final signed version lives, named so someone who was not in the deal can find it. Pull the dates out of the document and onto a calendar: start, end, renewal, and the deadline to give notice if you do not want the renewal. Note who approved it and who signed it. Keep the amendments and side letters next to the original, because a contract plus three email changes nobody saved is a contract you cannot actually read.
A shared folder and a spreadsheet carry all of that. Add a tool when the manual version stops keeping up, not before you know what you are tracking.
Is your process good enough? Four questions to ask internally
Can you name who approved your three largest commitments? If working that out takes more than a few minutes, the gap is in your records, not your judgment.
What is on the written list that calls for a second read? If the list only exists in one person's head, it stops working the first week that person is on vacation.
Does your signing practice match your own governing documents? If your company is an LLC, hold the last three agreements you signed up against your operating agreement and articles of organization. If it is organized another way, ask counsel which of your documents sets signing authority before you write the rule.
For each renewal in the next two quarters, who gets told, and how long before that contract's notice deadline? The reminder date comes from the contract's own notice window, not from a standard number. A 90-day window and a 30-day window are different calendar entries.
What changes depending on your seat?
For founders
You are the one who sets the list. Set it too low and you will be reading purchase orders all week. Set it too high and commitments you would have wanted to see go past you. Every review step buys you information and costs you some speed, and that trade is yours to make.
For business owners and operators
This one lives in your software subscriptions and your renewal calendar. Auto-renewing tools, price increases, notice windows: those are the line items nobody looks at until they land. The person who owns the budget is usually the right person to own the dates.
For investors and boards
If an investor or acquirer asks for signed agreements, the approvals behind them, and the obligations that survive a change of control, the company either pulls them out of its records or pieces them back together from memory. Deciding now where those three things live is what makes the first answer possible.
What to put in place first
- If you cannot currently find every signed customer and vendor agreement, build the shared folder and the date list before you write any policy. A policy over missing documents is decoration.
- Put the renewal date, the notice deadline, and the notice address from each live agreement on one calendar, each with a named owner.
- If a routine contract has been sitting unsigned for a week while people wait for permission nobody defined, name the approver for that category this week and tell the team.
- If your list of situations calling for a second read is not in writing, write the first version in one sitting, keep it to a handful of items, and agree it with whoever will do the reading.
- Decide what happens when one of those situations comes up and the reviewer is out: the deal waits, or a named person says it can move forward without that second read. That settles who answers for the holdup; it is not a grant of signing authority.
- Read your own governing documents against the last three agreements you signed, and take any mismatch to counsel instead of fixing it by assumption.
- Revise the list the first time it sends you something that did not need review, and the first time something slips past it.
Where to start
Start with the narrowest version that puts a name against each row of the table above. Then let one month of real deals show you where the rule is wrong.
The real test comes later, the first time someone needs an answer faster than the rule allows. You can change the rule, in writing, and tell people you changed it. Or you can let that one deal go around it, in which case the next person is likely to do the same thing and stop mentioning it. The second path risks costing you the records, and you may not notice until an investor, a renewal, or a departing employee asks a question you cannot answer.
Questions founders ask about contract approval
Does every contract need legal review?
No. Reviewing everything is how a process gets abandoned. Sit down with whoever will do the reading and agree on a short written list of situations that call for it, such as size relative to your revenue, long or auto-renewing terms, customer data, intellectual property, indemnities, or a form the other side says cannot be changed. Everything outside that agreed list moves without a second, specialist read.
Who should be allowed to sign contracts at a small company?
That depends on your own governing documents and on the law of the state where you formed the company, which is why the answer is not the same everywhere. A single founder signing everything can be a legitimate operational design at small scale, provided the rule is written down and matches what the company's own formation documents and governing state law actually say.
Do we need contract management software?
Not to start. A shared folder for final signed copies, a spreadsheet with renewal and notice dates, and a note of who approved and who signed will do the work. Add a tool when the manual version stops keeping up.
Should we set a dollar threshold for approval?
A threshold can help, but there is no universal number, and any figure borrowed from an article is a guess about your business. Set it against your own revenue and cash position, and pair it with triggers that have nothing to do with price, because expensive terms show up in small contracts too.
If someone signs outside our policy, is the contract still binding?
Your internal policy governs your own team. It does not by itself void an agreement, and following it does not guarantee that an agreement is enforceable. Whether a particular contract binds the company depends on the facts, the documents, and the governing law, which is a question to put to counsel rather than answer from a policy document.
This article is for informational purposes only and does not constitute legal advice. Every company's situation is different, and you should consult with qualified legal counsel before making compliance decisions based on the developments discussed here.