I spent a morning turning one employment-law clause into something a script can check, and the interesting part was not the code. It was that a single word in the statute — "or" — makes one of the two wage floors unverifiable from the text alone.

The subject is probation in a Chinese employment contract. The rules live in four documents: the Labour Contract Law, its 2008 implementing rules, a 2020 Supreme People's Court interpretation, and a 1996 set of rules for foreign employees. The clause I cared about sets how long a probation may run. It is a ladder keyed to the contract term, and the ladder is the part a contract-checker can automate.

The ladder, as the statute writes it

Four bands, in Article 19:

Contract term Longest probation
under three months, or a contract for a specific task none
three months up to one year one month
one year up to three years two months
three years or more, or open-ended six months

The boundaries are written in Chinese range notation: "three months and above but under one year", "one year and above but under three years", and so on. The word 以上 includes the boundary and 不满 excludes it. So a contract of exactly twelve months sits in the two-month band, and one of exactly thirty-six months sits in the six-month band. A parser that reads these as plain inequalities gets both boundaries wrong.

That is the whole reason I wrote a function instead of a checklist: the off-by-one sits exactly where people read fastest.

def max_probation_months(contract_months: int, task_based: bool = False) -> int: """Article 19 caps, with the Chinese range wording made explicit.""" if task_based or contract_months < 3: return 0 if contract_months < 12: return 1 # three months and above, under one year if contract_months < 36: return 2 # one year and above, under three years return 6 # three years and above, or open-ended assert max_probation_months(2) == 0 assert max_probation_months(3) == 1 assert max_probation_months(11) == 1 assert max_probation_months(12) == 2 assert max_probation_months(35) == 2 assert max_probation_months(36) == 6 assert max_probation_months(60, task_based=True) == 0 

Two more rules from the same article are cheap to check and easy to miss. A probation is counted inside the contract term, so a two-year contract with two months of probation still ends at month twenty-four. And a contract that states only a probation term is not a probation at all: the stated period becomes the contract term.

The part a script cannot check

Article 20 sets the pay floor during probation: not below 80% of the lowest wage for the same post in the unit, or 80% of the wage agreed in the contract, and never below the local minimum wage. The implementing rules repeat the sentence almost verbatim.

The "or" is doing a lot of work. If the two reference wages differ — say a contract wage of 10,000 and a same-post lowest tier of 9,000 — the text does not say whether the floor is 7,200, 8,000, or the higher of the two. Practice is said to take the higher, which would be 8,000 here, but I found no national document that resolves it. Writing a checker that silently picks one is worse than writing one that refuses and prints both.

So the function returns both, and the caller decides:

def probation_wage_floors(contract_wage: float, same_post_lowest: float, local_minimum: float) -> dict: return { "pct_of_contract": 0.8 * contract_wage, "pct_of_post": 0.8 * same_post_lowest, "local_minimum": local_minimum, # absolute floor, always applies } 

The minimum wage is the only unambiguous floor in that dictionary. It is set by province and moves on its own schedule, which is why the function takes it as an input rather than looking it up.

What an over-long probation costs

Article 83 is the reason the ladder matters in practice. Where the agreed probation exceeded the cap and was actually served, the employer pays compensation for the months served beyond the cap, measured at the monthly wage that applies after probation ends.

Two details there are easy to skim past. The measure is the post-probation wage, not the probation wage, so a large step-up at the end inflates the compensation. And the base is the excess months only, not the whole probation.

def excess_months(contract_months: int, probation_months: int, months_served: int) -> int: cap = max_probation_months(contract_months) served_in_probation = min(probation_months, months_served) return max(0, served_in_probation - cap) assert excess_months(12, 3, 3) == 2 # 1-year contract, 3-month probation served assert excess_months(24, 6, 5) == 3 # left after 5 of 6 months assert excess_months(7, 2, 2) == 1 # 7-month contract, 1-month cap 

The compensation is a separate payment from wages. The months worked are paid anyway; Article 83 adds the excess months again at the post-probation rate. It is not a refund, and it does not void the contract.

Probation does not buy a cheaper exit for incompetence

Article 21 limits termination during probation to two grounds: Article 39 and the first two items of Article 40. Agreement and resignation are separate routes and are not covered by that limit.

The distinction costs money. Termination for "not meeting the recruitment conditions" sits in Article 39 and carries no severance. Termination for incompetence after training sits in Article 40(2), which requires thirty days' notice or one month's wage in lieu, plus severance. An employer who treats probation as a discount on dismissal is reading the wrong article.

One procedural asymmetry is worth knowing: where a dismissal is challenged, the employer carries the burden of proof. That is Article 44 of the 2020 interpretation, and it applies to the "not meeting conditions" ground like any other.

The negative check that took the longest

The rule says a probation may be agreed only once between one employer and one worker. I read the article looking for a time limit — a window after which a rehire could carry a new probation — and found none. The restriction is stated without a condition, so a script can treat "has this employer and worker agreed a probation before" as a permanent flag.

That said, I could not verify the edge cases: a transfer to an affiliate, a worker who returns a decade later, a probation extended by agreement within the cap. None of those is addressed in the four texts, and I did not read local court practice.

What this is and is not

This is a reading of primary texts, not legal advice. Every article number above was read in the source document rather than taken from a summary, and the arithmetic is mine with assumed wages. The open items — the "or" in Article 20, the extension question, the affiliate question, whether compensation needs a labour-authority order before arbitration — are written out on the site version of this piece, which is the canonical copy:

Probation in China: six-month caps and an 80% pay floor

If you are checking a contract rather than writing a parser, the ladder plus the excess-month formula covers the part the text settles. The rest needs a lawyer who reads local practice, which is exactly the part I left unfilled.

Sources, all read on 2026-11-22:

Drafted with an AI assistant from my own reading of the primary documents; every clause number and link here was checked against the source.

Read next, on the same four documents: