Prepare a client spreadsheet without internal columns

Prepare a dated snapshot for one recipient, compare every saved value, and keep recipient-access verification separate.

A client needs the status of two jobs. Your working spreadsheet also contains other clients, internal costs, and notes. Before sending a link, decide exactly which rows and values the recipient may receive. Use those values to prepare a separate file with saved values, without formulas or source connections. Reopen and check this static output.

You will have a snapshot for one recipient as of a specified date. This process suits a one-time handover in a small service team. If the client needs continuously updated data or collaborative editing, a static file will not meet that need. Make a separate access decision before giving them access to your internal spreadsheet.

Hiding and protection do not remove internal data

Google says sheet or range protection restricts editing and should not be used as a security measure. Editors can unhide sheets; the documentation also describes unhiding them in a copy made by a viewer. Hidden columns can be shown again in the interface. Do not treat hiding as removing data from the file you hand over. See protection and hidden sheets and hidden rows and columns.

Google also documents making a copy and downloading a file. A copy alone does not establish that you removed internal content. What matters is the finished output’s contents, rather than its filename or what was visible on screen. See copying and downloading.

1. Define the output before copying

Name the person responsible and record:

• the recipient and purpose of the snapshot;
• the date the data represents;
• allowed job identifiers or another unambiguous row selection;
• allowed columns in their required order;
• the output format and existing approved delivery method.

“Without internal costs” is insufficient. Even the right columns can contain another client’s job. A status field may contain an internal comment alongside the status. Selecting columns, selecting rows, and checking their actual contents are three separate tasks.

If you are unsure whether particular text belongs with the recipient, pause preparation and have the responsible person assess it. Do not transfer it or replace it with a guess before that decision.

2. Prepare a fresh output using approved values only

For a few cells, a manual process is enough: write the approved headers in a new blank file, transcribe the checked displayed values for the selected jobs, and compare them with the source. Leave the internal original unchanged.

Start with a blank destination. Do not copy an entire workbook intending to delete parts later. Do not carry over source links, formulas, internal comments, or extra sheets. If you need a calculated result, transfer its verified displayed value and check that it retains its unit and meaning. Use an unambiguous date format, such as 2026-10-20 in the example below.

Google documents Paste special within a single spreadsheet. Do not treat that documentation as verification of a process between files. This guide therefore does not promise that pasting values between two workbooks resolves dependencies or preserves the correct display. See the scope of Paste special.

3. Compare the output with an exact expectation

The following example is entirely fictional. It is neither a client engagement nor a Google account test. It shows the difference between internal source material and an output you can check cell by cell.

The internal source has eight columns:

job_id, client, deliverable, due_date, status, internal_cost, internal_note, source_url

Its three jobs are:

The table intentionally omits the internal columns. The complete fictional source CSV contains them. Only jobs DEMO-A-01 and DEMO-A-02 and four columns are approved for Client A in this example. The expected output is exactly:

job_id,deliverable,due_date,status
DEMO-A-01,Homepage design,2026-10-20,Awaiting review
DEMO-A-02,Change summary,2026-10-22,In progress

The Client A CSV contains this static example. Check the order of all four headers, both identifiers, and every value. The third job must not slip through simply because it has the same columns. The output must also exclude client, internal_cost, internal_note, and source_url.

Use the source-to-output diagram to compare all eight fields and three source records with the two approved records. It illustrates a manual, reviewed selection, not an automatic exporter or verified recipient access.

These CSV examples are for practice. They are not forms for submitting real internal data to a public website. CSV here is plain tabular text; it requires neither an exporter nor a live Google Sheets connection.

4. Open the exact file you intend to deliver

Check the saved output, rather than only its preview before saving. For CSV, inspect the file’s text too: do headers, rows, and values match? Then use your intended application to check accented characters, column separation, dates, and whether any content behaves as a formula. A correct-looking first screen does not replace these checks.

For another format, also inspect extra sheets, hidden sections, comments, links, and any source connections. This guide does not automatically sanitize arbitrary workbooks. If you cannot reliably assess the contents, return to a smaller fresh output with checked values.

A value starting with =, for example, warrants review. Removing one character is not a universal repair. Base the decision on the actual contents and destination application.

5. Check contents and access separately

Before delivery, check who currently has access to the destination file and its containing folder. Google Drive distinguishes Viewer, Commenter, and Editor roles; access can be inherited from a folder. A work or school account may restrict external sharing. The documentation used here covers My Drive files, rather than a complete audit of shared drives, groups, or an organization’s environment. See sharing files in Google Drive.

During preparation, do not change live permissions, send invitations, or bypass a restriction with a public link. If the existing approved delivery method does not allow the intended recipient access, record the specific problem and pass it to the responsible person.

Opening the file yourself verifies only your access. During subsequent authorized delivery, have the intended recipient open it and record the actual result. Until then, keep the status “recipient access unverified.” Neither this article nor its example performed that delivery. For the broader file handover, see client files and access.

A checklist for your next snapshot

Use the output checklist for the exact saved file. Before delivery, confirm that it contains the right rows, columns, and values, carries over no formulas or source links, and has appropriate access. Recipient verification remains a separate step with its own result.

For repeated outputs, you could later prepare a local tool with an explicit allowlist of columns and jobs. It would need to check the actual input and output and leave delivery to a person. No such tool is supplied here; you can check this small finished example directly against the CSV above.

Sources: Google documentation checked October 17, 2026; publication dates of the individual pages are unknown. The process and fictional example are editorial recommendations. They are not a customer-account test, legal assessment, or guarantee that all sensitive data has been removed. Recheck the procedure if protection, copying, pasting, or sharing documentation changes.