guide

Last updated June 25, 2026

Germany Work Permit Change of Employer: New Salary, New Contract, and Approval Risk

This article treats Germany Work Permit Change of Employer: New Salary, New Contract, and Approval Risk as a decision file rather than a generic overview. It explains understanding the visa, residence, work-permit, renewal, and refusal issues behind Germany Work Permit Change of Employer: New Salary, New Contract, and Approval Risk, then shows how to separate eligibility, sponsor or employer evidence, official forms, timing, refusal risk, and appeal or reapplication choices. The later sections connect official sources to keep open, fast diagnostic table, and why employer changes need a new salary review so the next step is easier to judge. Read it before an appointment, application, renewal, refusal response, or document request so the evidence file is built in the right order.

This guide explains how to review a change of employer, new contract, salary increase or salary drop, new role, and new route evidence before a candidate resigns, starts work, or relies on old approval facts. It is written for candidates, new employers, HR teams, recruiters, and relocation advisers.

Source check date: May 19, 2026.

Official sources to keep open

• Make it in Germany: Zustimmung der Bundesagentur fuer Arbeit explains BA consent and employment-condition comparison.
• Bundesagentur fuer Arbeit: Vorabzustimmung fuer auslaendische Beschaeftigte explains preliminary consent.
• Bundesagentur fuer Arbeit: Fachkraefte aus dem Ausland beschaeftigen is the employer hub.
• BMAS: Beschaeftigungsverordnung overview provides regulatory context.
• BAMF: Blaue Karte EU gives official Blue Card context and refusal-ground context.
• Make it in Germany: Blaue Karte EU lists Blue Card requirements and salary thresholds. For 2026, it states EUR 50,700 gross annual salary for regular occupations and EUR 45,934.20 for shortage occupations and recent entrants. Verify current-year figures before filing.
• Make it in Germany: Visum zum Arbeiten fuer Fachkraefte explains skilled-worker routes.
• Make it in Germany: Fachkraefteeinwanderungsgesetz summary gives broader skilled-immigration context.

Direct answer

Before changing employer in Germany, review the new job as a new salary and employment-condition package. Compare old and new employer, role, salary, hours, location, contract duration, and route. Do not assume an old approval cures a lower salary, changed role, or new employer declaration. The new file should stand on its own current documents.

Fast diagnostic table

Why employer changes need a new salary review

A work permit approval is tied to facts. If those facts change, the new situation should be reviewed before the candidate relies on it. The exact legal steps depend on the status, route, timing, and conditions, but the practical content discipline is consistent: build a current package for the new job.

Salary can change in either direction. A higher salary may still need documentation if the role, hours, employer, or location changes. A lower salary may create a direct threshold or comparability concern. A different bonus mix may make assured salary weaker. A part-time arrangement may change the hourly or annual picture. The file should not reuse old calculations without checking new facts.

For Blue Card-related files, salary thresholds should be checked for the current year. For 2026, Make it in Germany states EUR 50,700 gross annual salary for regular occupations and EUR 45,934.20 for shortage occupations and recent entrants. For skilled-worker routes with BA review, the new salary and conditions should be understandable against the new role and employer.

The strongest change-of-employer package uses an old-versus-new comparison table. It shows employer, role, duties, salary, hours, location, contract duration, route, and source documents. It prevents the candidate from making a job move based on a vague assumption that the new offer is close enough.

Review module: old approval facts

The old approval facts issue should be handled as a current-facts review. A German work permit file is not strengthened by adding more narrative if the source documents still leave salary, employer identity, working time, or route logic unclear. The reviewer needs to see what the job is, who employs the person, what salary is assured, which hours apply, and which legal route is being requested.

The specific issue is the candidate assumes prior approval covers all future jobs. This matters because agency, employer-change, assignment, and transfer cases often involve more than one party. A recruiter, staffing provider, client, old employer, new employer, payroll entity, and candidate may each describe the same job differently. The filing package must turn that operational complexity into one coherent set of facts.

