guide

Last updated June 25, 2026

Germany Work Permit Fixed-Term Contracts: Salary, Duration, Renewal Promises, and BA Evidence

Germany Work Permit Fixed-Term Contracts: Salary, Duration, Renewal Promises, and BA Evidence brings the main checks together so you can see the issue, the evidence, and the safer next step in one place. It explains understanding the visa, residence, work-permit, renewal, and refusal issues behind Germany Work Permit Fixed-Term Contracts: Salary, Duration, Renewal Promises, and BA Evidence, 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 fixed-term contracts need salary discipline 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 handle fixed-term contracts, project contracts, renewal promises, annualized salary, probation, and contract extension language in German work permit and Blue Card files. It is written for candidates, HR teams, project employers, startups, universities, consultancies, 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

For a fixed-term German work permit file, show the contract duration, assured gross salary, weekly hours, role, route, renewal status, and whether salary is annualized or paid only for the fixed term. Do not use an expected renewal or conversion to permanent employment as current evidence unless it is contractually documented and route-relevant.

Fast diagnostic table

Why fixed-term contracts need salary discipline

A fixed-term contract can be perfectly legitimate, but the filing package must not pretend that it is an indefinite contract if it is not. Salary, duration, renewal, and role must be presented together. If the file cites an annual salary but the contract lasts six months, the reviewer should not have to guess whether the annualized figure is route evidence, payroll shorthand, or a future assumption.

For Blue Card files, the gross annual salary threshold still matters and the official current-year source should be checked. For 2026, Make it in Germany states EUR 50,700 for regular occupations and EUR 45,934.20 for shortage occupations and recent entrants. If the contract is fixed-term, the package should be especially clear about the salary basis being used and how it is assured during the contract.

For skilled-worker routes with BA review, duration can interact with employment conditions, project reality, and comparability. The question is not merely whether the candidate is useful for the project. The question is whether the documented employment conditions for the actual contract make sense for the role being approved.

The strongest package uses a fixed-term salary exhibit. It shows start date, end date, gross monthly salary, gross annualized salary if relevant, weekly hours, role, route, renewal status, and documents superseded. It keeps expected renewal separate from assured current employment.

Review module: contract duration

The contract duration question should be handled as a filing-fact issue, not as a general career narrative. A German work permit file is evaluated through current documents: contract, salary, hours, employer declaration, role description, route evidence, and any comparator or threshold calculation. If the package makes the reviewer infer which fact is current, it is weaker than it needs to be.

The practical issue is the file highlights salary but hides the end date. This matters because salary-sensitive cases often fail through ambiguity rather than through an obviously impossible job. A candidate may have a reasonable explanation, and an employer may have a genuine business reason, but the authority still needs the current employment condition in a verifiable form.

Useful evidence includes contract start date, end date, and term summary. The evidence should separate assured salary from context, current conditions from future changes, and primary employment from any secondary arrangement. Where the file relies on a route threshold or comparable-condition review, the calculation should be visible and source-checked.

The correction is put duration in the salary exhibit. Correct source documents first, then explain them. If the contract, employer declaration, and memo disagree, the file is not ready. A cover letter should point to corrected documents, not repair contradictions that remain in those documents.

The common trap is annualizing salary without stating the fixed term. That trap creates unnecessary risk because it asks the authority to solve the employer's internal documentation problem. A clean package says what counts, what does not count, and who is responsible for each fact.

Expected result: reviewer understands the actual employment period. This does not guarantee approval, but it creates a package that can be reviewed, escalated, corrected, or refiled without rebuilding the case from scattered emails.

Review module: annualized salary

The annualized salary question should be handled as a filing-fact issue, not as a general career narrative. A German work permit file is evaluated through current documents: contract, salary, hours, employer declaration, role description, route evidence, and any comparator or threshold calculation. If the package makes the reviewer infer which fact is current, it is weaker than it needs to be.

