Skip to main content

WORK PLAN SKELETON (BETA)

The Work Plan Skeleton is a section built into some Typewiser documents' templates. It gives you one place to settle the shape of your work plan, the work packages, the tasks inside them and the milestones, before Typewiser writes the full work plan description. You review a short structure first, adjust it until it holds together, and only then generate the long narrative that goes into the proposal. The skeleton is a working panel. It belongs to the template, not to the proposal, and it is not exported with the document you submit.

note

The Work Plan Skeleton is not part of every template. It appears in the documents that implement it, and it is always introduced by an Instructions line that says the panel will not be exported.

Why this section​

A work plan is rarely right at the first attempt. The split of effort between work packages, the number of tasks, the position of the milestones, all of these tend to change once you see them side by side. If you have already generated several pages of description, every structural change means rewriting or regenerating that text. The skeleton separates the two jobs. Settling the structure is quick, because the skeleton is short enough to read in one pass and to discuss with your partners. Writing the description is slow, so you do it once the structure is agreed. Typewiser then treats the finalised skeleton as instructions, so the description follows the plan you approved.

Where to find the Work Plan Skeleton​

The skeleton sits in the Editor, inside the part of the document that covers the description of the Work Plan of a project. For example, in Horizon Europe templates this is the section on "Quality and efficiency of the implementation", immediately before the detailed description of a Work Plan and Resources.

Specific markers identify it:

  • A heading named Work Plan Skeleton.
  • An Instructions line beneath that heading, stating that the section defines the skeleton of your work plan before the full narrative is written.
  • A second Instructions line closes the panel. Everything below it is proposal content and does appear in the submitted document.

How to generate the skeleton​

Typewiser plans your Work Plan from what it knows about your project, so the skeleton is only as good as the material behind it. Before you generate, upload at least one document describing the project at a high level to the Knowledge Library.

Useful material includes:

  • A project concept note, an abstract, or a summary of the idea.
  • The objectives and the results you expect to deliver.
  • The partner list, with the role each partner plays.
  • The planned duration of the project.
  • Any earlier proposal or draft with a work plan you want to follow.

Typewiser combines this with what it knows about the funding programme, so the first structure already reflects the conventions of the call, for example a coordination and management work package, or a separate work package for dissemination, exploitation and communication.

  1. Open the document and go to the Work Plan Skeleton section.
  2. 🪄Generate the section in the same way as any other section of the document.
  3. Read the result before you do anything else with the document.

A generated skeleton usually contains:

  • The project Duration, in months.
  • A WP overview table listing, for each work package, its number, title, lead participant, person-months, start month and end month, with a total for the consortium.
  • A block for each work package, giving its objectives and a task breakdown with the effort allocated to each task.

Revise the skeleton​

Read the structure as an evaluator would, then edit it directly in the panel. It is worth checking:

  • Coverage. Every objective is delivered by a work package, and nothing is delivered twice.
  • Effort. The distribution of person-months reflects where the real work sits, and the total matches the budget you intend to submit.
  • Leadership. Each work package is led by the partner whose expertise justifies it.
  • Timing. Start and end months leave room for dependencies, and no work package ends after the project does.
  • Tasks and milestones. There are enough to show control, and few enough to report on.
  • Call conventions. Management, and dissemination, exploitation and communication, appear where the programme expects them.

Edit the panel as you would any other part of the document.

Generate the full work plan description​

When the structure is settled, generate the work plan sections. Typewiser reads the skeleton as instructions and combines it with the Knowledge Documents in the library to write the full description. The output is proposal content and follows the official template. Because the description is generated from the skeleton, work package numbers, titles, leads and effort figures carry through consistently from one table to the next.

Change the Work Plan after the description exists​

Work back through the same route, at the level the change calls for:

  • For a wording change inside one task, edit the description directly.
  • For a structural change, such as adding or removing a work package, moving tasks, or shifting effort, change the skeleton first, then generate the description again.

Regenerating replaces the text in the work plan sections.