Import your households and accounts first. Packets are built from the data in SurgeTK at build time.

Turn on the Value Adds you want in Settings › Value Adds. A new Surge automatically includes every Value Add that is turned on for your firm at the moment you create it.

Buckets and Guardrails are on by default. Beneficiary, Net Worth, Homework (the Meeting Worksheet) and 1099 need the Pro plan to turn on. The Roth Conversion Letter stays off until you turn it on.

Add your logo in Settings › Firm Info. Packets use the Firm Logo and the Firm Branding Color set there.

Included Value-Adds: tick the Value Adds to include. The list shows only Value Adds that are turned on for your firm.

Packet order & uploads: drag items by the handle to set the page order. Value Adds and uploaded PDFs can be mixed in any order. Click Add PDF to attach a PDF. Each upload has a trash icon ("Delete").

An uploaded PDF goes into every household's packet in this Surge. There are no per-household uploads.

You upload one file at a time. A new upload is added at the end of the order. Drag it to where you want it.

Uploads belong to the Surge. Deleting one removes it from every packet built after that.

Buckets, Guardrails, Beneficiary, Net Worth, Homework, 1099 Letter and Roth Conversion Letter.

Each one must be turned on in Settings › Value Adds.

The One Page Plan is a prospecting tool and can never be added to a Surge packet.

If a Value Add is turned off in Settings after it was added to a Surge, the next Prepare removes it from that Surge. Turning it back on in Settings does not add it back. Tick it again in Manage Packet Contents.

Pages follow the Packet Contents order exactly, uploads included.

SurgeTK adds no cover page, divider pages, or packet-wide page numbers. The pages are joined as they are.

Value Add pages carry the Firm Logo and Firm Branding Color from Settings › Firm Info. A missing logo shows the "Missing Firm Logo" warning.

All active households in your firm. Archived households are hidden unless you choose Include archived in Filters.

The advisor filter in the top bar applies to this table, including its "Unassigned" option.

If your role limits you to your own households, the advisor filter is locked and the table shows only those households.

Filters opens a menu with Prepared Status (All, Prepared, Not Prepared), Warnings (All, Has Warnings, No Warnings), Household Status (Active, Include archived) and Meeting Date (From, To). Click Apply to use them or Clear all to reset.

The search box ("Search households") matches household names and advisor names.

Builds one combined PDF for all selected households and opens it in a new tab, where you can view, download, or print it.

The card says: "This does not save household snapshots, mark households as "Prepared," or attach individual PDFs." Nothing is saved in SurgeTK, nothing appears in Batch History, and the households are not marked Prepared.

The new tab shows "Building your Quick PDF Packet…" and "This usually takes only a few seconds. Please keep this tab open while we generate your PDF." The PDF then appears in the tab.

The PDF contains each household's Value Adds and the Surge's uploaded PDFs, in Packet Contents order. Its title is the Surge name followed by the date.

Up to 20 households per Quick PDF.

If any Value Add fails to render, the whole Quick PDF fails. After three minutes without a result, the tab shows: "This is taking longer than expected. This may be a larger packet. Please give us a few more moments. If this is taking longer than 2 minutes, please close this tab and try again."

The finished PDF link stays valid for one hour.

Builds a separate packet for each selected household on SurgeTK's servers, saves it, marks the household Prepared, and downloads one ZIP file with every packet.

This is the option that records packets in Batch History and on each household page.

The build queue is shared by every SurgeTK firm and takes turns between firms. A busy period makes your batch wait longer.

Each builder handles one household at a time. Extra builders start when the queue grows.

For each household, the build first refreshes all of the household's Value Adds, then renders each included Value Add, joins the pages with your uploads in Packet Contents order, and saves the packet.

More Value Adds and more uploads per household mean a longer build.

A dimmed overlay covers the page. The popup shows a percentage, "Building advisor packets…" and "Please do not refresh or close your browser."

A moment later a helper appears: "Stand up. Stretch your legs. Grab a coffee — this may take some time." with "Each packet typically takes around 20–30 seconds. Larger households with more value-adds may take a little longer."

The Prepare Packets cards also show "5-10 seconds per household" for Quick PDF and "1-2 minutes per household" for Prepare & Download Packets. Actual times depend on the queue and on the packet contents.

The popup shows "Finished Preparing (X/Y) Advisor Packets", the line "The process is finished. Packets should have been downloaded automatically. You can safely refresh the page to see the updated status." and a Refresh page button. The Households table does not update on its own; click Refresh page.

X is the number of households that got a packet. Y is the number of households that were built. Skipped archived households are listed under it.

