SCRAP is a simple structure for writing clear, actionable internal emails. It helps Product Managers communicate updates, decisions, or changes with minimal back-and-forth.
It stands for:
- Situation
State the current context clearly. What’s happening? What is this about? → “We’re preparing for the Q3 release and wrapping up the final feature set.” - Complication
Explain the tension, change, blocker, or risk. Why are you writing this? → “One of the features is behind due to unexpected API delays from the backend team.” - Resolution
Describe what’s been done or proposed to handle it. This shows momentum and initiative. → “We’ve identified a workaround that removes external dependencies for the MVP.” - Action
Specify exactly what you need from the reader. Be clear and direct. → “Please review the revised scope and confirm by Wednesday.” - Politeness
End with a brief, respectful sign-off. Not forced friendliness—just basic consideration. → “Thanks for the quick turnaround last week—appreciated.”
Use SCRAP when you want to communicate efficiently, reduce ambiguity, and keep people moving. It’s useful for product updates, scope changes, decision summaries, or status emails where clarity and momentum matter.