Translate Mobile Number Porting and Transfer Status Correctly

To translate a mobile-number porting notice correctly, first separate keeping a telephone number from activating a SIM or eSIM. A request to switch provider, receipt of a porting code, scheduled transfer and successful port completion are different states. Never write that the customer’s number is active on the new network just because the request has been accepted.

Searches for mobile number porting translation, PAC code meaning, STAC code, mobile provider switching, number transfer pending, port request rejected, SIM swap warning and phone number activation status often happen while people are losing signal, waiting for messages or preparing to change network. Incorrectly translating a transfer status can lead to service disruption, billing confusion or mistaken confidence about account security.

This practical guide teaches a translation workflow for porting authorisation codes, scheduled transfer windows, old and new provider roles, dual-service periods, rejection reasons and fraud warnings. Because number-portability rules differ by country, the examples distinguish the United Kingdom’s PAC/STAC terminology from general international processes, and do not treat one nation’s deadlines or compensation rights as worldwide guarantees.

Quick answer: what the reader must know first

This article owns mobile-number portability across providers, including code issuance, transfer request, date, rejection and completion. It does not duplicate the existing guide to eSIM QR code installation and device activation, or the mobile roaming charges guide. Its specific question is whether the telephone number has transferred and what evidence proves that result.

Keeping the same phone number when changing network is a portability process involving provider authorisation, customer identity and a transfer cutover. The UK’s Ofcom explains PAC for switching while keeping the number and STAC for switching without retaining it. Those are U.K.-specific labels, not international universal codes. A number may be scheduled to transfer on one day while a new SIM is already installed; both statements can be true. Treat transfer status and SIM state as distinct. Security is crucial: the FTC warns that an unauthorised SIM swap can redirect calls and messages, so an unexpected transfer notice needs verification through a trusted provider channel.

The problem beneath the words

A common error begins when a translator treats every notice as a simple vocabulary exercise. In this subject the material carries identifiers and operational states: old provider, new provider, mobile number, porting authorisation code, PAC, STAC, transfer request, account holder, security PIN, SIM, eSIM, cutover, network activation, incoming calls, SMS, completion confirmation, early termination fee, credit balance, fraud alert. These are not decorative details. They tell people which source to trust, what stage an event has reached, and whether there is a decision or merely a request for a decision. An apparently tidy translation can become less accurate when a qualifier is removed.

The correct question is not merely ‘Which English word matches this expression?’ It is ‘Which real-world conclusion is this expression licensed to convey?’ A good translator takes the source as evidence, separates what is known from what is pending, and reconstructs the same action in the destination language. The examples below are invented teaching cases, not official notices. For an actual transaction, the reader must consult the current authority, carrier or institution.

First principles: build the right mental model

1. Porting is not SIM installation

A SIM or eSIM profile is a means of network access; the port transfers rights to use a telephone number between providers. A device can show service without the old number having moved.

Apply this distinction when reading mobile number porting translation. Identify the smallest source phrase that proves the claim, then identify the boundary beyond which the phrase does not speak. In a bilingual review, ask whether the target text retains the same boundary. If the translation removes it, a fluent sentence can create a new promise, prohibition or assumption that nobody authorised.

2. The customer may choose retention or a new number

In U.K. switching guidance, PAC supports keeping the number and STAC supports switching without keeping it. Translators must not treat both as interchangeable activation codes.

Apply this distinction when reading PAC code meaning. Identify the smallest source phrase that proves the claim, then identify the boundary beyond which the phrase does not speak. In a bilingual review, ask whether the target text retains the same boundary. If the translation removes it, a fluent sentence can create a new promise, prohibition or assumption that nobody authorised.

3. An issued code is potential, not success

Receiving a PAC allows a subsequent request. Until the receiving provider applies it and the process completes, the current number relationship has not necessarily changed.

Apply this distinction when reading STAC code. Identify the smallest source phrase that proves the claim, then identify the boundary beyond which the phrase does not speak. In a bilingual review, ask whether the target text retains the same boundary. If the translation removes it, a fluent sentence can create a new promise, prohibition or assumption that nobody authorised.

4. Expiry refers to the code, not the phone number

A message that a transfer code expires after a period is not evidence the customer’s phone number expires. The translator must attach each deadline to the correct object.

Apply this distinction when reading switching provider. Identify the smallest source phrase that proves the claim, then identify the boundary beyond which the phrase does not speak. In a bilingual review, ask whether the target text retains the same boundary. If the translation removes it, a fluent sentence can create a new promise, prohibition or assumption that nobody authorised.

5. Cutover is a transition with uncertainty

Scheduled port times are operational targets, and communications might be interrupted. Preserve forecast language and the specific provider’s explanation rather than promising a seamless universal change.

Apply this distinction when reading port request pending. Identify the smallest source phrase that proves the claim, then identify the boundary beyond which the phrase does not speak. In a bilingual review, ask whether the target text retains the same boundary. If the translation removes it, a fluent sentence can create a new promise, prohibition or assumption that nobody authorised.

