# Pebble Board: sharing an internal project update

These are two complete, original fictional versions of the same guide. Pebble Board is fictional. The labels O01–O20 and N01–N21 are paragraph locators, not change annotations. Compare Version 1 (old) → Version 2 (new).

## Version 1 — old

### Purpose and access

[O01] Use this guide to prepare and share an internal project update from Pebble Board.

[O02] Only workspace members can open an update; this guide does not cover public links.

### Prepare the update

[O03] A workspace editor prepares the update. The board owner reviews it before it is sent.

[O04] Schedule the update for Friday at 16:00 UTC.

[O05] Saved drafts remain available for 30 days after their last edit.

[O06] Drafts can be discarded without sending an update.

### Select recipients

[O07] Updates go to the recipients selected on the board.

[O08] Recipients may be added or removed until the editor selects Share update.

### Update contents

[O09] Each update includes the title, summary and status of every visible card.

[O10] Cards marked Internal only are never included.

[O11] Attached files are not included.

### Preview and send

[O12] The recipient preview lists exactly the cards that will be sent.

[O13] A scheduled update can be cancelled until dispatch begins.

### Delivery and recovery

[O14] Delivery failures appear in the activity log.

[O15] Every selected recipient receives a delivery receipt in the activity log within two minutes.

[O16] The system retries a failed delivery once.

[O17] Editors can resend a failed update from the activity log.

### Status labels

[O18] Status labels: Draft; Ready; Sent.

### Handling information

[O19] Do not include passwords, access tokens or personal contact details in an update.

### Getting help

[O20] For a missing update, send the update ID and dispatch time to the workspace help channel.

## Version 2 — new

### Purpose

[N01] Use this guide to prepare and share an internal project update from Pebble Board.

### Handling information

[N02] Do not include passwords, access tokens or personal contact details in an update.

### Access and recipients

[N03] Only workspace members can open an update; this guide does not cover public links.

[N04] Updates go to the recipients selected on the board.

[N05] Recipients may be added or removed until the editor selects Share update.

### Prepare the update

[N06] A workspace editor prepares and sends the update. Board-owner review is optional.

[N07] Schedule the update for Friday at 15:00 UTC.

[N08] Saved drafts remain available for 30 days after their last edit.

[N09] Drafts can be discarded without sending an update.

### Update contents

[N10] Each update includes the title and status of every visible card. Summaries are not included.

[N11] Cards marked Internal only are not included unless the editor switches on Include internal cards.

[N12] Attached files are not included.

### Preview and send

[N13] The preview shows the update title and number of selected recipients.

[N14] A scheduled update cannot be cancelled after it is queued.

### Delivery and recovery

[N15] Only failed deliveries appear in the activity log.

[N16] The system does not retry a failed delivery automatically.

[N17] The board owner can resend a failed update from the activity log.

### Reuse and sharing

[N18] Editors may save a recipient group on the board for use in later updates.

[N19] The confirmation screen shows a Copy update link action after dispatch.

### Status labels

[N20] Status labels:

- Draft
- Ready
- Sent

### Getting help

[N21] For a missing update, send the update ID and dispatch time to the workspace help channel.