Every serious source of advice tells candidates to read the bare act. Considerably fewer explain what that involves, so a great deal of bare act reading amounts to running one's eyes over statutory language and retaining very little.
Reading a bare act well is a specific skill. It is closer to reading a schematic than reading prose.
A provision is a set of conditions, not a sentence
The most useful habit is to stop reading a section as a sentence and start reading it as a set of ingredients that must each be satisfied.
Take any operative provision and break it into its elements: who it applies to, what conduct or circumstance triggers it, what conditions qualify it, and what consequence follows. Written out as separate lines, most provisions turn out to have more moving parts than they appear to have in continuous text.
This matters because legal problems are almost always built on one ingredient being absent or contested. If you have never separated the ingredients, you cannot see which one is in issue.
The small words carry the weight
In statutory language, the connectives decide the outcome.
- "And" requires every condition; "or" requires any one
- "May" and "shall" carry different consequences, though the distinction is not always as rigid as it first appears
- "Notwithstanding" signals that this provision overrides something else, and you should immediately ask what
- "Subject to" signals the reverse, and the same question applies
- "Save as otherwise provided" tells you the rule you are reading is not complete on its own
Reading quickly past these words is the most common way to misread a section confidently.
Provisos, exceptions and explanations do different jobs
They are not interchangeable, and treating them as generic add-ons loses real content.
A proviso typically carves something out of the main provision. An exception removes a category from its scope. An explanation clarifies meaning without changing scope, and often exists precisely because the main text was found ambiguous.
Where a provision has several provisos, their order and relationship to each other matters. It is worth working out what each one is doing rather than absorbing them as a block of qualifying text.
Definitions are operative, not preliminary
The definitions section is routinely skipped because it looks like preamble. It is not. A defined term means what the statute says it means, which is frequently narrower or wider than ordinary usage.
Whenever a section uses a term that is defined, substitute the definition mentally and reread. Problems are often constructed exactly at the gap between the ordinary meaning of a word and its statutory definition.
Follow the cross-references
Statutes are networks, not lists. A section that refers to another section is incomplete until you have read the other one.
This is slow the first time and fast afterwards, because you begin to hold the structure in mind. Skipping cross-references produces the specific failure of knowing a provision in isolation and being unable to apply it, since applications almost always involve more than one section.
Read the structure before the sections
Before reading a chapter closely, read its headings and the sequence of sections in it. Statutes are usually organised with an internal logic: definitions, then substantive obligations, then procedure, then consequences, then miscellaneous.
Knowing where you are in that structure tells you what a section is likely doing before you read it, which makes the reading substantially faster.
Verify currency, always
Where legislation has been recently replaced or renumbered, notes, guides and older commentary may cite provisions by numbering that no longer applies. Secondary sources lag, sometimes by years.
The bare act is the authority for what the provision currently says and where it currently sits. This is the single strongest practical argument for the habit: not that bare act reading is virtuous, but that everything else you rely on can quietly go out of date, and this does not.