Skip to main content
GullySystem
Professional services

Business solutions for Translation and interpretation services

Explore software for work such as “Certified translation of personal certificates”. Review each business function below, including when it fits and what to check before implementation.

Translation and interpretation services

How the business operates.

A translation firm sells the work of other people. Linguists in several countries translate, edit and proofread, while interpreters attend meetings, hearings and appointments on the firm’s behalf. A project manager stands between them and the client, and most of the detail lives in an inbox. That is the weak point.

Quotes by word count and language pair

Price jobs from word count, language pair, subject and urgency, using a rate card for each client, so two managers quoting the same files reach the same figure. Revisions stay on record.

Job and file tracking

Hold the brief, source files, reference material and delivered files on one job, with a stage each for translation, editing and proofreading.

Linguist database and assignment

Record each linguist’s language pairs, subjects, certifications, rates and availability. Assign work from that list.

Interpreting bookings

Book interpreters by language, venue or remote link, date and hours. Confirmation goes to the client and to the interpreter.

Glossaries and client style notes

Keep approved terms and style instructions for each client, so every linguist on a job works from the same list.

Linguist payments

Check each freelancer’s invoice against completed jobs and agreed rates. Release approved lines for payment, and keep the rest on hold with a note.

Client invoicing and purchase orders

Raise invoices from delivered jobs in the client’s currency, carrying the purchase order reference that the client’s own accounts team will look for.

Translation memory and term base

Previously translated segments and approved terms are stored per client and language pair. Linguists reuse them on repeat jobs. The project manager sees which segments in a new file already match.

Certified translation and notarisation log

Sworn, certified and notarised translations are tracked with the stamp, the signing linguist and the courier details. Clients know when originals travel and when they arrive. Late authority submissions are avoided.

Linguist availability and leave calendar

Freelance and in-house linguists mark days off and busy periods. Project managers see who can take a rush file in a given language. Double-booking a scarce Japanese reviewer is avoided.

The records that hold the operation together.

  • Client and contact records. Keep each client’s contacts, billing details, rate card, purchase order rules and standing instructions in one place.
  • Quotes by word count. Price a job from word count, language pair, subject area and urgency, with revisions kept against the quote.
  • Job tracking and deadlines. Follow each job through brief, translation, editing, proofreading and delivery, with deadlines and owners shown on a board.
  • Linguist database. Record every linguist’s language pairs, subjects, certifications, rates, availability and past work.
  • Assignment and briefing. Offer work to linguists from the matching list, record who accepted, and send the brief and reference files from the job.
  • Interpreting bookings. Book interpreters by language, date, venue or remote link and hours, and confirm with both client and interpreter.
  • Glossaries and style notes. Hold approved terms and style instructions per client and subject, so linguists share one reference.
  • Source and delivered files. Store source files, translated files, certificates and client approvals against the job they belong to.

Operational bottlenecks to check

Jobs are tracked in several places

Briefs sit in email, source files in shared folders and deadlines in a spreadsheet that only one person updates properly. The project manager rebuilds the status of each job by hand every morning.

Linguist availability is guesswork

Linguists work in certain pairs and subjects, and take leave at different times, so finding the right free person means scrolling through old messages from several weeks.

Quotes and invoices use different word counts

A quote rests on the count taken at the start, and source files get revised before delivery. The invoice may then be raised on another figure. Clients notice. Disputes follow.

Freelancer invoices are checked line by line

Each linguist invoices in their own format and currency, and totals rarely match the jobs the project manager remembers assigning. Finance compares every line with the job record before paying.

Interpreting hours arrive late

Start and end times come by message after the session, sometimes days later, and travel time is added from memory. Billing waits until the coordinator has collected them all.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Request

    A client sends files or a booking request. The agency opens a job, records the language pair and notes the deadline.

  2. 2. Quote

    The project manager counts words, applies the client’s rate card and sends a quotation. The client’s approval is noted on the job.

  3. 3. Assignment

    A linguist is chosen by language pair, subject and availability. The brief, glossary and files go to them from the job.

  4. 4. Review

    The translation passes to an editor and then a proofreader. Each stage is marked done with the person who did it.

  5. 5. Delivery

    Final files go back to the client, with any certification statement attached. The job is closed once the client confirms.

  6. 6. Billing and payment

    Delivered work produces the client invoice. The linguist’s invoice is checked against the same job and approved for payment.

Roles and responsibility boundaries.

For the agency owner

See jobs by client and language, margin on each, invoices outstanding and linguists carrying the heaviest load.

For project managers

Manage quotes, assignments, deadlines and delivery for every job you own, and spot those running late.

For interpreting coordinators

Hold the booking calendar, match interpreters to sessions and collect hours after each one.

For finance staff

Raise client invoices, check linguist invoices against jobs and prepare payment runs.

For freelance linguists

See your assigned jobs, briefs, glossaries and deadlines, and follow the status of your own invoices.

Reports your managers need.

  • Jobs by client, language pair and stage
  • Work due this week by linguist
  • Margin on each job and client
  • Interpreting hours by interpreter and client
  • Client invoices outstanding by age
  • Linguist payments approved and pending

Connections to scope

  • Email
  • Cloud file storage
  • Video call platforms
  • Calendar
  • Accounting software export
  • Translation memory tools

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Languages and rate cards

Language pairs, subject areas and client rates follow the way your agency quotes.

Review stages

Your own sequence of translation, editing, proofreading and certification becomes the stage list for every job.

Linguists and open jobs migrated

Your linguist list, contact details and jobs in progress are brought in from spreadsheets or the tool you use now.

Currency and tax settings

Clients and linguists can be set up in different currencies, with tax rules for each country reviewed during implementation.

Where it runs

The system runs on GullySystem servers. Stages, rates and invoice layouts are changed by GullySystem staff on request.

Limitations to settle before implementation

  • A single freelance translator with a few regular clients can work from a folder and an invoice template.
  • A team that needs machine translation or a translation memory engine will still need a dedicated tool for the language work itself.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • Certified translation of personal certificates
  • Visa and immigration document files
  • University admission documents
  • Court and legal documents
  • Business agreements and corporate papers
  • Technical manuals and product literature
  • Interpreters for meetings, factory visits and conferences
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements