Skip to main content
GullySystem
Professional services

Workflow and Approvals for Translation and interpretation services

Route business requests through defined approval steps.

Platform

Does this function belong in your operation?

Use when requests need explicit approval before money, stock or records change.

A transaction or request requires authorisation.

A translation passes from linguist to reviewer to quality check to delivery, with client sign-off where the contract asks for it. Rejections go back with comments. Status is visible to the account manager.

Bring the records the workflow depends on.

  • Request types
  • Approval limits
  • Delegation and escalation rules

Outputs to check

  • Request and decision history
  • Pending-approval queue
  • Authorised downstream action record

Follow the workflow and approvals workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Define authority

    Set request types, value limits and delegation rules.

  2. 2. Submit the request

    Collect the evidence and proposed transaction details.

  3. 3. Route the decision

    Identify the approver with authority for the current request.

  4. 4. Record the outcome

    Retain approval, rejection or return comments and timestamps.

  5. 5. Release the handoff

    Allow only the authorised downstream action and reapprove material changes.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Owner or partner

Clears the day’s approvals between meetings, and sees what they cleared last week.

Department head

Approves what belongs to their team and nothing beyond it.

Whoever raises it

Knows where the request is standing without ringing anyone.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Approver unavailable

Use the documented delegation rule and retain the acting approver.

Value changes after approval

Return the revised request for the required approval rather than inheriting the old decision.

Request withdrawn

Stop pending actions and preserve the previous decision history.

Can this work independently?

Approval routing can operate as a standalone register, but blocking a transaction requires the transaction system to honour the decision. Role and delegation data identify authority; audit records retain evidence. An approval message alone should not be mistaken for execution of payment or fulfilment.

Systems and records it connects with

  • Purchase orders: Authorised supplier commitments and open line balances.
  • Price lists and schemes: Effective-dated rates and customer eligibility rules.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • Leave and holiday management: Approved absence and branch calendar information.

Configure, test and introduce the workflow.

  • We sit with the owner and department heads. You describe what needs whose approval. A table of rules returns for your correction.
  • Named approvers and their stand-ins are entered. Each person sees what they will receive. Purchase orders, discounts or leave requests are linked to the rules. Test requests are raised for each type.
  • A single department uses the screens for real approvals. Its group chat is closed. Remaining departments follow. Waiting times and reasons for refusal are reviewed with the owner.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Unapproved requests cannot take restricted actions.
  • Decisions retain an approver and time.
  • Absent-approver cases follow the agreed rule.
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.

See the full industry workflow, reports and implementation plan →

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.

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.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  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.

Industry reports to connect with

  • 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

Questions before implementation.

When should translation and interpretation services consider workflow and approvals?

Use when requests need explicit approval before money, stock or records change. A transaction or request requires authorisation.

What should we bring to the requirements discussion?

Bring anonymised examples of Request types; Approval limits; Delegation and escalation rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Route business requests through defined approval steps. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

An approval workflow records authority; it does not determine whether a transaction is legally or commercially appropriate.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Unapproved requests cannot take restricted actions. Use this check when reviewing the first working version.

Related functions for translation and interpretation services.

    Talk to us

    Discuss workflow and approvals for your business.

    Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

    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