Comparing versions of a bill or Act is easier when you treat each text as a controlled record rather than as a series of similar documents. This guide sets out a repeatable method for checking version dates, tracking amendments, comparing clauses and definitions, and identifying which changes have practical consequences.
Overview
A bill can change substantially between introduction and enactment. It may begin as an introduced bill, move through committee review, receive amendments during debate, pass in a revised form, and later become an Act. Separate amendment papers, schedules, explanatory documents and commencement notices may also affect how the final law operates.
The latest document is not always the right document for every question. If you want to understand what lawmakers originally proposed, compare the introduced version with the committee version. If you need to know what was passed, use the final passed text. If you are checking what rules apply today, confirm the enacted Act and its commencement information. A reliable legislation summary should make those distinctions clear.
Before comparing text, identify the jurisdiction, chamber or legislature, bill number, short title, long title, publication date and document type. Record these details in a simple version log. This prevents a common research error: comparing documents with similar titles but different stages, jurisdictions or amendment histories.
| Record | What to capture |
|---|---|
| Identity | Jurisdiction, bill number, title and session |
| Stage | Introduced, committee, report, passed, assented or enacted |
| Date | Publication date and, where relevant, approval or commencement date |
| Source | Official document location or public records reference |
| Status | Pending, amended, passed, enacted, repealed or not commenced |
How to compare options
1. Define the comparison question
Start with the practical question you need to answer. “What changed?” is too broad for a precise review. Better questions include: Which duties were added? Did the definition of a regulated activity change? Was the commencement date altered? Which amendments affect publishers, employers, suppliers or public bodies? Has a proposed power been removed or narrowed?
Your question determines which versions matter. A historical comparison may require the introduced bill and the enacted Act. A compliance review may require the current consolidated Act, amendment Acts and commencement notices. A report on legislative intent may also require amendment tables, committee reports or explanatory material, while keeping those documents separate from the operative legal text.
2. Build a version map
List every relevant document in chronological order. Give each file a short label, such as “V1 — introduced,” “V2 — committee,” “V3 — passed,” and “V4 — enacted.” Do not rely only on filenames; official repositories may use similar labels for different documents.
For each version, note whether it contains the full bill, selected amendments, a replacement schedule or an amendment table. An amendment paper may say that a clause is omitted or replaced without reproducing the whole bill. It therefore cannot always be read as a standalone version.
3. Compare structure before wording
First check whether provisions were added, removed, renumbered or moved. Compare the table of contents, part headings, schedules and clause numbers. Structural changes often reveal the most important developments before you examine individual sentences.
Next compare the operative provisions. Focus on words that change legal effect, including “must,” “may,” “must not,” “only,” “unless,” “except,” “prescribed” and “reasonable.” A small wording change can alter whether a duty is mandatory, whether an exception applies or whether a power is discretionary.
4. Separate text changes from status changes
A changed bill text does not automatically mean the new rule is in force. Track legislative stage and commencement separately. An Act may have received approval but have provisions that start on different dates, depend on regulations or require a government notice. For a current legal update, check the applicable bill status and enactment history, then verify any stated Act commencement date.
Feature-by-feature breakdown
Definitions
Definitions deserve an early, separate review because they can change the reach of many later clauses. Compare whether a term was added, removed, narrowed, expanded or linked to another instrument. Check singular and plural forms, territorial limits, exclusions and references to “including” or “but not limited to.”
When writing a plain English law summary, explain both the definition and its practical effect. For example, do not merely say that a new term was inserted. State which people, activities, records, products or organisations may now fall within the bill’s scope.
Duties, prohibitions and permissions
Mark every provision that creates an obligation, prohibition, permission or power. Compare the actor required to act, the action required, the deadline, the triggering condition and any exception. A clause that changes “may publish” to “must publish” has a different effect from one that changes only a heading or cross-reference.
Also check whether a duty applies immediately or only after regulations, guidance, registration or a commencement notice. These dependencies are easy to miss in a redline because they may appear in a separate clause or schedule.
Enforcement and consequences
Review provisions dealing with offences, penalties, civil claims, notices, inspections, appeals, investigations and information-sharing. Compare who can take action, what threshold must be met, the available remedy and any stated defence. Schedules may contain enforcement details that are not obvious from the main clauses.
Dates and transitional provisions
Compare commencement, expiry, review and transitional language. Transitional provisions may decide whether existing licences, contracts, applications, records or proceedings continue under the old rules or move to the new framework.
Do not treat a bill’s proposed date as a confirmed implementation date. Label dates according to their status: proposed, approved, appointed by notice, commenced or superseded. If a government notice or gazette notice changes the practical timetable, record it alongside the Act rather than burying it in a general note.
Schedules and cross-references
Schedules often contain forms, technical requirements, lists of affected legislation, exemptions or consequential amendments. Check every cross-reference after clauses are renumbered. A comparison that covers only the main body can miss a significant change in a schedule or an amendment to another Act.
Purpose and supporting documents
Explanatory notes, bill analyses, fiscal notes and legislative digests can clarify the intended operation of a proposal, but they are not substitutes for the legal text. Use them to identify issues for review and to explain context. For guidance on separating analysis from operative wording, see how to read a fiscal note, bill analysis and legislative digest.
Use redlines carefully
Automated redline tools are useful for locating additions and deletions, especially in long documents. They may struggle with renumbered clauses, scanned PDFs, tables, footnotes, formatting changes and text moved between sections. Treat a redline as a discovery tool, not as the final analysis. For a practical workflow, see redline tools for legislation.
Best fit by scenario
For a news or content publisher
Use the introduced and latest available versions to explain the direction of travel, but label the proposal clearly. State whether the text is pending, amended or enacted. Highlight only changes that affect readers, and link each claim to the relevant version rather than presenting a proposal as current law.
For a business monitoring compliance
Compare the current operative rules with the latest proposed version. Prioritise definitions, duties, reporting deadlines, penalties, exemptions, transitional arrangements and commencement dates. Maintain an issues list with three columns: confirmed current requirement, proposed change and action to monitor.
For legal or policy research
Create a complete legislative history. Preserve each version, amendment paper, explanatory document and relevant notice. Record why each change matters, but distinguish textual evidence from interpretation. Where several amendments interact, compare the complete replacement text rather than relying on isolated amendment instructions.
For a civic transparency project
Present the timeline in plain language. Let users move from bill identity to version history, clause changes and current status. Include a note explaining that a passed or enacted text may still have provisions awaiting commencement. This helps readers understand the difference between legislative approval and an enforceable rule.
A reusable comparison worksheet
For each material change, record:
- Version changed from and version changed to
- Clause, section or schedule reference
- Exact wording added, removed or replaced
- Type of change: scope, duty, definition, process, enforcement or timing
- Plain English effect
- Who may be affected
- Commencement or dependency
- Source document and page or paragraph reference
- Confidence note where the practical effect requires further interpretation
When to revisit
Update a bill comparison whenever a new version is published, an amendment paper is tabled, the bill changes stage, the final text is approved, a commencement notice is issued or related regulations are made. Revisit it after a bill is withdrawn, carried over, reintroduced or replaced, since a later bill may not have the same wording or status.
Set separate monitoring dates for legislative text and implementation. A bill tracker can alert you to stage changes, while government notices and public records searches may be needed to confirm commencement, regulations or administrative directions. Keep the original comparison intact and add a new version entry instead of overwriting earlier findings.
Before publishing or relying on the result, run a final check:
- Are the jurisdiction, bill number and session correct?
- Did you compare complete texts as well as amendment instructions?
- Have definitions, schedules, cross-references and transitional provisions been reviewed?
- Is the legal status clearly labelled as proposed, passed, enacted or commenced?
- Have you separated the wording of the law from explanatory commentary?
- Does every practical conclusion point to a specific clause or official document?
A disciplined version log turns a difficult document comparison into a maintainable legislation summary. It also gives readers a clear way to return when the underlying text changes, without confusing a proposal, a passed bill and an operative Act.
