The old way. The dispatch manager opens the calendar. Every event from every team is on screen at once: field installs, NOC maintenance windows, customer site surveys, leave, training days. To plan capacity for next Thursday's fibre rollout, they mentally subtract everything that isn't relevant, then count the remaining blocks per team, then second-guess the count because half the events look similar. Five minutes later they open a separate spreadsheet that they maintain by hand because "the calendar is for what's actually happening; this spreadsheet is for planning." The team operates two calendars: the real one and the planning one. They drift.
What ISPCQ does. The calendar has a lens. Pick a dimension — a team, a note type, a service area — and every event outside that lens dims. The relevant blocks stay vivid; the rest become context, not noise. The team roster auto-scopes to the user's access, so an area manager only sees their teams in the picker. Hover an event and the full note detail comes up in a tooltip — no click, no navigation, no losing position. The lens hint lives in a header strip so it's the first thing a new manager notices, not a footer afterthought.
The operational outcome. Capacity decisions are made inside the calendar, not against a parallel spreadsheet. The planning spreadsheet stops existing. Over-commit is visible at the point the new event is being added — the lens already shows the team's remaining gaps for that week. New dispatch managers reach productivity in their first week instead of inheriting a tribal-knowledge spreadsheet from the predecessor.
