Capture & deduplication
Classify sales lead seniority and department
Inspect representative roles in each category and leave a neutral treatment for ambiguous job descriptions.
Start with a small representative sample
A founder wants to filter captured outreach prospects by role without building a large manual lookup table.
Choose a source page you are authorized to use. Make a named list for the job so you can compare new rows with earlier entries from the same source. Include a typical row, a row with a missing or ambiguous value, and a row with formatting that tends to break the next step. A sample can be just a few rows as long as it gives you a way to verify the process before using a whole campaign.
Build a test set with chief officers, founders, directors, managers, and individual contributors. Include one hybrid role from each relevant department.
Check the source before export
Start in the ordinary page or view containing the records and choose an appropriately named list. Click the toolbar capture button and inspect the added count. For a multi-page job, move to the next page yourself, wait for it to render, and capture into the same list. Compare the first few added records with the visible source. If the page is a virtualized grid, work from the segments you can actually see after changing the view.
A term like Head of can indicate responsibility at different levels depending on the organization. Check the original role when the distinction matters.
Write down the number of source records you expect to review. If only part of a source table renders at once, make sure your count describes the portion you actually captured. The evidence can be simple: a distinct first row, a last visible row, and a field you can find again later. On a repeated run, these reference points help explain the difference between a bad mapping and a changed source page.
Work through an example
The table shows what a useful before-and-after check looks like for Seniority and department. Use it as a model for your own field map. Inspect the visible input first. Look at the output in its intended form, then consider what an operator would do if the source value turned out to be unavailable or different. When the field has more than one legitimate interpretation, include a second example with a different expected result.
| Field | Visible example | Expected result |
|---|---|---|
| Seniority and department | SVP, Sales | VP / Sales |
Inspect representative roles in each category and leave a neutral treatment for ambiguous job descriptions.
Look for a qualifier indicating Sales Operations, People Operations, or other cross-functional work. Compare the displayed title and the classifier output side by side.
Try COO, VP of Engineering, Senior Recruiter, and People Operations Manager together. Observe how title expansion, seniority, and department each change independently. Keep the department blank if the role text lacks enough evidence.
Review the cases that can slip through
Equating a normalized role tag with organizational authority can misroute a personalized campaign.
Evaluate whether a compound role belongs in the campaign at all before debating the derived tag. For example, a small-company founder may still own engineering while a large-company VP title implies a very different scope. Building small, reviewable segments often yields a better workflow than making a universal role taxonomy.
Check the sample after filtering and editing. Search should return both the ordinary case you expect and the exception you selected deliberately. If the exception is hard to find, add a review note or place it in a separate list. Keep an original source reference where it is useful. The goal of this pass is a repeatable decision about those few ambiguous rows before the selection takes on a life of its own.
Prepare the destination
Open the Workbench in its own tab and inspect raw source columns as well as derived ones. Use the search box to find representative names, employers, or terms. Update a cell if the visible source supports the change. A skipped duplicate may be an expected overlap from two pages, or an ambiguous match you need to look at. Keep the context of a match available before relying on the final total as a measure of what was captured.
Use the derived tags for filtering and keep the original job title as a review field for the operator.
Label the first output a trial and record the list name, selection, target format, and the field that determines whether the row can be used. Compare at least one expected blank and an ordinary populated row after export. Keep test changes easy to roll back. For larger jobs, measure the number of rows that need manual handling so you know where the remaining review will take time.
Validate what the recipient will use
Compare the final presentation to the human decision that uses it. A CSV is suited to an editable follow-up, TSV works for a quick paste, a PDF supports reading in a meeting, and a ZIP keeps campaigns apart. Capture and export are separate decisions, especially when a list contains contact details that only one reviewer needs. If the downstream task needs just a narrow set of rows, apply a filter in the Workbench before the CSV, TSV, or PDF step.
Review whether a category decision would change what the team sees or does. When it would, require original source evidence for high-impact exceptions.
Review special cases where a Director title has an operational meaning or Manager occurs inside a product name or title modifier. Group the results by how the labels will be used downstream. A coarse filter can be helpful even when only a human can make an important final judgment.
Review one result where the converted value looked straightforward and one where your team had to choose between plausible interpretations. Give the recipient the updated row count and a practical next action. If review exposed a source inconsistency, note the observable issue and include enough context for the recipient to reproduce it. Close the loop by storing or removing the trial material according to how long your team needs it.
Record the minimum needed for a repeat run
Save a simple checklist with your source path, list name, review filter, format, and destination fields. Keep the choices about Seniority and department near the top so the next operator can pick a meaningful test row. A useful recurring process records the fields that affected the outcome and the points where someone needed judgment. It can be rerun when the source layout changes without forcing every old decision into a script.
LeadSheet Clean keeps captured rows and derived values in the browser. Start with Standard Clean CSV or copy TSV when you need a quick review sample. Lifetime Pro adds unlimited export rows, specialized presets, PDF briefs, and multi-list ZIPs. Select the path that produces the format and selection required for your handoff, and verify the license or Free allowance before repeating a large export.