Skip to main content

Timezones

REMO works for teams spread across timezones — photographers shooting in one region, editors working in another, and clients booking from anywhere. This reference explains the one rule that keeps everyone on the same page: a shoot time always means the time at the property.

Property-local shoot times are the anchor​

Every shoot time in REMO is anchored to the property's local timezone. When a shoot is booked for "10 AM," that means 10 AM at the property, no matter where you happen to be when you read it.

That property-local time is what you see across the app:

  • In admin and client job lists, shoot times display in the property's local timezone.
  • On invoices, the shoot time is shown in the property's local timezone.

REMO resolves the property's timezone from its location when the job is created and remembers it on the job, so the meaning of the shoot time never drifts.

Why anchor to the property?

A sunrise or twilight shoot only makes sense in the property's own clock — "7 AM" has to be 7 AM where the camera is. Anchoring every shoot time to the property keeps that meaning correct as your photographers spread across regions.

Each member has their own timezone​

Every team member carries a timezone of their own. It's used to interpret that person's working hours: a photographer's "9 AM to 5 PM" is read in their zone, not the workspace's.

This matters most for availability matching. When REMO looks for photographers who can take a shoot, it converts the shoot's time into each photographer's own timezone before checking it against their working hours. A photographer in a different region from the property is matched correctly against their local schedule — not against the property's clock or the workspace's.

Set your timezone in your profile

A member's timezone lives on their profile alongside their working hours. Existing members start out matched to the workspace timezone, so nothing changes until someone refines theirs — for example, an editor working in a different region switching to their own zone.

The display rule​

Two clocks can apply to any time, and REMO is consistent about which one it shows:

  • Property-local — wherever a shoot time appears (job lists, invoices, the schedule), it's shown in the property's local timezone, because that's where the shoot happens.
  • Member-local — wherever a member's own availability is shown, it's shown in that member's timezone, because those hours belong to that person.

In short: shoot times follow the property; availability follows the person.

Editor coverage uses member timezones​

The editor coverage widget — which tells your operations team whether an editor is on shift now and when the next shift begins — is driven by member timezones. Each editor's working hours are evaluated in their own timezone, so the "on shift now" and "next shift" readouts reflect real local availability rather than a single fixed clock.

This is what lets a coverage view work for a team whose editors are in different regions: REMO takes each editor's own hours, in each editor's own zone, and shows you the combined picture of who is actually available right now.

www.remo-app.com/schedule

For where the coverage widget appears and how the rest of the schedule reads, see Scheduling.

  • Scheduling — the workspace schedule, photographer availability, time off, and the editor coverage widget.