The practical issue is annual salary is used without explaining payment period. This matters because salary-sensitive cases often fail through ambiguity rather than through an obviously impossible job. A candidate may have a reasonable explanation, and an employer may have a genuine business reason, but the authority still needs the current employment condition in a verifiable form.

Useful evidence includes monthly gross, payment count, annualized figure, contract duration. The evidence should separate assured salary from context, current conditions from future changes, and primary employment from any secondary arrangement. Where the file relies on a route threshold or comparable-condition review, the calculation should be visible and source-checked.

The correction is show arithmetic and label annualization. Correct source documents first, then explain them. If the contract, employer declaration, and memo disagree, the file is not ready. A cover letter should point to corrected documents, not repair contradictions that remain in those documents.

The common trap is using an annual number to mask a short paid term. That trap creates unnecessary risk because it asks the authority to solve the employer's internal documentation problem. A clean package says what counts, what does not count, and who is responsible for each fact.

Expected result: threshold discussion is transparent. This does not guarantee approval, but it creates a package that can be reviewed, escalated, corrected, or refiled without rebuilding the case from scattered emails.

Review module: renewal promise

The renewal promise question should be handled as a filing-fact issue, not as a general career narrative. A German work permit file is evaluated through current documents: contract, salary, hours, employer declaration, role description, route evidence, and any comparator or threshold calculation. If the package makes the reviewer infer which fact is current, it is weaker than it needs to be.

The practical issue is extension is expected but not documented. This matters because salary-sensitive cases often fail through ambiguity rather than through an obviously impossible job. A candidate may have a reasonable explanation, and an employer may have a genuine business reason, but the authority still needs the current employment condition in a verifiable form.

Useful evidence includes renewal clause or no-guarantee statement. The evidence should separate assured salary from context, current conditions from future changes, and primary employment from any secondary arrangement. Where the file relies on a route threshold or comparable-condition review, the calculation should be visible and source-checked.

The correction is label renewal as assured, conditional, or expected. Correct source documents first, then explain them. If the contract, employer declaration, and memo disagree, the file is not ready. A cover letter should point to corrected documents, not repair contradictions that remain in those documents.

The common trap is using expected renewal as current evidence. That trap creates unnecessary risk because it asks the authority to solve the employer's internal documentation problem. A clean package says what counts, what does not count, and who is responsible for each fact.

Expected result: future context no longer contaminates current facts. This does not guarantee approval, but it creates a package that can be reviewed, escalated, corrected, or refiled without rebuilding the case from scattered emails.

Review module: project-based role

The project-based role question should be handled as a filing-fact issue, not as a general career narrative. A German work permit file is evaluated through current documents: contract, salary, hours, employer declaration, role description, route evidence, and any comparator or threshold calculation. If the package makes the reviewer infer which fact is current, it is weaker than it needs to be.

The practical issue is project need is described but employment conditions are vague. This matters because salary-sensitive cases often fail through ambiguity rather than through an obviously impossible job. A candidate may have a reasonable explanation, and an employer may have a genuine business reason, but the authority still needs the current employment condition in a verifiable form.

Useful evidence includes project note, role description, salary table. The evidence should separate assured salary from context, current conditions from future changes, and primary employment from any secondary arrangement. Where the file relies on a route threshold or comparable-condition review, the calculation should be visible and source-checked.

The correction is connect project term to current job and salary. Correct source documents first, then explain them. If the contract, employer declaration, and memo disagree, the file is not ready. A cover letter should point to corrected documents, not repair contradictions that remain in those documents.

The common trap is sending client/project context instead of employment evidence. That trap creates unnecessary risk because it asks the authority to solve the employer's internal documentation problem. A clean package says what counts, what does not count, and who is responsible for each fact.

Expected result: project reality supports rather than replaces the contract. This does not guarantee approval, but it creates a package that can be reviewed, escalated, corrected, or refiled without rebuilding the case from scattered emails.

Review module: fixed-term probation

The fixed-term probation question should be handled as a filing-fact issue, not as a general career narrative. A German work permit file is evaluated through current documents: contract, salary, hours, employer declaration, role description, route evidence, and any comparator or threshold calculation. If the package makes the reviewer infer which fact is current, it is weaker than it needs to be.

