How Pff Mock Draft Actually Works When You Sit Down To Use It
I spend way too many hours each offseason digging through PFF's grading system to find players who fly under the radar in standard mock drafts. The platform itself gives you a framework, but the real value is in how you use the data they provide. Most people open the mock draft tool, look at the top fifty or so picks, and call it a day. That's where the hidden gems live if you know what to filter for. The core mechanism is straightforward. PFF grades every player on a 0 to 100 scale across multiple positional metrics. Their mock draft generator pulls those grades into a projected board. The trick is that the public-facing version shows one projection based on aggregate grades. What most people don't realize is that you can manipulate the view by adjusting positional need filters, conference filters, and combine performance toggles. I found this by accident when I was trying to cross-reference a prospect's PFF grade against their actual game film for a team message I was writing. I toggled off the top tier and let the generator run anyway. The board looked completely different. Here's the part that took me three years to figure out properly. PFF's hidden gems aren't the lowest-ranked prospects. They're the mid-tier guys whose grades cluster above 75 in specific situational categories that don't get headline coverage. An interior defensive lineman who grades out at a 78 overall but has a 91 run-stop grade and plays on a roster that rarely blitzes. A slot receiver with a 76 overall but a 94 YAC after catch number because he played behind a bad offensive line last season. Those guys exist in massive numbers on the PFF board. The public mock drafts skip over them because the raw overall grade looks unremarkable. You have to dig into the sub-metrics.
I ran into a specific problem last year that highlighted exactly how the tool works under the hood. I was building a mock for a team that had a glaring gap at left tackle. Their historical draft tendency was to grab the best athlete available regardless of fit. I put the best tackle on the board, projected him there, and the rest of the round looked wrong. The pick didn't make sense for how that organization actually evaluates players. What I ended up doing was exporting the full mock data, filtering out by previous draft tendencies I'd tracked over the prior four years, and then manually remapping the selection. It took about twenty minutes using the CSV export feature PFF makes available. The tool doesn't do this automatically because organizational fit isn't part of their algorithm. The actual filtering method that works is this sequence. First, set your positional need to the position you're targeting. Second, disable the elite tier toggle so you aren't locked into the top five or ten at each spot. Third, sort by the situational grade column rather than overall grade. This alone shifts the entire board. Fourth, cross-reference with combine results if you care about athletic testing. Fifth, look at the college strength of schedule modifier. Players from weaker conferences often inflate their numbers against lesser competition, and PFF tags that clearly if you know where to look. The biggest pitfall I see repeatedly is people treating PFF grades as gospel truth without accounting for sample size. A junior college transfer with twenty career snaps graded by PFF gets the same numerical weight as a three-year starter. The number looks identical on the surface. I learned this the hard way in 2022 when I drafted a guy based on his 82 overall grade and spent six hours realizing he'd played seventeen games in three seasons before that year. PFF doesn't hide this information, but you have to scroll past the main card to find the snap count history. I now require a minimum of two hundred career snaps before I give any grade serious consideration. Anything below that threshold gets flagged as preliminary data regardless of what the number says.
Another nuance that barely gets discussed is how PFF adjusts grades for schematic context. A zone-blocking scheme running back will look significantly different in PFF's rushing breakdown than a gap-running back in the same league. The grades are adjusted to account for scheme, which means comparing a zone runner against a power runner directly is misleading. The gem here is finding players who would outperform their grade in a new system. If a PFF grade of 77 comes from a spread offense in the FCS and you're projecting that same player into a zone-heavy NFL system, his actual impact could easily land closer to an 82 or 83 equivalent. The reverse is also true. A 79 grade from a pro-style option attack might not translate well. The export feature is probably the most useful part of the whole platform and it gets completely ignored. You can pull the entire mock draft board into a spreadsheet format, then apply your own filters and sorting. I usually build a secondary projection sheet that overlays my own notes on top of PFF's data. The combined view is where the actual gems show up clearly. It takes maybe forty-five minutes to set up properly, but once the template is built, each subsequent draft takes about fifteen minutes to complete end to end. If you're going to use this approach, stop treating the public mock draft as a finished product. It's raw material. The platform gives you the grading engine, the snap count data, the situational breakdowns, and the export function. What you do with those pieces determines whether you just get another version of what everyone else sees or whether you actually find someone who hasn't been projected yet. The hidden gems aren't hidden because the data is secret. They're hidden because the average user stops looking at the first layer.
Get the Full Details
