2026-06
Scheduling, calendar and inventory — the base
The release that closes the full sequence: a five-step scheduling wizard, a window calendar, a server inventory reconciled from several sources, and templates.
- Published
Highlights
- Five-step scheduling wizard — update type, hosts, owner and contacts, window, review
- Window calendar in month, week, quarter and year views
- Server inventory reconciling one row per machine across several inventory sources
- One template per update type, used for the email, the calendar invitation and the ticket
The first release that closes the sequence end to end: from choosing an update type through to an invitation landing in the system owner's calendar.
The scheduling wizard
Five steps, in the order the decisions are made: update type, hosts, system owner and contacts, the window, and a review before anything is sent. The host step takes a bulk paste — a list copied out of a spreadsheet is matched against the inventory and selected automatically.
A reconciled server inventory
Hosts arrive from several inventory sources that do not agree with one another. The system produces one row per machine, reconciles hardware, system and owner, and derives cadence and next-due date from them.
Calendar invitations
Every event produces two invitations with distinct identifiers: one to the system owner and the contacts, one to the creator. The reason is technical — a meeting organiser cannot accept their own meeting, and without the second copy the window never lands in the coordinator's own calendar.
Templates
One template per update type, shared by the email, the invitation and the ticket. Template variables follow the selection, so an update type that operates on databases offers the database columns rather than the host ones.
[VERIFY] — versions here are calendar-based (YYYY-MM) and name the month the scope closed. If a different numbering is already in use with customers, align to it before publishing.