The practical issue is probation consumes much of the contract. This matters because salary-sensitive cases often fail through ambiguity rather than through an obviously impossible job. A candidate may have a reasonable explanation, and an employer may have a genuine business reason, but the authority still needs the current employment condition in a verifiable form.

Useful evidence includes probation clause and salary timeline. The evidence should separate assured salary from context, current conditions from future changes, and primary employment from any secondary arrangement. Where the file relies on a route threshold or comparable-condition review, the calculation should be visible and source-checked.

The correction is show whether pay changes during the term. Correct source documents first, then explain them. If the contract, employer declaration, and memo disagree, the file is not ready. A cover letter should point to corrected documents, not repair contradictions that remain in those documents.

The common trap is treating probation as a minor detail in a short contract. That trap creates unnecessary risk because it asks the authority to solve the employer's internal documentation problem. A clean package says what counts, what does not count, and who is responsible for each fact.

Expected result: salary during the real term is visible. This does not guarantee approval, but it creates a package that can be reviewed, escalated, corrected, or refiled without rebuilding the case from scattered emails.

Review module: conversion to permanent

The conversion to permanent question should be handled as a filing-fact issue, not as a general career narrative. A German work permit file is evaluated through current documents: contract, salary, hours, employer declaration, role description, route evidence, and any comparator or threshold calculation. If the package makes the reviewer infer which fact is current, it is weaker than it needs to be.

The practical issue is conversion is used to make file look stronger. This matters because salary-sensitive cases often fail through ambiguity rather than through an obviously impossible job. A candidate may have a reasonable explanation, and an employer may have a genuine business reason, but the authority still needs the current employment condition in a verifiable form.

Useful evidence includes conversion trigger and current contract terms. The evidence should separate assured salary from context, current conditions from future changes, and primary employment from any secondary arrangement. Where the file relies on a route threshold or comparable-condition review, the calculation should be visible and source-checked.

The correction is separate current fixed-term contract from future conversion. Correct source documents first, then explain them. If the contract, employer declaration, and memo disagree, the file is not ready. A cover letter should point to corrected documents, not repair contradictions that remain in those documents.

The common trap is describing future indefinite job as current job. That trap creates unnecessary risk because it asks the authority to solve the employer's internal documentation problem. A clean package says what counts, what does not count, and who is responsible for each fact.

Expected result: current approval facts stay honest. This does not guarantee approval, but it creates a package that can be reviewed, escalated, corrected, or refiled without rebuilding the case from scattered emails.

Review module: university or research term

The university or research term question should be handled as a filing-fact issue, not as a general career narrative. A German work permit file is evaluated through current documents: contract, salary, hours, employer declaration, role description, route evidence, and any comparator or threshold calculation. If the package makes the reviewer infer which fact is current, it is weaker than it needs to be.

The practical issue is grant or project end date is not reconciled. This matters because salary-sensitive cases often fail through ambiguity rather than through an obviously impossible job. A candidate may have a reasonable explanation, and an employer may have a genuine business reason, but the authority still needs the current employment condition in a verifiable form.

Useful evidence includes grant term, contract, salary, role evidence. The evidence should separate assured salary from context, current conditions from future changes, and primary employment from any secondary arrangement. Where the file relies on a route threshold or comparable-condition review, the calculation should be visible and source-checked.

The correction is align funding context with employment terms. Correct source documents first, then explain them. If the contract, employer declaration, and memo disagree, the file is not ready. A cover letter should point to corrected documents, not repair contradictions that remain in those documents.

The common trap is assuming academic context explains salary automatically. That trap creates unnecessary risk because it asks the authority to solve the employer's internal documentation problem. A clean package says what counts, what does not count, and who is responsible for each fact.

Expected result: fixed research roles are easier to review. This does not guarantee approval, but it creates a package that can be reviewed, escalated, corrected, or refiled without rebuilding the case from scattered emails.

