Personal Relations with Sources
Chapter 3: Avoiding Conflicts in Our Editorial Work
Personal relationships with people we cover—friends, family, romantic partners, or close social ties to PR reps—can create real or apparent bias in product reviews. Staff must disclose those relationships to an editor before assignment on related categories or brands, as described in family ties when relatives are involved. This section applies across wearables, smart home, phones, and every category where readers rely on Option Cutter comparisons, Top Picks, and Content Egg buy paths alongside honest verdict prose.
When disclosure alone cannot neutralize the conflict, another reviewer handles the piece, comparison row, or Top Picks slot. Editors document the reassignment briefly in internal notes.
Casual acquaintance at trade shows is normal; ongoing favors, private group chats pitching exclusives, or shared business ventures are not. If a reviewer joined a brand’s beta community with perks, treat it like any other material connection.
Former employment at a manufacturer you now cover requires transparency in methodology or author bio when a reasonable reader would care, especially for competitive categories like phones or smart home.
Readers do not need your address book, but they deserve coverage chosen for merit, not loyalty—see gifts and benefits for perk limits.
Networking apps and private Discord servers for creators are common; joining a brand-run server with early access perks counts as a relationship to disclose before covering that ecosystem on Option Cutter.
Blocklists for toxic PR behavior are maintained internally; they are not punishment for tough questions, but for harassment, bribery offers, or repeated embargo breaks.
Volunteer beta programs for apps and firmware should be disclosed in author notes when they influenced timing of coverage or access to features readers cannot yet buy. Questions about how these standards apply to your assignment belong in editor chat before publish. Document decisions in editor notes or the CMS so future updates honor the same rule; repeat issues escalate to leadership and may affect samples, affiliate-heavy beats, or outside-work approvals.
Disclose early: friend on the PR team, cousin in product marketing, roommate running a brand’s Discord. Early notice lets editors reassign before hours of testing create sunk-cost pressure to go easy on a launch. Document decisions in editor notes or the CMS so future updates honor the same standard.
Trade-show friendships are normal; private deal-flow friendships are not. If a rep shares exclusive discount codes tied to your coverage, treat it as a benefit to disclose, not a casual favor you can hide in a comparison footnote. Document decisions in editor notes or the CMS so future updates honor the same standard.
Former employers in categories you still cover warrant bio or methodology transparency when a reasonable reader would care. A phone reviewer who left a major OEM should not solo-review that brand’s new flagship without editor sign-off. Document decisions in editor notes or the CMS so future updates honor the same standard.
Beta communities with perks are relationships. Access to pre-release firmware can speed reviews but never skips retail verification paragraphs readers need before they spend money on accessories or subscriptions. Document decisions in editor notes or the CMS so future updates honor the same standard.