The Questions We Ask Before We Accept a Project And Why They Save Everyone Time

AI Overview

Picture a product team gearing up to launch in Japan, Korea, and Indonesia. There’s a UI string file ready to go out, a four-week deadline already in the calendar, and a budget that’s been signed off two levels up. What isn’t settled yet: whether the buttons can actually hold translated text without breaking layout, whether half those strings are final or still placeholders, and whether “Indonesian” means general-use Bahasa Indonesia or the more formal register the compliance screens need.

None of that gets resolved until it turns into a scramble mid-project, because nobody asked before the deadline got locked in.

This is the pattern behind most localization delays, and it’s rarely a translation quality problem. It’s a pre-project assessment that never happened. The conversation that should take place before anyone signs off on scope, price, or timeline. Skip it, and the risk doesn’t disappear. It just moves downstream, to a point where it’s far more expensive to fix.

Why Localization Projects Actually Get Stuck

Ask anyone who’s managed a multilingual rollout and they’ll tell you the same thing: projects rarely fail because of bad translation. They fail because of bad assumptions, made early and left unchallenged.

The pattern shows up in a few recurring ways:

• Scope creep disguised as clarification. A “simple” product description turns out to need transcreation, not translation, once someone notices the jokes and idioms don’t survive a literal pass.
• Platform surprises. A CMS with no support for right-to-left text, or a character limit that works in English but breaks the moment Thai expands the string.
• Market assumptions that don’t hold. Traditional Chinese for Taiwan is not Simplified Chinese for mainland China, and treating “Chinese” as one line item on a quote causes real rework later. Read our article on what is the difference between Simplified and Traditional Chinese here.
• Tone mismatches. A brand voice built for a US audience can land as either too casual or unintentionally rude once it’s dropped into a market with different expectations around formality.

None of these are exotic problems. They’re the ordinary cost of skipping the conversation that should have happened before the kickoff call. And the cost isn’t abstract. It’s a delayed launch, a reworked budget, and a client-side team that now has to explain the slippage upward.

Two things make this conversation more urgent right now. The global economic situation is tighter, so buyers look harder at every budget and every partner. And restrictions on how companies handle and move data keep piling up. As a result, clients now ask new questions before they hand over content: Will AI touch our files? Where are they stored? Who works on them, and where? A project that can’t answer those on day one can stall before translation even starts.

The Questions We Ask Before We Accept a Project

We’ve learned, sometimes the hard way, that a good onboarding questionnaire does more work than a good quote. Before we accept a localization project, we’re asking things like:

• What platform is this content living in? A help center, a mobile app, a regulatory filing, and a marketing site all impose different technical constraints, and each one changes how we plan the work.
• Which markets, specifically? Not “Southeast Asia”. Vietnam, or the Philippines, or both, and whether the content needs to speak to urban or rural audiences differently.
• What’s the tone, and who decided it? Marketing copy and a medical device instruction manual don’t share a voice, even from the same client, and we want to know before we assign linguists.
• How flexible is the deadline, really? Not the date on the calendar, but the actual room to negotiate if a legal review or a design change pushes something by a week.
• Who signs off, and how many rounds of review does that involve? A project with five stakeholders and no single decision-maker needs a different schedule than one with a clear approver.
• Is there existing terminology or a style guide? Or are we building one from scratch, which is a different project entirely.

These questions are the same ones a good project manager on the client side should want asked, because every one of them heads off a renegotiation later. Skipping this step just moves the delay to a point where it’s more expensive to fix.

We also ask a few questions that are specific to working across Asian markets, where the standard Western localization checklist doesn’t quite cover it:

• Does the content need to account for multiple writing systems within one language pair, such as Simplified versus Traditional Chinese, or Hanja alongside Hangul in certain Korean contexts?
• Are there regulatory or cultural review steps, common in medical device and pharmaceutical filings across the region, that need to be built into the timeline from day one, not discovered mid-project?

And because of the wider climate, we now ask how the work itself gets handled:

• Will AI be used, and if so, how? Which tools, on which content, and with what human review before anything ships? Some clients want AI in the workflow. Others want it kept out entirely. Both are reasonable, and we need to know which applies before we plan the work.
• Where will the documents be stored? Which servers hold the source files and translations, in which country, and who controls them?
• Where is the team located? Linguists, reviewers, and project managers included. Some contracts and data-protection rules care about this.

A Real Example: What Changes When You Ask First

A medical device manufacturer came to us planning a launch across Japan, Vietnam, and Indonesia. Their initial inquiry was straightforward on paper: translate the user manual and packaging insert into three languages, on a four-week timeline.

Our pre-project assessment surfaced three things in the first conversation:

1. Japan’s regulatory body requires specific formatting and terminology conventions for medical device labeling that differ from general translation norms, meaning this wasn’t a translation task, it was a regulated-content task requiring linguists with that specific background.
2. The Vietnamese market materials needed a formality register appropriate for a clinical audience, distinct from the more general-use Vietnamese the client had used in prior consumer marketing.
3. The four-week timeline hadn’t accounted for an internal legal review round on the client’s side, which, once we asked, turned out to take two weeks on its own.

Because we asked before accepting the project, we restructured the timeline to eight weeks, brought in linguists with regulatory experience for Japan specifically, and built the legal review into the schedule instead of around it. The client’s own compliance team later told us the Japan filing went through without a single formatting correction, a first for them in that market.

Nobody enjoys hearing “four weeks” turn into “eight weeks” in a first conversation. But it’s a far easier conversation than the one that happens in week five, when the deadline has already been promised upward and there’s no room left to fix it properly.

The Real Value of Asking First

A structured pre-project assessment isn’t paperwork. It’s the fastest way to find out whether a four-week estimate is actually a four-week job, before anyone’s calendar depends on it.

For localization project management specifically, this matters more than it does in most other services, because the cost of an unasked question doesn’t show up as a typo, it shows up as a regulatory rejection, a relaunch, or a brand voice that lands wrong in a market the client cared about getting right.

At 1-StopAsia, this onboarding process is built into how we take on every project, not layered on top of it. It’s slower at the start and considerably faster everywhere after.

If you’re planning a localization project and want to know what questions we’d ask about yours, from tone of voice to AI use and server location, get in touch for a pre-project consultation.