Salary cap

Salary Cap House Rules for Online Franchise Leagues

The game enforces a salary cap, but it was designed for a league of AI GMs, not 32 people looking for an edge. House rules close the gaps. These are the ones leagues add most often, why each exists, and how to enforce them without auditing every roster by hand.

Updated November 15, 2026 · 7 min read · By the FranchiseHuddle team

Quick answer

Ban position changes made to cut a re-signing price, limit how many star free agents a team can sign each offseason, cap free-agent contract length, forbid cutting and re-signing the same player cheaper, and give over-the-cap teams a warning and a deadline before a penalty.

Why the game's cap isn't enough

The in-game cap stops a team spending more than it has. It doesn't stop owners making their players cheaper to keep, stacking free agency, or using the release button as a cap tool. Each house rule below closes one specific loophole. Adopt the ones your league has actually seen.

Position changes to dodge re-signing costs

A player's re-signing price depends heavily on his position. Move a star quarterback to punter before his contract is up, and his asking price can drop dramatically; move him back after he signs. It is the best-known cap exploit in online franchise play.

The rule: no position changes in the final year of a contract, and any position change needs commissioner approval and a real depth-chart reason.

Star free agents per offseason

A team with cap room can sign every top free agent in one night. Leagues limit it: no more than two free agents rated 80 or higher per team per offseason is a common line. Pick your own numbers; the point is that free agency spreads talent instead of concentrating it.

Contract length for free agents

Long, cheap free-agent deals let a team lock in value for years. Capping free-agent contracts (three years is common) keeps stars coming back to the market and keeps the league competitive across seasons.

Cutting and re-signing

Releasing a player and immediately re-signing him at a lower number is a cap trick, not roster management. Ban re-signing a player your team released in the same season.

Over the cap: warn, then penalize

Teams end up over the cap by accident: a re-signing, an injury replacement, a trade that looked fine. Make the first step a warning with a deadline (one advance is common) and the second a penalty the league agreed in advance, such as a suspended player, a lost pick, or a forced release.

How to enforce it without spreadsheets

Every one of these rules can be checked from contract and roster data after each advance: who changed position, who signed which free agent, for how long, and which teams are over. The work is in looking every week. Leagues either assign a cap officer with a spreadsheet, or use a league tool that reads the franchise and flags breaches automatically.

Where FranchiseHuddle does the work

Everything above works with a spreadsheet and a lot of patience. These are the parts FranchiseHuddle takes off your plate:

Questions

What is the QB to punter trick?

Changing a player's position to one with a lower market value before re-signing him, so his contract demand drops, then changing him back. Most leagues ban it outright.

How many star free agents should a team be allowed to sign?

Two players rated 80 or higher per offseason is a common starting point. Smaller leagues with more cap room per team sometimes go to one.

What penalty should a team over the cap get?

A warning with a deadline first, since most overages are accidents. If it isn't fixed, the penalty should hurt but be proportionate: a lost late-round pick or a forced release is typical.

Your league is two minutes from running itself.

Create a free league, connect EA, and watch the site and Discord update themselves. Upgrade to hands-off automation whenever you're ready.

Start free See pricing →