FIGR / UI TEMPLATE

Team Calendar

Coordinate launches, reviews, meetings, and team availability in a weekly view with enough project context to avoid collisions. The screen connects Calendar and My schedule so product teams can find the “Add event” action while checking events this week and conflicts.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Roadmap review and Design critique, rather than an empty visual shell.

Team Calendar

BUILD ON THIS

Make it yours in Figr.

Explore this screen, then bring in your own product and design system to shape the next version.

Use this template ↗

At a glance

Screen

Calendar

Primary action

Add event

Pattern

Calendar

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps with

Product teams need a clear “Add event” action without losing sight of events this week, conflicts and the affected records. Keep the decision and its outcome clear before moving to the next task.

What to look for

  • Primary action: Add event is clearly available where the task happens.
  • Main view: Calendar keeps the starting point obvious.
  • Connected view: My schedule supplies nearby context.
  • Metric: Events this week is visible with a meaningful value.
  • Another signal: Conflicts helps people judge what to do next.
  • Representative record: Roadmap review makes the example specific.
  • Second record: Design critique shows the pattern works beyond one item.

States to consider

  • No availability in selected range; show what people can do instead of leaving a blank panel.
  • Loading calendar without changing the layout unexpectedly.
  • Slot conflict or reschedule; explain the problem and preserve work.
  • Permission denied for my schedule; clarify who can continue.
  • Success after choosing Add event; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where it fits

Calendar → My schedule → Add event → Review outcome

Patterns in this screen

Calendar, Calendar, My schedule, Team, accessible states, contextual actions

UX choices to review

Show timezone, time range and conflicts before a user commits. Offer a clear path back to available slots.

In this design, people should be able to compare Roadmap review with Design critique. Make events this week clear, then use conflicts to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Add event” action. The happy path alone is not enough.

Related UI examples: Product Roadmap, Docs Workspace, Sprint Planning.

Try a similar screen in Figr

Design a team calendar screen for our existing software product. Use our real design-system tokens, components and product language. Show Calendar and My schedule, include believable records such as Roadmap review, and make add event easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr

KEEP EXPLORING

More ways to approach your next screen.

Browse other product UI examples, compare patterns, and pick the direction that suits your product.

Explore all 500 templates ↗