How to Prepare a Postdoctoral Application and Fellowship Host Proposal

A postdoctoral application can look like one document, but it is usually a chain of decisions owned by different people. An employer may recruit for an advertised project. A funder may ask you to propose a project with a host institution. A university may have to approve a contract or an internal submission before the application can leave the organisation. Immigration, where relevant, is a separate government process. The strongest application keeps these routes connected without pretending that one person or one page controls all of them.

The first step is to identify which route you are using. In an advertised postdoc vacancy, the employer or research organisation normally defines the role, asks for the documents listed in the vacancy, and controls the recruitment process. In an individual fellowship, you may be responsible for the project idea while a host researcher and host institution provide support, facilities, training, and an institutional submission. The current call, host guidance, and application form decide what each person must do. A general postdoc checklist cannot replace those instructions.

This guide shows how to prepare for both routes. It helps you read the live vacancy or fellowship call, build a research-fit evidence base, select truthful CV and output evidence, shape a proposal or statement, prepare a host conversation, coordinate references and institutional approvals, and record mobility, contract, funding, and immigration questions. It includes a route comparison, a host-proposal readiness worksheet, and a final Truth Check. It does not write a proposal for you, promise host support, predict a selection decision, or give legal advice.

The practical aim is simple: when you submit, another person should be able to see what route you are applying through, what you are proposing, why the work fits the host or role, which evidence supports each claim, and which conditions are still controlled by an official office. If you cannot answer one of those questions, pause and find the page or person that owns it before you invest more time.

Start by separating the two postdoc routes

The phrase “postdoctoral application” covers several arrangements. Treating them as the same can lead you to send the wrong documents, ask a host for the wrong kind of support, or miss a formal step. Begin with a short route record before you edit your CV or write a research statement.

Advertised recruitment for a defined role

An advertised vacancy normally starts with a role description. It may be attached to a funded project, a department, a research institute, a laboratory, or an employer-wide research programme. The vacancy should tell you who employs the researcher, where the work is based, what work is expected, which documents are required, and how to apply. It may name a principal investigator or research lead, but the named researcher is not automatically the application owner.

For this route, your application is evidence that you can perform the work described in the vacancy. Your cover letter or statement should connect your experience to the stated tasks, methods, data, and outcomes. Your research record matters, but it should be selected for the role rather than presented as a complete history. If the role is part of a wider programme, read the programme and employer pages as well as the vacancy. The employer's application portal and instructions control the submission.

Do not turn a defined vacancy into an unsolicited fellowship proposal. You can mention how your experience would help the project and, if the vacancy invites it, discuss a possible extension. You should not promise to redesign the project before you have understood the role, its funding, and its contract.

Host-led or individual fellowship submission

In a fellowship route, you may bring the research question and ask a host researcher or institution to support the proposal. The application may require a host letter, a supervisor statement, a training plan, information about facilities, or an institutional declaration. The funder may assess the applicant, the project, the host, and the value of the proposed mobility or training together.

The MSCA Postdoctoral Fellowships page is an official example of a host-led fellowship model. It explains the broad route, but the current call documents, application form, and host institution instructions control the conditions for a particular submission. The MSCA funding page can help you locate current calls. It is not a substitute for the call text.

Other fellowship routes have their own structure. SNSF Postdoc.Mobility sets out a Swiss mobility-fellowship route whose current guidance must be checked for the applicant's situation. JSPS research fellowships provide an official Japanese example with programme-specific host and application conditions. These pages are useful models for understanding different routes, not proof that one set of rules applies to all fellowships.

Your host is usually a research partner and an institutional connection, not a private admissions office. A host can help you decide whether the project fits the group, explain the research environment, and provide the support named in the call. The funder still decides the award under its current process. The host may also need to obtain approval from a department, research office, or legal and finance team before the proposal can be submitted.

A quick route comparison

Use this table before you open a blank document. Replace the examples with the wording from your live source.

If your route does not fit either column, describe it in plain language. A research institute may offer a fellowship-like contract. A university may run an internal competition before forwarding a proposal to an external funder. A national programme may ask for both a host and a central application. The exact source controls the next action.

Read the controlling call or vacancy before you plan the application

