What Clause 4 Actually Covers
Before a single word gets translated, ISO 17100 expects a translation service provider to have done some serious groundwork. Clause 4 of the standard governs the pre-production phase, which is everything that happens between a client making an enquiry and the translation work actually beginning. This includes assessing the feasibility of a project, issuing a quotation, reviewing what the client needs, and formalising an agreement.
On this page
This clause is often underestimated. Organisations seeking ISO 17100 certification tend to focus their energy on the production workflow in Clause 5, where the translation, revision, and checking steps sit. But auditors who have worked through multiple translation services certifications will tell you that many nonconformities trace back to weak pre-production practices. A project that starts without a clear agreement almost always runs into problems downstream.
If you are a quality manager at a language services company, an ISO consultant working with translation providers, or an auditor preparing to assess against this standard, understanding what Clause 4 requires in practice is essential. This article walks through each element of the clause and explains what conformity actually looks like on the ground.
The Purpose of the Pre-Production Phase
The pre-production phase exists to protect both the provider and the client. From the provider's perspective, it is the opportunity to confirm that the work is achievable, that the right resources are available, and that the scope and requirements are understood before committing. From the client's perspective, it is the point at which expectations get set clearly and any ambiguities get resolved.
ISO 17100 is a process standard. It does not just ask whether a translation is accurate. It asks whether the process that produced the translation was controlled, competent, and traceable. The pre-production phase is the foundation of that process. If requirements are vague, if feasibility was never checked, or if there is no documented agreement, the rest of the workflow has no solid base to rest on.
This is worth keeping in mind when you are auditing or implementing Clause 4. The question is not just whether a quote was sent. The question is whether the organisation genuinely understood what was required before work began, and whether that understanding was captured in a way that can be verified.
Clause 4.1: Feasibility and Enquiry Assessment
The first substantive requirement in Clause 4 is that the translation service provider must assess the feasibility of the project before accepting it. This sounds straightforward, but it covers several distinct considerations.
What Feasibility Assessment Involves
A feasibility assessment under ISO 17100 requires the provider to consider whether they can meet the client's requirements with respect to:
- The language combination requested
- The subject matter or technical domain of the content
- The required quality level and any specific process steps the client expects
- The timeline and volume of work
- Any special requirements such as terminology databases, style guides, or reference materials
This is not a formality. An organisation that accepts a highly specialised legal translation into a language combination where they have no qualified reviser available is not meeting the intent of this clause. The feasibility check is meant to catch exactly that kind of mismatch before the project starts.
What Auditors Look For Here
When auditing Clause 4.1 conformity, the first thing to establish is whether the organisation has a defined process for feasibility assessment. This does not need to be elaborate, but it needs to exist and be followed consistently. Look for evidence such as:
- A checklist or intake form that captures key project parameters
- Records showing that resource availability was checked before acceptance
- Cases where projects were declined or modified because feasibility could not be confirmed
That last point is important. If every single enquiry results in acceptance with no documented assessment, that is a flag. Real feasibility checking will sometimes result in a provider declining work or negotiating modified terms. If that never happens, the process is probably not functioning as intended.
Clause 4.2: Quotation
Once feasibility has been established, the provider issues a quotation. Clause 4.2 sets out what that quotation must address. The standard does not prescribe a format, but it does require that the quotation cover certain elements so that both parties have a shared understanding of what is being agreed to.
Key Elements of a Compliant Quotation
A quotation under ISO 17100 should address the scope of work clearly enough that there is no ambiguity about what is included. In practice, this means the quotation should specify:
- The source language and target language or languages
- The nature and volume of the content to be translated
- The services included, for example whether the quotation covers translation only or translation plus revision
- Any assumptions about the quality level or process steps
- Delivery timelines
- Pricing and payment terms
- Any conditions or dependencies, such as the client providing reference materials
One area where providers frequently fall short is failing to specify which process steps are included. ISO 17100 defines a mandatory production workflow that includes translation and revision as the minimum. If a client requests a reduced scope, that needs to be explicitly agreed and documented. A quotation that simply says “translation services” without specifying the steps is ambiguous and creates risk for both parties.
Audit Considerations for Clause 4.2
When auditing this clause, sample a selection of quotations and check whether they contain the elements described above. Pay particular attention to whether the scope of services is clearly defined. Ask the project manager or account manager to walk you through how a typical quotation is prepared. This will often reveal whether the process is genuinely followed or whether quotations are being issued informally without adequate review.
Also check whether the quotation process is consistent across the organisation. In smaller providers, quotations may be prepared by different people with different levels of rigour. The management system should ensure a consistent standard regardless of who prepares the document.
Clause 4.3: Requirements Review
Before accepting a project, the provider must review the client's requirements. This is the ISO 17100 equivalent of what ISO 9001 calls contract review, and the intent is the same: to confirm that the provider fully understands what is being asked, that any ambiguities have been resolved, and that the provider is capable of meeting those requirements.
What the Review Should Cover
The requirements review under Clause 4.3 should address at minimum:
- The completeness and clarity of the source material
- Any specific terminology, style, or formatting requirements
- The intended use of the translated content and the target audience
- Any reference materials the client is providing
- Accessibility of the client for queries during the project
- Any regulatory or legal requirements that apply to the content
This last point is relevant in sectors like medical devices, legal services, or pharmaceutical translation, where accuracy is not just a quality issue but a compliance matter. An auditor reviewing a provider that handles regulated content should check whether the requirements review process captures those additional obligations.
Handling Incomplete or Ambiguous Requirements
A well-functioning requirements review process will sometimes identify gaps in what the client has provided. ISO 17100 expects the provider to resolve those gaps before work begins, not after. This means contacting the client to clarify requirements, documenting what was agreed, and only proceeding once the requirements are clear.
In practice, this is one of the most common areas where translation providers cut corners. Time pressure leads to projects starting before requirements are fully understood, with the expectation that issues will be sorted out during production. That approach creates rework, delays, and dissatisfied clients. It also creates a nonconformity against Clause 4.3 if the provider cannot demonstrate that requirements were reviewed and confirmed before work commenced.
Documented Evidence of the Review
ISO 17100 requires that the requirements review be documented. The form of that documentation is flexible, but the record needs to show that the review happened and what was confirmed. This could be a completed intake form, an email exchange with the client that confirms requirements, or a project brief signed off by the project manager.
When auditing, ask to see the documented output of the requirements review for a sample of projects. If the only evidence is a verbal confirmation that “we always check with the client,” that is not sufficient. The record needs to exist and be retrievable.
Clause 4.4: Agreement
The final element of the pre-production phase is the agreement between the provider and the client. This is the point at which both parties formally commit to the terms of the project. Clause 4.4 requires that the agreement cover all relevant aspects of the project and that it be documented.
What the Agreement Must Address
The agreement should capture everything that was established during the feasibility assessment, quotation, and requirements review. Key elements include:
- The scope of services to be provided
- The source and target languages
- The production workflow to be applied, including which steps are included
- Delivery format and timeline
- Responsibilities of both parties, including what the client will provide and when
- Confidentiality arrangements, particularly for sensitive content
- How queries and changes will be handled during the project
- Pricing and payment terms
The agreement does not need to be a lengthy formal contract, although for large or ongoing projects that is often appropriate. For smaller projects, the agreement might be a purchase order combined with a terms and conditions document, or a confirmed quotation that the client has accepted in writing. What matters is that both parties have a shared, documented understanding of what has been agreed.
Changes to Agreements
One aspect of Clause 4.4 that deserves specific attention is how changes to agreed scope are handled. Translation projects frequently evolve. The client may add content, change the deadline, or modify the target language. ISO 17100 expects that any changes to the original agreement are reviewed, agreed, and documented in the same way as the original.
In practice, this means the provider needs a process for handling scope changes that goes beyond informal verbal agreement. When auditing this element, look for evidence of how mid-project changes are managed. Ask the project manager what happens when a client requests additional content after the project has started. If the answer is that the team just absorbs the change without any formal review or documentation, that is a gap against Clause 4.4.
Linking the Agreement to the Production Workflow
One of the more practical aspects of the agreement under ISO 17100 is that it needs to specify the production workflow that will be applied. This is where Clause 4 connects directly to Clause 5. The agreement should make clear whether the project will follow the full mandatory workflow, which includes translation and revision as a minimum, or whether any additional steps such as proofreading or review are included.
If a client requests a reduced scope, for example translation without revision, that can be accommodated under ISO 17100 but only if it is explicitly agreed in writing. The provider cannot simply omit revision because it is inconvenient and claim conformity. The agreement must reflect what will actually be done, and the production records must match the agreement.
For more on how the production workflow operates once the pre-production phase is complete, the article on ISO 17100 Clause 5 Production: Inside the Mandatory Translation Workflow covers those requirements in detail.
Common Nonconformities Against Clause 4
Having worked through what Clause 4 requires, it is worth being direct about where providers most commonly fall short. These are the patterns that come up repeatedly when auditing translation service providers against ISO 17100.
No Documented Feasibility Assessment
The most common gap is the absence of any documented feasibility check. The provider may argue that feasibility is assessed informally, but without records there is no way to verify that it happened consistently. This is a straightforward nonconformity against Clause 4.1.
Quotations That Do Not Specify the Workflow
Quotations that say “translation services” without specifying whether revision is included are problematic. This creates ambiguity about what the client is purchasing and what the provider is obligated to deliver. Auditors should flag this as a gap against Clause 4.2.
Requirements Review Done After Work Has Started
In time-pressured environments, it is common for translation to begin before the requirements review is complete. This is a clear nonconformity against Clause 4.3. The standard requires the review to happen before production commences, not concurrently with it.
Verbal Agreements Without Documentation
For smaller projects or repeat clients, providers sometimes rely on verbal agreements or informal email threads that do not constitute a clear documented agreement. This creates risk and does not meet the requirements of Clause 4.4.
No Process for Managing Scope Changes
Many providers have no formal process for handling changes to agreed scope. Changes are absorbed informally, which means there is no documented record of what was changed, when, and on what terms. This is a gap against Clause 4.4 and often leads to disputes with clients.
Practical Advice for Implementing Clause 4
If you are implementing ISO 17100 for the first time or strengthening an existing system, here is what makes a practical difference in the pre-production phase.
First, create a project intake process that captures all the information needed for a feasibility assessment and requirements review in one place. A well-designed intake form or project brief template will prompt the project manager to consider all the relevant factors before accepting a project. This does not need to be complex, but it does need to be consistently used.
Second, standardise your quotation template to include the production workflow as a specific line item. Make it explicit whether revision is included, and if a client requests translation only, make sure that reduced scope is clearly documented and that the client has acknowledged it in writing.
Third, treat the agreement as a living document. Build a simple process for handling scope changes that requires written confirmation before additional work proceeds. This protects the provider and gives the client clarity about what they are committing to.
Fourth, train your project managers on what the pre-production requirements actually mean. Many nonconformities against Clause 4 arise not from bad intentions but from a lack of understanding about what the standard expects. Project managers who understand the purpose of each step are far more likely to apply it consistently.
For a broader understanding of how ISO 17100 fits alongside other quality management frameworks, the article on ISO 17100 vs ISO 9001: How the Translation Standard Fits Alongside Quality Management is worth reading alongside this one.
How Auditors Should Approach Clause 4
When auditing Clause 4, the most effective approach is to trace a sample of completed projects back through the pre-production phase. Start with the final deliverable and work backwards: was there an agreement? Does the agreement match what was delivered? Was there a requirements review? Is there a documented feasibility assessment? Does the quotation specify the workflow that was applied?
This backward trace is more revealing than simply asking whether the provider has a procedure for pre-production. Procedures are easy to write. Evidence that the procedure was followed consistently across a sample of real projects is what demonstrates genuine conformity.
Also pay attention to how the provider handles difficult situations. Ask what happens when a client provides incomplete source material. Ask what happens when a project scope changes mid-way through. Ask whether the provider has ever declined a project because it was not feasible. The answers to these questions will tell you far more about the maturity of the pre-production process than any document review alone.
If you are building your auditing skills across ISO standards and want to understand how to audit process-based standards like ISO 17100 with confidence, the training courses at Audit Workshop cover auditing techniques that apply across quality, environmental, and safety management systems. The skills involved in tracing audit evidence through a process, identifying gaps between documented procedures and actual practice, and writing findings that are specific and defensible are transferable across any standard you audit against.
