Judge a trade, or find one.
The Trade Evaluator scores a deal on the table for every team in it. The Trade Finder takes the rosters and returns the trades the other manager can also say yes to. Both priced off the betting market, at your league’s scoring.
Two tools, one board
How the trades are judged →Your league is synced
Load your league and every team box below fills itself: type a team’s name and its roster comes with it. The desk’s own matches show here too.
1. The players in the trade
Who sends whom. Type a name and it fills in. With three or four teams, say where each player goes.
2. The teams’ rosters (optional)
Add each team’s full roster and the trade is judged on the lineup it changes rather than on the players alone. Type the names, paste a list, or paste or drop a screenshot of the roster page.
3. Anything else to weigh?
Team records, standings, injuries, byes, who is chasing a playoff spot, who has clinched. Name a team (or say “I” or “my team” for yours) with its record or situation and its horizon adjusts: a clinched team is scored on the fantasy playoffs, a team that needs wins now on the next three weeks. Each team box shows how it was read.
Settings: scoring, lineup, horizons, balance
A team chasing a playoff spot needs the next three weeks; a team that has clinched needs weeks 15–17. Score each side on its own clock. A team your notes describe uses the horizon its situation implies; your focus sets your clock, and the control below it sets everyone else’s.
How these trades are judged
How the number is made →A trade is a change to two lineups, not a swap of two names.
A roster is worth what it starts
Every player is projected at your scoring from the same board the rankings use, and each team’s lineup is filled the way your league fills it: the named slots first, then flex and superflex from whoever is left. The bench counts a little, as insurance, and a backup quarterback in a one-QB league counts for almost nothing. Kickers and defenses are left out.
The Evaluator scores every team in the deal
For a two-, three- or four-team trade, each team’s lineup is filled before and after, counting what it sends and what it receives. A team that gains three quarters of a point a week or more is called a gain, one that loses as much a loss, and anything between is about even. When the deal is not a yes for everyone and the rosters are in, the evaluator shows the closest trades among the same teams that are.
The Finder tries every swap
Fill in two to four rosters and the engine tries every one-, two- and three-player swap between your team and each of the others, keeping only swaps where both lineups improve by at least three quarters of a point a week. The balance slider orders what survives: at Even by the smaller of the two gains, at In my favor by yours alone. It cannot surface a trade the other manager should refuse.
Each side has to want it. A lineup gain is necessary, not sufficient: a manager asked to send the best player in the deal, or forty points more of projection than comes back, for half a point a week says no, whatever the lineup math says. So before a trade is shown, each side is argued from that manager’s chair: the lineup gain on their own horizon; who gets the best player in the deal; projected points sent against received; whether a throw-in they must open a roster spot for would only be the next cut; the depth left at each position; for a team scored on the next few weeks, what the deal costs over the season; and whether their gain is a fraction of yours. A side that sends the best player needs at least a point and a half a week for it. A side that sends more projection than it gets needs a lineup gain of at least half the difference. A side gaining under two points a week needs at least thirty percent of what the other side gains. A trade is offered only when both cases hold, and the case is printed under each side so you can make it to the other manager in their words. The Evaluator runs the same test on the trade you typed and says when the other side would refuse, and why.
The gauge is your side of it. Under the verdict, every team in the deal is scored twice more on the same clock: the next three weeks and the rest of the season (the fantasy playoffs when you have clinched). Each row shows every team’s gain on that horizon and marks the team the trade helps most. Your situation decides which of the two counts more: a team that needs wins now is weighed 70/30 toward the next three weeks, a team playing the whole season 35/65 the other way, a team built for the playoffs 25/75. The needle is that weighted gain per week, from three points lost on the left to three gained on the right, and the call is Go at three quarters of a point or better, No go at as much lost, and the lineup fit settles the ground between: a trade that raises your weakest starter is a narrow Go, one that opens a hole is a narrow No go.
Rosters are optional in the Evaluator. List only the players and each side is scored on those players alone: what it gets against what it sends, at your scoring, on its horizon. That answers whether the names are fair. Add the rosters and the score becomes the change to the lineup each team actually starts, which is the better answer whenever a two-for-one opens or closes a starting slot, and the card says which of the two it is showing.
Horizons are per team. A gain is measured on the weeks that team is playing for: this week, the next three, the rest of the season, or the fantasy playoffs, and stated per week so a three-week horizon and a twelve-week one are on the same scale. Your notes set a team’s horizon when they describe it: “clinched” or a record of .700 or better means the fantasy playoffs; “needs wins,” “on the bubble” or .400 or worse means the next three weeks; “must win this week” means this week; “eliminated” or “rebuilding” means the rest of the season.
Your notes. Beyond setting horizons, the factors you type are read by a language model after the numbers are in. It explains whether they should change the call; it never changes a projection, and the scores stand on their own.
What it does not know. It cannot see your league’s roster limits, its trade deadline, who is on injured reserve, or which manager is unreachable. A team that receives more players than it sends needs roster spots; the card says so. Screenshots are read by a model into names only, and every name is then matched to the board here in your browser, so nothing it read can become a projection on its own.