Good applications are built from the route's actual instructions. Do not start with a generic postdoc template and try to force the opportunity into it. Collect the current vacancy or call, the application form, the host guidance, and the pages that explain the role of the employer, funder, and institution. Then turn those sources into a working brief.

Identify the owner of each decision

Write the name of the organisation that controls each part of the process. A useful record may include:

The source owner matters because a helpful person may not own the rule. A principal investigator can explain the research. A research office can explain internal submission. A funder can explain the call. A government authority controls immigration rules. Keeping those roles separate prevents you from treating a friendly email as a formal decision.

Make an instruction ledger

Create a simple ledger with the exact wording or a faithful summary of each requirement. Add the source link and the action it creates. For example, if the call asks for a research proposal, a host statement, and a training plan, record each as a separate item. Do not treat “proposal and supporting documents” as one task.

Include the following fields:

• the route name and the current source URL;
• the application owner and submission portal;
• the applicant conditions stated by the source;
• the host conditions and the host's required documents;
• the research scope, method, and assessment criteria;
• required files, format limits, and page or word limits;
• the formal closing point and any earlier internal deadline;
• references, letters, signatures, and approvals;
• employment, mobility, or location information stated by the source; and
• questions that remain unanswered and the office or person that can answer them.

Keep the source wording in your notes, but use your own plain-language action beside it. “Host declaration required” becomes “ask the host whether the institution has an approved form and when it must be signed.” This translation is for planning. The official instruction remains the authority.

Record the evaluation criteria as evidence questions

Calls often use broad labels such as excellence, impact, feasibility, training, or career development. Do not repeat those words without asking what evidence they require. Look at the current call, guide, and evaluation form. If an evaluation form is published, use its questions to organise your proposal. If it is not published, do not invent a scoring grid.

For a defined vacancy, turn each stated responsibility into a question. What task must the postdoc perform? Which methods are essential? Which outputs are expected? What collaboration or communication is named? For a fellowship, turn each criterion into a question about the applicant, project, host, training, and expected value of the route. Your draft should answer those questions with evidence, not with adjectives.

Check the application form early

An application form can contain constraints that are easy to miss in a public summary. Download or open the current form before writing a long proposal. Note the order of fields, character limits, required uploads, consent statements, declarations, and whether some sections are completed by the host or institution. A proposal that fits the public call may fail if it cannot be placed into the form's limits.

Do not assume that a PDF from a previous cycle is current. If the funder provides a page with a current form, follow that link. If the form is supplied through a portal that you cannot yet access, ask the official contact how to obtain the current instructions. Do not use a third-party template as a substitute.

Build a dependency map

Most delays come from dependencies, not from the writing itself. Draw a short chain that shows what must happen before the next step. A fellowship may require you to identify a host, discuss the project, obtain a host statement, pass an internal review, complete a funder form, and submit before the external closing point. An advertised vacancy may require references or right-to-work evidence only after shortlisting. The chain differs by route.

Write the dependency as an action and an owner. “Host reviews proposal” is different from “host confirms institutional support” and from “research office approves submission”. Put a question beside any step you cannot verify. This map gives you a reason to contact a host or office and helps you avoid asking the wrong person.

Build a research-fit evidence base

A postdoc application is not a contest to show that you have read the most papers. It is an explanation of why your prior work, the proposed or advertised research, and the host or employer form a credible next step. Build the evidence before you write the story.

Begin with the work you have actually done

List your completed research contributions, not only your job titles. For each project, note the question, data or materials, method, your role, the result or output, and what you learned. Include work that is finished, in progress, or submitted, but label the stage truthfully. A manuscript under review is not a published paper. A code repository is not automatically a validated method. A conference presentation is not the same as a peer-reviewed article.

The list can contain different kinds of evidence: a dataset you prepared, a method you implemented, a collaboration you supported, a protocol you improved, a paper you authored, a software tool you released, or a teaching and mentoring activity relevant to the role. Use the source or document that can support each claim. If a result is confidential, describe your role without disclosing restricted data.

Connect prior work to the next question

For each major experience, write a bridge sentence. It should say what the experience prepares you to do in the postdoc and what new learning the role would add. For example, “My doctoral work developed an image-analysis workflow for a defined dataset. The advertised project would let me apply that experience to a new biological question while adding the group's experimental training.” This is stronger than “I am passionate about interdisciplinary research.”

