# reverse schedule

First of all, you have to write a realistic timeline. To make a timeline, you start at the back, your ultimate goal: a big party to celebrate your beautiful map. From there, you work towards the start. This way, you have enough time to do all the steps. We’ve seen maps being published in any time between 4 months and several years, depending on how much time the creators had, how easy it was to find money and the life events of the people involved. 

You start at your release. When do you want to release your map? You can try to let this release go together with an event or important moment in your city. There might be an event, anniversary or historical fact that creates a good moment to hand out and promote your map. If you don’t have such an event, think about when tourist season might start, or when it would be convenient for your city government to promote it.

From the experience the network has collected, we can tell you the whole USE-IT project duration is:

{% columns %}
{% column %}

* 4 months if you’re super fast
  {% endcolumn %}

{% column %}

* 6-8 month is the average time
  {% endcolumn %}
  {% endcolumns %}

We know it can be difficult to picture it, so here is an easy example: 

{% stepper %}
{% step %}

#### **5 to 8 months until publishing**

* Prepare a presentation, contact funders and meet supporting organizations.
* Send funding applications and answer open calls.
  {% endstep %}

{% step %}

#### **4 months until publishing**

* Start your research and make a longlist of the content of this year's map.
* Collect input from the team and possibly from the organization you work with.
  {% endstep %}

{% step %}

#### **3 months until publishing**

* Have the designer make a draft for illustrations and ideas.
* The writers write the content.
* The proofreading from USE-IT Europe and other people you ask to proofread.A
  {% endstep %}

{% step %}

#### **2 months until publishing**

* The designer produces the cartography, the illustrations and a draft of the layout.
* The finishing of the graphic design and layout.
* Graphic design proofread: is everything in the right place, are the icons right, do the numbers match between text and map and so on.
  {% endstep %}

{% step %}

#### **1 month until publishing**

* Final proofreading by USE-IT Europe and presidents approval
* Send to print.
* Digital map preparation.
* Plan the launch party.
* Make a distribution plan.
  {% endstep %}

{% step %}

#### **Launching month!**

* Launch party and distribution.
* Making content for social media.
  {% endstep %}

{% step %}

#### **The month after publishing**

* Do an evaluation of this year's project.
* Make a report for organization and funders.
* Make a plan for next year, apply for funding.
* More distribution, social media content and sponsors meetings.
  {% endstep %}

{% step %}

#### **And somewhere in between**

* Come to the USE-IT annual meeting.
  {% endstep %}
  {% endstepper %}

***

{% hint style="success" %}
*EXPLORE OUR RESOURCES*\
→ [The Timeline](https://prezi.com/p/ccgc-jb5-hsx/timeline/) by FUND-IT team\
→ [Mastering the Work Breakdown Structure](https://use-it.travel/fund-it/art3-wbs), a blog article by FUND-IT team\
→ [Using gantt charts for effective project scheduling](https://use-it.travel/fund-it/art4-ganttcharts), a blog article by FUND-IT team\
→ [The Perfect Funder Guidebook](https://drive.google.com/drive/folders/1nwlgKDN6e0ojqbFbRzFVpTVmiZIdTaOe) by FUND-IT team
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://use-it.gitbook.io/use-it-wiki/funding-your-project/prepare-your-project-plan/reverse-schedule.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.