6. Status depends on who reports it

The losing provider may say release authorised while the gaining provider says activation pending. These are different stages, not necessarily contradictory accounts.

Apply this distinction when reading number transfer completed. Identify the smallest source phrase that proves the claim, then identify the boundary beyond which the phrase does not speak. In a bilingual review, ask whether the target text retains the same boundary. If the translation removes it, a fluent sentence can create a new promise, prohibition or assumption that nobody authorised.

7. A phone number is an identity-sensitive asset

Control of incoming SMS and calls can affect account access. Porting and SIM replacement alerts have security implications, so translations should preserve warnings and not solicit secret codes.

Apply this distinction when reading SIM swap warning. Identify the smallest source phrase that proves the claim, then identify the boundary beyond which the phrase does not speak. In a bilingual review, ask whether the target text retains the same boundary. If the translation removes it, a fluent sentence can create a new promise, prohibition or assumption that nobody authorised.

8. Local law cannot be translated into global law

Ofcom’s one-working-day switching rules and code terminology apply within its regulatory context. Other countries can use different processes. Label the jurisdiction and avoid converting a U.K. service promise into an international right.

A ten-step method for reliable translation

Step 1: Identify jurisdiction and provider pair

Capture the country, the losing provider, the receiving provider and the customer’s requested number. Local procedures differ, and the same word ‘switch’ can conceal different products.

Begin with the heading, issuer, date, channel and target audience. A short push notification can inherit restrictions from a linked notice or portal. Do not translate the highlighted sentence in isolation when adjacent labels establish whether it is a warning, request, status update or confirmation.

For this stage, use old provider as a sample field. Check it against the issuer’s original layout and note what a reader could wrongly infer if it were mislabeled. A useful review record contains the source wording, proposed translation, evidence for the decision, unresolved questions and the checked version.

Step 2: Determine whether the number is retained

Mark clearly whether the customer intends to keep the old number or receive a new number. In U.K. materials distinguish PAC and STAC; do not mislabel one as the other.

Record actor, object, status, date, amount, place, identifier, restriction, condition and recipient action separately. Blank fields remain blank, not ‘not applicable’. This table makes silent inference visible and allows another reviewer to compare the source with the target without needing to guess the translator’s reasoning.

For this stage, use new provider as a sample field. Check it against the issuer’s original layout and note what a reader could wrongly infer if it were mislabeled. A useful review record contains the source wording, proposed translation, evidence for the decision, unresolved questions and the checked version.

Step 3: Protect identifiers and secrets

Copy the phone number and reference labels exactly when authorised, but do not expose live PACs, account PINs or one-time codes in publicly shared translations or screenshots.

The difference between requested, received, reviewed, scheduled, approved, issued and completed is not stylistic. These words describe different points in a workflow. Use the source’s actual event and do not upgrade a preliminary stage because a stronger English verb reads more smoothly.

For this stage, use mobile number as a sample field. Check it against the issuer’s original layout and note what a reader could wrongly infer if it were mislabeled. A useful review record contains the source wording, proposed translation, evidence for the decision, unresolved questions and the checked version.

Step 4: Identify issuance versus submission

A code being issued by the old provider is not proof the new provider has received or accepted it. Follow both administrative events.

Circle ‘may’, ‘only’, ‘except’, ‘unless’, ‘until’, ‘subject to’, ‘not yet’ and ‘if’. A missed negative or moved exception can invert practical meaning. After translation, read every restriction aloud and confirm it still applies to the same people, objects and circumstances.

For this stage, use porting authorisation code as a sample field. Check it against the issuer’s original layout and note what a reader could wrongly infer if it were mislabeled. A useful review record contains the source wording, proposed translation, evidence for the decision, unresolved questions and the checked version.

Step 5: Translate eligibility and expiry

Code expiration, contract status, early exit charges and account restrictions may appear in the same notice. Preserve which rule attaches to which item.

Transcribe IDs and other identifiers exactly. Reformat times and dates only if the local convention makes them clearer without losing original information. Do not silently convert a code, a quantity, a ranking or a timestamp into a different kind of field.

For this stage, use PAC as a sample field. Check it against the issuer’s original layout and note what a reader could wrongly infer if it were mislabeled. A useful review record contains the source wording, proposed translation, evidence for the decision, unresolved questions and the checked version.

Step 6: Carry the date and time correctly

Distinguish requested date, scheduled switching date, estimated cutover window and completed transfer timestamp, including local time and public holidays.

Use target-language sentence structures that readers can follow on their first reading. Accuracy is not an excuse for clumsy literal syntax; naturalness is not permission to invent a new promise. Put the action close to the person expected to perform it.

For this stage, use STAC as a sample field. Check it against the issuer’s original layout and note what a reader could wrongly infer if it were mislabeled. A useful review record contains the source wording, proposed translation, evidence for the decision, unresolved questions and the checked version.

