Changing the source file does not tell you what someone gets from last month's link.
A lead magnet can exist in several places at once: the editable original, a downloadable file, a page that describes it and copies people have already saved. Plan the update around those different places. Otherwise, the page can promise one edition while the download provides another.
This guide produces a change record for one existing, free, nonpersonal resource. It covers a planned revision before anyone reports a failure. Finish with the proposed edition, its existing link destinations and the evidence needed to approve the update.
Identify the edition that is actually available
Start with the public entry page, the download reached through it and the editable source. Give the current resource an understandable edition identifier. Record the identifier inside the file as well as in your working notes; a filename can change when someone saves it.
Use an identifier you can maintain, such as “Room preparation worksheet — edition 1.” Add a date only when you know what it means. A file's saved date, the date its facts were checked and the date it became available are different events.
Download the currently offered copy through the intended reader path. Open the saved file and identify its contents. Finding edition 2 in your editing folder does not establish that readers receive edition 2.
Describe the change before replacing anything
Write one sentence about what changes for the reader. “Updated the resource” hides the decision. “Added a missing step for listing items that cannot be moved” gives the reviewer something to assess.
Separate the change into one of three working categories:
- A correction keeps the same task but fixes something inaccurate or unclear.
- An addition helps finish the same task without changing its promised output.
- A different task or offer needs its own scope decision. It may belong in a separate resource.
These categories are an editorial aid, not a technical versioning standard. A small text edit can still be important if it changes an instruction. Record its effect instead of judging it by the number of words changed.
Map where an old link can still be used
List the places the business controls: the entry page, a confirmation page, a prepared message or a help article. Record the exact resource each place currently references. Do not include private recipient details in this register.
Then identify links already distributed, such as a link in an earlier email. Editing a new email draft does not change that old message. Give each old destination an explicit proposed outcome: continue serving an identified edition, provide an approved explanation and current route, or remain unresolved until an owner decides.
Changing URLs, access rules or redirects is implementation work. Assign it to the responsible owner; this worksheet does not authorize it. Keep intentional CF2 journeys outside a CFAI resource update unless they are explicitly part of the same approved task.
Work through a fictional edition change
Harbor Room Studio offers a free Room preparation worksheet, edition 1. It helps a reader list room dimensions, existing items and questions for a future design conversation. It does not provide a design or reserve a consultation.
The proposed edition 2 adds a field for items that cannot be moved and clarifies a blank measurement example. Rae owns the content. Kit owns the delivery path. These people, files and decisions are invented; no update has been executed.
Scroll horizontally to compare all columns.
| Record | Current situation | Proposed decision |
|---|---|---|
| U01: entry page | Describes the room preparation task and links to edition 1 | Keep the task description; name edition 2 only when that file is actually available through the link. |
| U02: confirmation page | Offers the same worksheet through a second link | Include this link in the update and check its saved file separately. |
| U03: previously sent email | Contains an older direct file link | Ask Kit what that exact destination will serve. Do not assume changing the entry page changes it. |
| U04: proposed bonus | A teammate wants edition 2 to include a paid design consultation | Hold the bonus. It changes the offer and needs a separate decision, not a silent file revision. |
For this example, the content owner approves the added field as part of the existing task. The old email destination remains unresolved. That means the preparation is incomplete even if the new document looks finished.
The proposed change note is: “Edition 2 adds a place to list items that cannot be moved and clarifies the measurement example.” It describes the revision without claiming that every previous reader received it.
Check the file, not just the button
Browsers and other systems can reuse stored responses. MDN's HTTP caching guide explains that behavior and describes versioned resource URLs as one caching approach. It does not establish how your current file host behaves.
Ask the delivery owner how this update reaches readers. Do not prescribe a cache setting or assume that renaming a file fixes every old link. For the approved plan, open each in-scope entry route and save the resource it actually provides. Check the internal edition, changed instructions and usable blank sections.
Record the URL, time, browser context and observed edition. Keep “new visit checked” separate from “returning visit checked.” If one context serves the old edition, record that result and ask the owner to investigate before declaring the update finished.
If the resource has a text alternative, check that it contains the same essential revision. A corrected PDF and an unchanged text copy can give readers different instructions. Keep each required format in the same change record.
Decide what previous readers need
An update on a website does not establish that a file already saved on someone's device has changed. Do not promise that all old copies have been replaced.
Ask the content owner whether the change needs a notice for earlier readers. A spelling correction and an instruction that could lead someone to do the wrong thing deserve different judgments. Record the decision, its reason and any authorized communication route. A notice drafted in this worksheet has not been sent.
If an earlier edition is inaccurate, do not make it the automatic fallback merely because it used to be available. Choose a checked correction or an honest explanation of the unresolved access. The owner must decide what is appropriate for the actual issue.
Close one update with a usable record
Use the lead-magnet update worksheet to connect the change, editions, controlled placements, old links and saved-file observations. Mark each planned check NOT RUN until it happens. Finish with a content decision and a delivery decision; either can still be unresolved.
For a ClickFunnels AI project, bring that record to the agent guide under the current workflow and access requirements. This exercise does not establish built-in file versioning, automatic replacement, email delivery or builder access. Identify the first old link whose outcome is unknown. Resolve that one before calling the update complete.