The bridge must not imply that the host has promised training unless the source states it. You can say that you hope to develop a skill or that the project would expose you to a method. You can say that the group page names a facility you would need to learn. You cannot say that access, supervision, or collaboration is confirmed until the current host or vacancy page confirms it.

Read the host's work at the right level

For a fellowship, study the proposed host's current institutional page, group page, and recent work. For a vacancy, read the project page and the employer or institute context. Confirm the person's current role on the institution's page. ORCID's getting-started guidance and its explanation of the source of information on a record can help you find publications, but a self-managed researcher record is not final proof of a current appointment.

Use publication metadata carefully. Crossref's explanation of metadata enrichment is useful for understanding why a DOI record may contain several pieces of information. Verify the work on a publisher, institutional repository, or current research page when the detail matters. Do not build your fit argument from a search snippet or from a profile that has no current institutional connection.

Read enough to identify the connection, not enough to imitate the host. Note the questions the group studies, the methods it uses, the evidence it can access, and the limits it acknowledges. A fellowship proposal should add a clear question that fits this setting. It should not simply repeat a host paper or promise to extend every line of the group's work.

Check the research environment without turning it into a ranking

Look for evidence about facilities, data access, specialist methods, collaborations, training, and support that are relevant to your project. A group page can show a facility, but it does not automatically confirm that a postdoc can use it or that the necessary staff time is available. Ask the host about the practical arrangement. If the opportunity names a formal facility or centre, keep the official page in your notes.

Use DORA's declaration on research assessment as a reminder to read research rather than rely on journal metrics. A high-impact journal name is not evidence that a host can support your method. A lower-profile publication may be more relevant to the work you want to do. Explain the connection in terms of question, method, and evidence.

Keep a fit matrix

Make a matrix with five columns: your evidence, the role or call, the host or group, the missing evidence, and the sentence you might use. A row could look like this:

Do not write the final sentence until you have checked the missing evidence. If the host page does not support the claim, remove it or ask a focused question. The matrix protects you from vague fit language and makes it easier to tailor the CV, statement, and host conversation.

Prepare the CV and research outputs

The CV is an evidence map, not a catalogue. A selector should be able to see what you have done, what you can do for this role or project, and where to verify the important details. The format and page limit in the vacancy or fellowship instructions always come first.

Follow the requested format

Read the current call or vacancy for a template, page limit, font guidance, file format, anonymisation rule, and requested sections. Some routes ask for a short CV. Others ask for a longer academic record with a selected publication list, teaching, mentoring, software, data, or service. Use the required format. A beautiful document that ignores the form is not a stronger application.

If the source does not set a page limit, choose a length that lets you show relevant evidence without repeating it. State dates and roles accurately. Use a consistent system for publications and outputs. Do not add a headshot, personal information, or a list of metrics unless the route asks for it or it is normal and necessary in the relevant field.

Put relevant evidence near the front

Start with a short research profile that names your field, methods, and the type of contribution you make. Then show the experience most related to the opportunity. A fellowship proposal may need a profile that explains your independence and trajectory. An advertised vacancy may need a profile that makes the role's tasks easy to find.

The opening should not claim that you are an expert in every requested method. If your experience is adjacent, say what you have done and what you are ready to learn. A truthful statement such as “I have used related statistical models and would extend this experience to the project's longitudinal data” gives the selector something concrete to assess.

Select outputs with a reason

Choose publications, preprints, datasets, software, protocols, patents, reports, or other outputs that support the application. Add a short explanation when the form permits it. Explain your contribution, the question, the method, or the relevance. Do not list every paper simply to make the CV longer.

Label each output's status correctly. Use the publisher or repository record for the title, DOI, authorship, and publication state. If a paper is submitted, say “submitted” only if that is true. If it is in preparation, do not present it as a manuscript under review. If a dataset is restricted, describe its existence and your role without sharing private material.

Explain your contribution to collaborative work

Postdoctoral applications often include team research. Make your contribution visible without diminishing other authors. Say what you designed, implemented, analysed, wrote, supervised, or coordinated. Use the role language requested by the route when available. A selector should not have to guess whether you led the method or only assisted with one part.