Step 7: Trace both networks

The old SIM may work during preparation, while the new network may be active for a temporary number. Do not treat either observation as confirmation that the original number has ported.

Hide the source and ask what the translated text authorises the reader to believe or do. Then compare that answer against the original evidence. A target sentence can be grammatical, clear and still dangerously wrong in its implied next step.

For this stage, use transfer request as a sample field. Check it against the issuer’s original layout and note what a reader could wrongly infer if it were mislabeled. A useful review record contains the source wording, proposed translation, evidence for the decision, unresolved questions and the checked version.

Step 8: Read rejection reasons literally

Unmatched identity, invalid code, expired code and unsupported number range require different corrective actions. Translate the actual cause rather than declaring fraud or technical failure.

When the source is ambiguous, truncated or internally inconsistent, keep a query in the translation file and ask the responsible organisation. Do not conceal uncertainty by choosing a confident interpretation simply to finish publication.

For this stage, use account holder as a sample field. Check it against the issuer’s original layout and note what a reader could wrongly infer if it were mislabeled. A useful review record contains the source wording, proposed translation, evidence for the decision, unresolved questions and the checked version.

Step 9: Preserve cybersecurity warnings

Unexpected SIM replacement or transfer alerts can indicate account takeover risk. Translate the warning faithfully and refer to the provider’s verified contact channel rather than providing a code to an unsolicited caller.

For safety, health, financial or access-critical material, ask a competent human to review numbers, restrictions, status and jurisdiction-specific terms. Machine translation and AI can provide drafts but are not authoritative sources of live status.

For this stage, use security PIN as a sample field. Check it against the issuer’s original layout and note what a reader could wrongly infer if it were mislabeled. A useful review record contains the source wording, proposed translation, evidence for the decision, unresolved questions and the checked version.

Step 10: Validate the completion event

Seek a recorded completion message or provider confirmation, and confirm incoming calls or SMS only when such checks are specified. Do not infer completion from a signal icon alone.

Keep a date, source link, language pair, reviewer and revision identifier for important translations. If the issuer updates the message, compare versions instead of assuming an earlier translation is still current.

For this stage, use SIM as a sample field. Check it against the issuer’s original layout and note what a reader could wrongly infer if it were mislabeled. A useful review record contains the source wording, proposed translation, evidence for the decision, unresolved questions and the checked version.

Worked examples: source, risky interpretation and safe translation

These are illustrative English glosses of source-language notices, followed by a misleading translation and a faithful target-language meaning. They are invented to train precise handling of workflow states; they do not assert that any named organisation has issued them. In actual bilingual work, the translator should check the original-language wording, grammatical scope and document context.

Example 1: PAC issued

Illustrative source: “Your PAC has been issued and is valid for 30 days”

Misleading version: “Your number has been transferred”

Faithful version: “The porting authorisation code has been issued and remains valid for 30 days”

The central distinction is the difference between an instruction and a result. Code issuance is before transfer. A person following the flawed version might act as though the process is complete when it has not begun. Compare the grammatical subject, the governing verb, and every qualifier before finalising the target.

Example 2: STAC issued

Illustrative source: “Your STAC is ready for switching without retaining your number”

Misleading version: “Use this to keep your old number”

Faithful version: “Your service termination authorisation code is ready for a switch without number retention”

Read this as a question of evidence. The customer’s retention choice would be reversed by the wrong wording. The incorrect sentence is attractive because it sounds definite, but fluency cannot supply facts that the source has withheld. Test the finished translation by asking which part of the original actually authorises each conclusion.

Example 3: Code submitted

Illustrative source: “We have received your number-porting code”

Misleading version: “The transfer is complete”

Faithful version: “The new provider has received your porting code”

Time, scope and status govern this example. Receipt does not establish cutover. The translation must preserve whether a condition applies now, might apply later, or applies only after further checking. That distinction helps the reader make a decision without being falsely reassured or needlessly alarmed.

Example 4: Code rejected

Illustrative source: “The submitted PAC was not recognised”

Misleading version: “Your telephone number is invalid”

Faithful version: “The submitted PAC was not recognised; verify the code”

The recipient’s next action changes if the wording drifts. The failure concerns the code, not number ownership. Before approving the target, ask another reader to explain exactly what they would do. If the answer differs from the source instruction, revise the verb or condition rather than merely polishing style.

Example 5: Expired PAC

Illustrative source: “Your PAC has expired; request a new code”

Misleading version: “Your mobile number has expired”

Faithful version: “The porting authorisation code has expired; request a replacement code”

A label is not a substitute for a complete statement. The deadline is attached to an authorisation token. Look for the object to which the number, condition, restriction or status belongs. Translation errors often occur because a short interface phrase is copied without its heading or explanatory text.

Example 6: Port requested

Illustrative source: “Number transfer requested for 9 November”

