All features

Advanced Filters & Saved Views

Structured data is only useful if you can act on it before the client calls.

Every field RayCruit captures is filterable, and any filter can be saved as a named view the whole team shares. The result is that the first question of the morning stops being 'where did we leave this' and becomes a list with a number next to it.

  • Filters across candidates, mandates, customers and pipeline
  • Any filter saved as a named, shared view
  • Live counts that move with the pipeline
  • Operational hygiene queues, not just search
Candidates · Filters
Candidate pool with saved views for shortlist, in interviews, placed this month, review needed, stale matrix and missing consent, an advanced filter bar and the filtered result table.

The problem

Recruiters spend the first hour of the day reconstructing yesterday.

Without shared queues, every recruiter keeps a private mental list of what needs attention — who is waiting on a client response, which interview is tomorrow, which candidate never returned their consent. It works until the list gets long, someone is away, or a client asks for a status update on a search nobody has touched in nine days.

  • Status is reconstructed by opening records one at a time
  • Each recruiter tracks outstanding work differently
  • Operational problems — stale matrices, missing consent — surface only when they cause damage
  • Team leads have no consistent way to see where a search is stuck

Filter anything, save it, share it.

Advanced filters reach every structured field the platform holds, across objects. Saved views make the useful combinations permanent and shared, so the team works from the same queues.

01

Cross-object filtering

Filter candidates, mandates, customers and pipeline state on structured fields — skills, languages, availability, stage, owner, client, commercial model and more.

02

Saved views

Any filter combination becomes a named view. Views are shared, so 'Waiting for customer' means the same thing to everyone in the firm.

03

Work queues with live counts

Each view carries a live count, which turns the sidebar into a genuine to-do list rather than a set of bookmarks.

04

Delivery queues

Shortlist, interviews this week, waiting for customer and placed this month cover the day-to-day rhythm of a search team.

05

Hygiene queues

Matrix stale, consent missing and mandates with no candidates surface the operational problems that quietly damage delivery.

06

Team and personal scope

Views can serve the whole firm or a single recruiter's workload, so oversight and daily work use the same mechanism.

Turning a question into a queue

The pattern is always the same, which is what makes it stick.

  1. 01

    Ask the question

    Which shortlisted candidates are waiting on client feedback longer than a week?

  2. 02

    Build the filter

    Combine pipeline stage, submission state and time in stage.

  3. 03

    Save the view

    Name it and make it available to the team.

  4. 04

    Work the queue

    The view carries a live count and updates as the pipeline moves.

  5. 05

    Review it

    Team leads use the same views for oversight, so everyone reads the same numbers.

How search firms use it

The Monday standup

Interviews this week and waiting for customer replace a status round-table that used to take forty minutes.

Consent hygiene

A consent missing queue catches gaps before a candidate profile is sent to a client rather than after.

Stalled searches

Mandates with no candidates and matrix stale expose the searches that have quietly stopped moving.

What changes

Less status archaeology

The pipeline answers the status question instead of a person reconstructing it.

Shared definitions

A saved view means everyone measures 'waiting for customer' the same way.

Problems caught early

Hygiene queues surface issues while they are still cheap to fix.

See it in motion

The platform, end to end, in two minutes.

How the modules hand over to each other in the real product — customer and mandate, candidate and matrix, the workspace where a pairing is decided, and the material that goes to the client.

2 min

See the modules working together.

A demo follows one mandate across every module, which is the only way the connections become obvious.