Useful evidence includes old approval summary and current title conditions. The evidence should be current, dated where relevant, and tied to the route. If salary is the concern, the package needs assured gross salary and hours. If employer identity is the concern, the package needs the legal employer and assignment context. If a role or employer changed, the package needs a version-controlled explanation of what changed and which documents are superseded.

The correction is identify which facts supported the old status. Correct the source documents first, then write the explanation. A cover memo should point to a contract, annex, employer declaration, salary table, or assignment note that already says the right thing. It should not be asked to repair a contradictory bundle.

The common trap is treating approval as portable without review. That trap creates avoidable refusal risk because it asks the authority to infer facts that the employer could have documented. In salary-sensitive cases, inference is weaker than evidence.

Expected result: the team understands what changed. This does not guarantee approval, but it gives the employer, candidate, and adviser a package that can be reviewed without guessing which employment condition is real.

Review module: new salary

The new salary issue should be handled as a current-facts review. A German work permit file is not strengthened by adding more narrative if the source documents still leave salary, employer identity, working time, or route logic unclear. The reviewer needs to see what the job is, who employs the person, what salary is assured, which hours apply, and which legal route is being requested.

The specific issue is new salary is not recalculated against route or comparator. This matters because agency, employer-change, assignment, and transfer cases often involve more than one party. A recruiter, staffing provider, client, old employer, new employer, payroll entity, and candidate may each describe the same job differently. The filing package must turn that operational complexity into one coherent set of facts.

Useful evidence includes new contract, salary table, hours. The evidence should be current, dated where relevant, and tied to the route. If salary is the concern, the package needs assured gross salary and hours. If employer identity is the concern, the package needs the legal employer and assignment context. If a role or employer changed, the package needs a version-controlled explanation of what changed and which documents are superseded.

The correction is test the new salary from scratch. Correct the source documents first, then write the explanation. A cover memo should point to a contract, annex, employer declaration, salary table, or assignment note that already says the right thing. It should not be asked to repair a contradictory bundle.

The common trap is reusing old salary memo. That trap creates avoidable refusal risk because it asks the authority to infer facts that the employer could have documented. In salary-sensitive cases, inference is weaker than evidence.

Expected result: new job has its own salary evidence. This does not guarantee approval, but it gives the employer, candidate, and adviser a package that can be reviewed without guessing which employment condition is real.

Review module: salary decrease

The salary decrease issue should be handled as a current-facts review. A German work permit file is not strengthened by adding more narrative if the source documents still leave salary, employer identity, working time, or route logic unclear. The reviewer needs to see what the job is, who employs the person, what salary is assured, which hours apply, and which legal route is being requested.

The specific issue is candidate accepts lower pay without route check. This matters because agency, employer-change, assignment, and transfer cases often involve more than one party. A recruiter, staffing provider, client, old employer, new employer, payroll entity, and candidate may each describe the same job differently. The filing package must turn that operational complexity into one coherent set of facts.

Useful evidence includes old/new salary comparison and route memo. The evidence should be current, dated where relevant, and tied to the route. If salary is the concern, the package needs assured gross salary and hours. If employer identity is the concern, the package needs the legal employer and assignment context. If a role or employer changed, the package needs a version-controlled explanation of what changed and which documents are superseded.

The correction is assess whether lower salary still fits. Correct the source documents first, then write the explanation. A cover memo should point to a contract, annex, employer declaration, salary table, or assignment note that already says the right thing. It should not be asked to repair a contradictory bundle.

The common trap is assuming personal willingness solves salary issue. That trap creates avoidable refusal risk because it asks the authority to infer facts that the employer could have documented. In salary-sensitive cases, inference is weaker than evidence.

Expected result: risk is visible before resignation. This does not guarantee approval, but it gives the employer, candidate, and adviser a package that can be reviewed without guessing which employment condition is real.

Review module: salary increase with role change

The salary increase with role change issue should be handled as a current-facts review. A German work permit file is not strengthened by adding more narrative if the source documents still leave salary, employer identity, working time, or route logic unclear. The reviewer needs to see what the job is, who employs the person, what salary is assured, which hours apply, and which legal route is being requested.