Misleading version: “Number transferred on 9 November”

Faithful version: “Transfer of the telephone number has been requested for 9 November”

This is a useful audit of certainty. Requested date and completed date differ. Separate what the sender knows from what is being requested, predicted or evaluated. A strong translation leaves unresolved questions unresolved, and it keeps the responsible authority visible to the reader.

Example 7: Port scheduled

Illustrative source: “Port scheduled for the next working day”

Misleading version: “Port completed today”

Faithful version: “The number transfer is scheduled for the next working day”

The central distinction is the difference between an instruction and a result. A schedule is a plan. A person following the flawed version might act as though the process is complete when it has not begun. Compare the grammatical subject, the governing verb, and every qualifier before finalising the target.

Example 8: Estimated time

Illustrative source: “The switch is expected to finish by evening”

Misleading version: “The switch is guaranteed to finish by evening”

Faithful version: “The transfer is currently expected to finish by evening”

Read this as a question of evidence. Expected does not equal guaranteed. The incorrect sentence is attractive because it sounds definite, but fluency cannot supply facts that the source has withheld. Test the finished translation by asking which part of the original actually authorises each conclusion.

Example 9: Country condition

Illustrative source: “This instruction applies to U.K. mobile provider switching”

Misleading version: “These rules apply to every country”

Faithful version: “This process applies to the U.K. mobile network context described”

Time, scope and status govern this example. Jurisdiction must remain explicit. The translation must preserve whether a condition applies now, might apply later, or applies only after further checking. That distinction helps the reader make a decision without being falsely reassured or needlessly alarmed.

Example 10: Old provider active

Illustrative source: “Old SIM remains active until the transfer”

Misleading version: “Your new number is already active”

Faithful version: “The old SIM remains in service until the porting cutover”

The recipient’s next action changes if the wording drifts. One provider’s service state does not settle the other’s. Before approving the target, ask another reader to explain exactly what they would do. If the answer differs from the source instruction, revise the verb or condition rather than merely polishing style.

Example 11: Temporary number

Illustrative source: “New SIM is active with a temporary number”

Misleading version: “Your old number has transferred”

Faithful version: “The new SIM is working with a temporary telephone number”

A label is not a substitute for a complete statement. Provisioning and portability are separate. Look for the object to which the number, condition, restriction or status belongs. Translation errors often occur because a short interface phrase is copied without its heading or explanatory text.

Example 12: Old SIM disconnects

Illustrative source: “Old SIM may stop receiving calls during the switch”

Misleading version: “The transfer was cancelled”

Faithful version: “The old SIM may lose incoming-call service during cutover”

This is a useful audit of certainty. Temporary loss can be part of transfer. Separate what the sender knows from what is being requested, predicted or evaluated. A strong translation leaves unresolved questions unresolved, and it keeps the responsible authority visible to the reader.

Example 13: New SIM prompt

Illustrative source: “Insert the new SIM after receiving the provider’s instruction”

Misleading version: “Your number is already active”

Faithful version: “Insert the new SIM when the new provider instructs you to”

The central distinction is the difference between an instruction and a result. Device action and completion need separation. A person following the flawed version might act as though the process is complete when it has not begun. Compare the grammatical subject, the governing verb, and every qualifier before finalising the target.

Example 14: eSIM ready

Illustrative source: “eSIM profile downloaded; number transfer pending”

Misleading version: “The original number is active on the eSIM”

Faithful version: “The eSIM profile is installed; porting of the original number remains pending”

Read this as a question of evidence. A technical profile may exist before the port. The incorrect sentence is attractive because it sounds definite, but fluency cannot supply facts that the source has withheld. Test the finished translation by asking which part of the original actually authorises each conclusion.

Example 15: Account mismatch

Illustrative source: “Port cannot proceed because account details do not match”

Misleading version: “Your transfer has been refused permanently”

Faithful version: “Transfer is blocked by a mismatch in account information”

Time, scope and status govern this example. Corrective identity verification may resolve the issue. The translation must preserve whether a condition applies now, might apply later, or applies only after further checking. That distinction helps the reader make a decision without being falsely reassured or needlessly alarmed.

Example 16: Ownership check

Illustrative source: “Proof of account-holder authority is required”

Misleading version: “You have already passed verification”

Faithful version: “The provider requires evidence of authority over the account”

The recipient’s next action changes if the wording drifts. The user must supply evidence; approval has not occurred. Before approving the target, ask another reader to explain exactly what they would do. If the answer differs from the source instruction, revise the verb or condition rather than merely polishing style.

Example 17: Existing contract

Illustrative source: “Early termination charges may apply”

Misleading version: “Switching has no cost”

Faithful version: “Early exit charges might apply under your current agreement”

A label is not a substitute for a complete statement. Charges and conditions should not be erased. Look for the object to which the number, condition, restriction or status belongs. Translation errors often occur because a short interface phrase is copied without its heading or explanatory text.

