← All publications

Preparing a useful conversation before submission

Before submission, conversations with partners, experts, local authorities or funders can move a project forward. Provided they have a clear function.

A meeting is not meant for asking for a decision in advance. It serves to better understand a priority, a constraint, a potential role or a piece of information that is still missing. This distinction is important: the assessment remains independent, but a project can and should be prepared before a call opens.

Start with the context

The other party must be able to understand quickly which project is being discussed. A few elements are enough: the need addressed, the stage of progress, the objective, the area concerned and the step the project holder is preparing.

This context should not turn into an exhaustive presentation. Its role is to allow the other party to situate their possible contribution.

Formulate a precise question

Useful preparation starts with a question.

Does the project respond to an identified priority? Does a deployment assumption seem realistic? What level of maturity must be reached before approaching a stakeholder? What contribution can be expected from a partner? What timetable constraints need to be built in?

A clear question gives the conversation its direction. It avoids asking for a general opinion on a project that is still too broad to call for a useful answer.

Choose a legitimate contact

Each question calls for a different contact.

A customer can talk about use. A specialist can shed light on a technical point. A local authority can clarify a territorial priority. A co-funder can explain what makes a financing step more legible. An operational partner can clarify the conditions for implementation.

The contact's legitimacy strengthens the quality of the answer and avoids involving people in subjects that do not fall within their role.

Prepare the items to share

A useful conversation rests on simple, reliable items. A one-page framing note, a timetable diagram, a budget assumption, a description of the need or a short technical note are often enough.

The aim is not to send a full application ahead of time. It is to give the other party the information they need to answer the question asked.

Plan a traceable follow-up

A good meeting produces an identifiable follow-up.

It may confirm an assumption, bring a risk to light, lead to a sequence being revised, give rise to an additional document or help identify another stakeholder to involve. This follow-up should be recorded, shared with the project team and built into the preparation of the application. The purpose of the conversation, the role of each party and the useful information should remain traceable.

This traceability does not turn the conversation into a heavy procedure. It simply prevents useful information from disappearing after the meeting.

Respect each party's role

Preparing conversations upstream is legitimate when they serve to understand, to coordinate and to produce verifiable elements. Relevant information must circulate fairly between the parties concerned.

This work is neither about seeking privileged access nor about obtaining a promise of a decision. It aims to build a clearer project for all the stakeholders who will have to implement or assess it.

Before your next meeting, ask yourself one last question: what should be clearer at the end of this conversation than at the beginning?