History guide

History shows saved drafts with their mode, project association, date, source, final generated text, and interaction activity. Free workspaces see a shorter recent history; paid workspaces keep a deeper communication record.

Draft next update opens the dashboard draft workspace, selects the project, and adds starter notes based on cadence, project memory, and recent risk signals. Draft follow-up starts from a saved History item, selects Follow-up mode, and leaves the input ready for the client reply, blocker update, or new progress since that saved draft. A signed-in workspace can choose whether generated drafts save to History by default, and each draft can override that setting before generation. Drafts created before sign-in are temporary and are not saved to workspace History.

Turning History off prevents generated drafts from being saved to your workspace History. Temporary processing, security logs, abuse-prevention logs, billing records, and operational records may still exist where needed.

• Copy a previous draft.
• Expand or collapse longer drafts.
• Pin important drafts so they stay at the top of History.
• Filter by source, pinned items, Gmail sends, Slack sends, or shared drafts.
• Sort by newest, oldest, recently updated, or most interacted.
• Send a saved draft through Slack or Gmail.
• Share a reviewed draft through the native share sheet or clipboard.
• Draft the next regular update from the matching project.
• Draft a follow-up when a client replies or something changes after an update.
• Delete saved History items you no longer want visible in workspace History.
• Filter History by active or archived projects.

After you send an update, paste the client's reply or new project progress into Follow-up mode. ClientCadence uses saved project History to draft the next message without repeating old completed work.

Example: if the previous update said the auth issue and Stripe flow were done while homepage assets were still pending, and the client replies that Stripe is approved and assets will arrive tomorrow, the follow-up should acknowledge the approval, focus on the remaining homepage assets, and give the next review step.

Archiving a project removes it from Active projects without removing the related History. Archived project History remains visible with an Archived project label, and the project can be restored from the Projects page.

Web app items come from the dashboard generator. Slack items come from direct messages, mentions, or the slash command. Gmail items are reserved for Gmail-origin workflows as the product expands.

Before sending a new weekly update, review the last few saved drafts for that project. Reuse phrasing that worked, check whether the same blocker is repeating, then draft the next message with fresh notes.