Example 18: Credit balance

Illustrative source: “Check how unused prepaid credit will be handled”

Misleading version: “Credit will be automatically refunded”

Faithful version: “Verify the treatment of any remaining prepaid credit”

This is a useful audit of certainty. No refund is promised by the instruction. Separate what the sender knows from what is being requested, predicted or evaluated. A strong translation leaves unresolved questions unresolved, and it keeps the responsible authority visible to the reader.

Example 19: Double billing

Illustrative source: “Review whether both accounts are being charged during migration”

Misleading version: “Double charging is authorised”

Faithful version: “Check the billing periods on both provider accounts during the change”

The central distinction is the difference between an instruction and a result. A warning to review is not a ruling that charges are valid. A person following the flawed version might act as though the process is complete when it has not begun. Compare the grammatical subject, the governing verb, and every qualifier before finalising the target.

Example 20: Completion notice

Illustrative source: “Port completed at 14:20 local time”

Misleading version: “Port was only requested at 14:20”

Faithful version: “The number transfer was completed at 2:20 p.m. local time”

Read this as a question of evidence. This is the recorded completion state. The incorrect sentence is attractive because it sounds definite, but fluency cannot supply facts that the source has withheld. Test the finished translation by asking which part of the original actually authorises each conclusion.

Example 21: Calls not working

Illustrative source: “Incoming calls may take time to route after completion”

Misleading version: “The number transfer was unsuccessful”

Faithful version: “Incoming-call routing may still be updating after the reported transfer completion”

Time, scope and status govern this example. Post-cutover symptoms are not a definitive cause. The translation must preserve whether a condition applies now, might apply later, or applies only after further checking. That distinction helps the reader make a decision without being falsely reassured or needlessly alarmed.

Example 22: SMS delay

Illustrative source: “Some SMS messages may be delayed during cutover”

Misleading version: “Texts are permanently lost”

Faithful version: “Text-message delivery may be delayed during the switch”

The recipient’s next action changes if the wording drifts. Duration and permanence are not asserted. Before approving the target, ask another reader to explain exactly what they would do. If the answer differs from the source instruction, revise the verb or condition rather than merely polishing style.

Example 23: Unauthorised request

Illustrative source: “If you did not request this transfer, contact the provider immediately”

Misleading version: “Ignore the message unless service stops”

Faithful version: “If you did not authorise this porting request, contact your provider promptly using trusted contact details”

A label is not a substitute for a complete statement. The message is a security warning, not mere information. Look for the object to which the number, condition, restriction or status belongs. Translation errors often occur because a short interface phrase is copied without its heading or explanatory text.

Example 24: Suspicious caller

Illustrative source: “Do not share the porting code with unsolicited callers”

Misleading version: “Give the code to whoever claims to be support”

Faithful version: “Never disclose the code to an unsolicited caller”

This is a useful audit of certainty. Identity risk is created by supplying secrets. Separate what the sender knows from what is being requested, predicted or evaluated. A strong translation leaves unresolved questions unresolved, and it keeps the responsible authority visible to the reader.

Example 25: Port lock

Illustrative source: “Port-out protection is enabled; further verification is required”

Misleading version: “The port has completed”

Faithful version: “Port-out protection is active, so additional verification is needed”

The central distinction is the difference between an instruction and a result. A security lock inhibits rather than confirms transfer. A person following the flawed version might act as though the process is complete when it has not begun. Compare the grammatical subject, the governing verb, and every qualifier before finalising the target.

Example 26: Request cancelled

Illustrative source: “Your port request was cancelled at your instruction”

Misleading version: “Your mobile account has been permanently closed”

Faithful version: “The number-porting request was cancelled as requested”

Read this as a question of evidence. Cancellation of the transfer is not necessarily cancellation of service. The incorrect sentence is attractive because it sounds definite, but fluency cannot supply facts that the source has withheld. Test the finished translation by asking which part of the original actually authorises each conclusion.

Example 27: Multiple lines

Illustrative source: “Only number ending 2468 is included in this transfer request”

Misleading version: “All family-plan numbers will switch”

Faithful version: “This request covers the listed number ending 2468 only”

Time, scope and status govern this example. Do not extend one line’s status to a group. The translation must preserve whether a condition applies now, might apply later, or applies only after further checking. That distinction helps the reader make a decision without being falsely reassured or needlessly alarmed.

Example 28: Wrong carrier

Illustrative source: “New provider name does not match the request; confirm with support”

Misleading version: “The unfamiliar provider is authorised”

Faithful version: “The receiving provider listed differs from the requested provider; verify through a trusted channel”

The recipient’s next action changes if the wording drifts. Mismatch should trigger verification, not assumption. Before approving the target, ask another reader to explain exactly what they would do. If the answer differs from the source instruction, revise the verb or condition rather than merely polishing style.

Example 29: Cutover postponed

Illustrative source: “Transfer deferred pending additional checks”

