How to Map SPICED Fields in HubSpot

How do you map SPICED fields in HubSpot?

AskElephant recommends a 17-property starting schema for SPICED in HubSpot: five evidence fields, five element statuses, one Critical Event date, and six shared provenance and review fields. Store the current qualification state on the deal, preserve source calls and timestamps across the deal history, and separate automatic evidence capture from interpretations that require manager confirmation.

The goal is not to reproduce a SPICED worksheet inside the CRM. It is to create a current, explainable qualification view that supports coaching, pipeline review, forecasting, and handoff.

After processing more than 398 billion revenue AI tokens as of July 15, 2026, AskElephant has found that structured, source-backed evidence is more useful than a standalone summary score for coaching and forecast review.

AskElephant is an AI-native revenue work system that takes responsibility for advancing CRM updates, follow-ups, handoffs, coaching, and alerts—shaped to how each team actually operates.

What is the AskElephant Qualification Data Model?

The AskElephant Qualification Data Model organizes CRM methodology data into four layers: Evidence → Status → Provenance → Approval. Evidence records what the buyer revealed. Status makes qualification reportable. Provenance preserves the source and time. Approval distinguishes explicit capture from interpretation that requires a manager or RevOps review.

Minimum Production Schema — 14 properties: five SPICED evidence fields, five element status fields, Critical Event Date, Source URL, Observed At, and Review Status. The full 17-property starting schema adds Reviewed By, Last Reviewed, and Schema Version.

This guide provides a recommended schema, not official HubSpot defaults or AskElephant internal property names. Adapt labels and internal names to your portal's existing naming and governance conventions.

If the team has not agreed on the framework itself, start with how to score calls with SPICED or BANT. Field design should follow the settled evidence standard—not define it accidentally.

What do you need before creating SPICED properties?

Before creating SPICED properties, settle the framework definitions, choose the HubSpot object that owns the current qualification state, document existing naming conventions, and identify the reports or workflows each property must support. You also need sample calls and deals for testing. A field without a decision, workflow, or owner becomes property bloat.

Prepare these inputs:

A written definition for Situation, Pain, Impact, Critical Event, and Decision
Confirmed, partial, missing, and not-applicable evidence standards
A list of existing deal, contact, and company properties that may overlap
A naming prefix approved by RevOps
HubSpot property-settings permission
Sample active, won, lost, and stalled deals
Named owners for data quality, methodology, and automation

Review the existing HubSpot custom properties glossary before adding fields. Reuse an existing property when its meaning, object, options, and ownership already match the requirement.

HubSpot's property documentation recommends defining the field type, rules, visibility, access, and sensitivity settings in the property editor. Those controls should be designed with the data—not added after the methodology is already live.

What should a SPICED HubSpot schema contain?

A useful SPICED schema contains the current evidence for each framework element, a status that shows evidence quality, a date for the Critical Event, structured Decision details, and shared provenance fields. Keep the current view easy to filter. Preserve longer history in associated activities or another record designed for repeated observations.

The minimum schema has three layers:

Qualification evidence: What the buyer said about each SPICED element
Qualification state: Confirmed, partial, missing, or not applicable
Provenance and governance: Source, observed date, review status, and reviewer

Layer	Why it exists
Evidence	Lets another person inspect the buyer context behind the field
Status	Makes missing or partial qualification filterable and reportable
Source	Connects the current value to a call, email, or approved record
Observed date	Shows when the evidence was current
Review state	Distinguishes auto-captured, needs review, and approved values

Do not begin with one SPICED Score property. A total score is useful only after the element-level state is clear.

Step 1: Which HubSpot object should own SPICED data?

Keep the current SPICED qualification state on the deal object, associate the relevant contacts, and decide which evidence belongs on the current deal versus an activity or separate history record. Define the scope before creating properties. SPICED describes a specific buying motion, so the same company can have different evidence across two simultaneous opportunities.

Use these ownership rules:

