All guides

Capture & deduplication

Print a B2B lead brief as PDF

Open print preview, check that headers repeat and long URLs wrap, then use the browser's Save as PDF destination.

Start with a small representative sample

A founder wants a paged meeting handout from a filtered list with company, role, and source details grouped for quick review.

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.

Set a Workbench search that produces the intended subset and compare the count with the generated brief. Check long company names and source-specific fields.

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.

An unusually long raw table cell may span more than one page. Inspect the page breaks and limit the brief to the rows needed for the meeting.

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 Lead brief. 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.

FieldVisible exampleExpected result
Lead briefA filtered list of eight potential partnersA paged local preview with eight visible lead entries

Open print preview, check that headers repeat and long URLs wrap, then use the browser's Save as PDF destination.

Inspect the print layout at the target paper size. Pay attention to header repetition, wrapping, and any added browser URL or date decorations.

Prepare a test brief with a long site address, a narrow name column, and a record that includes raw table values. Review its second page or use a longer list when verifying how the headers repeat and rows break.

Review the cases that can slip through

Printing the interactive Workbench grid can clip horizontally scrolling fields or show its editing controls.

A PDF makes it easy to review a shortlist in order but obscures underlying joins and calculations. Choose filters in the Workbench first and verify the resulting lead selection after opening the brief. If you forward the PDF, note when the directory content was captured and which rows still need confirmation.

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.

Keep PDF access limited to the necessary reviewers, and retain a structured CSV separately if the next step requires editing.

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.

Keep decision notes outside the copy if the audience only needs the source values. Use the separately editable CSV for any further cleanup.

In the browser print dialog, choose the intended paper size and check browser-added headers or footers before saving. Share a readable PDF only after comparing its selection with the current Workbench and confirming the audience actually needs the visible contact fields.

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 Lead brief 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.