Guide Users With Sample Data Rows (Then Remove Before Use)

Why sample rows are powerful

A good sample row shows users exactly what you want. No guessing. No ambiguity. Users see the format and copy it. This single technique prevents more errors than detailed instructions.

Shows real format, not just instructions

Users see an actual example with real data. They understand immediately. Example beats explanation.

Reduces support questions

When users can see exactly what you want, they don't email asking 'Is this right?' or 'What format?'

Works across languages and skill levels

A concrete example works for non-native speakers and users unfamiliar with spreadsheets.

Prevents common mistakes

Users who see '1299.99' in the example are far less likely to type '$1,299.99'.

Improves data consistency

When everyone copies the same format, your data is clean and consistent.

Example comparison:

Just a header

Email Address

One address or several? Work or personal? People guess.

With sample row

Email Address
john.smith@company.com   ← sample row

One full work address per row. Nothing to guess.

Creating effective sample rows

Sample rows should be realistic, complete, and easy to identify.

Use realistic, recognizable data

Use data that feels real. 'john.smith@company.com' is better than 'test@test.com'. It helps users understand context.

Fill every column

Include data for all fields, even optional ones. Show what complete data looks like.

Show edge cases when relevant

If a phone field can have extensions or special formatting, show that in the example.

Make it easy to identify

Put the sample row immediately below the header. Use a comment or color to mark it. Make it obvious.

Keep it minimal (one row only)

One sample is enough. Multiple examples confuse users. One clear example is perfect.

Use comments to explain non-obvious fields

For complex fields, add a comment: 'Sample: Include area code (555) 123-4567'. Keep it brief.

Protect sample rows from accidental changes

You don't want users accidentally modifying the sample row or deleting it. Lock it down so it stays intact.

Option 1: Lock the row (Excel)

1Select the rows people will fill in, from row 3 down (for example rows 3 to 500)
2Right-click → Format Cells → Protection tab, untick 'Locked', and click OK
3Leave rows 1 and 2 (header and sample) as they are: every cell is locked by default
4Go to Review → Protect Sheet, leave 'Delete rows' unticked, add a password if you want one, and click OK

If someone tries to change the header or the sample row, Excel shows a message that the cell is protected. Rows 3 and below work as normal.

Option 2: Mark with color + instructions

If you can't lock rows, use visual cues:

• Color the sample row (light gray or light blue)
• Add text in column A: "SAMPLE - Replace with your data"
• Bold the sample row to make it obvious

Header Row
[SAMPLE] john.smith@company.com  (555) 123-4567  100 Main St
[YOUR DATA]
[YOUR DATA]

Pro tip

Lock the entire first two rows (header + sample). Let users edit only rows 3 and below. This prevents them from messing with your structure.

Remove sample rows before importing

The sample row is for the spreadsheet, not your data. You must remove it before importing into your workflow.

How to remove the sample row:

1Open the completed spreadsheet
2If you protected the sheet, unprotect it: Review → Unprotect Sheet
3Right-click the row 2 number (the sample row) and choose 'Delete'
4Your actual data rows move up
5Save the file as CSV
6Now import as usual. The sample is gone.

Why it matters:

If you import the sample row as real data, it will appear in your system. Your database will have "john.smith@company.com" as a real customer. That's not what you want.

Automation tip

If you're processing many files, create a script that automatically removes row 2. This prevents human error and ensures sample rows never get imported.

Sample row templates by use case

Customer Contact List

First Name,Last Name,Email,Phone,Company
John,Smith,john.smith@company.com,(555) 123-4567,Acme Corp

Note: The sample shows a full email address and how to write the phone number, so the headers can stay the names your import expects.

Product Pricing

Product Name,SKU,Price,Quantity,Notes
Blue Wireless Mouse,BW-MOUSE-01,29.99,100,In stock

Note: Price shows no $ symbol. SKU shows format. Quantity is a whole number.

Event Registration

First Name,Email,Event Date,Attendance,Dietary
Jane,jane@example.com,01/15/2026,Yes,Vegetarian

Note: The date shows the format (MM/DD/YYYY here, if that's what your system reads), Attendance shows Yes/No, and the optional field is still filled in.

Invoice Data

Invoice Number,Invoice Date,Amount,Status,Due Date
INV-2026-001,2026-01-15,1299.99,Paid,2026-02-15

Note: Dates use YYYY-MM-DD. Amount has no symbols. List the allowed Status values (Paid, Pending) in your instructions.

Sample row checklist

Sample row is immediately below the header

All columns are filled (even optional fields)

Sample data is realistic and recognizable

Format is exactly what you expect users to copy

Sample row is visually distinct (color, bold, text label)

Sample row is locked to prevent accidental changes

Instructions tell users to delete the sample before importing

Sample row gets removed before data is imported to workflows

Each file type (customers, invoices, etc.) has its own sample

Sample row uses realistic company/person data (not 'test')

Edge cases are shown if relevant (e.g., phone with extension)

You have a process to remove samples automatically if possible

Collect clean data with guided templates

Import Builder helps you create data collection forms with clear field labels, validation, and real-time feedback so users always enter the right format.

Start building free