# Global portfolio office hours across time zones | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-coordinate-office-hours-across-time-zones
Last updated: 2026-11-05

Publish a rotation, not a fixed hour. Pick three windows in UTC so that each one falls inside the working day of most of your founders, cycle the sessions through them so no region always gets the early or the late slot, and give anyone who still cannot attend a written lane that gets the same answers. Recheck every published time in the weeks when clocks change. Ask for a time window and a question only, never company facts, and wait for a CEO's written request before anything moves toward SourceX.

This page is the scheduling layer. The booking form, the triage and the conduct of a slot are set out in [running an AI data office hour for a venture network](/guides/how-to-run-an-ai-data-office-hour-for-a-venture-network), and a drop-in format for members is in [the trade network's office hour](/guides/the-trade-network-s-data-opportunity-office-hour). Either one fits inside the rotation below.

## A spread-out portfolio asks the same questions at different hours

Founders in Austin, Lisbon and Singapore tend to ask the same things about licensing company records for AI training: who in the company decides, which kinds of records can fit, what a first conversation commits them to and what the fund's interest is. The answers are the same everywhere, with one exception that a global office hour has to say out loud in every window. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. The founder in Singapore needs that English condition; the founder in Lisbon does not.

What never differs by region is the role of money raised. SourceX's screening page explains that none of the checks it screens on mentions funding, so a company's round, investors or fame says nothing about whether it fits. The decision to talk to SourceX at all belongs to each company's CEO.

The format follows from the spread. Short live sessions serve whoever is awake; a written lane serves everyone else; and no session is recorded by default, because a recording carries what a founder said about their own company to people who were never in the room.

## The timezone-fair scheduling design

Five rules, set before the first invitation.

1. **Anchor in UTC.** Fix the windows in UTC, not in the host's local time, and show each band its local equivalent.
2. **Two of three.** Every window must fall inside the working day of at least two founder bands, and every band must have at least two windows inside its day.
3. **Rotate the cost.** Cycle the windows in order, so each band misses one window per cycle and none misses two in a row.
4. **Give the written lane equal standing.** A question sent in writing gets the same answer as one asked live, and both go into the same written answers page.
5. **Recheck at every clock change.** Republish local times before each change date in any band you serve.

To find the bands, send founders one question: which of these UTC windows could you attend? Keep only the counts per band. The answer needs no company name, no role and nothing about the business.

**An Illustrative rotation.** Founders sit in three bands, at UTC-5, UTC+1 and UTC+8, in a month with no clock change. The example treats 07:00 to 20:00 local as inside the day; ask your own founders where their edges are.

| Window (UTC) | Band at UTC-5 | Band at UTC+1 | Band at UTC+8 | Who hosts |
|---|---|---|---|---|
| A, 07:30 | 02:30: written lane | 08:30 | 15:30 | A host in the UTC+1 band |
| B, 14:00 | 09:00 | 15:00 | 22:00: written lane | A host in the UTC-5 or UTC+1 band |
| C, 23:30 | 18:30 | 00:30: written lane | 07:30 | A host in the UTC+8 or UTC-5 band |

Each band gets two live windows and one written-lane turn per cycle, and each host works inside their own day. Keep a short ledger per cycle: for each band, live windows offered and turns spent in the written lane; for each host, sessions run outside their own day. The host column should stay at zero. If it does not, the rotation is being paid for by one person's evenings.

**The written lane.** Questions arrive by form or email, carrying the question and nothing else. The host rewrites each one so it names no company, shows the founder the rewrite, then answers it in the shared answers page within a stated number of working days in the host's own band. A founder who used the written lane should never learn less than one who stayed up for a live window.

## The weeks when clocks disagree

Clock changes do not happen on the same day everywhere, and a rotation anchored in UTC moves against local time when they happen. Two calendars matter for most U.S. and European portfolios:

- **United States.** A 2016 Department of Transportation release says daylight saving time runs from the second Sunday in March to the first Sunday in November, that areas observing it must follow those dates, and that Hawaii, most of Arizona and several territories do not reset their clocks (our paraphrase).
- **European Union.** Directive 2000/84/EC sets summer time from 1.00 a.m. Greenwich Mean Time on the last Sunday in March to the same time on the last Sunday in October, in every Member State (our paraphrase).

Put those rules on a calendar and two awkward stretches appear. In 2026, European clocks went back on 25 October and U.S. clocks go back on 1 November, so this week the gap between a founder in an EU country and one in a U.S. state that observes daylight time is one hour shorter than usual. In 2027, U.S. clocks go forward on 14 March and European clocks on 28 March, and the gap shrinks by an hour again for those two weeks. A window that sat at 09:00 for a founder in one band can sit at 08:00 or 10:00 during these stretches.

Three habits keep the rotation honest. Every invitation shows UTC and the invitee's local time. The host resends local times on the last working day before each change date in any band served. And for bands outside the U.S. and EU, the host checks that country's official clock-change dates once a year rather than assuming they match either calendar.

## Optional seats, and what stays with the founder

Every window is optional, and skipping all three costs a founder nothing: the written lane carries the same answers. Hold to these boundaries in every band.

- **Ask for a window and a question.** No company figures, headcounts, system names, records or customer names, on the poll, the booking or the written lane.
- **Keep the lists at home.** No attendance list, poll result or question log goes to SourceX. Nobody collects company data for SourceX, in any time zone.
- **Disclose the fund's interest.** Say at the start of each window, and at the top of the written answers page, that the fund or platform may be a registered SourceX partner that could be paid a reward if a company it introduces licenses data, that SourceX pays any reward and does not deduct it from the payout the company agrees, and that conditions apply.
- **Imply nothing about any company.** Taking part does not suggest a company qualifies, that SourceX endorses the host or that anyone gets preferential access to a company's data. The host decides nothing for any company; its CEO does.
- **Move only on a written request.** An introduction happens only when a company's CEO asks for one in writing, sent by someone who signed the SourceX Channel Partner Agreement first. Where several people across time zones know the same company, agree on one sender before anyone writes; only one introduction can be credited, and SourceX settles overlapping claims in duplicate review. The 90-day credit window runs from the recorded introduction, whichever band the CEO is in.

Questions the host cannot answer from published pages, such as rights, price or a specific company's fit, go on the [founder question backlog](/guides/a-backlog-for-founder-questions-your-platform-team-cannot-answer) with a named owner rather than into a late-night guess.

## Measuring fairness and requested follow-up

Count per band, with the denominator written next to each figure.

| Measure | How to count it | What it tells you |
|---|---|---|
| Live coverage | Windows inside the band's day, divided by windows held | Below two of three means the rotation shortchanges that band |
| Written-lane share | Written questions from the band, divided by all its questions | A high share can mean the windows miss the band, or that founders prefer writing |
| Answered | Founders who said yes to "did this answer your question?", divided by those asked | The main benefit measure, by band |
| Clock-change misses | Founders who arrived at the wrong time, divided by bookings in change weeks | Any miss means the invitation format needs fixing |
| Introductions requested | CEOs who asked in writing, divided by founders who took part | Counted, never targeted |
| Host load | Sessions a host ran outside their own day, divided by sessions they hosted | Should stay at zero |

Neither SourceX nor any portfolio has published figures like these for office hours on data licensing. After two full cycles, read the table and decide whether to keep three windows, drop to one plus the written lane, or stop.

## What could make the rotation the wrong design

- **A concentrated portfolio.** If nearly every founder sits in one band, two of the three windows serve almost nobody. One window and the written lane is the better design.
- **Lost follow-up.** A written answer cannot ask the founder what they meant. Offer a live turn in the next cycle to anyone whose written question needed one.
- **The host's interest.** Disclosure helps, but a host who could be paid still shapes the answers. Rotating hosts across bands spreads the effect without removing it.
- **Rules that move.** Clock-change rules are set by governments and can change, and the DOT release notes that a state may opt out by state law; SourceX's location and language rules are on its dated screening page. Re-read both before each cycle.
- **Demand.** Whether any company's records match what SourceX needs now is decided only in SourceX's review, and requirements differ from one program to the next. A well-attended office hour can still produce no fit at all.

**Methods note.** The five rules, the 07:00 to 20:00 band and the ledger are a design built on the clock-change rules in the DOT release and Directive 2000/84/EC, SourceX's program terms (Version 2026-10-22.2, since replaced by version 2026-11-04) and its screening page, all read on 27 October 2026. They have not been tested with founders, and the rotation's effect on attendance or introductions has not been measured. The platform-side context is in the [overview for venture platform teams](/for/venture-platform-teams), and more formats are in the [guides library](/guides).

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

Before the first window opens, [register as a partner](/register) if anyone on the team may ever submit an introduction, link [who qualifies](/who-qualifies) in every invitation so each band hears its own location rule, and keep the dated [program terms](/terms) beside the rotation.

Scheduling office hours for a global portfolio is network work; anyone weighing SourceX itself as an investment is making a separate decision and can request materials through the [SourceX investor overview](https://sourcex.si/investors).

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://www.transportation.gov/briefing-room/news-digest-dot-28-16
- https://eur-lex.europa.eu/eli/dir/2000/84/oj
- https://sourcex.si/investors
