Detroit-first. Draft-obsessed.

PistonsDraft started as a 2026 NBA Draft room built around Detroit's real roster problems. Now the draft is over, the board stays live as the archive, and the next job is tracking what Detroit actually got.

Profiles, rankings, mock context, targets, Intel, and Fit Score still matter — but now they serve the next phase: Okorie, Onyenso, Summer League, rookie development, and the first look at 2027.

For fans who want more than a transaction recap. PistonsDraft is for people who care how a rookie fits next to Cade, what Summer League actually tells us, which scouting signals matter, and where Detroit's next draft cycle starts.

If you're here for a hot take that ignores the actual roster and cap sheet, this isn't it.

We write every rookie report, Summer League note, scouting profile, and Intel piece with the current Pistons roster in mind: Cade, Ausar, Duren, the bench, and the cap. If a player or prospect doesn't fit Detroit, we say so — even if the national board loves him.

Voice is blunt, measured, first-person "we." No corporate gloss. Light snark, no tabloid hype. We default to "could" or "might" instead of predicting like we work for a team.

Every profile carries a Pistons Fit Score out of 100. It's a six-pillar editorial model — Cade Spacing, Defensive Identity, Immediate Role Readiness, Frontcourt Need, Bench Pull-Up, Grit / Role Discipline — calibrated for what Detroit actually needs around its current core. Numeric only. No letter grades.

It applies the same way to a 2026 archive prospect, an incoming rookie, or an early 2027 name. It is not a national draft grade and it is not objective truth. A top-five talent can still score poorly here if the fit with Cade and the frontcourt is wrong. Read the full Fit Score methodology →

Intel articles — rookie reports, Summer League notes, roster context, and 2027 scouting — cite the underlying source on every claim that isn't ours: national reporters, team beats, video breakdowns, on-the-record scouts. The Sources block at the bottom of every Intel piece is the receipt.

When we synthesize across reporters, we say so. When something is our projection or our take, it's framed that way and not laundered as reporting.

• Editorial / opinion. Our rankings, Fit Scores, mock slotting, Detroit angle, and the take in any Intel piece. Not reported, not predicted — argued.
• Sourced reporting. Anything attached to a citation in the Sources block of an Intel piece. We are restating or synthesizing other reporters' work and crediting them.
• Social / forum chatter. The Buzz section and the chatter rail on Intel articles surface what fans, accounts, and message boards are saying. It is labeled as chatter, not as reporting, and we don't treat it as confirmed.

Editorial questions, tips, or pitches: editor@pistonsdraft.com

Spot something wrong — a stat, a quote, a misattributed source? Tell us: corrections@pistonsdraft.com. We log corrections on the Corrections page.