Skip to the template

Update for a client

A short update for someone outside the team, covering what's done, what's next and what you need from them.

Have your agent do it

Would you like this done once, or automatically?

A regular update keeps a client or stakeholder informed without anyone having to remember to write it. Fill in the parts in [square brackets], then paste this to your agent.

Once
Write a short update for [the person, such as a client] from this week's work in the [name of your Space] Space: what's done, what's next and anything we need from them. Leave out internal discussion. Use the template at https://avalandra.com/help/template-files/client-update. Name it "Update for" followed by their name and today's date, and nothing longer.
Automatically
Every [Friday at 3pm, or another time], write an update for [the person, such as a client] from the week"s work in the [name of your Space] Space: what"s done, what"s next and anything we need from them, leaving out internal discussion. Use the template at https://avalandra.com/help/template-files/client-update, named "Update for" followed by their name and today"s date. Show it to me before anyone else sees it.

When to use it

  • A client or stakeholder needs to know where things stand.
  • You're following up after a meeting with someone outside the team.

What to name it

Update for [person] [date], such as “Update for the board 7 Nov”. Keep it that short; agents otherwise tend to write long, descriptive titles.

What it looks like

Filled with sample contentOpen the file on its own
DocumentUpdate for the board 7 Nov

Used in

  1. Meeting summaryOne meeting's decisions, actions with owners, quotes with the speaker and time, and open questions.
  2. BriefA new working document, such as a brief, spec or plan, written from what's in the Space.

For agents

  • Fetch the template from https://avalandra.com/help/template-files/client-update.
  • Keep its <style> blocks and class names. Replace every piece of sample content with content from the record, and never carry over its names, Spaces, documents or dates.
  • Title the document Update for [person] [date], filled in, such as “Update for the board 7 Nov”. No longer, descriptive titles, and no title or label repeated inside the document: Avalandra shows the name above it.
  • Delete sections with nothing in them, and link every claim to its source with web_url.
  • Create it with ava document create (kind html, source_format html, and a parent_id for the folder), then read warnings in the response for anything the renderer removed.
  • If the prompt still contains [square brackets], ask the person what goes there.
Support