What Is a Session Law? How It Differs From the Code

Short answer: a session law is a law exactly as it was passed, published in the order lawmakers passed it. At the federal level, most of them are called public laws. The code is the other copy: the same laws sorted by subject, with later changes worked in. When you look up a rule on a government site, you usually land on the code. The session law is the original it was built from, and the two can read differently.

TL;DR

• A session law is one act, as passed, in the order of the legislative session. Most federal ones are public laws, such as Public Law 108-187.
• A slip law is the first separate printed copy of a single act.
• The code sorts all current laws by subject and edits in later changes. This is why a code section can say something the original act never did.
• A short line under each section, called the history line or credit line, names the act that created it and the acts that changed it.
• If you cite the wrong copy, or an out-of-date one, you may be quoting words that no longer apply.

What is a session law? Two copies of the same law

Picture a company handbook. Every time the company changes a policy, it sends a memo. The memos pile up in date order. That pile is the session laws. Once a year someone also prints a clean handbook, sorted by topic, with every memo already folded in. That is the code.

The federal bound set of session laws is called the Statutes at Large. A citation like "117 Stat. 2706" means volume 117, page 2706.

A federal example: the CAN-SPAM Act

Say your company sends marketing emails. The rule you want is in a law Congress passed in 2003.

The session law. It is Public Law 108-187. The "108" is the 108th Congress, the two-year term it passed in. The "187" means it was the 187th public law of that term. The President approved it on December 16, 2003. You can read it on the official GovInfo site. It has 16 sections, and section 5 contains this duty: a commercial email must provide "a valid physical postal address of the sender."

The code. The Code sorts the act by subject, so its sections appear under Title 15. Section 5 of the act became 15 U.S.C. § 7704, and the official US Code site shows it there.

The link between them. At the bottom of 15 U.S.C. § 7704 is the credit line: "Pub. L. 108-187, § 5, Dec. 16, 2003, 117 Stat. 2706." Read it as a map. It says this section comes from section 5 of Public Law 108-187, approved on that date, printed at page 2706 of volume 117.

Notice what changed on the way. Section 1 of the act is only its short title, "CAN-SPAM Act of 2003". The Code does not give it a section number. It prints it as a note under 15 U.S.C. § 7701. So the act and the code do not match one for one.

A state example: California's data breach notice rule

States have the same two copies. California calls its session laws "Statutes of" a year, and each one gets a chapter number. Its code is split by subject into codes such as the Civil Code.

Your business holds customer records. The rule on telling people about a breach is California Civil Code § 1798.82. The history line at the bottom of the official section page reads: "Amended by Stats. 2025, Ch. 319, Sec. 1. (SB 446) Effective January 1, 2026."

That line points to a specific session law: Chapter 319 of the Statutes of 2025, which began as Senate Bill 446. The bill's own summary says earlier law required disclosure "in the most expedient time possible and without unreasonable delay." The current code text says the disclosure "shall be made within 30 calendar days of discovery or notification of the data breach." A business that read an older copy would be working from a looser deadline than the one that now applies.

What "as amended" means

When a legislature changes a law, it does not reprint the whole thing. It passes a new act that says "section X is amended to read" and gives the new wording. The code then swaps the new words in.

A section described as "as amended" is the original law plus every change since. Each change has its own session law. The history line is your list of them. A long list means the section has been reworked often, and an old copy is more likely to be wrong.

Why the code can differ from the act

• Later acts changed it. The most common reason.
• Parts were repealed. The act still exists in the record. The code drops the repealed words.
• The editors moved things. Code editors sort the text into subjects and may place some provisions as notes.
• Not every code is itself the law. Some federal titles are enacted into law as a whole. Others are an editorial compilation. For those, if the code and the Statutes at Large disagree, the Statutes at Large control. The Office of the Law Revision Counsel, which compiles the federal code, says so on its site.

Why it matters to a business

Most mistakes here are quiet. A contract clause quotes a deadline from an old act. A compliance memo cites the code but misses a change passed last session. A vendor's summary describes the original act when the rule has since moved.

If you act on the wrong text, you may miss a deadline, skip a required notice or promise something that is no longer required.

What goes wrong

• You cite the act when you mean the current rule. The act may be years out of date.
• You cite the code when the question is what lawmakers passed. Then you want the session law.
• You ignore the history line. It is the fastest clue that something changed.
• You trust an unofficial copy. Check the official legislature or government site.
• You mix levels. Federal acts do not tell you what your state requires.

Questions to ask

1. Is this text the act as passed, or the code?
2. What does the history line say, and when was the last change?
3. Which session law made that change?
4. Is this the official site?
5. Is it federal, or which state?

Our guide on how to cite a statute or regulation shows how to write the citation down. For the federal side in more detail, see Statutes at Large explained and the US statutes guide. If you track pending bills before they become law, read bills versus enacted law.

This is general information, not legal advice.

This guide is part of US Law Data: The Complete Guide, a map of where US law comes from and how to use it.

FAQ

What is a session law? A session law is a law as passed, printed in the order lawmakers passed it during a legislative session. It is the original wording of one act. The code is built from these.

What is a public law? A public law is a federal law that applies to the public at large, as opposed to a private law that helps one named person or group. Congress numbers each one by term and order of passage. Public Law 108-187 was the 187th of the 108th Congress.

What is a slip law? A slip law is the first separate printed copy of a single federal law, issued soon after it is signed. The slip laws of a session are later gathered into the bound Statutes at Large.

What is the difference between session laws and the code? Session laws are arranged by date and show each act as passed. The code is arranged by subject and shows the law as changed since. If you want the rule today, look at the code. If you want the exact words lawmakers voted on, look at the session law.

What is a history line or credit line? It is the short note under a code section that names the acts that created or changed it. For example, "Pub. L. 108-187, § 5, Dec. 16, 2003, 117 Stat. 2706" points to the enacting act. Follow it to find the original text.

Can a code section be wrong? Editors can make mistakes, and a copy can be out of date. For many federal titles, the Statutes at Large control if the two conflict. Check the official source and the history line before relying on a section.

Where do I find both? Federal session laws are on GovInfo and Congress.gov, and the federal code is on the Office of the Law Revision Counsel's site. Each state's legislature publishes its own code and usually its session laws.

Vaquill AI holds federal public laws as enacted alongside the US Code, and the public law citations in a code section's credit line link to the enacting text. If you want that data in your own product, see the Vaquill AI legal data API.

Priyansh Khodiyar

Co-Founder & CTO

Priyansh leads engineering and AI at Vaquill AI: the pipelines that pull statutes, regulations and court rules from every US jurisdiction's official publisher, and the REST API, MCP server and open dataset that serve them.