The website supplies the timezone
Nuvilo schedules work in the timezone saved for the selected website. Your laptop clock, browser location and another colleague’s timezone should not become the publishing reference for that website.
Choose a named timezone such as Europe/London or America/New_York at website creation. Named zones account for daylight-saving rules; a fixed offset such as UTC+1 does not describe a location’s full year.
Before planning a date
- Check the website selector.
- Open that website’s settings and confirm its timezone.
- Return to the article, campaign or post you are scheduling.
- Read the local date and time shown by the workflow.
- Save and reopen the item to confirm the planned time.
For example, a website set to Europe/London with a post planned for 09:00 should publish at 09:00 London time even when an editor works from another country. Daylight-saving transitions can make some local times ambiguous or unavailable. Prefer an ordinary daytime slot and review the saved result near a clock change.
Planning is different from preparation
A publication date says when approved content is intended to go live. A preparation date says when generation or another background stage can begin. Package generation windows and Autopilot prerequisites can keep preparation waiting even when an item is already visible on the calendar.
Changing an article’s source date can affect linked campaign plans. Review dependent social posts and approve any changed work again where required.
When a time looks wrong
Confirm you are viewing the intended website, then compare its saved timezone with the label beside the schedule. Refresh after saving changes. Check whether the item is a planned draft, queued generation, approved schedule or completed publication.
If a website timezone changes after content has been planned, inspect upcoming items individually. Do not assume every historical or already saved date has been rewritten. A published post’s actual delivery time and link remain evidence of what happened.