Formal Requirements During Your Visa Process: What to Do

Read: 9 min

While reviewing a visa application, Colombia's Ministry of Foreign Affairs may issue a formal requirement — a formal request for additional information or documentation needed to continue evaluating the case. Receiving a requirement doesn't automatically mean the application will be denied, but it does demand a timely, complete, and well-supported response.

Why requirements are issued

Requirements can arise for various reasons: incomplete documents, inconsistent information between the form and submitted evidence, the need to clarify aspects of a family, employment, or investment tie, or simply a request for additional documents the authority considers relevant to resolving the case with more certainty. A requirement isn't, in itself, a negative sign: in many cases it's simply the mechanism through which the authority seeks to complete a file that may otherwise be perfectly on track for approval.

The response deadline: the most urgent thing of all

One of the most important aspects of receiving a requirement is strictly respecting the deadline given to respond. These deadlines tend to be short, so it's essential to review the communication immediately and start gathering the requested documentation or information without delay. Missing the deadline without a response can lead to the application being closed or an unfavorable decision, regardless of how solid the rest of the file was.

How to structure a good response

When preparing your response, it's advisable to be precise and answer exactly what was requested, avoiding unnecessary information that could raise new questions. If the requirement asks for a specific document, that document must be provided meeting all formal requirements, such as apostille or translation, as applicable. Attaching additional documents that weren't requested, with the idea of "reinforcing" the response, can have the opposite effect: it introduces new information the authority didn't ask for and that could open additional questions about aspects that weren't previously in question.

When the requirement asks for an explanation, not just a document

In some cases, the requirement may refer to inconsistencies requiring a reasoned explanation rather than just an additional document. In these situations, drafting a clear, organized response backed by available evidence can make a difference in the final outcome. For example, if the requirement asks about a discrepancy between two dates in different documents, the response should explain the origin of that discrepancy (a transcription error, a difference in date format between countries) and, whenever possible, provide an additional document supporting the explanation, rather than simply stating that "it's an insignificant error."

One requirement shouldn't turn into several

One goal when responding to a requirement should be resolving it completely in the first response, avoiding loose ends that trigger a second round of questions. This means anticipating what other related information the authority might need to fully close the point, without going to the extreme of overloading the response with unrequested documents, as mentioned above. Finding that balance — being thorough without being excessive — is precisely where prior experience with this kind of process helps the most.

Applicable legal framework

The immigration authority's power to request additional information while reviewing a visa falls under Decree 1067 of 2015 and general principles of Colombian administrative law, which allow public entities to request clarifications or supplementary documents before making a final decision on an application, as a safeguard for both the administration and the applicant.

Difference between a requirement and a final denial

It's important not to confuse a requirement with a final unfavorable decision. A requirement is, by definition, an intermediate stage of the process: the authority hasn't yet made a final decision, and is giving the applicant the opportunity to complete or clarify their file before deciding. A final denial, on the other hand, is the substantive decision that closes the process, against which different mechanisms exist, such as the reconsideration remedy, if the applicant believes the decision was incorrect. Confusing these two stages can lead to disproportionate reactions — for example, assuming all is lost upon receiving a simple requirement — when in reality it's a concrete opportunity to strengthen the case.

Repeated requirements: a sign something isn't being resolved well

If the same case receives more than one requirement on related points, it's worth pausing to review whether previous responses truly addressed the substance of what the authority was asking, or whether they only responded partially or tangentially. A pattern of successive requirements on the same topic usually indicates that the original response didn't resolve the underlying concern, more than a problem with the case itself.

What to do if you don't understand exactly what's being asked

A common practical problem is receiving a requirement written in technical or ambiguous terms, without it being entirely clear what specific document or clarification is expected. In this situation, it's not advisable to respond with a rushed interpretation of the requirement without being sure you've understood it correctly, since a response that doesn't address what was actually requested can trigger a second requirement or, in the worst case, an unfavorable decision on the grounds that the original request wasn't addressed.