Misleading version: “Transfer completed despite delay”

Faithful version: “The transfer has been postponed while checks continue”

A label is not a substitute for a complete statement. A postponement is not a completion. Look for the object to which the number, condition, restriction or status belongs. Translation errors often occur because a short interface phrase is copied without its heading or explanatory text.

Example 30: Late completion

Illustrative source: “Provider confirms transfer completed one day after planned date”

Misleading version: “Transfer completed on the planned date”

Faithful version: “The provider reports completion one day later than originally scheduled”

This is a useful audit of certainty. Planned and actual dates must remain separate. Separate what the sender knows from what is being requested, predicted or evaluated. A strong translation leaves unresolved questions unresolved, and it keeps the responsible authority visible to the reader.

Example 31: Complaint pending

Illustrative source: “Your transfer complaint has been logged”

Misleading version: “Compensation has been approved”

Faithful version: “Your complaint about the transfer has been registered”

The central distinction is the difference between an instruction and a result. Logging a complaint is not granting a remedy. A person following the flawed version might act as though the process is complete when it has not begun. Compare the grammatical subject, the governing verb, and every qualifier before finalising the target.

Example 32: Unknown state

Illustrative source: “We cannot confirm transfer status; contact the new provider”

Misleading version: “The original number is working normally”

Faithful version: “Transfer status is not currently confirmed; contact the receiving provider”

Read this as a question of evidence. The source has no outcome evidence. The incorrect sentence is attractive because it sounds definite, but fluency cannot supply facts that the source has withheld. Test the finished translation by asking which part of the original actually authorises each conclusion.

A deeper comparison: five kinds of translation error

One wrong sentence can have several different causes. The same repair method should not be applied blindly to every error. The following diagnostic categories help a reviewer locate where meaning changed before rewriting the target.

1. Status inflation

A requested or scheduled event becomes approved or completed. Repair by checking the event verb against an actual confirmation record.

Find the related pattern in Example 2 and Example 8. Rewrite the misleading sentence without looking at the safe version, then compare your result. If you cannot explain which word or clause caused the error, you have not yet repaired the translation; you have only guessed at another formulation.

2. Scope expansion

A rule about one person, device, unit, route or time window is translated as a universal policy. Restore the source’s category and qualifier.

Find the related pattern in Example 3 and Example 9. Rewrite the misleading sentence without looking at the safe version, then compare your result. If you cannot explain which word or clause caused the error, you have not yet repaired the translation; you have only guessed at another formulation.

3. Timing drift

A forecast, issue date, expiry, appointment or completion date is assigned to the wrong event. Build a timeline with separate labels.

Find the related pattern in Example 4 and Example 10. Rewrite the misleading sentence without looking at the safe version, then compare your result. If you cannot explain which word or clause caused the error, you have not yet repaired the translation; you have only guessed at another formulation.

4. Role reversal

The duty of the sender, recipient or approving authority is moved to someone else. Identify every actor and draw an arrow to the action they own.

Find the related pattern in Example 5 and Example 11. Rewrite the misleading sentence without looking at the safe version, then compare your result. If you cannot explain which word or clause caused the error, you have not yet repaired the translation; you have only guessed at another formulation.

5. False certainty

An uncertain or conditional statement becomes a definite prediction. Restore modality and preserve what the source does not know.

Find the related pattern in Example 6 and Example 12. Rewrite the misleading sentence without looking at the safe version, then compare your result. If you cannot explain which word or clause caused the error, you have not yet repaired the translation; you have only guessed at another formulation.

Practice and transfer: eight revision exercises

Try each task before reading its answer. For classroom use, ask learners to justify each change by pointing to a specific source field. For professional use, retain the answer as a miniature issue log.

Exercise 1: Code submitted

An editor gives you this source: “We have received your number-porting code” and proposes: “The transfer is complete”. Mark the exact status, scope, number, time or permission that changes. Write a faithful target sentence and state what additional document would be needed before claiming a more definitive outcome.

Suggested revision: “The new provider has received your porting code”. Reasoning: Receipt does not establish cutover. The further check is not permission to improve the claim; it is a request for better evidence. In a team, one learner can defend the original and another must show which source detail was lost or invented.

Exercise 2: Port scheduled

An editor gives you this source: “Port scheduled for the next working day” and proposes: “Port completed today”. Mark the exact status, scope, number, time or permission that changes. Write a faithful target sentence and state what additional document would be needed before claiming a more definitive outcome.

Suggested revision: “The number transfer is scheduled for the next working day”. Reasoning: A schedule is a plan. The further check is not permission to improve the claim; it is a request for better evidence. In a team, one learner can defend the original and another must show which source detail was lost or invented.

Exercise 3: Temporary number

An editor gives you this source: “New SIM is active with a temporary number” and proposes: “Your old number has transferred”. Mark the exact status, scope, number, time or permission that changes. Write a faithful target sentence and state what additional document would be needed before claiming a more definitive outcome.

