Improvement

SurgeTK Release Notes - October 3, 2026

Shared by Jevohn • October 03, 2026

This release is about what a Redtail sync keeps. A client you delete in SurgeTK stays deleted. An account type you set stays set. Your firm can keep children and grandchildren out of households. The Homework sheet also keeps the spacing you type in its notes, and it saves the meeting time in the time zone you choose.

Most of what follows is live for every firm and happens on its own. Three items ask for a step from you. The Family members filter stays off until an Admin ticks a relationship. A meeting time typed before this release may need to be entered again with its time zone. A client deleted before this release is not yet on the Deleted contacts list. Each is marked below.

Deleted clients stay deleted

A Redtail contact you delete in SurgeTK no longer comes back on the next sync.

A deletion is remembered. SurgeTK kept no record of a deletion before. Any sync that read the contact again brought the client back: a normal sync when the contact changed in Redtail, and every full read after a reconnect or "Re-read every contact". SurgeTK now records each deletion, and every sync leaves those contacts out.
Every way to delete counts. Deleting a client, removing a member in Edit Household, and deleting a whole household each record the deletion of every Redtail contact involved.
Find them in Sync Filters. Go to Settings, Integrations, Redtail, then Sync Filters. The new Deleted contacts card lists each contact with the name, the date, and who deleted it.
Restore brings a contact back. Click Restore to take the contact off the list. The next sync that reads that contact adds them back. Restoring does not start a sync, and Restore is unavailable while a sync is running. Only Admins can restore.
Sync history shows the count. The sync history drawer shows "deleted in SurgeTK, left out" with the number of contacts the run skipped.
"Re-read every contact" no longer brings deleted clients back. The checkbox text now says so.
A reconnect with the same username keeps your normal sync. Every reconnect used to make the next sync a full read of every contact. Now only a change of Redtail environment or username does. Entering a new password after a Redtail password change keeps the incremental sync. Disconnect still resets it.
Clients deleted before this release are not on the list until SurgeTK adds them. Until then, if one of them comes back after a sync, delete it once more and it stays out.
Zoho is unchanged. This applies to Redtail contacts only.

An account type you set is kept

A Redtail sync no longer replaces the account type you chose.

Your type wins. Every sync used to write Redtail's type over every account, so an account you changed from Other to IRA went back to Other on the next sync. A type you set in the account window is now kept through every sync.
A real type is never changed to Other. When Redtail has no type for an account, or one SurgeTK cannot classify, the sync leaves the type SurgeTK already has. This applies to every account, not only the ones you edited.
The account window shows the difference. When Redtail's type differs from the one in SurgeTK, a line under Account Type says so, such as Redtail says: Other ("Fee-Based Account"). It shows in view and in edit mode.
"Use Redtail's type" hands the type back. Click the button next to that line to take Redtail's type. From then on the sync updates that account's type again.
Sync history shows the count. The drawer shows "kept your account type" with the number of accounts the run left alone, next to "kept your status".
Reports follow your type. For an account whose type you set, Buckets, Guardrails, the Net Worth report and the RMD table read your type. Before, they could read Redtail's label first.
A type from an account import is kept too. A recognized type in your import file is not replaced by a later sync.
Set a reverted type again. If a sync changed one of your types back before this release, open the account, set the type, and save. It stays from then on.
Zoho is unchanged. A Zoho sync still writes Zoho's type.

Keep children and grandchildren out of households

A firm on Redtail can now choose which family relationships come across.

A new Family members card in Sync Filters. Go to Settings, Integrations, Redtail, then Sync Filters. Tick the relationships to keep out. Child, Grandchild and Other are offered to start. After a sync, the card also offers the relationship names your own Redtail families use. Spouse is never offered.
Why this was needed. Everyone linked in a client's Redtail family came across, whatever their category or status, so a child with the same status as a spouse could not be filtered out. The relationship Redtail stores for each family member is now the control.
New imports only. A ticked relationship stops new members from coming in. Members already in SurgeTK are not removed. Delete those by hand, and with this release they stay deleted. An excluded member's own accounts stop syncing.
The head of household always comes across.
Your category and status filters still apply. A child whose own Redtail contact passes those filters still imports as a contact in their own right. Those filters remain the control for that.
Sync history shows the count. The drawer shows "Family members kept out by relationship".
Nothing changes until you tick a relationship. The list starts empty.

Homework notes keep what you type

Meeting Notes, the Homework column and Client Questions keep your spacing on screen, in Print and in the PDF.

Indents, tabs, spaces and blank lines are kept. They were saved before, but the sheet, the printed page and the PDF collapsed them.
Tab indents. In an open note box, Tab inserts an indent at the cursor, or indents every selected line. Shift+Tab removes one indent. Tab used to move out of the box and save.
Ctrl+Enter saves. Cmd+Enter on a Mac. Escape still cancels, and clicking away still saves. A one-line hint under the box names the keys. It never prints.
The cursor lands at the end. The box used to open with all the text selected, so the first key press replaced the note.
The box grows as you type. There is no inner scrollbar.
Special characters print as typed. A "<", "&", "$" or quotation mark in a note could lose text or print as markup on the sheet and in the client PDF. Each prints as typed now.
Insurance notes and tax-year notes keep their line breaks when you view them.
The sticky note on a Value Add no longer doubles blank lines when you save it.
Snapshots and generated packets keep their old layout. A saved snapshot or a Surge packet already generated shows the notes as it did when built. Build it again to pick up the spacing.
Notes are plain text. There is no bold, color or font change.

Homework meeting time is saved in your time zone

A meeting time typed on the Homework sheet now saves and shows at the hour you typed.

The hour no longer shifts. A typed time was read in the wrong time zone, so 2:00 PM could print as 7:00 AM, and saving the sheet again could move it once more. The time you type is now read in the meeting's time zone, and saving without a change moves nothing.
Pick the time zone in the Meeting details card. With Annotations on, click the meeting line on the sheet. The card now has a Time zone select with Eastern, Central, Mountain, Arizona, Pacific, Alaska, Hawaii, UTC, and your browser's zone. A record with no zone takes your browser's zone the first time you save a time.
Every place shows the same time. The sheet header, the Meeting details card, the inline edit box and the Surge composer table all show the meeting's time zone. The Surge table adds the zone when it differs from yours, such as 2:30 PM CST. The zone is still not printed on the sheet.
Meetings synced from a Surge calendar were never affected. They always carried their time zone.
A time typed before this release may still be wrong. Check the meeting line on the sheet. If the hour is wrong, open the Meeting details card, set the Time zone and the time, and save.

Smaller fixes

A Zoho sync survives a dropped connection. A sync that lost its connection to Zoho partway through failed with no retry. It now retries that page up to three times before it gives up.

Updated in the Help Center

These articles now describe the behavior in this release.