# Time to Productivity: What It Means When You're Hiring Globally > Machine-readable page from EOR Overview (https://eoroverview.com/), an independent research platform for Employer of Record services. > Canonical page: https://eoroverview.com/glossary/time-to-productivity/ > Methodology: how providers are researched, scored and compared is documented at https://eoroverview.com/methodology/. > Disclosure: EOR Overview is free to use. We may earn a referral fee from some providers; this never affects a rating or ranking position (https://eoroverview.com/disclosure/). Time to productivity measures how long it takes a new hire to reach the performance level where they can do their job independently and meet their role's core output targets. For domestic hires, the clock starts on day one. For international hires, the clock often starts weeks earlier - with compliance setup, work authorization, and EOR onboarding all happening before the person writes a single line of code or closes a single deal. ## Explanation What is time to productivity? Time to productivity (TTP) is the period between a new hire's official start date and the point where they are independently performing at the expected level for their role. "Full productivity" is not a universal standard - each organization defines it through role-specific benchmarks such as sales quota attainment, ticket resolution rates, project delivery, or manager sign-off on competency milestones. In global hiring, TTP has an additional layer: the pre-start phase. When you hire someone in another country through an Employer of Record, the EOR must register the employment contract, set up payroll in the local currency, and sometimes obtain work permits before the person can legally start. That setup period - often two to four weeks depending on the country - directly affects how quickly your team sees output, even if it does not appear in your formal TTP calculation. Why TTP works differently across borders Domestic onboarding and international onboarding share some steps, but the differences are substantial. Here is a comparison of what affects TTP in each context: Factor Domestic hire International hire via EOR Contract and compliance setup Days One to four weeks depending on country Work authorization Usually immediate (right-to-work check) May require visa or permit - weeks to months Equipment and system access Typically pre-provisioned Shipping across borders, import duties, lead times Time zone alignment Rarely an issue Can delay real-time collaboration and feedback loops Language and documentation Single language Contracts, training materials may need local-language versions Probationary period rules Varies by state/province Legally mandated in many countries; affects milestone timing Benefits enrollment complexity Standard HR system Country-specific statutory benefits managed by EOR The upshot is that a TTP benchmark built on your domestic workforce will be inaccurate if applied to international hires without adjustment. Companies that use a single global TTP target often flag international employees as "slow ramp" when the real bottleneck was a four-week permit process in Germany or a public holiday cluster in Brazil. How to calculate time to productivity The basic formula is straightforward: TTP = Date of full productivity - Official start date Where "full productivity" is defined by a pre-agreed benchmark for each role. The harder work is deciding what counts as the start date and what counts as full productivity. Setting a meaningful start date for global hires For international employees, consider tracking two dates: the contract start date (when the EOR employment agreement takes effect) and the active work date (when the employee actually begins tasks). The gap between these two is invisible cost that TTP calculations often miss. Some HR teams call this "pre-productivity lag" and track it separately so they can attribute it correctly to compliance overhead rather than onboarding quality. Defining full productivity by role type There is no universal definition of "fully productive." Common approaches include: - Output-based benchmarks: A sales hire is fully productive when they close deals at a target monthly rate. A developer is fully productive when they ship features at the team's average velocity without requiring review beyond normal peer review. - Competency sign-off: A manager formally signs off that the employee can handle core responsibilities independently. - 30/60/90-day milestones: Progressive targets at 30%, 60%, and 90% of expected output, with full productivity declared at the 90% threshold or beyond. For international hires, build country-specific milestone adjustments where local law affects pace. In France, for example, a mandatory probationary period (période d'essai) runs alongside your TTP clock - if you terminate during that period, the legal process differs from a standard dismissal. That affects how aggressively managers push performance targets in weeks two and three. Factors that affect TTP in global teams Role complexity Technical and specialized roles take longer to ramp everywhere. A software engineer joining a large codebase, or a finance analyst learning a proprietary risk model, needs weeks of context before independent output is realistic. This is the same domestically and internationally - but international hires often have less access to informal knowledge transfer (hallway conversations, in-person shadowing) that speeds things up for co-located teams. EOR onboarding quality The EOR you choose directly affects TTP. A slow EOR that takes three weeks to finalize a contract in a country where setup normally takes five days adds dead time to your ramp. When evaluating EOR providers, ask specifically about their average time to contract completion by country - this is a concrete predictor of pre-start lag. Misclassification risk and its TTP cost Some companies try to shortcut international hiring by engaging workers as independent contractors rather than employees. In the short term, this appears to compress TTP because there is no EOR setup period. In practice, it creates a different problem: workers classified as contractors often cannot be integrated as deeply into teams, given system access, or assigned work in the same way as employees - which paradoxically slows their real productivity. If a misclassification audit later reclassifies them as employees, back-taxes, penalties, and potential termination reset the clock entirely. Time zones and async collaboration A hire in Singapore working with a team in London faces a narrow overlap window. If onboarding relies on synchronous training sessions, live Q&A with managers, or real-time code reviews, the effective ramp time stretches. Companies with strong async onboarding documentation - recorded walkthroughs, written runbooks, structured self-paced learning - see shorter TTP for distributed international hires. Country-specific onboarding rules Several countries impose legal requirements that touch onboarding directly: - Mandatory orientation periods: Some countries require safety briefings or formal induction records before employees begin certain types of work. - Probationary period length: Mexico allows up to 30 days for standard roles and up to 180 days for senior roles. Spain allows up to six months for degree-level positions. These periods affect the pace at which managers feel comfortable assigning full responsibility. - Working hour restrictions: In some countries, new employees cannot legally be asked to work overtime during probation. This limits the "intensive first weeks" approach some companies use to accelerate ramp. Tracking TTP across a global workforce When your workforce spans multiple countries, a single TTP number across the company is not very useful. A more practical approach: - Segment by country: Track TTP separately for each major hiring location. This surfaces whether a country's longer TTP is due to role complexity, EOR friction, or onboarding gaps. - Separate pre-start lag from ramp time: Log the days between offer acceptance and active work start as a distinct metric. This makes EOR setup time visible and comparable across providers. - Use role-family benchmarks, not company-wide averages: A company-wide average TTP that mixes customer support reps (fast ramp) with principal engineers (slow ramp) tells you nothing useful. Build benchmarks per role family, then compare by country within each family. - Survey new hires at 30 and 60 days: Ask international hires specifically about access problems, documentation gaps, and whether time zone friction affected their ramp. This qualitative layer explains what the numbers cannot. Common TTP metrics for global teams Metric What it measures Global hiring note Pre-start lag Days between offer acceptance and active work start Heavily affected by EOR setup speed and work permit timelines Time to first meaningful output Days to first independently completed task Delayed by system access issues common in cross-border setups Time to role proficiency Days to manager sign-off on core competencies Probationary period rules affect when managers formally assess this 30/60/90-day output ratios Actual output vs. benchmark at each milestone Build country-adjusted benchmarks where legal constraints apply Onboarding satisfaction score New hire self-reported readiness and support quality Surfaces EOR-related friction that quantitative metrics miss How to reduce TTP for international hires Most advice on reducing TTP focuses on domestic onboarding. For global teams, the highest-impact actions are different: - Choose an EOR with fast country-specific setup: The difference between a two-week and a four-week contract finalization in a given country is two weeks of paid salary with zero output. This is often the single largest controllable driver of TTP for international hires. - Ship equipment before the start date: International shipping takes time. If a laptop arrives on day eight, you have lost a week. Budget for early shipping and local equipment procurement where faster. - Build async-first onboarding documentation: Recorded product walkthroughs, written role guides, and self-paced training modules work across time zones. They also reduce the dependency on managers being available in real time. - Grant system access on day one: In cross-border setups, IT provisioning often lags because the employee's details are in an EOR system rather than the company's main HR system. Coordinate access provisioning with your EOR before the start date. - Assign a local peer buddy where possible: If you have other employees in the same country or time zone, a peer buddy reduces the cultural and logistical isolation that slows international hires in their first weeks. - Adjust milestone targets for the first 30 days: If pre-start lag consumed two of those weeks, the 30-day output benchmark should reflect that. Applying a standard domestic 30-day target to someone who had two weeks of administrative onboarding sets them up to fail on paper while performing fine in practice. TTP and the cost of a slow ramp Every day a new hire spends below full productivity has a cost: their salary, their portion of manager time, and the opportunity cost of work that is not getting done. For international hires, this cost compounds because salaries are often paid from the contract start date while actual work output does not begin until compliance setup is complete. This is not a reason to avoid international hiring - the talent access and cost advantages often outweigh the ramp cost. But it is a reason to track TTP with country-level precision and hold your EOR partner accountable for setup speed. A slow EOR is not just an administrative inconvenience; it has a measurable dollar cost that shows up in your TTP data if you are tracking the full picture.