In Nonprofit Cloud, the way we model groups of people—such as households, families, or boards—has been standardized using the Group Membership feature set.

To represent a "Household," the system uses a combination of a Business Account (as the container) and a Party Relationship Group (as the definition).

Step-by-Step Implementation:

Individual Accounts: First, ensure each spouse has their own Person Account. This is crucial for tracking individual giving history, life milestones, and program participation.

The Group Record: The consultant creates a Business Account with a record type of "Group."

The Party Relationship Group: Crucially, a Party Relationship Group record is created and linked to that Business Account. The Type field on this record must be set to Household. This tells the system that this specific group is a domestic unit rather than a professional association or board.

Relationship Mapping: Finally, the consultant uses the Account Contact Relationship object to link the two Person Accounts to the Household Business Account. Roles (e.g., "Primary Member," "Spouse") are assigned here.

Option C is a "data silo" mistake; you should never track two distinct people in one record as it breaks reporting for birthdays, emails, and individual engagement. Option B is an old NPSP concept; while NPC still uses Contact Roles, they are a result of the relationship model, not the method used to "track that they are part of a household."