Review module: consultancy assignment term

The consultancy assignment term question should be handled as a filing-fact issue, not as a general career narrative. A German work permit file is evaluated through current documents: contract, salary, hours, employer declaration, role description, route evidence, and any comparator or threshold calculation. If the package makes the reviewer infer which fact is current, it is weaker than it needs to be.

The practical issue is client project duration drives contract but is not explained. This matters because salary-sensitive cases often fail through ambiguity rather than through an obviously impossible job. A candidate may have a reasonable explanation, and an employer may have a genuine business reason, but the authority still needs the current employment condition in a verifiable form.

Useful evidence includes assignment note and employer identity map. The evidence should separate assured salary from context, current conditions from future changes, and primary employment from any secondary arrangement. Where the file relies on a route threshold or comparable-condition review, the calculation should be visible and source-checked.

The correction is show legal employer and contract term. Correct source documents first, then explain them. If the contract, employer declaration, and memo disagree, the file is not ready. A cover letter should point to corrected documents, not repair contradictions that remain in those documents.

The common trap is client statement replaces employer contract facts. That trap creates unnecessary risk because it asks the authority to solve the employer's internal documentation problem. A clean package says what counts, what does not count, and who is responsible for each fact.

Expected result: employment relationship remains central. This does not guarantee approval, but it creates a package that can be reviewed, escalated, corrected, or refiled without rebuilding the case from scattered emails.

Review module: route recheck

The route recheck question should be handled as a filing-fact issue, not as a general career narrative. A German work permit file is evaluated through current documents: contract, salary, hours, employer declaration, role description, route evidence, and any comparator or threshold calculation. If the package makes the reviewer infer which fact is current, it is weaker than it needs to be.

The practical issue is route chosen as if contract were indefinite. This matters because salary-sensitive cases often fail through ambiguity rather than through an obviously impossible job. A candidate may have a reasonable explanation, and an employer may have a genuine business reason, but the authority still needs the current employment condition in a verifiable form.

Useful evidence includes route memo using current term and salary. The evidence should separate assured salary from context, current conditions from future changes, and primary employment from any secondary arrangement. Where the file relies on a route threshold or comparable-condition review, the calculation should be visible and source-checked.

The correction is retest route with fixed-term facts. Correct source documents first, then explain them. If the contract, employer declaration, and memo disagree, the file is not ready. A cover letter should point to corrected documents, not repair contradictions that remain in those documents.

The common trap is copying a permanent-role memo. That trap creates unnecessary risk because it asks the authority to solve the employer's internal documentation problem. A clean package says what counts, what does not count, and who is responsible for each fact.

Expected result: strategy matches documents. This does not guarantee approval, but it creates a package that can be reviewed, escalated, corrected, or refiled without rebuilding the case from scattered emails.

Review module: candidate appointment pack

The candidate appointment pack question should be handled as a filing-fact issue, not as a general career narrative. A German work permit file is evaluated through current documents: contract, salary, hours, employer declaration, role description, route evidence, and any comparator or threshold calculation. If the package makes the reviewer infer which fact is current, it is weaker than it needs to be.

The practical issue is candidate carries old permanent offer. This matters because salary-sensitive cases often fail through ambiguity rather than through an obviously impossible job. A candidate may have a reasonable explanation, and an employer may have a genuine business reason, but the authority still needs the current employment condition in a verifiable form.

Useful evidence includes final bundle and superseded list. The evidence should separate assured salary from context, current conditions from future changes, and primary employment from any secondary arrangement. Where the file relies on a route threshold or comparable-condition review, the calculation should be visible and source-checked.

The correction is remove or label superseded documents. Correct source documents first, then explain them. If the contract, employer declaration, and memo disagree, the file is not ready. A cover letter should point to corrected documents, not repair contradictions that remain in those documents.

The common trap is old offer contradicts fixed-term contract. That trap creates unnecessary risk because it asks the authority to solve the employer's internal documentation problem. A clean package says what counts, what does not count, and who is responsible for each fact.

