Export only the rows that are actually ready
Exporting is the easiest step to rush and the easiest one to get wrong. If the sheet still contains unreviewed rows, the export can carry that uncertainty into the next tool. This workflow exists to make the handoff deliberate: only approved rows move forward, and only the fields the next system needs come along with them.
The key idea is to decide what the destination expects before you export anything. A CRM import does not need the same shape as an outbound tool or a reporting sheet. By narrowing the export to the right columns, you avoid extra cleanup later and keep the receiving workflow easier to maintain.
- Filter to approved rows before exporting.
- Match the export columns to the target system.
- Keep review status in the sheet if the handoff is not final.
This is also the point where the spreadsheet becomes a control layer instead of a dumping ground. The team can keep enrichment and scoring context in Cockpit, then hand off a cleaner subset to another tool when the rows are ready. That makes it easier to rerun the workflow later, because the source sheet still contains the review trail.
| Destination | What to keep in the export |
|---|---|
| Outbound tool | Email, first name, company, and any personalization fields. |
| CRM | Identifiers, core company fields, and routing data. |
| Reporting sheet | Approval status, enrichment results, and summary columns. |
When the export is done well, the next system gets exactly what it needs and nothing extra. That is what turns a reviewed spreadsheet into a reliable handoff rather than just another file.