Deal: Current Situation, Pain, Impact, Critical Event, Decision, element statuses, source, and review state
Contact associations: Connect the people involved, but do not assume a plain association records Champion, economic buyer, evaluator, approver, or procurement roles
Company: Durable facts such as industry, employee range, or installed technology when they apply across deals
Activities: Call-specific transcript, summary, timestamp, and evidence excerpt
Custom object: Optional repeated evidence records when deal properties and activities cannot support the required history

Avoid copying current Pain or Critical Event onto the company. A renewal, expansion, and new-logo opportunity can have different urgency and decision criteria.

Plain associations show that a contact and deal are connected; role semantics require a custom association label or a separate deal property. HubSpot requires Professional or Enterprise for custom association labels and Enterprise for custom objects. On lower tiers, use ordinary associations plus controlled deal properties for the current buying-role map.

If your team tracks multiple concurrent deals per account, see multi-account automation for the broader object-boundary problem.

Step 2: How do you define SPICED evidence standards?

Define confirmed, partial, missing, and not applicable for Situation, Pain, Impact, Critical Event, and Decision. Document the evidence required for each status so fields reflect buyer statements instead of rep confidence. The definition should tell an AI, rep, or manager what qualifies, what remains uncertain, and which next question would improve the record.

Element	Confirmed evidence	Partial evidence	Missing	Not applicable
Situation	Business environment, current process, people, priorities, constraints, and trigger for change are understood	General context exists but important operating detail or trigger is unclear	Current state is not documented	The call has no reasonable role in updating current context
Pain	Specific friction, inefficiency, or risk is stated in buyer language	A symptom appears without severity or operating consequence	No material pain is documented	Pain discovery is outside the call objective
Impact	Rational outcome, emotional stake, and consequence of action or inaction are concrete	Improvement matters but consequence is vague or unquantified	No business consequence is documented	Impact should not reasonably be revisited on this call
Critical Event	Deadline, milestone, or external force and why it matters are confirmed	Desired timing exists without a force that makes action necessary	No credible event or timing driver is documented	The call has no timing or milestone objective
Decision	Success criteria, tradeoffs, stakeholders, approvers, process, and steps are mapped	Some criteria or participants are known but the path is incomplete	Decision process and criteria are unknown	The decision process is outside the call objective

Keep evidence and coaching behavior separate. A rep may ask a strong Impact question and receive a vague answer. The deal's Impact remains partial while the rep behavior can still be coached positively.

Step 3: Which HubSpot properties should you create?

Create a compact property set for current status, evidence, critical dates, decision context, source, observation time, and review state. Use suggested names consistently, but adapt internal names to the governance rules already used in your HubSpot portal. Property labels should help people understand the field; internal names should remain stable for integrations and reporting.

Which properties map the five SPICED elements?

Map every SPICED element to an evidence property and a controlled status property. Add separate structured fields only when they support a real filter, workflow, or decision. Critical Event needs a date as well as context, while Decision benefits from criteria and process fields that managers can inspect independently.

Suggested label	Suggested internal name	HubSpot type and field type	Purpose
SPICED — Situation Evidence	`spiced_situation_evidence`	string / textarea	Current environment, process, people, and trigger
SPICED — Situation Status	`spiced_situation_status`	enumeration / select	Missing, Partial, Confirmed, Not applicable
SPICED — Pain Evidence	`spiced_pain_evidence`	string / textarea	Buyer-stated friction, inefficiency, or risk
SPICED — Pain Status	`spiced_pain_status`	enumeration / select	Evidence quality
SPICED — Impact Evidence	`spiced_impact_evidence`	string / textarea	Consequence of action and inaction
SPICED — Impact Status	`spiced_impact_status`	enumeration / select	Evidence quality
SPICED — Critical Event	`spiced_critical_event`	string / textarea	Event, milestone, or external force
SPICED — Critical Event Date	`spiced_critical_event_date`	date / date	Buyer-confirmed date
SPICED — Critical Event Status	`spiced_critical_event_status`	enumeration / select	Evidence quality
SPICED — Decision Evidence	`spiced_decision_evidence`	string / textarea	Criteria, tradeoffs, stakeholders, and process
SPICED — Decision Status	`spiced_decision_status`	enumeration / select	Evidence quality