Expected result: appointment answers match package. This does not guarantee approval, but it creates a package that can be reviewed, escalated, corrected, or refiled without rebuilding the case from scattered emails.

Review module: refusal response

The refusal response question should be handled as a filing-fact issue, not as a general career narrative. A German work permit file is evaluated through current documents: contract, salary, hours, employer declaration, role description, route evidence, and any comparator or threshold calculation. If the package makes the reviewer infer which fact is current, it is weaker than it needs to be.

The practical issue is response argues renewal probability after salary concern. This matters because salary-sensitive cases often fail through ambiguity rather than through an obviously impossible job. A candidate may have a reasonable explanation, and an employer may have a genuine business reason, but the authority still needs the current employment condition in a verifiable form.

Useful evidence includes refusal phrase, term exhibit, corrected salary table. The evidence should separate assured salary from context, current conditions from future changes, and primary employment from any secondary arrangement. Where the file relies on a route threshold or comparable-condition review, the calculation should be visible and source-checked.

The correction is answer current term and salary directly. Correct source documents first, then explain them. If the contract, employer declaration, and memo disagree, the file is not ready. A cover letter should point to corrected documents, not repair contradictions that remain in those documents.

The common trap is defending future renewal instead of current evidence. That trap creates unnecessary risk because it asks the authority to solve the employer's internal documentation problem. A clean package says what counts, what does not count, and who is responsible for each fact.

Expected result: refile addresses the actual contract. This does not guarantee approval, but it creates a package that can be reviewed, escalated, corrected, or refiled without rebuilding the case from scattered emails.

Review module: employer declaration

The employer declaration question should be handled as a filing-fact issue, not as a general career narrative. A German work permit file is evaluated through current documents: contract, salary, hours, employer declaration, role description, route evidence, and any comparator or threshold calculation. If the package makes the reviewer infer which fact is current, it is weaker than it needs to be.

The practical issue is declaration omits fixed term or uses different dates. This matters because salary-sensitive cases often fail through ambiguity rather than through an obviously impossible job. A candidate may have a reasonable explanation, and an employer may have a genuine business reason, but the authority still needs the current employment condition in a verifiable form.

Useful evidence includes revised declaration and contract cross-check. The evidence should separate assured salary from context, current conditions from future changes, and primary employment from any secondary arrangement. Where the file relies on a route threshold or comparable-condition review, the calculation should be visible and source-checked.

The correction is make forms match the contract. Correct source documents first, then explain them. If the contract, employer declaration, and memo disagree, the file is not ready. A cover letter should point to corrected documents, not repair contradictions that remain in those documents.

The common trap is date mismatch across documents. That trap creates unnecessary risk because it asks the authority to solve the employer's internal documentation problem. A clean package says what counts, what does not count, and who is responsible for each fact.

Expected result: authority-facing documents align. This does not guarantee approval, but it creates a package that can be reviewed, escalated, corrected, or refiled without rebuilding the case from scattered emails.

Operating note: term owner

Owner: HR operations. Required output: start/end date and renewal-status table. This output should be treated as part of the filing discipline, not optional internal housekeeping.

Risk: duration is less visible in attachments. The risk usually appears when teams try to move quickly after an offer, refusal, or appointment deadline. Fast filings still need one source of truth for salary, hours, route, employer, and document version.

Final check: could a reader who knows nothing about the case identify the salary being relied on and the employment condition being approved? If not, the package needs another correction pass.

Operating note: salary owner

Owner: payroll or compensation. Required output: monthly and annualized gross salary calculation. This output should be treated as part of the filing discipline, not optional internal housekeeping.

Risk: salary basis is ambiguous. The risk usually appears when teams try to move quickly after an offer, refusal, or appointment deadline. Fast filings still need one source of truth for salary, hours, route, employer, and document version.

Final check: could a reader who knows nothing about the case identify the salary being relied on and the employment condition being approved? If not, the package needs another correction pass.

Operating note: route owner