The specific issue is higher salary distracts from changed duties. This matters because agency, employer-change, assignment, and transfer cases often involve more than one party. A recruiter, staffing provider, client, old employer, new employer, payroll entity, and candidate may each describe the same job differently. The filing package must turn that operational complexity into one coherent set of facts.

Useful evidence includes role description and qualification map. The evidence should be current, dated where relevant, and tied to the route. If salary is the concern, the package needs assured gross salary and hours. If employer identity is the concern, the package needs the legal employer and assignment context. If a role or employer changed, the package needs a version-controlled explanation of what changed and which documents are superseded.

The correction is review role fit as well as salary. Correct the source documents first, then write the explanation. A cover memo should point to a contract, annex, employer declaration, salary table, or assignment note that already says the right thing. It should not be asked to repair a contradictory bundle.

The common trap is thinking higher pay cures every issue. That trap creates avoidable refusal risk because it asks the authority to infer facts that the employer could have documented. In salary-sensitive cases, inference is weaker than evidence.

Expected result: new job identity is coherent. This does not guarantee approval, but it gives the employer, candidate, and adviser a package that can be reviewed without guessing which employment condition is real.

Review module: new employer declaration

The new employer declaration issue should be handled as a current-facts review. A German work permit file is not strengthened by adding more narrative if the source documents still leave salary, employer identity, working time, or route logic unclear. The reviewer needs to see what the job is, who employs the person, what salary is assured, which hours apply, and which legal route is being requested.

The specific issue is old employer forms remain in bundle. This matters because agency, employer-change, assignment, and transfer cases often involve more than one party. A recruiter, staffing provider, client, old employer, new employer, payroll entity, and candidate may each describe the same job differently. The filing package must turn that operational complexity into one coherent set of facts.

Useful evidence includes new employer declaration and contract. The evidence should be current, dated where relevant, and tied to the route. If salary is the concern, the package needs assured gross salary and hours. If employer identity is the concern, the package needs the legal employer and assignment context. If a role or employer changed, the package needs a version-controlled explanation of what changed and which documents are superseded.

The correction is replace employer-specific documents. Correct the source documents first, then write the explanation. A cover memo should point to a contract, annex, employer declaration, salary table, or assignment note that already says the right thing. It should not be asked to repair a contradictory bundle.

The common trap is copying old declaration templates. That trap creates avoidable refusal risk because it asks the authority to infer facts that the employer could have documented. In salary-sensitive cases, inference is weaker than evidence.

Expected result: authority sees current employer facts. This does not guarantee approval, but it gives the employer, candidate, and adviser a package that can be reviewed without guessing which employment condition is real.

Review module: start date control

The start date control issue should be handled as a current-facts review. A German work permit file is not strengthened by adding more narrative if the source documents still leave salary, employer identity, working time, or route logic unclear. The reviewer needs to see what the job is, who employs the person, what salary is assured, which hours apply, and which legal route is being requested.

The specific issue is candidate plans to start before review path is clear. This matters because agency, employer-change, assignment, and transfer cases often involve more than one party. A recruiter, staffing provider, client, old employer, new employer, payroll entity, and candidate may each describe the same job differently. The filing package must turn that operational complexity into one coherent set of facts.

Useful evidence includes approval condition check and adviser note. The evidence should be current, dated where relevant, and tied to the route. If salary is the concern, the package needs assured gross salary and hours. If employer identity is the concern, the package needs the legal employer and assignment context. If a role or employer changed, the package needs a version-controlled explanation of what changed and which documents are superseded.

The correction is confirm timing before resignation or start. Correct the source documents first, then write the explanation. A cover memo should point to a contract, annex, employer declaration, salary table, or assignment note that already says the right thing. It should not be asked to repair a contradictory bundle.

The common trap is assuming payroll start is enough. That trap creates avoidable refusal risk because it asks the authority to infer facts that the employer could have documented. In salary-sensitive cases, inference is weaker than evidence.

Expected result: candidate avoids premature work risk. This does not guarantee approval, but it gives the employer, candidate, and adviser a package that can be reviewed without guessing which employment condition is real.

