How do we write deliverables?
Deliverables are contractual. The list of deliverables can be found in the Annex 1 and in the Participant Portal. The list in the Participant Portal is useful for following up the deadlines.
The deliverables are the proof of your work towards the commission. This means:
- The volume, effort, time planned for the work should be reflected in the deliverable i.e. a big task should result in relatively extensive report
- You should document, methods, the process leading up to the results and the results
- You should also document failures and negative results (as you will claim costs for this work as well)
Your work is measured against the project objectives. The deliverables must therefore document that you have achieved your objectives. Check the deliverables against the objectives and state how your results fulfil/contribute to the objectives.
Consider the format and writing style of your deliverable and write accordingly:
- A conference paper
- An article
- A technical report describing a work process
- A test/experiment
- A description of a thing and its development
- etc
If the deliverable is not a document or text (but a thing, SW, drawings or other) you must still describe it in a text that you submit as a deliverable.
If several partners are responsible for a deliverable be sure to have enough time to integrate the contribution of each partner into one text. It is the lead beneficiary that is responsible. If the work is relatively separate a deliverable may consist of sub-reports from individual partners.
The procedures for review of publications is agreed in the Consortium Agreement.