Owner: filing adviser. Required output: fixed-term route memo. This output should be treated as part of the filing discipline, not optional internal housekeeping.

Risk: permanent-role logic is reused. The risk usually appears when teams try to move quickly after an offer, refusal, or appointment deadline. Fast filings still need one source of truth for salary, hours, route, employer, and document version.

Final check: could a reader who knows nothing about the case identify the salary being relied on and the employment condition being approved? If not, the package needs another correction pass.

Operating note: project owner

Owner: hiring manager. Required output: project role and duration confirmation. This output should be treated as part of the filing discipline, not optional internal housekeeping.

Risk: project facts conflict with contract facts. The risk usually appears when teams try to move quickly after an offer, refusal, or appointment deadline. Fast filings still need one source of truth for salary, hours, route, employer, and document version.

Final check: could a reader who knows nothing about the case identify the salary being relied on and the employment condition being approved? If not, the package needs another correction pass.

Operating note: candidate owner

Owner: relocation contact. Required output: appointment fact sheet. This output should be treated as part of the filing discipline, not optional internal housekeeping.

Risk: candidate mentions expected renewal as if assured. The risk usually appears when teams try to move quickly after an offer, refusal, or appointment deadline. Fast filings still need one source of truth for salary, hours, route, employer, and document version.

Final check: could a reader who knows nothing about the case identify the salary being relied on and the employment condition being approved? If not, the package needs another correction pass.

Operating note: version owner

Owner: case coordinator. Required output: superseded permanent-offer list. This output should be treated as part of the filing discipline, not optional internal housekeeping.

Risk: old offer remains in the bundle. The risk usually appears when teams try to move quickly after an offer, refusal, or appointment deadline. Fast filings still need one source of truth for salary, hours, route, employer, and document version.

Final check: could a reader who knows nothing about the case identify the salary being relied on and the employment condition being approved? If not, the package needs another correction pass.

Operating note: refile owner

Owner: response lead. Required output: concern-to-correction table. This output should be treated as part of the filing discipline, not optional internal housekeeping.

Risk: response argues future extension instead of current salary. The risk usually appears when teams try to move quickly after an offer, refusal, or appointment deadline. Fast filings still need one source of truth for salary, hours, route, employer, and document version.

Final check: could a reader who knows nothing about the case identify the salary being relied on and the employment condition being approved? If not, the package needs another correction pass.

Operating note: declaration owner

Owner: HR sponsor. Required output: declaration matching term and salary. This output should be treated as part of the filing discipline, not optional internal housekeeping.

Risk: forms show different dates. The risk usually appears when teams try to move quickly after an offer, refusal, or appointment deadline. Fast filings still need one source of truth for salary, hours, route, employer, and document version.

Final check: could a reader who knows nothing about the case identify the salary being relied on and the employment condition being approved? If not, the package needs another correction pass.

Template language for a fixed-term salary exhibit

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

Contract term: [start date] to [end date]. assured gross salary: EUR [monthly amount] per month, equivalent to EUR [annualized amount] per year if annualized. Weekly hours: [hours]. Renewal status: [not assured / conditional / automatic under clause]. Route relevance: [Blue Card threshold checked on date / skilled-worker comparable-condition evidence attached]. Superseded documents: [list].

Practical correction roadmap

First, make duration visible. If the contract is fixed-term, the term belongs in the filing summary.

Second, explain salary arithmetic. Annualized salary should not obscure how much is actually assured during the contract period.

Third, separate renewal from current evidence. Expected renewal may be context, but current documents carry the filing.

Fourth, recheck route fit. A short contract, reduced hours, or project role can change how the file should be explained.

Fifth, brief the candidate. They should not describe a fixed-term contract as permanent unless the documents support that.

Final audit before filing

Read the contract, employer declaration, salary exhibit, and cover memo together. The same start date, end date, salary, hours, and renewal status should appear in all of them. If not, correct the source documents before filing.

Practical FAQ for fixed-term salary files

Can a fixed-term contract support a German work permit? It can be possible, but the file must be honest about the term, salary, role, and route. Do not make a short contract look permanent by hiding the end date.