For Prepare & Download Packets, one ZIP file downloads. It is named after the Surge and holds one PDF per household, named after the household.

If the ZIP cannot be created you see: "The packets were generated, but the download archive could not be created. Open each household to download its packet, or run the Surge again."

A message sums up the result: "Surge completed — all N packets generated successfully.", "Surge completed with some issues. Opening results…", or "Surge completed — all households failed. Opening results…". When there are issues, the Batch Run Report opens on its own.

A Value Add that fails to render is left out of the packet. The packet is still saved and the household still gets the green Prepared check.

If every Value Add fails, the packet is a single page that reads "No Value-Adds were available to render for this household." It still shows as Prepared.

Always check the Batch Run Report after a batch with issues.

The Batch History tab lists every batch run in this Surge, by every user in your firm. Columns: Date / Time, Households, Value Adds, Result, Zip, Details. The search box is "Search batch history".

Result badges: "In progress", "All passed", "All failed", or "N of M had issues".

The Zip column downloads that batch's ZIP ("Download ZIP"). It contains only the households in that batch.

The Details column ("View details") opens the Batch Run Report. It counts Households, Passed, Partial, Failed and Skipped, and lists each household as "Passed", "Partial", "Failed", "Skipped" or "Building…". Partial and Failed rows expand to show each Value Add and its error text. A "retried" tag means the Value Add succeeded on a second try.

To rebuild, select the households and click Prepare again. The build always replaces the existing packet.

The old Prepared record is removed before the rebuild starts. If the rebuild fails, the household shows as not prepared and the old packet is no longer linked anywhere in SurgeTK.

Refreshes all of the household's Value Adds, not only the ones in the packet.

Saves a new snapshot on every Value Add in the packet, labeled with the Surge name. It appears in that Value Add's snapshot list.

If the household has a scheduled or completed meeting in this Surge's Calendar Mode, writes the earliest one's date, time, time zone and type into the household's Meeting Worksheet settings, replacing what was there. Households without a meeting keep their existing settings.

A packet is a fixed file. Each household's build reads the Surge's Packet Contents at the moment its build starts.

Saved changes apply to every build that starts afterwards, including households in a running batch whose build has not started yet.

To update a packet that already exists, re-prepare that household.

Edit: in the Surge list, open the three-dot menu and click Edit, or click the pencil ("Edit Surge") next to the date range in Basic View. The Edit Surge window has Name, Start Date and End Date, and a Save Changes button. Keep the End Date after the Start Date.

Delete: in the Surge list, open the three-dot menu and click Delete. The Delete Surge? window asks "Are you sure you want to permanently delete [Surge name] and all of its packets?" Click Delete. The Surge disappears from the list and its packets disappear from every household page. This cannot be undone.

There is no Duplicate option. Create a new Surge and set its Packet Contents again.

Click Add Meeting to add a meeting for a household: Start, End, Meeting type (Review, Intro, Check-in, Virtual, In-person, Other), Location and Notes.

Two rules apply: "Meetings cannot span multiple days." and "Meeting must fall within this Surge date range."

Use Multi-Select (calendar view) or Select all (list view) to pick meetings, then click Prepare (N) Packets. A single meeting's details panel has a Prepare Packet button. The same Prepare Packets window opens, and the limit is always 20 households.

A meeting must be linked to a household before it can be selected: "This meeting must be linked to a household before it can be selected for packet preparation."

Meetings can be pulled in from Calendly. See Calendly: Sync Meetings Into a Surge.

The build queue is shared with every other SurgeTK firm, and each builder handles one household at a time.

Every Value Add and upload adds render time, and all of the household's Value Adds are refreshed before the packet is built.

Your internet speed is not a factor. You can leave the page and come back later; the batch keeps running.

Archived households are skipped, with the message "N archived households skipped — restore them to include them in a surge." Restore them from the Households page first. See Archiving households and closing accounts.

Households you do not have access to are dropped without a message.

The download starts only on the page that watched the build. If you closed the tab, download the ZIP from Batch History.

If the popup says the download archive could not be created, open each household's packet from the Households tab, or run the batch again.

Surge Fundamentals & Calendar Design

Running a Surge Cycle

Improving Surge

Calendly: Sync Meetings Into a Surge

Understanding Value Adds in SurgeTK

Meeting Worksheet (Homework)

Why a Client or Account Is Missing From a Report

Setting Up Your Firm & Team Settings

Archiving households and closing accounts

Roles, seats, and permissions

Plans, billing, and cancellation