Lead with the current state

Say what is ready, what is in progress, and what is blocked. Use concrete descriptions the client can connect to the agreed scope.

Explain the important dependency

If input is needed, identify exactly what information or approval is missing and who should provide it. Avoid vague requests that create another round of messages.

Close with the next action

State what will happen next and who owns it. Keep the timing tied to the actual dependency rather than promising a deadline before the required information exists.

Turn the brief into a useful next step

Bring these notes into the conversation with your team or ADFBM. Keep the selected configuration, the responsible contact, and any open question together. Before an order or change is confirmed, make sure the people doing the work share the same written understanding.

Use the checklist below as a starting point, then adapt it to the business and assets you are authorized to manage. Product details and platform requirements should always be confirmed for the specific setup involved.