Skip to content
Civic TranslationSan Francisco

For language service providers

Overflow capacity that runs on your process.


You hold the contract and the client relationship. We take the volume that will not fit in the week — most often Vietnamese and Chinese — under your agreement, in your files, and invisible to the agency you serve.

Scope

What we take.

Public-sector document work in California: notices, forms, applications, handbooks, program materials, and web copy destined for an agency site.

Staffed directly, quoted same business day

  • Spanish

    Español

  • Chinese

    中文

    Traditional and Simplified

  • Vietnamese

    Tiếng Việt

Through vetted partner linguists, on confirmed availability

Filipino, Russian, Korean, Arabic. We confirm availability before we accept a date in these pairs rather than after.

Situations we are built for

  • A week where you are oversubscribed and the deadline is not movable.
  • A reviewer who fell through on a pair you normally cover yourself.
  • A client who moved a public-notice date forward after the schedule was set.
  • A pair you do not staff directly and would rather not build for one contract.
  • Review and certification of target text that already exists, where the file needs a qualified second pass before it goes to the agency.

Fit

We work to your process, not ours.

A subcontractor that asks a prime to change its workflow is a cost, not capacity.

  • Your NDA

    We sign yours. We do not ask you to sign ours, we do not require a mutual form, and we do not treat a subcontractor agreement as a negotiation.

  • Your style guide, glossary, and memory

    Send them and they govern. Where a client term list disagrees with our preference, the list wins. If we think an entry is wrong we flag it to your project manager and leave the entry alone until you decide.

  • Your CAT format

    We work in the bilingual files you send and return them in the same format. If your workflow runs in a server-based tool, we work inside your instance under accounts you issue, and you close them when the engagement closes.

  • Your QA form

    If you run a scorecard or a review checklist, we complete it in the fields you use. If you would rather we return our own review log, we do that instead.

  • Your file naming and your handoff route

    Folder structure, naming conventions, and delivery channel are yours. We will not ask your project managers to learn a portal.

  • Your deadlines, including the ones that move

    Rush handoffs are taken on the same terms as scheduled work. A subcontract quote comes back same business day, and if a date is not achievable you hear that before you commit to your client, not after.

  • A paid test piece

    We will take a paid test before you route live volume, scored by your reviewer against your criteria. Paid, so that it runs like a real job rather than a favor.

  • Invisible to your client

    No contact with your end client, no branding on deliverables, no marketing use of your name or theirs. We publish no client work and there are no case studies on this site.

Deliverables

What you get back.

Everything is returned in a form your production team can drop straight into the job it came out of.

Bilingual files back in the format you sent
XLIFF and its variants, plus a clean target. Segment status and locked content come back the way you set them.
A memory-compatible deliverable
TMX when you want the segments for your memory rather than only the finished file, so the work you paid for lands in the asset you keep.
Layout that survives the language
Text expansion, CJK line breaking, and right-to-left typesetting handled so the target file prints and posts like the source.
A review log
What changed, where, and why, at the level of detail your QA process expects. Written for a reviewer, not for a client-facing summary.
A certificate of accuracy under your name or ours
Your preference. Where it goes to your client on your letterhead, we supply the attestation content and stay off the document.
Terminology feedback to you, not to your client
Entries we believe are wrong, gaps we hit, and inconsistencies in the source, raised to your project manager so the correction reaches the client through you.

Getting started

How a first engagement usually runs.

Four steps, and you can stop after any of them.

Standing terms

Every job is reviewed by a qualified linguist in the pair before it goes back to you. That step is not sampled and is not dropped under deadline, which is what makes a short turnaround safe to pass on to your client.

  1. 01

    NDA and rates

    Send your nondisclosure agreement and your subcontractor rate sheet. We come back with the pairs and volumes we can hold, and we say plainly where we cannot.

  2. 02

    A paid test piece

    Real content, scored by your reviewer against your criteria. If the result is not what you need, that is the end of it and there is no follow-up call.

  3. 03

    One small live job

    Ideally a real deadline with some room behind it. That is where you find out whether the handoff, the file round-trip, and the response times actually work.

  4. 04

    Standing capacity

    A named contact, a response window we hold, and an agreed way to ask whether we have the week before you promise it.

Working the other direction — an agency award that needs a subcontractor rather than a prime? The public agency terms are the same ones we bring to a subcontract.

Send an NDA and a test piece.

Tell us the pair, the volume, and the week you are short. We confirm what we can hold and quote a subcontract job same business day.