> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://propwise.crisp.help/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to Share Updates Without Re-Explaining Everything

### TL;DR
|| PropWise ensures your buyer remains automatically in sync. When you update a property, document, or note, your client sees the latest version instantly—eliminating the need for follow-up emails or re-explaining context. This is crucial as it reduces deal friction caused by repetition and clarifying changes. PropWise effectively addresses both.
---

### When to use this
Consider this workflow whenever you might say:
* “Just to recap…”
* “This is the updated version…”
* “Ignore the last document I sent…”
* “Let me explain what changed since yesterday…”

Typical triggers include:
* Updating a property price, description, or status
* Uploading a new inspection report or disclosure
* Adding notes or clarifications after a buyer conversation
* Multiple stakeholders reviewing the same portfolio

If you’re explaining changes manually, the system may not be fully utilized.
---

### Step-by-step instructions

#### Option 1: Automatic Sync (Best for most situations)
**Use this when you want updates to speak for themselves.**

1. Open the relevant portfolio.
2. Update the property (price, description, status, tags) or upload a new document.
3. Save your changes.

**What happens next**
* Your buyer sees the updated version automatically the next time they open the portfolio.
* No notifications to manage.
* No context lost.
* No duplicate explanations.

This is the default and preferred workflow in PropWise.

#### Option 2: Contextual Notes (Best when interpretation matters)
**Use this when the update needs interpretation, not repetition.**

1. Open the property inside the portfolio.
2. Add a note explaining *why* the change matters (not what the change is).
3. Choose whether the note is:
* **Buyer-visible** (for guidance or reassurance)
* **Private** (for your internal reasoning)

Example of a good buyer-visible note:
| "Price dropped €25k - now aligned with comparable sales on this street.”

Avoid:
||| “Price updated from €525k to €500k.” (The system already shows that.)

#### Option 3: Chat Follow-Up (Best for decisions, not updates)
**Use chat only when an action or decision is required.**

1. Let the update sync automatically.
2. Send a short message in chat focusing on the *decision*, not the update.

Example:
| “I’ve updated the inspection docs. Let me know if this changes your interest level.”

This keeps chat high-signal and prevents it from becoming an audit trail.
---

### Common issues & tips
* **Over-explaining:**
   If the buyer can *see* the change, there’s no need to narrate it. Add meaning, not redundancy.
* **Version anxiety:**
   Buyers don’t need reassurance about “latest versions.” PropWise always shows the current state.
* **Using chat as storage:**
   Chat is for decisions and alignment. Notes and documents are for durable context.
* **Silent updates that matter:**
   If an update changes risk, price logic, or timing—add a note. Silence is only safe for neutral updates.
* **Performance tip:**
   Fewer messages = higher buyer confidence. Over-communication often signals uncertainty.
---

### Related articles
* [What Happens When a Property Is Updated After Sharing](https://propwise.crisp.help/en/article/what-happens-when-a-property-is-updated-after-sharing-rsofvi/)
* [How to Add Notes to a Property (Internal vs Buyer-Visible)](https://propwise.crisp.help/en/article/how-to-add-notes-to-a-property-internal-vs-buyer-visible-6im2em/)
* [How Clients Can Comment and Give Feedback](https://propwise.crisp.help/en/article/how-buyers-leave-feedback-on-properties-2c1zep/)
* [Best Practices for Managing Portfolios](https://propwise.crisp.help/en/article/what-are-some-best-practices-for-managing-portfolios-rcdha1/)