Can an expected renewal be counted as part of the current offer? Treat it as future context unless it is contractually documented and relevant to the route. A manager's expectation is not the same as a binding renewal clause.

Should the salary be shown as monthly or annual? Show both if annualization is used. The monthly gross salary proves what will be paid; the annualized figure can help threshold or comparator analysis when appropriate. The file should explain the arithmetic.

What if the project is funded for only six months? State that fact and connect it to the contract. If the employer expects more funding, label it separately. Do not let funding optimism replace current employment evidence.

What usually causes refusal risk? The common pattern is an old permanent offer, a new fixed-term contract, a salary table using annual figures, and an employer declaration that does not match either one. Version control prevents that.

Minimum evidence checklist

The fixed-term package should include the contract, term dates, salary table, working-time clause, role description, employer declaration, route memo, and renewal-status note. If there was an earlier permanent offer, include a superseded-document control internally and avoid uploading contradictory old documents unless specifically required or explained.

For salary, show monthly gross, assured payment frequency, annualized figure if used, and the total assured value over the contract term. The reviewer should not have to calculate whether the stated annual amount is a real annual obligation or a shorthand for a shorter period.

For route fit, show whether the route analysis depends on annual gross salary, comparable conditions, or both. If the route memo was originally drafted for a permanent role, rewrite it. Fixed-term facts deserve their own route explanation.

Example correction scenarios

Scenario one: the offer letter promised an indefinite role, but the signed contract is twelve months. Remove the old offer from the current appointment bundle or mark it as superseded. Update the employer declaration to match the signed contract.

Scenario two: the salary is shown as EUR 54,000 per year, but the contract is six months. Add a salary table showing monthly gross pay, annualized gross pay if relevant, and the assured salary over the actual term. That table prevents a misunderstanding about what is truly assured.

Scenario three: renewal is likely because the project normally extends. Put likely renewal in context, not in the current salary proof. If renewal is legally assured under a clause, cite the clause and explain the trigger.

Filing discipline for short contracts

Short contracts deserve extra discipline because small wording differences become material. A six-month contract with a clear monthly salary, clear hours, clear project role, and clear renewal status is easier to review than a twelve-month file that mixes annual salary language, old permanent-offer promises, and vague extension assumptions.

Before submission, ask whether the package would still make sense if the renewal never happens. If the answer is no, the current file is leaning too heavily on future context. Rebuild the current-term evidence first, then mention renewal separately.

Also ask whether the candidate understands the fixed-term facts. If the candidate describes the job as permanent at an appointment while the documents say fixed-term, the file loses credibility. The appointment script should match the signed contract.

The final internal question is whether the fixed-term salary would look fair if reviewed without the renewal story. If not, the employer should either improve the current offer, strengthen the comparator evidence, or reconsider the route timing. A renewal promise is useful context only after the current contract can be defended on its own terms.

For close cases, prepare two versions of the salary explanation: one for the current fixed term and one for the possible renewal. Use only the current-term version for the route calculation unless the renewal is already legally assured and reviewed. This split keeps future optimism from weakening the present evidence.

If the current-term version feels too weak to submit, treat that as a signal to improve the current documents rather than stretching the renewal narrative.

The cleanest fixed-term file is modest, precise, and current.

Add a final reviewer who was not involved in the offer negotiation. If that reviewer cannot explain the term, salary, hours, renewal status, and route in plain language, the package still depends too much on insider knowledge.

Practical next step

Create a fixed-term salary exhibit before filing or refiling. If duration, salary basis, renewal status, and route relevance are not visible, the package is still exposed.

Internal links for the cluster

• Junior, trainee, and graduate role salary refusal
• Salary increase after arrival and promotion amendments
• Offer changes, salary cuts, and reduced hours
• Part-time hours and salary review
• Gross versus net salary, deductions, and allowances
• Salary comparability without a Tarifvertrag
• Response letters and contract language templates
• Post-refusal recovery roadmap