These internal names are examples. Do not rename existing properties simply to match this guide; API references and workflows depend on stable internal names.

Which shared evidence fields should you add?

Shared evidence fields explain where the current qualification view came from and whether someone reviewed it. Use one set across all SPICED elements when the source is the same, or element-specific source fields when evidence commonly comes from different calls. Choose the smallest model that preserves enough provenance for your managers and RevOps team.

Suggested label	Suggested internal name	Type	Purpose
SPICED — Source URL	`spiced_source_url`	URL	Clickable link to source call or approved activity
SPICED — Observed At	`spiced_observed_at`	Date and time picker	Timestamp when evidence was observed
SPICED — Review Status	`spiced_review_status`	enumeration / select	Auto-captured, Needs review, Approved
SPICED — Reviewed By	`spiced_reviewed_by`	Controlled select or HubSpot user	Reviewer; use HubSpot user only when owner-level access semantics are intended
SPICED — Last Reviewed	`spiced_last_reviewed`	Date and time picker	Review timestamp
SPICED — Version	`spiced_schema_version`	string / text	Rubric version that produced the current status

If source and review state differ materially by element, add element-specific fields rather than storing misleading shared provenance.

HubSpot's Properties API documentation distinguishes the data type from the UI fieldType and requires stable internal names, labels, groups, and type definitions for API-created properties.

Step 4: How do you configure field types and access?

Match each property to the data it stores, use controlled options for reportable states, reserve multi-line text for evidence, and limit view or edit access where qualification data contains sensitive customer context. Choose field types based on reporting and workflow needs. A free-text field is flexible, but it cannot reliably trigger the same downstream logic as a controlled status.

Use these rules:

Textarea: Buyer evidence, Situation, Pain, Impact, Critical Event context, and Decision process
Select: Element status, review status, and any controlled methodology state
Date: Critical Event date
Date and time picker: Evidence observation and review timestamps
Controlled reviewer field: Named reviewer responsibility without changing record ownership semantics
Contact association plus role field or label: Buying roles tied to real contact records, subject to subscription support

Configure access deliberately:

Reps can view all SPICED evidence for their deals
Managers can review and approve interpretations
RevOps can edit definitions, options, and mappings
Sensitive evidence follows the portal's data-access policy
Integrations receive only the write permissions they require

Do not use a checkbox for "confirmed" when partial and not-applicable states matter. A checkbox collapses missing, unknown, and false into the same empty value.

Step 5: How do you preserve source and history?

Store the source call or activity, observation timestamp, and review status beside current qualification evidence. Newer information should update the current view without removing the evidence that explains how the deal changed. HubSpot deal properties should show the current qualification state; activities or a separate record should preserve the sequence of observations used to reach it.

Use a current-state plus evidence-history model:

A call produces a new SPICED observation.
The system stores the source, date, element, evidence, and proposed status.
The approved rule determines whether the deal property updates automatically or waits for review.
The current deal field reflects the latest approved state.
Earlier evidence remains attached to the deal through its source activity or history record.

This matters when evidence changes. A Critical Event may move. A champion may leave.

Impact may become more specific after executive discovery. The CRM should show what is true now without pretending the earlier evidence never existed.

For the evidence-scoring model itself, use the SPICED and BANT scorecard guide.

Step 6: How do you configure automatic writes and review?

Allow direct customer statements to populate evidence automatically, route ambiguous interpretation for review, and block automatic changes to manager-owned forecast decisions. Normalize values before writes because HubSpot property validation does not govern every automation path. Apply write modes by property so clear evidence moves quickly while consequential interpretation remains deliberate.