Having professional guidance when responding to a requirement helps correctly interpret what the authority is asking for and structure a response that strengthens the application rather than raising new doubts about the case, especially when the time available to respond is limited and there's no room for failed attempts.

Case study

An applicant receives a request for additional information, notes the deadline the same day, gathers the missing documents and replies with a clear cover letter listing each attachment. He keeps proof of submission.

Key takeaways on information requests

• Focus on the essentials: the points that most affect information requests are deadlines, complete answers and proof of submission.
• Plan early: most delays come from documents or deadlines handled at the last minute, so build a calendar from the start.
• Keep proof: save receipts, confirmations and copies of everything you file or receive.
• Stay consistent: names, dates and numbers must match across every document and form.
• Verify the current rules: requirements and procedures can change, so confirm them on official sources before acting.
• Ask when in doubt: a short consultation before acting costs far less than correcting a mistake afterwards.

A last practical tip

Read the request twice and list each item before gathering documents. Because every situation is different, treat this guide as general orientation and not as a substitute for advice on your specific case. Keeping a clear, chronological record of what you do and when you do it will help you respond quickly to any question and will make later procedures easier. If something in your file does not seem to fit the standard pattern, explain it in a short note and support it with documents instead of leaving it unexplained. Transparency, organization and anticipation are the habits that most often separate a smooth process from a complicated one.

A practical method for answering an information request

• Read the request in full and underline each specific demand.
• Note the notification date and the response deadline.
• Build a table: what they ask, what I have, what is missing, how I get it.
• Gather the documents and check their validity, apostille and translation.
• Draft a cover letter that goes point by point through what was requested and what is provided.
• File with proof of receipt and keep a copy of everything.

Complete response vs. partial response

If you cannot provide everything within the deadline, assess whether an extension can be requested or whether it is better to provide what you have and explain what is pending. What is not recommended is letting the deadline pass with no response at all. A partial, orderly and justified response is better than silence.

Learning from the request

Each request reveals which aspects of the file raised doubts. Use it as feedback to improve your documentation and avoid similar problems in later procedures.

Model structure for the response letter

A good response letter to an information request usually follows this structure:

• Reference: file number, date of the request and applicant details.
• Short introduction: a statement that the response is made within the deadline.
• Point-by-point answer: each demand, followed by what is provided and where it sits among the annexes.
• Clarifications: an explanation of any particular circumstance.
• Numbered annexes: a list of attached documents.
• Courteous closing: willingness to provide further information.

What to avoid when responding

• Vague answers or answers without documents.
• Disordered or unnumbered annexes.
• Defensive or confrontational tone.
• Information that contradicts the original file.
• Sending the response without proof of filing.

Repeated requests: a warning sign

If you receive several requests in a row for the same file, something is not being solved properly. Step back and review the whole file instead of answering one request at a time. Often a single clarifying document or a short explanatory letter addresses the underlying doubt.

Glossary

• To cure (subsanar): to correct or complete what is missing.
• Peremptory deadline: a term that does not allow extension except for exceptional reasons.
• Tacit withdrawal: the consequence of not answering in time, which may mean the file is closed.
• Annex: a document attached to a communication.

Keep a log

Note each request received, its date, the deadline, what was requested, what was answered and the date of the reply. That log will help if the procedure drags on or if you need to show your diligence.

Quick answers

What if I do not understand what they are asking? Read it again with the file in hand, and if doubt remains, seek guidance before the deadline runs out.

Can I ask for more time? Sometimes, if the rules allow and there is a justified reason; do it before the deadline expires.

Does a request mean denial? No. It means the authority needs more information to decide.

Written and immigration-reviewed by: María Fernanda Rodríguez · Updated: 25 Oct 2026

Notice: this content is general information and not individual legal advice, nor does it guarantee visa approval. Every case depends on its category and circumstances.

Back to blog