We All are Europe - AESAEC
We All are Europe - AESAEC
We All are Europe - AESAEC
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Module 5 – The Art of Successful Project Proposal Writing II: Linguistic Part<br />
5.2.3. Writing an application seen from a linguistic point of view<br />
Applications <strong>are</strong> specific types of text and therefore they should follow precise criteria and indicators.<br />
It is a special skill to put complex information into writing and to persuade a totally unknown<br />
person - very likely from a totally different country and with a totally different cultural background<br />
– by means of a text to give you money for something he / she has perhaps never heard of before in<br />
his / her life.<br />
Be aw<strong>are</strong> that not everybody is gifted with the ability to write successful proposals, and even if<br />
somebody is very good at writing poems or diaries, it does not necessarily mean that the same person<br />
is good at putting project ideas down on paper.<br />
However, it is very difficult to give recommendations about how to write a good proposal, because<br />
everyone (also every evaluator) will probably have their own preferences and ideas – nevertheless,<br />
we try to give you some (not only linguistic) hints for you to consider before starting to write an<br />
application.<br />
Successful proposal writing always starts with a thorough read through of the application<br />
details! One of the most common mistakes made is not going through all the details of the<br />
call and the application in the first place, in order to get an idea of what kind of projects<br />
the EC wants to be submitted (in terms of target groups, objectives, aims, duration, activities<br />
etc.)! Always follow these indicators and requirements – regardless of what you personally<br />
think concerning the requirements of an ideal project.<br />
Before you start writing make a basic plan of your project idea including all important activities,<br />
results, outputs etc. and try to structure them in rough – use this plan as a guideline<br />
and check it regularly!<br />
For a more detailed development try to work top-down instead of bottom-up. Start from<br />
the general frameworks and requirements of the programme and plan downwards to detailed<br />
activities and outcomes – this way you <strong>are</strong> making sure your project is always on solid<br />
ground.<br />
Usually you can submit your project in several languages (always in one of EN, DE or FR, and<br />
quite often also in any of the other official EU languages). If you choose a language other<br />
than your mother tongue you should really have excellent skills in that foreign language –<br />
otherwise you really <strong>are</strong> on thin ice!<br />
Do some basic research to get a better idea about your chosen topic and also to get a feeling<br />
for the circumstances associated with it in other counties or at the EU level – this is crucially<br />
important to the EU!<br />
Be authentic in whatever you <strong>are</strong> writing, which means write about things you understand<br />
yourself – experienced evaluators will find out very easily if you do have a good grasp of<br />
what you <strong>are</strong> writing about.<br />
Do not assume that your project idea and its frameworks <strong>are</strong> understood easily by others<br />
just because you understand them – be aw<strong>are</strong> that outside your region, country, culture,<br />
field of profession etc. and without any pre-knowledge, it might be extremely difficult to<br />
follow your descriptions and arguments.<br />
Write in clear and if possible short and understandable sentences – remember that an<br />
evaluator may read through hundreds of pages a day and therefore to make his / her task<br />
easier describe your main ideas clearly and concisely. (By the way, nowadays electronic application<br />
forms <strong>are</strong> quite often used which have character limitations for each section!)<br />
89