Use three write modes:

Mode	Appropriate use	Example
Automatic	Explicit evidence and low-risk current state	Save the stated Critical Event date and source
Suggested	Ambiguous qualification or role interpretation	Suggest Decision status as partial and request review
Blocked	Manager-owned or forecast-sensitive judgment	Do not change forecast category from a SPICED score

HubSpot's property validation rules help control data entry, but the official documentation notes that enforcement varies by entry path and does not cover every workflow-driven update. Your integration must normalize dates, internal option values, and allowed formats before attempting the write.

For dropdown properties, map extracted language to exact internal option values. For dates, use the format expected by the API. For text evidence, preserve the customer language without inserting an unsupported interpretation into the quote.

AskElephant can write structured call data directly to HubSpot properties and complete CRM updates within minutes, according to AskElephant. The mapping should reflect your approved schema and evidence rules.

Step 7: How do you test and govern the SPICED schema?

Test the mapping against closed and active deals, compare the resulting fields with manager judgment, and build reports around missing evidence, stale observations, and review status. Assign a RevOps owner for future changes. A schema is ready when people can explain every field, automation can write valid values, and managers can trace important qualification changes to source evidence.

Test in two stages:

How do you test the property design?

Test the property design manually before enabling automated writes. Populate representative deals, build the intended filters and reports, and confirm that each field supports a real decision. Remove fields that duplicate existing data or cannot produce a useful workflow, report, coaching question, or handoff outcome.

Check:

Can a manager filter deals with missing Impact?
Can RevOps find Critical Events that are approaching or stale?
Can a rep open the source behind a status?
Can a reviewer distinguish auto-captured from approved evidence?
Can the schema represent changed evidence without overwriting the history?

How do you test automated field mapping?

Run the mapping in shadow mode against calls where managers already know the deal context. Compare the proposed value, status, source, and timestamp with an independent manager review. Track disagreement by SPICED element and write mode rather than hiding differences inside one overall accuracy number.

Include:

Calls with explicit, partial, contradictory, and missing evidence
Multiple calls from the same deal
Changed Critical Events and stakeholder context
Poor audio or ambiguous references
Existing property values that should be preserved
Dropdown values the system must normalize

AskElephant reports that Vendilli's CRM data completion increased from 15% to 90% when structured updates replaced manual entry. That outcome depends on a clear destination for each piece of evidence—not simply generating more notes.

What reports and workflows should SPICED fields support?

SPICED fields should support decisions people already make: which deals need qualification, where coaching is required, whether urgency is credible, which buying processes remain unmapped, and whether evidence is current. Build reports from element statuses and observation dates, then trigger work only when the signal has an owner and an approved response.

Useful views:

Deals with missing or partial Impact in discovery or later
Critical Event date inside 60 days with incomplete Decision evidence
Confirmed Pain with no measurable or concrete Impact
Decision status missing in proposal or negotiation stages
SPICED evidence not observed or reviewed within the approved freshness window
Auto-captured qualification awaiting manager review

Useful workflows:

Create a coaching task when a stage-appropriate element remains missing
Notify the deal owner when Critical Event evidence becomes stale
Route ambiguous Decision interpretation to a manager
Add approved SPICED context to a sales-to-CS handoff
Include qualification gaps in deal-risk review

Do not trigger punitive action from one missing field. SPICED is a diagnostic framework. A missing element should create the next question, not a verdict about the rep or deal.

What mistakes should you avoid when mapping SPICED?

The most common mistakes are creating one unexplained score, storing every element in free text, duplicating properties across objects, omitting source and review fields, treating validation as protection for every write path, and letting automation convert ambiguity into a confirmed value. Avoid them with a compact schema, controlled statuses, provenance, stable names, and field-specific approval rules.