For a host proposal, connect the contribution to the new project. If your doctoral work included a method that the host group does not yet use, explain what you can bring and where you will need training. The proposal is not a promise that one person can do everything alone. It is a plan for a credible collaboration.

Include work that shows research practice

Evidence of responsible research practice can be relevant even when it is not a publication. You might include a reproducible analysis, a data-management contribution, a registered protocol, a code review, open materials, a mentoring role, or a research-training activity. Select the evidence that matches the call or vacancy. Do not use “open science” as a label without showing the practice.

The UNESCO open science framework provides a broad public reference for open-science ideas. It does not set the requirements for a particular employer or funder. If a call asks for data sharing, open access, or a data-management plan, follow that call's wording and your institution's policy.

Check links and identifiers

Use stable DOI, publisher, repository, ORCID, or institutional links when appropriate. Check that a link opens the work you name. Do not rely on a profile that changes without notice. If an output is not publicly available, describe it in the format the route permits rather than adding a broken or private link.

Shape a research proposal or statement

A proposal is a reasoned plan, not a promise of a result. It should show that the question matters, that your approach is possible in the proposed setting, and that you understand what the route asks the host and applicant to contribute. A statement for an advertised vacancy may be shorter and more closely tied to the job description. A fellowship proposal may need a full research plan, host fit, training, mobility, impact, and career-development explanation. Use the current form and evaluation criteria to decide the exact shape.

Start with the decision the proposal must support

Before drafting, write one sentence: “This document must help the selector decide whether...” Complete it using the call or vacancy. It might be whether you can deliver the advertised project, whether your proposed research is excellent and feasible, or whether the host environment gives the project a credible path.

Then write the questions the document must answer. For an advertised role, they may include: Do you have the methods and experience stated in the vacancy? Can you work with the team? Can you manage the tasks within the role? For a fellowship, they may include: Is the research question clear? Is the method suitable? Why this host? What training is needed? What can be achieved in the available period? Which outcome matters and who could use it?

Define a focused research question

Use one clear question or a small set of connected aims. Explain the problem in plain language before you use field terms. A selector should understand what you want to find out, why it matters, and what would count as useful evidence.

Avoid a proposal that contains several unrelated projects. A long list of aims can hide that the method, time, data, and host support do not match. If you need an exploratory phase, state it as part of a sequence rather than adding more topics. A clear question also makes it easier for the host to say whether the work fits the group.

Explain the method with enough detail to show judgment

Name the methods, data, instruments, or sources you plan to use. Explain why they answer the question and what their limits are. You do not need to write a full protocol unless the call asks for one. You do need to show that the method is not a decorative list.

For an experimental project, explain the main design, controls, measurements, and analysis. For a computational project, explain the data, model or algorithm, validation, and reproducibility plan. For a mixed or interdisciplinary project, explain how the parts connect and who supplies the expertise. For work with human participants, mention the need for ethics review and data protection without claiming approval before the relevant institution grants it.

Be explicit about what you will do if the first method fails. A short alternative plan can show that you understand the research risk. Do not write a second full project. State the decision point, the evidence you would use, and the practical change you would make.

Show feasibility through dependencies

Feasibility is not the same as optimism. List the dependencies: data access, equipment, field permission, software, collaborators, training, approvals, recruitment, or a host's supervision time. For each dependency, say whether it is confirmed, requested, or still to be checked. A proposal is stronger when its unknowns are visible.

If the host page names a facility, cite the page in your private evidence record and ask how access works. If a collaborator is needed, do not list that person as committed until they have agreed through the route. If the call requires an institutional statement, make sure the host knows what the institution may need to approve.

Connect the proposal to the host without making it a compliment

Explain why this host can support the question. Use the host's current research, method, facility, training, or collaboration as evidence. Then explain what you bring and what you need to learn. “The host is excellent” is not a fit argument. “The group has an active programme in the measurement method named in the call, while my prior work adds a different analysis approach” is a starting point for a real discussion.

Do not say that the host has agreed to supervise, provide equipment, or release data until the current host conversation or institutional document confirms it. Use conditional language in the early draft: “I would discuss access with the host” or “the proposal depends on confirmation of...” Then update the document when the host and institution have made a formal commitment.

