Free template · No signup
A multilingual content calendar names the source owner, target markets, translation window, reviewers and release date for each asset. This free template helps you plan those handoffs before the source deadline consumes the local review time.
Use it for a campaign launch, a translated blog schedule or a product release. Separate simultaneous launches from evergreen work that can follow a rolling schedule.
The sample plans a fictional product setup article for English and Mexican Spanish. Its dates are an example schedule, not a delivery promise. Adjust the review window to your team's availability and the content's risk.
Edit the worked example. These fields are processed in your browser and are not sent to a Vitra server. Page analytics, if enabled, are separate.
Your handoff, ready to edit
Setup article — how does a new owner charge Luma One safely?
en-US source + es-MX article; supporting square image; website publication.
Product writer; source approved by October 20, 2026.
Translation draft October 21; language + product review October 22–23; final preview October 26.
Web editor; target October 27, 2026; status planned, not approved.
Depends on setup UI version 2 and the approved es-MX glossary. Reopen review if the charging instruction or linked support page changes.
0 of 5 checks selected. This is not a quality score or release approval.
Free. No signup required. Markdown includes selected checks; CSV contains the editable fields. Changes are not saved after leaving or reloading this page.
If every market needs the asset on the same day, translation and review have to happen before that day. Put source approval early enough to leave room for both. Use a rolling schedule for evergreen posts when simultaneous release adds little value.
Not every market needs a translated version of every source article. A local team may need a different example, event or question. Add those original assets to the same plan so local content is visible without being treated as an exception to the central calendar.
A date on a spreadsheet can be mistaken for a promise. Record status and the next owner beside it. When a claim changes, mark the affected language work for review instead of leaving an old approval beside new text. Check the CMS preview and export before the final release.
When the job repeats
Connect planning to blog creation and translation while keeping the review responsibility visible.
Only when the launch or audience need calls for it. A campaign or product announcement may need a simultaneous release; evergreen content can use a rolling schedule that leaves enough time for local review.
No. It is a general-purpose planning sheet. Import or copy it into the system your team uses after mapping the fields. A calendar row does not automatically create or publish an article.