Contact Fields Worth Recording and Those to Skip

The test for any field

It is tempting to add a field for everything you might one day want to know. A year later you have forty columns, most of them empty, and nobody trusts the rest. A better approach is to ask one question before adding any field: what specific decision or action will this information support?

If you cannot name a use, such as addressing an email, deciding who follows up, or grouping customers, the field is a candidate to skip. Each extra field costs time to enter, time to keep current, and carries some privacy responsibility if it concerns a person.

Fields that are almost always worth recording

These support basic communication and identification.

• Name: ideally first and last name in separate fields, so you can address people correctly.
• Email address or phone number: at least one reliable way to reach the person, depending on how you actually communicate.
• Company or organisation: useful for business customers, so several contacts can be linked together.
• Role or job title: helps you judge who makes decisions. It is optional for consumers.
• Owner: the team member responsible for the relationship. This is easy to forget and extremely useful.
• Source: how the person first came to you, such as a website form, a referral or an event.
• Date created and date last contacted: simple timestamps that make follow-up and clean-up much easier.

Fields that are useful for some businesses

Include these only if you will use them.

• Customer status: for example lead, active customer or past customer. Keep the list short and clearly defined.
• Preferred contact method or language: worthwhile where it changes how you reach people.
• Interests or products bought: helpful for relevant messaging, and often better derived from purchase or activity history than typed by hand.
• Location at city or region level: useful if you run local events or have regional service areas.
• Consent status and date: a record of what someone agreed to and when. Rules differ by country, and the idea is covered further in the discussion of marketing consent.

A good habit is to prefer dropdowns and checkboxes over free text for fields you plan to filter on. Free text produces many spellings of the same thing, which makes grouping unreliable.

Fields to think twice about

Some fields add risk or clutter with little benefit.

• Date of birth: often collected “for birthday offers” when a month and day, or nothing at all, would do. If you need to confirm age, consider whether you must store the exact date.
• Full home address: necessary for deliveries, but not for a newsletter subscriber.
• Personal social media profiles: rarely needed, and they may be out of date.
• Sensitive details: information about health, religion, political views, finances or similar matters carries stricter rules in many places. Unless you have a clear need and a lawful basis, leave it out. Check the rules that apply to you; this is general information, not legal advice.
• Free-text notes that include opinions about people: people may have a right to see data held about them in some jurisdictions, so write notes as if the person could read them.
• Duplicated information: if the same fact is stored in two places, one will go stale.

What data minimisation means here

Data minimisation is the principle of collecting and keeping only the personal data you need for a stated purpose. Many privacy laws, including GDPR, include a version of it, although details vary by country and change over time. The broader principle is explained in the article on data minimisation.

For your records, the principle suggests a few practical habits:

• Decide what each field is for before you create it.
• Make optional fields genuinely optional on forms.
• Review fields periodically and remove those nobody uses.
• Delete or anonymise records you no longer have a reason to keep.

There is a business benefit too: smaller, cleaner records are easier to maintain, which supports the routines described in the article on keeping CRM data accurate over time.

An illustrative review

Imagine a small training business with these fields: name, email, phone, company, job title, date of birth, home address, favourite colour, and three free-text notes. A quick review might go like this.

1. Name, email, company and job title are used in every message. Keep.
2. Phone is used only for course reminders. Keep, but mark optional.
3. Date of birth, home address and favourite colour have never been used. Remove or stop collecting.
4. Three notes fields are merged into one, with a clear convention for what goes in it.

The result is a shorter form, which can also help completion, as discussed in the article on form design, though results vary.

A simple field policy

Write a one-page list of every field, its purpose, who may edit it and when it is reviewed. Share it with anyone who enters data. It takes little time and prevents the slow build-up of fields nobody can explain. Your list will differ from another business’s, and that is fine: the right fields are the ones you will actually use.