Include a training and development plan that follows the work

Training should answer a real need in the project. Identify what you already know, what you need to learn, and how the host or institution could support that learning. The plan might include a method course, mentoring, research-integrity training, data management, leadership, teaching, or communication. Use the host's published training information only as evidence of what may be available. Confirm the specific arrangement with the host.

The NIH postdoctoral and residency training resource is an official example of how postdoctoral training and career development can be described in a national research system. It is not a universal checklist. Do not copy its structure into a fellowship proposal unless the current route asks for it.

State outcomes without promising a breakthrough

Describe outputs that follow from the work: a paper, dataset, code, protocol, conference contribution, report, training activity, or future grant direction. Explain who may use the result and how you would share it under the host's and funder's rules. Avoid claims that the project will solve a large social problem or produce a guaranteed commercial result.

A good outcome section respects uncertainty. It can say that the project will test a question and create evidence that may support a later application, method, or collaboration. It should not say that a funder will accept the work, a journal will publish it, or a host will obtain a particular grant.

Edit against the form, not only against the prose

When the draft is complete, place each paragraph into the relevant form field or section. Remove material that the form does not ask for. Check that every claim has a source, an output, an experience, or a clearly labelled plan behind it. Ask a colleague to read the proposal only after you have checked the official structure; a colleague cannot correct a missing form field by improving your style.

Prepare the host conversation

A host conversation is a working discussion, not a request for a personal favour. It should help both sides decide whether the route, project, timing, and support are realistic. Start with the call or vacancy and make your questions specific.

Decide whether contact is part of the route

Read the current instructions before emailing. Some fellowships expect an applicant to identify a host and develop a proposal together. Some calls use a central portal and do not require informal contact. Some vacancies name a research lead for project questions but require every application through the employer system. The page that controls the route decides what contact means.

If an instruction says not to contact individual researchers, follow it. Use the official office or named contact for a factual question. If the route requires a host, write to a potential host only after you have confirmed that the person and institution are eligible or plausibly connected to the route. Do not ask a host to bypass a formal process.

Send a short, prepared first message

The first message should tell the host why you are writing, which route you are considering, what research question you want to discuss, and what you are asking for. Include one relevant connection to the host's current work. Do not attach a full proposal unless the instructions invite it. A short two-page concept note can be useful if the host asks for one, but it should not replace the call's form.

The message should let the host say “yes, this is relevant”, “not my area”, or “please contact the office” without a long reply. You can write something like this in your own words:

“I am preparing an application for the current fellowship route named on the funder's page. My proposed work asks [one question] using [one method]. Your group's current work on [specific topic or method] appears relevant because [one connection]. The call requires a host discussion and institutional support. Would you be open to a short conversation about whether the project fits your group and what the host process would require? I have attached a one-page summary only to make the question easy to assess.”

This is a starting structure, not a template that guarantees a reply. Change it to match the route, the host's instructions, and your actual evidence. Never say that a host “has agreed” until the host has agreed through the relevant process.

Ask about the work and the support, not about a promise

In the conversation, ask questions that the host can answer. Which part of the project fits the group's current work? What method or evidence would need to change? Which facilities or collaborators might be relevant? What training would be realistic? Does the institution have an internal review before the external deadline? Which documents would the host and institution need to provide?

You can also ask how supervision would work, how often the group meets, and which office handles the contract or submission. These questions are about planning. They are not a demand for a guarantee. A host may need to consult colleagues or a research office before giving a final answer.

Clarify the host's role in writing

After a useful conversation, send a short summary of what was agreed and what remains open. Ask the host to correct your understanding. Record whether the host is:

• willing to explore the proposal;
• willing to provide a named support document if the institution approves;
• the academic contact but not the submission owner;
• able to confirm research fit but not funding or immigration terms; or
• unable to support the route.

Do not turn an informal “this sounds interesting” into a commitment. If the call requires a host declaration, use the current form or wording supplied by the funder or institution. A private email may help you plan, but it may not satisfy a formal evidence requirement.

Protect both sides' time