Review module: contract duration

The contract duration issue should be handled as a current-facts review. A German work permit file is not strengthened by adding more narrative if the source documents still leave salary, employer identity, working time, or route logic unclear. The reviewer needs to see what the job is, who employs the person, what salary is assured, which hours apply, and which legal route is being requested.

The specific issue is new contract is fixed-term but old job was permanent. This matters because agency, employer-change, assignment, and transfer cases often involve more than one party. A recruiter, staffing provider, client, old employer, new employer, payroll entity, and candidate may each describe the same job differently. The filing package must turn that operational complexity into one coherent set of facts.

Useful evidence includes term dates and salary exhibit. The evidence should be current, dated where relevant, and tied to the route. If salary is the concern, the package needs assured gross salary and hours. If employer identity is the concern, the package needs the legal employer and assignment context. If a role or employer changed, the package needs a version-controlled explanation of what changed and which documents are superseded.

The correction is review duration and renewal facts. Correct the source documents first, then write the explanation. A cover memo should point to a contract, annex, employer declaration, salary table, or assignment note that already says the right thing. It should not be asked to repair a contradictory bundle.

The common trap is using old permanent-role logic. That trap creates avoidable refusal risk because it asks the authority to infer facts that the employer could have documented. In salary-sensitive cases, inference is weaker than evidence.

Expected result: new contract is accurately presented. This does not guarantee approval, but it gives the employer, candidate, and adviser a package that can be reviewed without guessing which employment condition is real.

Review module: location change

The location change issue should be handled as a current-facts review. A German work permit file is not strengthened by adding more narrative if the source documents still leave salary, employer identity, working time, or route logic unclear. The reviewer needs to see what the job is, who employs the person, what salary is assured, which hours apply, and which legal route is being requested.

The specific issue is new workplace or remote pattern is not explained. This matters because agency, employer-change, assignment, and transfer cases often involve more than one party. A recruiter, staffing provider, client, old employer, new employer, payroll entity, and candidate may each describe the same job differently. The filing package must turn that operational complexity into one coherent set of facts.

Useful evidence includes workplace clause and remote map. The evidence should be current, dated where relevant, and tied to the route. If salary is the concern, the package needs assured gross salary and hours. If employer identity is the concern, the package needs the legal employer and assignment context. If a role or employer changed, the package needs a version-controlled explanation of what changed and which documents are superseded.

The correction is update location and working-condition evidence. Correct the source documents first, then write the explanation. A cover memo should point to a contract, annex, employer declaration, salary table, or assignment note that already says the right thing. It should not be asked to repair a contradictory bundle.

The common trap is assuming location is administrative. That trap creates avoidable refusal risk because it asks the authority to infer facts that the employer could have documented. In salary-sensitive cases, inference is weaker than evidence.

Expected result: new employment condition is clear. This does not guarantee approval, but it gives the employer, candidate, and adviser a package that can be reviewed without guessing which employment condition is real.

Review module: route change

The route change issue should be handled as a current-facts review. A German work permit file is not strengthened by adding more narrative if the source documents still leave salary, employer identity, working time, or route logic unclear. The reviewer needs to see what the job is, who employs the person, what salary is assured, which hours apply, and which legal route is being requested.

The specific issue is new job fits a different route better. This matters because agency, employer-change, assignment, and transfer cases often involve more than one party. A recruiter, staffing provider, client, old employer, new employer, payroll entity, and candidate may each describe the same job differently. The filing package must turn that operational complexity into one coherent set of facts.

Useful evidence includes route comparison memo. The evidence should be current, dated where relevant, and tied to the route. If salary is the concern, the package needs assured gross salary and hours. If employer identity is the concern, the package needs the legal employer and assignment context. If a role or employer changed, the package needs a version-controlled explanation of what changed and which documents are superseded.

The correction is choose route based on current facts. Correct the source documents first, then write the explanation. A cover memo should point to a contract, annex, employer declaration, salary table, or assignment note that already says the right thing. It should not be asked to repair a contradictory bundle.

