What problem does this solve?
Describe the real situation, not just the activity you want to run.
A good idea is only the starting point. Before you bring a short-term or long-term plan forward, build the situation, proposal, people, requirements, risks and expected outcome into one clear recommendation.
If you cannot answer these honestly, the idea may need more thinking or discussion before it becomes a recommendation.
Describe the real situation, not just the activity you want to run.
Explain the reason for considering it at this point rather than leaving the timing unexplained.
Think beyond yourself. Identify the people, teams or areas that may need to contribute or adapt.
Consider time, people, coordination, resources, dependencies and management attention.
Name the important risks and unknowns before someone else has to discover them for you.
Use this sequence to turn your thinking into a decision-ready conversation. The aim is clarity, not paperwork for its own sake.
Set the context. What is happening, what problem or opportunity are you responding to, and why does it deserve attention now? Keep it factual and relevant.
State clearly what you are proposing. Explain what would be done, the intended approach, and the decision or direction you are asking management to consider.
Identify who may be affected, who needs to contribute, and who should be consulted. A strong proposal shows that the wider picture has been considered.
Set out the practical requirements: people, time, coordination, resources, dependencies and any other support needed to carry it out responsibly.
Show that you have considered uncertainty. Describe meaningful risks, constraints, dependencies and what could be done to reduce or manage them.
Explain what you expect to happen if the proposal proceeds and how you would know whether it achieved what it set out to achieve.
Do not wait until the formal submission to discover that someone important was never considered. Early discussion makes the recommendation more practical and gives the eventual decision-maker a clearer picture.
Use the early conversation to sense-check the situation, the scope of the idea and what needs to be understood before you build the recommendation. Your supervisor can also help you identify whether other colleagues or functions need to be consulted.
Then identify the relevant colleagues or functions affected by the proposal or needed to execute it. Do not invent support or assume agreement: consult the people who genuinely need to contribute, and reflect their important input in the recommendation.
Follow the working route you supplied: build the thinking before asking for the decision.
Capture the idea and the situation behind it. Do not stop at the activity you want to do.
Sense-check the idea with the people who may be affected or who can add useful context.
Bring the thinking to your immediate supervisor before turning it into a formal recommendation.
Complete the outline, quality-check it, then submit the recommendation to the Sales Manager.
The relevant superior and management decide whether, how or whether not to proceed.
A decision closes one conversation and starts the next piece of work.
Clarify the approved scope, owners, actions and timing. Execute within the decision given, then review what happened against the expected outcome and measures.
Understand the reason for the decision where appropriate. Capture what the conversation teaches you, then decide whether the idea should be left there or rethought.
Identify the information, consultation, resource or condition that needs to be addressed before the recommendation can be reconsidered.
Work through the six parts below. This worksheet is intentionally simple: it helps you think before you submit. When you are ready, copy the assembled draft into your normal working document or discussion.
Use this as a final pause before you send the recommendation upward.