You signed it in five minutes, standing at the HR desk, with a pen someone already handed you. The fine print wasn't written for you — it was written against the day you'd want to quit, complain, or ask for what you were promised verbally. An employment contract isn't paperwork. It's the one document that decides what happens the moment there's a conflict between you and your employer. And almost always, only one side wrote it.

Here's the good news: the language in these documents isn't magic. It repeats across companies and industries, because lawyers copy templates from each other — templates built to favor the employer. Learn a dozen patterns once, and you'll recognize them in every contract that lands on your desk afterward.

Who's holding the pen

The first thing to understand: the contract isn't drafted by a neutral third party. It's drafted by the company's lawyer, whose job is to protect the company, not balance the interests of both sides. This isn't a conspiracy — it's just incentives. The lawyer is paid by the employer, and their success metric is minimizing the company's risk and obligations, not yours.

That gives you a simple reading rule. Any phrase that sounds vague — "at the company's discretion," "as reasonably determined," "as needed," "in accordance with internal policy" without naming which policy — isn't sloppy drafting. It's space left open on purpose, so a decision can be made unilaterally later. Every time you hit language like that, ask: what if that "discretion" gets used against me? If the answer scares you, that's the clause you either pin down in writing or strike before you sign.

Probation and grounds for termination

A probationary period isn't inherently unfair — both sides need time to find out if the fit is real. The problem lives in the details often left vague. Check whether the contract states an exact probation length and what happens automatically at the end of it — does employment continue on standard terms, or does something else need to happen first. Check for a clause letting the company extend probation unilaterally, with no cap. That's a red flag: it turns a trial period into an indefinite state of legal exposure.

Then look at the grounds for termination. If the language is loose — "cultural misfit," "loss of trust" with no specifics, "other grounds at management's discretion" — that's a loophole that, in theory, lets almost anything qualify as "cause," which often changes what you're owed on the way out. A well-drafted contract lists grounds concretely and points to actual law, rather than inventing its own categories.

> Our record. In the Maat system, a name is Ren: to name a thing is to take back some of its power over you. A vague clause in a contract is a word left deliberately unnamed, so the decision gets made not by law or fact but by whoever holds more leverage in the moment. Your job reading a contract is to name every foggy clause — ask plainly what it means, and make the answer show up on paper.

Overtime that "doesn't officially exist"

One of the most common traps is a clause about "flexible" or "irregular" hours, or a job title framed as "managerial" specifically so overtime supposedly doesn't need separate pay. Sometimes that's fair — real management roles with real authority. But often the same language gets dropped into a junior employee's contract for exactly one reason: so the company can demand extra hours without extra pay, hiding behind a title rather than the actual job.

Check three things: does the contract state concrete working hours; is there a separate clause on overtime compensation — pay, time off, a differential; and does the title on paper match what you'll actually be doing. If you're hired as a "specialist" but the contract is written in language meant for a "manager," that's not a coincidence — it's the title tuned to produce a specific legal effect.

A close cousin is a clause granting "flexible scheduling as business needs require" with no upper bound anywhere. Flexibility is fine when it runs both ways. When it only ever runs in the company's favor, it's just overtime wearing a nicer name.

Liability clauses and paycheck penalties

Some contracts include a clause making the employee fully liable for company losses — no cap, rather than the limited liability most jurisdictions default to for ordinary roles. Full personal liability is legitimate for a narrow set of positions that handle money or assets directly, and it's usually supposed to come with its own separate agreement. If that kind of clause shows up in an ordinary office contract with no direct link to handling company assets, that's worth a direct question about whether it's even enforceable where you live — and, if not, a request to strike it.

Also watch for penalty clauses buried inside the contract itself — deductions for lateness, "disciplinary fines," withholding pay for missed training. In most jurisdictions, unilateral deductions from wages as punishment are either flatly illegal or tightly restricted by statute, and a company can't simply write itself permission in an internal policy as if that settles the matter. The clause in the contract doesn't override the law — but until you notice it, you live as if it does.

IP assignment and staying quiet after you leave

Another block worth reading slowly covers intellectual property and non-compete terms. The IP clause usually sounds harmless: "everything the employee creates within the employment relationship belongs to the employer." Fine for work product. Not fine when the wording is broad enough to also sweep in your personal projects on your own time, just because they brush up against the company's line of business. Check whether the clause is scoped to "within the scope of job duties" — its absence is what makes the clause disproportionately wide.

A post-employment non-compete — a restriction on working for competitors or in the same field for a set period after you leave — is enforceable under certain conditions in some jurisdictions (often only when paired with compensation for that period) and largely unenforceable for most ordinary roles in others. Don't assume a clause is binding just because it's printed. This is exactly the case where checking your actual local law, or a lawyer, beats either panicking over the clause or signing it without a second thought.

How to push back before you sign

Contesting a clause after you've signed is always harder, slower, and more expensive than negotiating it before. So the real leverage sits at the moment most people skip, because they're afraid of looking difficult. Three concrete steps. First, list every vague or one-sided clause separately before you sign anything. Second, for each one, ask the company's representative a plain written question — "what does this mean in practice?" — and ask for the answer in writing, not verbally, because a written answer becomes evidence if there's ever a dispute. Third, for clauses that remain unacceptable after the answer, ask for the wording itself to be tightened — not deleted outright, but made concrete: "at the company's discretion" becomes "with 14 days' written notice stating the reason."

An employer with nothing to hide will usually agree to tighten the wording without a fight, because a concrete clause protects them too, as long as they're acting in good faith. Resistance to making a clause concrete is itself information about how that vagueness is meant to be used.

Do this today

Pull out your current employment contract — or the draft you were just sent for a new role — and read the whole thing in one sitting, pencil in hand. Mark every phrase like "at the company's discretion," "as needed," "as reasonably determined," and anything missing a concrete deadline, a concrete amount, or a concrete ground. Don't judge them yet — just find them all and write them on a separate sheet. It takes twenty minutes, and it turns a document you never actually read into a list of seven to ten specific questions you can now ask out loud.