The common trap is forcing old route onto new job. That trap creates avoidable refusal risk because it asks the authority to infer facts that the employer could have documented. In salary-sensitive cases, inference is weaker than evidence.

Expected result: strategy fits the new offer. This does not guarantee approval, but it gives the employer, candidate, and adviser a package that can be reviewed without guessing which employment condition is real.

Review module: candidate negotiation

The candidate negotiation issue should be handled as a current-facts review. A German work permit file is not strengthened by adding more narrative if the source documents still leave salary, employer identity, working time, or route logic unclear. The reviewer needs to see what the job is, who employs the person, what salary is assured, which hours apply, and which legal route is being requested.

The specific issue is candidate negotiates salary without immigration floor. This matters because agency, employer-change, assignment, and transfer cases often involve more than one party. A recruiter, staffing provider, client, old employer, new employer, payroll entity, and candidate may each describe the same job differently. The filing package must turn that operational complexity into one coherent set of facts.

Useful evidence includes pre-offer salary check. The evidence should be current, dated where relevant, and tied to the route. If salary is the concern, the package needs assured gross salary and hours. If employer identity is the concern, the package needs the legal employer and assignment context. If a role or employer changed, the package needs a version-controlled explanation of what changed and which documents are superseded.

The correction is check route before signing. Correct the source documents first, then write the explanation. A cover memo should point to a contract, annex, employer declaration, salary table, or assignment note that already says the right thing. It should not be asked to repair a contradictory bundle.

The common trap is discovering issue after resignation. That trap creates avoidable refusal risk because it asks the authority to infer facts that the employer could have documented. In salary-sensitive cases, inference is weaker than evidence.

Expected result: offer can be corrected early. This does not guarantee approval, but it gives the employer, candidate, and adviser a package that can be reviewed without guessing which employment condition is real.

Review module: refusal response

The refusal response issue should be handled as a current-facts review. A German work permit file is not strengthened by adding more narrative if the source documents still leave salary, employer identity, working time, or route logic unclear. The reviewer needs to see what the job is, who employs the person, what salary is assured, which hours apply, and which legal route is being requested.

The specific issue is response says candidate was already approved before. This matters because agency, employer-change, assignment, and transfer cases often involve more than one party. A recruiter, staffing provider, client, old employer, new employer, payroll entity, and candidate may each describe the same job differently. The filing package must turn that operational complexity into one coherent set of facts.

Useful evidence includes new job evidence and concern table. The evidence should be current, dated where relevant, and tied to the route. If salary is the concern, the package needs assured gross salary and hours. If employer identity is the concern, the package needs the legal employer and assignment context. If a role or employer changed, the package needs a version-controlled explanation of what changed and which documents are superseded.

The correction is answer the new employment condition. Correct the source documents first, then write the explanation. A cover memo should point to a contract, annex, employer declaration, salary table, or assignment note that already says the right thing. It should not be asked to repair a contradictory bundle.

The common trap is old approval used as main argument. That trap creates avoidable refusal risk because it asks the authority to infer facts that the employer could have documented. In salary-sensitive cases, inference is weaker than evidence.

Expected result: refile focuses on current job. This does not guarantee approval, but it gives the employer, candidate, and adviser a package that can be reviewed without guessing which employment condition is real.

Review module: handover between employers

The handover between employers issue should be handled as a current-facts review. A German work permit file is not strengthened by adding more narrative if the source documents still leave salary, employer identity, working time, or route logic unclear. The reviewer needs to see what the job is, who employs the person, what salary is assured, which hours apply, and which legal route is being requested.

The specific issue is old and new employers provide inconsistent information. This matters because agency, employer-change, assignment, and transfer cases often involve more than one party. A recruiter, staffing provider, client, old employer, new employer, payroll entity, and candidate may each describe the same job differently. The filing package must turn that operational complexity into one coherent set of facts.

Useful evidence includes single new package owner. The evidence should be current, dated where relevant, and tied to the route. If salary is the concern, the package needs assured gross salary and hours. If employer identity is the concern, the package needs the legal employer and assignment context. If a role or employer changed, the package needs a version-controlled explanation of what changed and which documents are superseded.

