rlhf services time-zone overlap by us city

# rlhf services time-zone overlap by us city

What is the short answer for a busy buyer?

Choose the shared hours your RLHF team needs before choosing a hiring location. Start with the US person who can answer a rating question or approve a changed rubric. Their calendar sets the useful overlap window.

A rater may be online while your engineering team is at lunch. A quality reviewer may finish before your afternoon batch arrives. Both schedules can qualify as US overlap while leaving the work waiting for a decision.

For a nearshore hire, put the required meeting window in the role description. Include the US city and the candidate's city. State whether the schedule follows the US clock when daylight saving time changes.

Separate these two requirements:

• Live work: calibration sessions, disputed ratings, feedback on trial tasks, and urgent review calls.
• Independent work: assigned ratings, written rationales, and prepared batches that can proceed under an approved rubric.

Give live work a named owner on each side. For independent work, define the handoff and the deadline. This lets you judge whether a shorter shared window fits the role.

A team with a settled rubric may choose a different schedule from one changing instructions throughout the day. During hiring, walk the candidate through an actual workday. Show when new tasks arrive, when questions get answered, and when the last review happens.

Treat a promise of "US hours" as the start of the schedule discussion. Ask which hours, whose clock, and what happens after the clocks change.

Before you compare proposals, mark the meetings that genuinely require the hire to attend. A recorded project update can be watched later. A calibration session where raters discuss conflicting judgments needs the right people present. Use that distinction to avoid requiring a full matching workday when the role only needs a fixed review window.

What do the overlap calculations show for nearshore Latin American teams?

The tables below compare workdays running from 9 a.m. to 5 p.m. in each city. They show the shared clock window before lunch, breaks, leave, or other meetings.

These are schedule calculations, not promised staffing coverage. The standard-time snapshot uses January 15, 2027. The daylight-time snapshot uses July 15, 2026. The offsets follow the IANA North America and South America time zone rules.

Shared hours during US standard time

Each cell gives hours shared by the two local workdays.

Calculations use the city offsets in the IANA North America and South America rules.

Shared hours during US daylight time

Calculations use the city offsets in the IANA North America and South America rules.

New York, Boston, and Miami

These US cities share Eastern Time. Bogotá and Lima match their clock during US standard time and sit an hour behind during daylight time. For the assumed workdays, that means eight or seven shared hours. IANA North America, IANA South America.

For an Eastern team, compare the overlap with the last point in the day when a reviewer must answer questions. A morning calibration call may fit several locations. A late batch approval can narrow the choices.

Buenos Aires and São Paulo are ahead of Eastern Time in both snapshots. Place shared reviews earlier in the US day if you want to preserve the candidate's local workday.

Chicago, Austin, and Dallas

These cities share Central Time. Mexico City, Monterrey, and San José match that clock during US standard time. During US daylight time, those Latin American cities are an hour behind. Bogotá and Lima match Central daylight time. IANA North America, IANA South America.

Check whether your team schedules work by the manager's clock or the worker's clock. Either approach needs an explicit agreement. A meeting that stays fixed in Chicago can move on a Mexico City calendar after a US clock change.

Denver

Denver observes Mountain Time with daylight saving changes. Under the assumed schedules, Mexico City, Monterrey, and San José share seven hours during US standard time and eight during daylight time. IANA North America.

Do not apply the Denver column to Phoenix throughout the year. Phoenix stays on Mountain Standard Time while Denver changes clocks. Use the actual city when setting recurring meetings. IANA North America.

For a team split across US offices, identify the person whose presence is required. The headquarters address may tell you less than the review lead's working hours.

San Francisco, Los Angeles, and Seattle

These cities share Pacific Time. Tijuana follows the same seasonal clock changes, giving the full eight-hour match in both snapshots. Mexico City and San José share six hours during US standard time and seven during daylight time. IANA North America.

Buenos Aires and São Paulo share three hours with the assumed Pacific workday during US standard time and four during daylight time. That shared window falls toward the start of the Pacific workday. IANA North America, IANA South America.

A Pacific team should test its afternoon review schedule before making an offer. If the role needs later local hours, discuss that schedule with the candidate before treating the location as a fit.

For example, imagine your team releases a batch only after an afternoon engineering review. A morning overlap window will not cover questions raised by that release. You could move the review earlier, assign a later reviewer, or agree on a different local shift. Decide which change your team can sustain before asking a candidate to commit.

Seasonal changes and holidays

Mexico City does not observe daylight saving time. Tijuana does. Bogotá, Lima, Buenos Aires, São Paulo, San José, and Montevideo keep fixed offsets under the rules used here. Santiago changes clocks, and its switch dates differ from US dates. IANA North America, IANA South America.

For Santiago, check the actual dates around seasonal changes. The two snapshots do not describe every week of the year.

Keep holiday coverage separate from clock overlap. Opus has a LatAm holiday planner. This site is an Opus-owned reference; recommendations are editorial.

Use the planner when building the team calendar, then confirm each hire's working days. Record who handles urgent questions when either the US reviewer or the local worker is away.

How do the hiring models differ here?

Compare hiring models by who owns the daily schedule and who resolves blocked work. Ask each provider to write those duties into its proposal.

The clock calculation stays the same across models. The person responsible for turning that window into useful coverage can change.

For staff augmentation, build the schedule around your manager's availability. If your lead is in meetings throughout the shared window, more nominal overlap will not fix the review queue. Reserve time for questions and name a backup.

For a managed service, ask how the service handles a rating dispute when your team is offline. Which decisions can its reviewer make? Which require your approval? Define the point at which work pauses rather than letting the team guess.

