Draft, submit and mark sponsor updates published
Sponsor updates are reviewed messages attached to one sponsorship. An officer drafts and submits, a different authorised person decides, and the officer marks an approved update published. Nothing is sent by these actions.
Fields
| Field | Rule | Safe training example |
|---|---|---|
| Title | Required, maximum 200 characters | Learning update — November |
| Update | Required body, maximum 4000 characters | Willow-27 is enjoying the agreed reading activities. |
| Photo kept at (optional) | Storage reference, maximum 500 characters | Approved internal reference without identifying filename |
The photo field stores a reference only. It does not upload a file, display an approved public image, create a download link or establish consent by itself. Avoid personal names, dates of birth, confidential casework, health details or identifying filenames in free text.
Draft and submit
- Open the exact sponsorship detail and review its current target/status.
- In New update, enter the reviewed title and body.
- Add a photo reference only when appropriate under the approved process.
- Choose Save draft and inspect the saved update.
- Choose Submit for approval once content is ready.
- Verify PENDING_APPROVAL and arrange the separate review through the team's process.
DRAFT and REJECTED updates can be edited/resubmitted with their current version. Pending updates are not edited in place. APPROVED and PUBLISHED content is frozen.
Respond to rejection
Read the rejection reason and decided-by information. Use Edit on the rejected update, remove/correct the identified content, save and resubmit. The same distinct-user decision rule applies to the new submission. A rejected message is not ready for external circulation.
Mark published
After approval, inspect the exact saved approved message and choose Mark published. Verify PUBLISHED and its publication actor/time. This records the publication decision; it does not send email, create a sponsor portal post, trigger a print run or deliver a photo.
The implemented beneficiary eligibility and photo-consent checks run at approval. Mark published checks approved status and authority; it does not claim a fresh full consent review at that step. If eligibility/consent changes between approval and proposed use, follow the organisation's current consent review process before external use. Do not assume the button automatically withdraws or revalidates old content.
If approved content needs changing, it cannot be edited; prepare a new update and follow review again. After an uncertain response, reload update status before another submission/publication request. This workflow does not have donation-style stored-intent replay.