Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Decision and method
Connect each follow-up to a specific proposal version and an agreed next action. Keep the sending date, recipient, validity where relevant and unresolved questions. Avoid automating external reminders before defining who checks the context and which situations should stop the sequence rather than trigger another message.
Illustrative example
Illustrative example: after version 2 is sent, the customer agrees to review scope on Thursday. The task refers to that meeting rather than sending a generic reminder on Wednesday. If version 3 appears, follow-up shows what changed and prevents the earlier document from being attached accidentally.
Acceptance check
Review active, superseded, rejected and accepted proposals. Each needs an understandable state without contradictory reminders. Accept the process when another colleague can continue the conversation with the correct version, understand the outstanding commitment and distinguish an internal target date from a promise actually made to the customer.
Key takeaways
- Follow-up should continue a concrete commitment using the currently valid version of the proposal.