Skip to content

Recognition — awards, rankings and directories

Directory submissions — Chambers, The Legal 500, IFLR1000 — run on the same raw material every year: which rankings the firm holds, which clients agreed to act as referees, and which work supports the submission. Recognition is where that is meant to live so it is not rebuilt from email each cycle.

Read this page before planning work around Recognition. In this release the objects exist and hold data, but the screens around them are minimal. This page describes what is genuinely there rather than what the feature is intended to become.


What exists today

Two objects, both with tabs in the CV Intelligence app:

Recognition — one record per ranking or award. Beyond the name, it carries four classification links: Primary Practice, Primary Industry, Primary Geography, and Primary Tag.

Recognition Contact — the people attached to a submission. This is the richer of the two, and holds the material a submission actually needs:

Field What it is for
Contact The person
Member Type Their role in the submission — referee, client reference
Client or Non-Client Whether the referee is a client
Point Person / Point Person Contact Who owns the relationship with them
Referring Lawyer / Referring Lawyer Contact Who at the firm put them forward
Work Highlight The work the reference speaks to
Relevant Transaction The specific matter or deal
Practice Area, Industry, Primary Practice, Primary Industry Categorisation
Also Referee For Where else this person is being used

Also Referee For is the field that earns its place. Asking the same client to act as a referee for four submissions in one cycle is the quickest way to lose their goodwill. This is where you check before adding them again.


What is missing in this release

Being direct about it, because planning around it otherwise wastes time:

  • The Recognition record page shows almost nothing. It displays Name, Owner, Created By, and Last Modified By — and nothing else. The four classification links on the object are not on the page, so they cannot be set or read from the record without an admin adding them.
  • Recognition Contacts do not appear on the Recognition record. The record has a Related tab, but it reports "No related lists to display" — so from a Recognition you cannot see its referees at all. You have to work from the Recognition Contact tab and filter, which is backwards from how a submission is actually assembled.
  • Recognition Contact has no custom page, so it renders with the default layout.
  • There is no submission workflow — no status, no deadline tracking, no submitted/won/lost lifecycle. A Recognition record is a label, not a process.

Together, these mean Recognition is a data store in this release, not a submissions tool.


Working with it anyway

If your firm is using Recognition now, the practical approach is:

  1. Work from the Recognition Contact tab, not from Recognition records. That is where the useful fields are.
  2. Build a list view on Recognition Contact filtered by the Recognition you are working on, and use that as your working set.
  3. Check Also Referee For before every ask, since nothing else will warn you.
  4. Keep the submission's own status in your existing tracker. The object does not hold one, and inventing a convention in a text field creates a migration problem later.

If you want the record page to be useful

Adding the four classification fields, and a Recognition Contacts related list, to the Recognition record page is a straightforward Lightning App Builder change your administrator can make without touching the package. If Recognition matters to your firm's cycle, that is a short conversation worth having — see the Admin Guide.