Set a reasonable response window based on the route's real deadline and the host's instructions. Do not send repeated messages every few days. If a host does not reply, use the official contact or consider another eligible host. A lack of reply is not a verdict on your research quality and does not justify sending the same proposal to every academic in a department.

Keep personal data and unpublished results out of ordinary email unless the host asks for them and the route gives a safe process. Passport scans, private medical information, and restricted datasets belong in the official system when they are required. Ask what a requested document is for before sending it.

Coordinate references, letters, and institutional approvals

Applications often fail at the edges. A strong proposal cannot compensate for a missing reference, an unsigned host form, or a submission that arrives through the wrong portal. Make the dependencies visible early.

Identify who submits each document

For every required document, record who writes it, who signs it, who uploads it, and who can change it. A funder may ask the applicant to upload a host letter. An institution may require its research office to submit the final application. A vacancy may request referee contact details and contact referees only after shortlisting. These are different workflows.

Read the current application instructions for privacy, consent, and format. Do not ask a referee to send a confidential letter to you if the route requires a direct submission. Do not upload a host statement yourself if the institution must submit it. If the instructions conflict, ask the official contact before the deadline.

Choose referees who can support the route

Select referees who know the work the application asks them to assess. A doctoral supervisor may be the right person for your research contribution. A project lead may be able to describe collaboration or a specific method. A department head may not know your day-to-day work well enough to write a useful letter. Follow any rules about conflicts, number of references, and referee eligibility.

Give each referee a concise packet: the current call or vacancy, the role or project summary, your CV, the proposal or statement, the exact submission route, and the date you need their response. Explain which experiences you hope they can discuss, but do not write claims for them to sign. Tell them if the application is confidential and how the funder handles their information.

Prepare a reference timetable

Work backward from the earliest step that depends on another person. If an internal office needs time to review a host proposal, that date may be earlier than the funder's public closing point. If references are requested only after shortlisting, do not pressure referees to submit before the route asks for them. Record each stage and mark the source that controls it.

Use a table with columns for document, owner, format, submission path, internal date, external date, and confirmation. Keep a screenshot or receipt only when the official system allows it. A private spreadsheet is enough; do not create a public list of referee details.

Check institutional approval needs

Host institutions may have research offices, finance teams, ethics committees, export-control teams, or other approval steps. The relevant requirement depends on the project and call. Ask the host whether an internal review is required, what information the office needs, and who submits the final application. Do not claim that approval is complete until the responsible office confirms it.

If a proposal involves human participants, personal data, samples, controlled materials, field sites, or a collaboration across countries, ask early about the institution's process. The application may need to describe the planned approval, but it should not state that approval has been granted before it has. The funder and host institution control the wording.

Keep letters distinct

A reference letter, a host statement, an institutional letter, an employer confirmation, and a support letter may sound similar while serving different purposes. Copy the exact name used in the call. Explain the difference to the person helping you. A reference usually discusses your ability and record. A host statement may describe supervision and fit. An institution letter may confirm the organisation's role or ability to receive an award. Use the correct document in the correct field.

Handle mobility, contract, funding, and immigration questions carefully

Postdoc routes often cross borders, but an application guide should not turn into a visa promise. Keep research preparation, employment terms, award conditions, and government permission as separate records.

Distinguish a fellowship award from employment

A fellowship may provide an award to support a researcher, a host project, or a period of mobility. An advertised postdoc may be an employment position with a salary, contract, benefits, and employer duties. The wording varies by route and country. Read the current call, award terms, vacancy, and host institution information. Do not use “funded” to mean a specific salary, tax treatment, or benefit unless the controlling source says so.

Ask who receives the funds, who employs you, who pays the researcher, and what costs the route covers. If the source is unclear, ask the funder or employer. A host researcher cannot decide the legal or tax treatment of an award in every jurisdiction.

Treat mobility rules as call-specific

Fellowship calls can include conditions about the applicant's previous residence, work history, or time in a host country. These rules vary by scheme and call. Never apply a general “international” or “mobile” rule from a blog to your case. Read the current call and ask the funder when the wording is unclear.

The official MSCA Postdoctoral Fellowships page is a useful starting point for the route's structure, but the live call and guide control the exact conditions. The same principle applies to SNSF, JSPS, and any national or institutional fellowship.

Separate offer evidence from government evidence