Suggested revision: “The new SIM is working with a temporary telephone number”. Reasoning: Provisioning and portability are separate. The further check is not permission to improve the claim; it is a request for better evidence. In a team, one learner can defend the original and another must show which source detail was lost or invented.

Exercise 4: Account mismatch

An editor gives you this source: “Port cannot proceed because account details do not match” and proposes: “Your transfer has been refused permanently”. Mark the exact status, scope, number, time or permission that changes. Write a faithful target sentence and state what additional document would be needed before claiming a more definitive outcome.

Suggested revision: “Transfer is blocked by a mismatch in account information”. Reasoning: Corrective identity verification may resolve the issue. The further check is not permission to improve the claim; it is a request for better evidence. In a team, one learner can defend the original and another must show which source detail was lost or invented.

Exercise 5: Double billing

An editor gives you this source: “Review whether both accounts are being charged during migration” and proposes: “Double charging is authorised”. Mark the exact status, scope, number, time or permission that changes. Write a faithful target sentence and state what additional document would be needed before claiming a more definitive outcome.

Suggested revision: “Check the billing periods on both provider accounts during the change”. Reasoning: A warning to review is not a ruling that charges are valid. The further check is not permission to improve the claim; it is a request for better evidence. In a team, one learner can defend the original and another must show which source detail was lost or invented.

Exercise 6: Unauthorised request

An editor gives you this source: “If you did not request this transfer, contact the provider immediately” and proposes: “Ignore the message unless service stops”. Mark the exact status, scope, number, time or permission that changes. Write a faithful target sentence and state what additional document would be needed before claiming a more definitive outcome.

Suggested revision: “If you did not authorise this porting request, contact your provider promptly using trusted contact details”. Reasoning: The message is a security warning, not mere information. The further check is not permission to improve the claim; it is a request for better evidence. In a team, one learner can defend the original and another must show which source detail was lost or invented.

Exercise 7: Multiple lines

An editor gives you this source: “Only number ending 2468 is included in this transfer request” and proposes: “All family-plan numbers will switch”. Mark the exact status, scope, number, time or permission that changes. Write a faithful target sentence and state what additional document would be needed before claiming a more definitive outcome.

Suggested revision: “This request covers the listed number ending 2468 only”. Reasoning: Do not extend one line’s status to a group. The further check is not permission to improve the claim; it is a request for better evidence. In a team, one learner can defend the original and another must show which source detail was lost or invented.

Exercise 8: Complaint pending

An editor gives you this source: “Your transfer complaint has been logged” and proposes: “Compensation has been approved”. Mark the exact status, scope, number, time or permission that changes. Write a faithful target sentence and state what additional document would be needed before claiming a more definitive outcome.

Suggested revision: “Your complaint about the transfer has been registered”. Reasoning: Logging a complaint is not granting a remedy. The further check is not permission to improve the claim; it is a request for better evidence. In a team, one learner can defend the original and another must show which source detail was lost or invented.

Three multi-message case studies

Real readers rarely see one notice alone. They see a message, a portal status, then a follow-up, sometimes in different languages. A translation must remain consistent across that sequence while acknowledging what changes.

Sequence 1: from message to decision

The first message says “Your PAC has been issued and is valid for 30 days”. Later the reader encounters “Your STAC is ready for switching without retaining your number” and “We have received your number-porting code”. These statements do not merge into one undifferentiated status. Translate them in order, retaining the source and timestamp for each. The earliest statement may still describe a different step from the latest one.

A reviewer should separately confirm: first, code issuance is before transfer.; second, the customer’s retention choice would be reversed by the wrong wording.; third, receipt does not establish cutover.. Then test the reader’s likely action after each message. This timeline approach is especially useful when customers forward screenshots out of order or when the same term appears in a policy, automated email and live status screen.

Sequence 2: from message to decision

The first message says “Old SIM remains active until the transfer”. Later the reader encounters “New SIM is active with a temporary number” and “Old SIM may stop receiving calls during the switch”. These statements do not merge into one undifferentiated status. Translate them in order, retaining the source and timestamp for each. The earliest statement may still describe a different step from the latest one.

A reviewer should separately confirm: first, one provider’s service state does not settle the other’s.; second, provisioning and portability are separate.; third, temporary loss can be part of transfer.. Then test the reader’s likely action after each message. This timeline approach is especially useful when customers forward screenshots out of order or when the same term appears in a policy, automated email and live status screen.

Sequence 3: from message to decision

The first message says “Review whether both accounts are being charged during migration”. Later the reader encounters “Port completed at 14:20 local time” and “Incoming calls may take time to route after completion”. These statements do not merge into one undifferentiated status. Translate them in order, retaining the source and timestamp for each. The earliest statement may still describe a different step from the latest one.