The correction is keep old employer context separate. Correct the source documents first, then write the explanation. A cover memo should point to a contract, annex, employer declaration, salary table, or assignment note that already says the right thing. It should not be asked to repair a contradictory bundle.

The common trap is mixing old and new facts. That trap creates avoidable refusal risk because it asks the authority to infer facts that the employer could have documented. In salary-sensitive cases, inference is weaker than evidence.

Expected result: current bundle is not contaminated. This does not guarantee approval, but it gives the employer, candidate, and adviser a package that can be reviewed without guessing which employment condition is real.

Operating note: candidate owner

Owner: candidate plus adviser. Required output: old-versus-new job table. Treat this output as part of the filing package, even if it is used internally to prepare a shorter authority-facing memo.

Risk: candidate resigns before route check. The risk usually appears when business teams move faster than document control. The fix is not slower hiring; it is clearer version control and better salary evidence.

Final check: if an outside reviewer reads only the current documents, can they identify employer, role, salary, hours, route, and assignment status? If not, the package needs another pass.

Operating note: new employer owner

Owner: new HR sponsor. Required output: new salary and declaration pack. Treat this output as part of the filing package, even if it is used internally to prepare a shorter authority-facing memo.

Risk: old employer assumptions are reused. The risk usually appears when business teams move faster than document control. The fix is not slower hiring; it is clearer version control and better salary evidence.

Final check: if an outside reviewer reads only the current documents, can they identify employer, role, salary, hours, route, and assignment status? If not, the package needs another pass.

Operating note: salary owner

Owner: new compensation team. Required output: gross salary and hours calculation. Treat this output as part of the filing package, even if it is used internally to prepare a shorter authority-facing memo.

Risk: bonus mix weakens assured salary. The risk usually appears when business teams move faster than document control. The fix is not slower hiring; it is clearer version control and better salary evidence.

Final check: if an outside reviewer reads only the current documents, can they identify employer, role, salary, hours, route, and assignment status? If not, the package needs another pass.

Operating note: route owner

Owner: filing adviser. Required output: current-facts route memo. Treat this output as part of the filing package, even if it is used internally to prepare a shorter authority-facing memo.

Risk: old route is forced onto new job. The risk usually appears when business teams move faster than document control. The fix is not slower hiring; it is clearer version control and better salary evidence.

Final check: if an outside reviewer reads only the current documents, can they identify employer, role, salary, hours, route, and assignment status? If not, the package needs another pass.

Operating note: timing owner

Owner: case coordinator. Required output: start-date and approval-path checklist. Treat this output as part of the filing package, even if it is used internally to prepare a shorter authority-facing memo.

Risk: candidate starts too early. The risk usually appears when business teams move faster than document control. The fix is not slower hiring; it is clearer version control and better salary evidence.

Final check: if an outside reviewer reads only the current documents, can they identify employer, role, salary, hours, route, and assignment status? If not, the package needs another pass.

Operating note: role owner

Owner: new hiring manager. Required output: role and qualification map. Treat this output as part of the filing package, even if it is used internally to prepare a shorter authority-facing memo.

Risk: new duties are underdocumented. The risk usually appears when business teams move faster than document control. The fix is not slower hiring; it is clearer version control and better salary evidence.

Final check: if an outside reviewer reads only the current documents, can they identify employer, role, salary, hours, route, and assignment status? If not, the package needs another pass.

Operating note: version owner

Owner: case coordinator. Required output: new current bundle and old-doc separation. Treat this output as part of the filing package, even if it is used internally to prepare a shorter authority-facing memo.

Risk: old documents confuse current facts. The risk usually appears when business teams move faster than document control. The fix is not slower hiring; it is clearer version control and better salary evidence.

Final check: if an outside reviewer reads only the current documents, can they identify employer, role, salary, hours, route, and assignment status? If not, the package needs another pass.

Operating note: refile owner

