Family Ties
Chapter 3: Avoiding Conflicts in Our Editorial Work
Family relationships—spouse, partner, parent, child, sibling in a decision-making role at a covered company—require disclosure before any related coverage, alongside personal relations rules. Editors reassign reviews, comparisons, or FAQ updates touching that brand when neutrality is in doubt. 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.
Household members in PR agencies representing clients we review trigger the same process as direct employment at the OEM.
Minor relatives in non-influential roles may not require public disclosure, but editors still need to know if Thanksgiving conversation could leak embargoed specs.
Family-owned small businesses in niche accessories may be coverable by another writer if the connection is immaterial to readers; leadership decides case by case.
Transparency inside the newsroom prevents awkward surprises on publish day; annual forms are covered in scope of guidelines.
Internships and summer jobs for relatives at covered companies trigger the same disclosure rules as executive roles; editors treat them seriously because informal hallway talk can still leak roadmap detail.
Updates to comparison pages after a family member joins a covered company trigger automatic conflict review even if the original author no longer works on that beat.
Roommates employed by covered companies trigger the same conversation as relatives; domestic proximity can leak embargoed specs at home. 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.
Relatives in decision-making roles at covered companies trigger reassignment before work begins. PR agencies employing family members count too—their clients are in scope even if your sibling is not on the OEM payroll directly. Document decisions in editor notes or the CMS so future updates honor the same standard.
Informal holiday conversation can leak embargoed specs. Editors need to know about close ties early, not after a draft is ready. Internal transparency prevents publish-day surprises that force embarrassing pulls or rushed rewrites. Document decisions in editor notes or the CMS so future updates honor the same standard.
Roommates and partners in industry roles follow the same logic as siblings. Shared kitchens and home offices are real leak paths for unreleased product names and roadmap slides left on a kitchen table. Document decisions in editor notes or the CMS so future updates honor the same standard.
Immateral family jobs in distant industries may not need public disclosure, but editors still document them when any reasonable shopper would care about neutrality on a specific brand battle we are actively comparing. Document decisions in editor notes or the CMS so future updates honor the same standard.