SANJIESAN LICENSING / Project timing
A launch date does not answer every timing question
The European IP Helpdesk identifies duration as an agreement issue. A project calendar answers a different practical question: when the team hopes to complete each activity. Put the two kinds of information beside each other for review, rather than assuming that a planned release date settles when every proposed use may begin or end.
List activities before dates
Write the actual sequence the team is considering: concept discussion, artwork preparation, sample review, public presentation and later use, for example. Treat this as a planning list, not a universal approval process. Identify which activities depend on an outside answer. A calendar with only a final launch marker can conceal the decisions that must happen much earlier for the intended plan to make sense.
Keep planned dates distinct from agreed conditions
Use separate fields for a target date and the document or decision that governs an activity. Do not invent an automatic renewal, grace period or permission from an empty calendar cell. If the team does not know what happens after a particular stage, write the question in plain language for its adviser. Keep uncertainty attached to the activity rather than hiding it in a general project note.
Recheck timing when the project changes
If the concept, route or intended public use changes, ask which timing questions need to be revisited. Keep the previous plan visible as history and issue a clear current version to the team. A revised schedule should not silently alter the meaning of a rights document. The useful handoff is an understandable calendar with named dependencies, not a confident launch promise built on unanswered questions.