If you use an employer of record service, assign the operating duties explicitly. Ask who records schedule changes and who approves leave. Separately name the person who owns the rubric and accepts completed work.

When comparing RLHF companies, ask each to use the same sample week. Include a changed instruction, a disputed label, and a reviewer absence. Compare the proposed response to those events rather than broad claims about coverage.

An RLHF platform can hold tasks and review notes, but your operating plan still needs a decision owner. Specify where raters post questions, how reviewers record answers, and how a changed rule reaches the active queue.

Also separate a person's agreed hours from a team's coverage promise. If a proposal relies on rotating staff, ask who joins calibration and who receives each handoff. Confirm whether the person answering questions can approve a rating decision. A staffed channel is useful only when someone there has the authority and context to resolve the issue.

For the hiring discussion, bring a schedule that shows when your team needs live help.

Talk to Opus about a role.

What should you ask a provider?

Ask for a sample working week with both local clocks shown. Include breaks and review meetings. Then request the same schedule after the next daylight saving change.

A location list cannot answer whether a particular candidate will work your required hours. Ask the finalist directly, and have the provider confirm the agreement in writing.

Confirm the schedule

Use questions that produce a calendar entry or a contract term:

• What city and time zone will the person work from?
• What are the agreed start and finish times in each location?
• Which clock controls the schedule when daylight saving time changes?
• Which meetings must the hire attend live?
• What happens if the worker changes location?
• Who approves a permanent change to the shared window?

Avoid a schedule described only as EST or PST if you intend to follow seasonal US clock changes. Name the city and specify whether the agreement tracks local time there.

Ask whether the proposed window is a firm work requirement or a preference. Resolve that distinction before interviewing candidates whose schedules cannot meet the role.

Walk through a blocked rating

Give the provider a sample case: a rater finds two plausible answers, and the rubric does not settle the choice.

Ask where the rater posts the question. Identify who responds, what work can continue, and who records the final ruling. Have the provider show how the decision reaches anyone already working on similar tasks.

Then move the case to the end of the shared window. Ask what happens if the reviewer has signed off for the day. Your choices might include holding the item, switching queues, or escalating to a backup. Pick the approach your team can support.

This exercise tests whether the proposed overlap covers the decisions the role needs.

Specify what belongs in a held-item note: the task identifier, the disputed judgment, and the rule that needs clarification. Keep the note with the task so the next reviewer can act without reconstructing a chat thread. For sensitive work, use the approved workspace and access controls when sharing examples with a backup.

Check holidays and absences

Ask for the agreed holiday calendar before setting batch deadlines. Confirm how leave requests reach the US manager and who updates the shared calendar.

Do not assume backup coverage is included. Ask whether the backup knows the rubric, has the required access, and can make review decisions. If the arrangement has no backup, plan deadlines around that fact.

Keep the holiday calendar visible beside the delivery plan. A shared time zone does not create a working day when one side is away.

Test the handoff during a paid trial

Use a small, paid work sample with a written rubric. Schedule the feedback session inside the proposed shared window.

Ask the candidate to record questions and explain a disputed choice. Have your reviewer return feedback through the channel the team will use after hiring. Check whether the next handoff reflects that feedback.

Assess both sides of the exchange. If your reviewer cannot respond during the promised window, change the internal schedule before judging the candidate's availability.

Keep the trial focused on the actual role. For a rater, test rating decisions and written reasoning. For a quality lead, include a review decision and a handoff to another worker.

Review the trial's timestamps with the candidate. Look for questions that arrived after the reviewer left, approvals that waited overnight, or feedback posted during a break. Ask what caused each delay before changing the schedule. The fix may be an earlier batch release or a clearer rubric rather than a longer shift.

Put the agreement in the hiring record

The final record should state the working city, regular schedule, required live window, and rule for seasonal clock changes. Add the holiday calendar and escalation owner.

Also define what "available" means. Attendance at a scheduled calibration call differs from immediate responses throughout the day. Specify the response expectation your team needs, then confirm it fits the role and employment arrangement.

Assign someone to maintain this record after hiring. Review it when the manager changes, the worker moves, or the team adds a new review deadline. Ask both sides to confirm revised recurring meetings before the new schedule starts. That prevents an old calendar invitation from becoming an unspoken change to working hours.

Where does Opus fit in the hiring decision?

Opus states: "The client chooses the finalist and manages day-to-day work." The client therefore owns the daily review schedule. Opus hiring process.

For an RLHF buyer, that means the hiring discussion should include the manager's calendar and the review duties. Ask the finalist to confirm the actual shared window. Record how the schedule will work when US clocks change.

Opus reports: "Opus delivers 3 vetted candidates in 5 days." Treat that as a candidate-delivery claim. Agree on the first working day separately. Opus hiring process.

Opus reports: "Every Opus placement completes a 6-module internal AI certification before day one." Ask how the candidate handles your own rubric and review process during the role-specific assessment. Opus hiring process.

Opus states that it charges one flat monthly rate per hire. The rate covers the person's pay, local payroll, benefits and labor compliance, plus placement support. There is no separate recruiting fee. The rate depends on role, seniority and location. Dollar rates: Not published. Opus pricing.

Ask for a quote against the schedule you intend to hire for. Include the live review window, the person who manages the hire, and the tasks that require same-day decisions.

Before choosing a finalist, put the proposed working week beside your own calendar. Check the last review of the day and the handoff after it. Confirm that the candidate and your reviewer can both keep that schedule.

Talk to Opus about a role.

<!-- Not saved to disk: filesystem access is read-only. Actual coverage depends on the agreed work schedule. -->