Product Guides
Step-by-step guidance for using MARPT’s decision-support tools and interpreting results.
Start with Advisor
Run structured intake, then review matches and the checklist outputs.
Understanding matches & strength
How scoring works, what “strength” means, and what to do with gaps.
Documents and checklists
How to interpret requirements, identify missing items, and prepare cleanly.
Warnings & risk signals
Common denial points, discretion patterns, and how to reduce avoidable risk.
Advisor
Eligibility logic → ranked pathways, checklists, warnings, and explanations.
Visa Library
Browse categories, filter by type, and open official-aligned summaries.
Visa Details (Visa Profiles)
One visa, fully decomposed: requirements, restrictions, notes, and source references.
Visa Comparison
Side-by-side: eligibility constraints, documents, costs, and tradeoffs.
Norm (AI)
Constrained explanations and “why” answers grounded to sources and outputs.
Submitting a case brief
How to submit a high-signal case without exposing sensitive personal data.
Approval and anonymization
What gets accepted, how sensitive details are handled, and why some cases are rejected.
How case patterns are displayed
How MARPT summarizes patterns and where discretion and enforcement signals appear.
Professional use (firms)
How firms can use structured case patterns for intake triage and client explanations.
Advisor
A jurisdiction-aware decision engine that maps your facts to likely visa pathways and produces structured outputs: matches, checklists, warnings, and explainers.
- Answer intake questions precisely (avoid assumptions).
- Review top matches and read the “why” reasoning summary.
- Use the checklist to prepare documentation and identify gaps.
- Read warnings carefully and resolve avoidable risk factors.
- Entering incomplete facts (missing income/source, duration, sponsor details).
- Confusing “eligible” with “approved” (discretion remains).
- Ignoring warnings that require follow-up documentation.
Visa Library
A browsable catalog of Colombian visa categories with structured summaries, constraints, and requirement groupings.
- Filter by visa type and use search for categories and keywords.
- Open a visa card to review the overview and typical requirements.
- Use the library as a reference when comparing options.
- Assuming a category applies without reviewing restrictions.
- Skipping “notes” sections that affect eligibility or documentation.
Visa Details (Visa Profiles)
A single-visa profile page that decomposes requirements, restrictions, validity, and notes into structured blocks.
- Start with the overview, then read requirement blocks top-to-bottom.
- Use notes to capture exceptions and edge-case constraints.
- Confirm which requirements apply to your profile (not all apply to all cases).
- Reading requirements out of context (missing applicability conditions).
- Ignoring document formatting rules (apostille, translations, validity windows).
Visa Comparison
A side-by-side comparison of visa pathways that highlights tradeoffs: eligibility constraints, documentation burden, typical costs, and restrictions.
- Select 2–3 visas you are realistically eligible for.
- Compare requirements and restrictions line-by-line.
- Use the comparison to decide what evidence you can produce cleanly.
- Comparing visas you are not eligible for (wastes time).
- Overweighting “ease” without considering renewal or restriction risks.
Norm (AI)
A constrained explanation layer that helps you understand outputs. Norm is a tool inside MARPT, bounded by sources and logic.
- Ask “why” questions about a specific match, checklist item, or warning.
- Request citations and ask for the exact requirement block being referenced.
- Use it to clarify tradeoffs and next steps, not to replace professional review.
- Asking broad questions without context (“Which visa should I pick?”).
- Treating explanations as approvals or guarantees.
Case Intelligence
A curated library of anonymized case briefs and patterns (when approved) that can reveal process realities, discretion points, and enforcement signals.
- Search for cases similar to your profile and pathway.
- Focus on patterns and risk signals, not anecdotal one-offs.
- Use insights to improve documentation and follow-up questions.
- Assuming a case outcome will generalize to your case.
- Sharing sensitive personal data in a submission.
Start with Advisor
A short workflow that turns your facts into ranked visa pathways and a checklist you can execute.
- Answer intake questions carefully.
- Open top matches and read reasoning + restrictions.
- Export or note the checklist and start gathering evidence.
- Guessing values or omitting context that affects eligibility.
- Not revisiting results after new facts or documents are available.
Understanding matches & strength
Strength scoring is a signal of fit and readiness based on what you provided and what the pathway requires.
- Read the “why” summary: what facts drove the match.
- Use gaps to guide next steps (documents, clarifications, timing).
- Compare top 2–3 options before committing effort.
- Assuming a high score means approval.
- Ignoring restrictions that matter more than score.
Documents and checklists
A structured requirement list that helps you gather evidence in the right order and avoid missing essentials.
- Start with identity and eligibility proof items.
- Confirm validity windows (bank letters, police certificates, etc.).
- Plan apostilles and translations early when needed.
- Collecting documents too early (expiring before filing).
- Missing formatting rules (notarization, apostille, translation).
Warnings & risk signals
Warnings surface common failure points and discretion-sensitive areas that require stronger evidence or professional review.
- Read each warning and identify what evidence would reduce the concern.
- Use Norm to ask for the exact requirement basis and citations.
- If a warning is material, consult a professional before filing.
- Ignoring warnings because the match score is high.
- Assuming “it worked for someone else” applies to your case.
Submitting a case brief
A structured story submission that helps MARPT extract patterns without exposing personal data.
- Write facts and timeline, not opinions.
- Remove names, passport numbers, addresses, and document images.
- Explain what happened and what changed the outcome.
- Including sensitive personal identifiers.
- Submitting too little context to interpret the outcome.
Approval and anonymization
MARPT reviews submissions for relevance, clarity, and safety before publishing a summarized pattern.
- Expect anonymization and summarization before publishing.
- Some submissions are retained privately for internal pattern work.
- Some submissions may be rejected if low-signal or unsafe.
- Assuming every submission will be published.
- Submitting content that is purely speculative or unrelated to immigration process reality.
How case patterns are displayed
Patterns are summarized insights that help users anticipate practical risk points and plan better documentation.
- Use patterns to identify what evidence is commonly decisive.
- Look for signals around timing, enforcement, and discretion.
- Cross-check with the relevant visa profile and checklist.
- Overfitting to one case outcome.
- Ignoring official constraints because a case “seemed to work.”
Professional use (firms)
Structured case patterns can support intake consistency, follow-up questioning, and client-facing explainers.
- Use patterns as prompts for better intake questions.
- Build internal checklists that align with MARPT outputs.
- Share high-level patterns with clients to set expectations.
- Treating patterns as dispositive outcomes.
- Relying on case stories without reviewing the visa’s official constraints.
Troubleshooting
- Confirm you completed intake questions (missing fields reduce matches).
- Try a broader profile: remove optional constraints and rerun.
- Check status for outages.
- Include the page URL and what you expected vs what happened.
- Add a timestamp and your browser/device.
- Use report an issue for the fastest triage.
Need help? Use Support for account and billing issues, or report a reproducible bug.