A reviewer should separately confirm: first, a warning to review is not a ruling that charges are valid.; second, this is the recorded completion state.; third, post-cutover symptoms are not a definitive cause.. Then test the reader’s likely action after each message. This timeline approach is especially useful when customers forward screenshots out of order or when the same term appears in a policy, automated email and live status screen.

Failure modes and how to recover

1. Avoid your number has been transferred

This mistake changes the original “Your PAC has been issued and is valid for 30 days” into a conclusion the sender did not give. Code issuance is before transfer. Return to the source, restore “The porting authorisation code has been issued and remains valid for 30 days”, and keep an issue note naming the unverified leap. If the misleading version has already circulated, correct it visibly so a recipient knows which reading supersedes the earlier one.

2. Avoid use this to keep your old number

This mistake changes the original “Your STAC is ready for switching without retaining your number” into a conclusion the sender did not give. The customer’s retention choice would be reversed by the wrong wording. Return to the source, restore “Your service termination authorisation code is ready for a switch without number retention”, and keep an issue note naming the unverified leap. If the misleading version has already circulated, correct it visibly so a recipient knows which reading supersedes the earlier one.

3. Avoid the transfer is complete

This mistake changes the original “We have received your number-porting code” into a conclusion the sender did not give. Receipt does not establish cutover. Return to the source, restore “The new provider has received your porting code”, and keep an issue note naming the unverified leap. If the misleading version has already circulated, correct it visibly so a recipient knows which reading supersedes the earlier one.

4. Avoid your telephone number is invalid

This mistake changes the original “The submitted PAC was not recognised” into a conclusion the sender did not give. The failure concerns the code, not number ownership. Return to the source, restore “The submitted PAC was not recognised; verify the code”, and keep an issue note naming the unverified leap. If the misleading version has already circulated, correct it visibly so a recipient knows which reading supersedes the earlier one.

5. Avoid your mobile number has expired

This mistake changes the original “Your PAC has expired; request a new code” into a conclusion the sender did not give. The deadline is attached to an authorisation token. Return to the source, restore “The porting authorisation code has expired; request a replacement code”, and keep an issue note naming the unverified leap. If the misleading version has already circulated, correct it visibly so a recipient knows which reading supersedes the earlier one.

6. Avoid number transferred on 9 november

This mistake changes the original “Number transfer requested for 9 November” into a conclusion the sender did not give. Requested date and completed date differ. Return to the source, restore “Transfer of the telephone number has been requested for 9 November”, and keep an issue note naming the unverified leap. If the misleading version has already circulated, correct it visibly so a recipient knows which reading supersedes the earlier one.

7. Avoid port completed today

This mistake changes the original “Port scheduled for the next working day” into a conclusion the sender did not give. A schedule is a plan. Return to the source, restore “The number transfer is scheduled for the next working day”, and keep an issue note naming the unverified leap. If the misleading version has already circulated, correct it visibly so a recipient knows which reading supersedes the earlier one.

8. Avoid the switch is guaranteed to finish by evening

This mistake changes the original “The switch is expected to finish by evening” into a conclusion the sender did not give. Expected does not equal guaranteed. Return to the source, restore “The transfer is currently expected to finish by evening”, and keep an issue note naming the unverified leap. If the misleading version has already circulated, correct it visibly so a recipient knows which reading supersedes the earlier one.

9. Avoid these rules apply to every country

This mistake changes the original “This instruction applies to U.K. mobile provider switching” into a conclusion the sender did not give. Jurisdiction must remain explicit. Return to the source, restore “This process applies to the U.K. mobile network context described”, and keep an issue note naming the unverified leap. If the misleading version has already circulated, correct it visibly so a recipient knows which reading supersedes the earlier one.

10. Avoid your new number is already active

This mistake changes the original “Old SIM remains active until the transfer” into a conclusion the sender did not give. One provider’s service state does not settle the other’s. Return to the source, restore “The old SIM remains in service until the porting cutover”, and keep an issue note naming the unverified leap. If the misleading version has already circulated, correct it visibly so a recipient knows which reading supersedes the earlier one.

11. Avoid your old number has transferred

This mistake changes the original “New SIM is active with a temporary number” into a conclusion the sender did not give. Provisioning and portability are separate. Return to the source, restore “The new SIM is working with a temporary telephone number”, and keep an issue note naming the unverified leap. If the misleading version has already circulated, correct it visibly so a recipient knows which reading supersedes the earlier one.

12. Avoid the transfer was cancelled

This mistake changes the original “Old SIM may stop receiving calls during the switch” into a conclusion the sender did not give. Temporary loss can be part of transfer. Return to the source, restore “The old SIM may lose incoming-call service during cutover”, and keep an issue note naming the unverified leap. If the misleading version has already circulated, correct it visibly so a recipient knows which reading supersedes the earlier one.

Frequently asked questions

What is mobile-number porting?

It is the process of keeping an existing phone number when moving it between providers, subject to the local rules and any eligibility conditions. It is different from simply installing a new SIM.