Creating properties before settling definitions: The CRM should implement the rubric, not become the place where managers debate it.
Using one SPICED score: A total hides the element and evidence that require attention.
Duplicating fields across objects: Deal-specific evidence belongs on the deal.
Using text for reportable state: Keep evidence in text and status in a controlled select.
Dropping source history: Current state without provenance cannot support trustworthy coaching.
Renaming internal properties casually: Integrations and workflows depend on stable internal names.
Assuming all validation applies to automation: Normalize values inside the write workflow.
Auto-confirming ambiguous evidence: Preserve uncertainty and request review.

Property restraint is part of good architecture. The broader guide to HubSpot properties worth automating helps place SPICED inside the full revenue schema.

How does AskElephant help with SPICED fields?

AskElephant takes responsibility for the repeatable work between recorded calls and your HubSpot SPICED schema. It can score calls against custom SPICED criteria, preserve timestamped coaching evidence, and write structured call data directly to mapped CRM fields. Your team defines the property schema, evidence standard, and approval boundary; managers retain judgment over qualification and forecast decisions.

AskElephant supports:

Custom SPICED scorecards and criteria
Automatic evaluation across recorded calls
Timestamped evidence and coaching moments
Direct HubSpot field updates
Manager and rep scorecard delivery
CRM updates within minutes, according to AskElephant

AskElephant has a 5.0 rating on the HubSpot Marketplace with more than 200 installs. See how customers use AskElephant and the broader CRM field automation map.

AskElephant pricing: Core starts at $99 per user/month when billed annually. White-Glove starts at $119 per user/month when billed annually and has a five-seat minimum. Enterprise pricing is custom. View pricing.

Watch how this works in HubSpot

What are common questions about SPICED in HubSpot?

RevOps and sales leaders most often ask how many properties they need, which object should own the data, whether to store a score or element statuses, how AI should populate fields, how to preserve history, and whether a custom object is required. Start with current deal evidence and provenance, then add complexity only when reporting or workflow requirements justify it.

How many HubSpot properties do you need for SPICED?

The starting schema shown here contains 17 deal properties: five evidence fields, five status fields, one Critical Event date, and six shared source, observation, review, and version fields. Element-specific provenance increases that count. Start compact and add properties only when a real workflow or decision requires them.

Should SPICED fields live on deals, contacts, or companies?

Keep opportunity-specific SPICED evidence on the deal. Associate contacts to identify participants; use custom association labels on Professional or Enterprise, or controlled deal properties on lower tiers, to record buying roles. Use company properties only for durable facts. Copying qualification state across objects creates conflicts between opportunities.

Should HubSpot store a SPICED score or element statuses?

Store element-level statuses and evidence first. A single score hides which qualification area is weak and why. If leadership needs a summary number, calculate it from the approved statuses while keeping Situation, Pain, Impact, Critical Event, Decision, source, and review state visible for coaching and pipeline decisions.

Can AI populate custom SPICED properties in HubSpot?

Yes, when each property has a clear definition, accepted value format, and mapped evidence rule. AI should capture explicit customer statements automatically and preserve the source. Ambiguous roles, inferred impact, low-confidence language, and forecast-sensitive interpretations should be suggested for review rather than written as confirmed.

How do you update SPICED fields without losing history?

Store the current value with its source call, observation timestamp, and review status, then preserve earlier evidence in call activities, notes, or a history object appropriate to your HubSpot tier. New evidence can update the current property while the underlying record still explains what changed and when.

Do you need a HubSpot custom object for SPICED?

Not for a basic implementation. Current SPICED qualification can live on deal properties, with contacts associated to the opportunity and source calls stored as activities. Custom association labels require a Professional or Enterprise subscription, while custom objects require Enterprise. Lower tiers can use ordinary associations plus deal properties for buying roles.

Which related guides should you read next?

These guides cover the methodology, broader HubSpot architecture, CRM field automation, deal-risk use, and sales-to-CS handoff around this schema. Use this article for the SPICED property implementation itself, then connect it to the relevant coaching and revenue-work systems without creating duplicate fields or parallel definitions.

Book a demo to see it in action