An award letter or employment contract may help you document funding or a role, but it is not the same as government permission to enter or work. The government authority decides which route, documents, and timing apply. The host institution may have an international office that can point you to official information. Use that office as a guide to the controlling government page, not as a replacement for it.

For example, the Canadian government study-permit application page and the Canada study-permit overview explain a government route for study. A postdoc's actual route may instead depend on the employment or research status described by the host and the current government rules. The UK Student visa course requirements and Appendix Student are official examples of why the route and source matter. They do not tell you which permission a postdoc needs.

Do not send a government application based on a host's guess. Ask the institution which official page applies, read the current requirements, and obtain professional advice when your case is complex. AcademicWings can help you keep questions and sources organised, but it cannot decide or guarantee an immigration outcome.

Record questions before you contact an office

Write each question in a form that identifies the route and the exact uncertainty. “Can I work there?” is too broad. “The current host offer describes a research appointment at the institute. Which government information page should I use to check the permission and evidence for this role?” gives the office a clear starting point. Keep the answer with the source and date. If the answer is verbal, ask where the current rule is published.

Postdoc application Truth Check

Use this audit when you think the application is ready. The purpose is not to make you feel certain. It is to show which evidence is complete, which statements are your interpretation, and what still needs confirmation.

Route and source

• Can you name the exact vacancy or fellowship call and open the current source?
• Do you know who receives the application and who submits it?
• Have you saved the current application form and host guidance?
• Are discovery listings clearly separated from the controlling employer, funder, or institution page?
• Did you check whether the route is a vacancy, host-led fellowship, internal competition, or another structure?

If the answer to any question is no, stop polishing the prose and complete the source record. A longer application cannot repair an unknown route.

Eligibility and documents

• Did you read the current eligibility wording rather than rely on a summary?
• Have you separated applicant conditions from host conditions and institutional conditions?
• Is every required file present in the requested format?
• Are output stages, dates, authorship, and roles truthful?
• Are reference and host letters assigned to the correct owner and submission path?
• Have you checked the form for hidden fields, declarations, or character limits?

Do not mark an item complete because you intend to do it later. Mark it complete only when the source and document record show that it is ready.

Research fit and feasibility

• Does the proposal or statement answer the route's evaluation questions?
• Is the research question focused enough for the available period?
• Do the method, data, facilities, and training match the host or advertised role?
• Have you stated what is confirmed, requested, and unknown?
• Does the proposal show what you bring and what you need to learn?
• Have you avoided copying the host's work or claiming a commitment that has not been made?

Ask a colleague to explain your project after reading the draft. If they cannot state the question, method, host connection, and next evidence, revise the structure.

Host and institution

• Does the current host page confirm the person's role and research connection?
• Does the host understand the call, the expected support, and any internal deadline?
• Have you asked who handles institutional approval and final submission?
• Is the host statement or letter in the current required form?
• Are facilities, supervision, collaborators, and training described as confirmed only when a controlling source supports them?

A host's interest is valuable, but it is not the same as an award, contract, or institutional approval. Keep those decisions separate.

Timing and personal evidence

• Have you worked backward from the official closing point and any earlier internal step?
• Are your references, translations, certificates, and approvals planned with enough time for the route?
• Did you check the page again after making a material change to the application?
• Have you written down the official source for funding, contract, mobility, and immigration questions?
• Are you avoiding a claim about visa permission, funding amount, or employment condition that the current authority has not confirmed?

If a high-risk fact cannot be checked, say so in your private record and ask the controlling office. Remove the claim from the public application unless the route requires a clearly labelled plan.

Follow one host proposal from question to submission

The following trace shows how to keep an individual fellowship proposal connected to evidence. It is a planning example, not a universal application template.

The starting question

Suppose you want to study a STEM problem that grows out of your doctoral research. You identify a fellowship call that allows a researcher to propose a project with an eligible host. Your first record should contain the current call, the application form, the host rules, and the institution's contact or research-office page. You write the question in one sentence and record the evidence from your previous work that prepares you to study it.

At this stage, do not call the project “approved”, “fully supported”, or “ready to submit”. You have a potential route and a research idea. The next decision is whether an eligible host can support the work under the call.

The host-fit check