Owner: response lead. Required output: new-job correction table. Treat this output as part of the filing package, even if it is used internally to prepare a shorter authority-facing memo.

Risk: response relies on prior approval. The risk usually appears when business teams move faster than document control. The fix is not slower hiring; it is clearer version control and better salary evidence.

Final check: if an outside reviewer reads only the current documents, can they identify employer, role, salary, hours, route, and assignment status? If not, the package needs another pass.

Template language for an old-versus-new comparison

Use this as a drafting prompt, not as legal advice:

Prior employer/role/salary: [summary]. New employer: [entity]. New role: [title and duties]. New assured gross salary: EUR [amount] per year for [hours] hours per week. Contract term and work location: [details]. Route review: [Blue Card threshold checked on date / skilled-worker comparable-condition evidence attached]. Old documents not relied on for new salary except as background.

Practical correction roadmap

First, list old facts and new facts separately. Do not blend them.

Second, test the new salary and hours before signing or resigning where possible.

Third, build a new employer declaration and role package. Employer-specific documents should come from the new employer.

Fourth, check timing. The candidate should understand whether approval, notification, or another step is needed before starting.

Fifth, if refused or questioned, answer the new job concern directly. Prior approval may provide background, but it does not prove new salary compliance.

Practical FAQ

Can a candidate rely on the old salary approval? Not without checking the current status and new job facts. Old approval was based on old documents.

Is a higher salary Usually safe? Higher salary helps, but role, hours, employer, location, and route still need review.

What if the new job pays less but is better for career growth? Career growth is not a substitute for route salary or comparable-condition evidence.

What should be checked before resignation? New salary, route, timing, employer declaration, contract duration, and start permission path.

Final audit before filing

Remove old employer documents from the current filing unless they are intentionally used as background and clearly labeled. The current package should prove the new job on its own.

Minimum evidence checklist

The minimum change-of-employer package should include the new employment contract, new employer declaration, new salary table, weekly-hours clause, new role description, work-location note, route memo, and old-versus-new comparison table. If the candidate has prior approval documents, keep them separate from the new job proof unless an adviser decides they are needed as background.

The salary table should show the new assured gross annual salary, not the old salary, old threshold memo, or recruiter comparison. If the salary is lower than the previous job, the file should explain the new role and route logic rather than pretending nothing material changed.

The timing checklist should identify resignation date, intended start date, appointment or notification path, and owner for confirming when work may begin. A salary-compliant offer can still create risk if the candidate starts before the relevant process is clear.

Example correction scenarios

Scenario one: the old job paid more, and the new job offers better career growth but lower salary. Build a new salary and comparator file. Do not use career growth as the main answer to an employment-condition concern.

Scenario two: the new employer uses a different title for similar duties. Add a role map showing what is actually changing. If duties are materially different, recheck qualification fit and route logic.

Scenario three: the candidate has already resigned before the salary issue is found. Move quickly, but do not improvise. Correct the new contract, employer declaration, and salary table before sending a response.

If the new package still depends on old employer documents to look compliant, the package is not ready. Prior approval can provide background, but the new employer's salary and conditions must stand on their own.

Before the candidate accepts, run one final practical test: would the new job be defensible if the old approval were unavailable? If not, the employer should improve the new documents, not lean on the old case history.

Also prepare the candidate for simple questions. They should know the new employer name, new title, new salary, new hours, and whether the role is a continuation or a genuine change. Consistent answers prevent avoidable confusion.

Practical next step

Create an old-versus-new employer table before accepting a salary-sensitive job change. If salary, hours, route, and start timing are unclear, pause before relying on the new offer.

For borderline moves, ask the new employer to fix the salary evidence before resignation, not after. That timing protects the candidate from discovering a permit problem only after the old job is already gone.

Internal links for the cluster

• Fixed-term contracts, salary, duration, and renewal
• Side income and salary refusal
• EOR, agency, and client-site offers
• Offer changes, salary cuts, and reduced hours
• Salary comparability without a Tarifvertrag
• Job description, degree match, and salary comparability
• Response letters and contract language templates
• Post-refusal recovery roadmap