Ask a Team to Avoid Screenshots of Text in Working Updates

Before you write

Use this example when routine updates arrive as images and are difficult to search, quote or use with accessibility tools. Gather the details below so the recipient can act without asking you to reconstruct the situation.

• Specific update workflow
• Information that should be text
• Approved document or email route

An email you can adapt

The subject “Readable text for [team] updates” identifies the request. Replace each bracketed field with a checked detail and remove any sentence that does not describe your situation.

Subject: Readable text for [team] updates

Hello team,
For future [updates], could we put the main status, dates and requested actions in readable text rather than only a screenshot? Images can still illustrate a problem where needed, with unnecessary details removed. Text will make the working record easier to search and help readers use their preferred viewing tools. Please tell [owner] if the existing process creates a technical barrier so we can agree a practical supported alternative.
Best, [sender]

Check the boundary

A text-first convention should not prohibit useful evidence images; it should make the essential meaning independently readable.

What a useful reply should settle

The response should establish a usable update format and identify any genuine workflow obstacle.

Check a later update for readable status and clear action ownership rather than merely counting attachments.