You read the host's current institutional and group pages, then one or two relevant publications from a publisher or repository. You identify the method, facility, data, and training connection. You write down what is missing: perhaps access to a specialist instrument, an internal collaborator, or an approval process. You send the host a short message that names the route and asks whether the idea is close enough for a conversation.

The host may say the question fits but the proposed method needs to change. That is useful evidence, not a rejection of your ability. You update the concept note, state the changed dependency, and ask whether the host can provide the support required by the call. If the host cannot support it, you keep the idea and find another eligible route rather than pretending the original fit exists.

The proposal and training link

You draft the proposal around the call's evaluation questions. The method follows the question. The feasibility section names what the host can confirm and what still needs institutional approval. The training plan follows your real needs. The host statement describes the host's role in the wording requested by the call. Each important claim has a source, a prior output, a host confirmation, or a clearly labelled plan behind it.

The host and institution review the required sections. A research office may ask for changes to budget, contract, ethics, data, or intellectual-property language. You do not remove those parts because they interrupt the story. They are part of the route. You keep the public call and the office's current instructions beside the draft.

The final submission record

Before submitting, you compare the final files with the current form and call. You check names, affiliations, dates, references, host documents, signatures, and permissions. You save the confirmation supplied by the official system. You record what is submitted and what remains a decision for the funder, host, employer, or government.

This record protects you after submission. If the funder asks for a correction, you can see which source and version you used. If the host changes role or the project terms change, you know which question must be checked again. A careful record cannot change a selection decision, but it can keep you from relying on a memory or an old page.

Submit through the official route and choose the next action

Submission is a process step, not the end of the evidence work. Use the portal, email address, or institutional route named by the current call or vacancy. Do not send a duplicate application to a host's private address unless the instructions say to do so. Check that the system has accepted the correct files and that a confirmation exists.

After submitting, keep a short record of the route, the version of the proposal, the host and referee documents, the source links, and the next date or action stated by the official organisation. If the application is unsuccessful, ask only for feedback the route offers. If you receive an offer, read the contract or award terms and return to the controlling sources for funding, employment, mobility, and immigration questions.

The AcademicWings guides can help you organise the next practical step. If you are still checking postdoctoral routes, use How to Find and Check Postdoctoral Positions Abroad. If you need to decide how or whether to contact a research lead, read When and How to Contact a Potential PhD Supervisor; the route is different for postdocs, but the same rule applies: let the current instructions decide what contact means. You can also browse opportunities, STEM fields, and universities while you keep the source record for the route you choose.

Sources for this guide

The links below are official starting points for the route structures, researcher records, publication discovery, training, and immigration-source hierarchy discussed here. They do not decide an individual's eligibility, host support, contract, award, or immigration outcome. For a live application, add the current call, vacancy, form, host page, institution page, and government page that control your case.

• MSCA Postdoctoral Fellowships: official description of a host-led postdoctoral fellowship route. The current call and application guide control the requirements for a submission.
• MSCA funding opportunities: official discovery page for MSCA calls. Confirm the applicable call and dates in the current documents.
• SNSF Postdoc.Mobility: official Swiss fellowship information. The current programme guide controls conditions and deadlines.
• JSPS research fellowships: official Japanese fellowship information. Use the applicable programme and host instructions for a real application.
• NIH postdoctoral and residency training: official example of postdoctoral training and career-development information in the United States. It is not a universal postdoc checklist.
• ORCID: getting started: explains researcher records and how works can be connected to a record. Confirm a current role on the institution's page.
• ORCID: where can I see the source of information on my record?: explains source and assertion information in an ORCID record.
• Crossref metadata enrichment: explains how publication metadata can be enriched and discovered. Verify important publication details on the publisher or institution page.
• DORA declaration: explains why research assessment should not rely on journal metrics alone.
• UNESCO Open Science: provides a broad framework for open-science ideas. A call or host policy controls what an individual application must include.
• Canada: apply for a study permit as a graduate student and Canada study permit: official government sources included to show why immigration questions must be checked with the authority that owns the route.
• UK Student visa course requirements and UK Immigration Rules: Appendix Student: official UK government sources that illustrate the need to check the route and current rules. They do not determine which permission a postdoc needs.