All topics
English

Build and use reports · 3 min read

Use related contacts and analyze policy members

Choose one row per policy or person and interpret repeated values correctly.

In this guide
  1. Include the related contact
  2. Switch to member-level rows
  3. Read policy blocks and people counts
  4. Filter a person or a policy intentionally
  5. Avoid repeating premium in totals
  6. Keep learning

For: CRMDAY One users with the Insurance profile.

Include the related contact

  1. Create or edit a Policies report.
  2. Keep One row per → Policy.
  3. Open Add or remove columns and find Related.
  4. Add Contact — Name, Email or State when available.
  5. Filter contact fields when relevant, such as State = FL, and check the links.

Deals and Tasks also support related contact fields, subject to access. This uses the contact linked to the record, not an unrestricted join with every contact. Accessible contact names can open their records.

Policy data with related contact name, email and state.
Policy data with related contact name, email and state. Open the image to enlarge it.

Switch to member-level rows

  1. In Policies, open Related data.
  2. Choose One row per → Policy member.
  3. Add Member — Name, Relationship and Applicant, with useful policy and contact columns.
  4. Review groupings, filters and metrics after changing mode.
  5. Check the preview and save with a name clearly indicating people.

Member fields appear in this mode. An immigration-status member template is available when permitted; review its initial scope, which also includes primary members and people not applying.

One-row-per-member mode with a count of 24 people.
One-row-per-member mode with a count of 24 people. Open the image to enlarge it.

Read policy blocks and people counts

The image contains 24 members in 12 fictitious policies. Blocks identify plan, Policy number, carrier, year and status; rows distinguish the primary applicant and dependents.

Screen pagination counts policies and keeps each result family together. Totals and charts count people. Filtering members keeps only matching rows; the primary member is not forcibly reinserted. A member row still opens the original policy.

Members in policy blocks with primary member, dependent and fictitious FFM App ID.
Members in policy blocks with primary member, dependent and fictitious FFM App ID. Open the image to enlarge it.

Filter a person or a policy intentionally

Use Member — Applicant to include only people applying. Member — Immigration status restricts person rows. Primary or dependent immigration-status policy fields select policies and may retain other members of matching policies.

FFM App ID is the ID entered in the Policy, not the policy number. Missing or inaccessible related contacts can disappear from related-field results; this does not prove the database value is empty.

Avoid repeating premium in totals

Policy values repeat per member. A $150 policy with three members can create three $150 rows. Summing them yields $450, not the premium of one policy.

Use one row per Policy for book premium totals, and member mode for people counts with clear applicant filters. Select only needed personal fields; related-contact export also depends on Contacts permissions.

Keep learning

Updated October 25, 2026.