Skip to content

Trip Planning

Part of: ClientVerse Core (every client).

What it is

Trip Planning is ClientVerse's tool for organizing business-development trips and events — a conference, a city visit, a client roadshow. A Trip anchors the plan: its legs (the stops or days), the targets the firm wants to meet, the participants travelling, and an optional business plan describing goals and follow-up. It turns a scattered "who's going where and to see whom" into one structured, shareable record.

Who it's for

  • BD — plans the trip, lines up targets, and tracks outcomes.
  • Attorneys — see where they're going, whom they're meeting, and what the firm wants from it.

How it works

The feature is anchored by the Trip object, cited from objects/core-key.yaml; field-level detail is in the Data Dictionary.

Trip (Trip__c)

A planned BD trip or event (8 fields), user-entered. A trip organizes four kinds of related detail:

  • Legs — the stops, cities, or days that make up the trip's itinerary.
  • Targets — the contacts, accounts, or prospects the firm wants to meet on the trip.
  • Participants — the firm people travelling or attending.
  • Business plan — the optional goals, talking points, and intended follow-up for the trip.

By relating targets and participants to a single Trip__c, the firm gets a clear picture of who is meeting whom, and can coordinate so attendees aren't unknowingly calling on the same target.

How to use it

Planning a trip (BD)

  1. Create a Trip__c for the event or visit.
  2. Add legs for each stop/day to lay out the itinerary.
  3. Add targets — the contacts and accounts the firm wants to engage. Pull these from lists and classifications to focus on the right audience.
  4. Add participants — the attorneys and BD staff attending.
  5. Capture the business plan: goals for the trip and the follow-up expected afterward.

During & after (attorneys / BD)

  • Attorneys review their legs, targets, and the business plan before they travel.
  • After the trip, follow-up is tracked against the trip and its targets so outcomes aren't lost.

Key objects

Object Fields Role
Trip__c 8 A planned BD trip/event, with legs, targets, participants, and a business plan

Trip Planning relates to other Core entities (accounts, contacts, experience) and to BD permissions. For the complete object and field reference see the Data Dictionary.

Configuration pointers

  • Trip management is governed by the BD permission sets — notably CV_BD_Trip_Management (plus CV_BD_Operations / CV_BD_Task_Management for the wider BD workflow).
  • See the Admin Guide for enabling BD features and the User Guide for the end-to-end BD workflow.

Limits & known issues

  • A trip is a planning artifact — its value depends on participants keeping targets and follow-up current; stale trips don't reflect what actually happened.
  • Coordinating overlapping targets across multiple concurrent trips relies on BD reviewing the target lists; ClientVerse surfaces the data but doesn't enforce de-confliction.