Community

What an RFE actually is, structurally

An RFE reads like a wall of dense text, but underneath it's a specific list of objections, each with a real, identifiable type. Recognizing the type changes how you respond to it. The four real categories an RFE objection falls into: - Insufficiency — the evidence exists but doesn't meet the standard (an award was submitted, but nothing shows it's nationally recognized) - Absence — the evidence for a claim isn't in the file at all - Final merits — even granting the individual criteria, the officer isn't convinced the totality shows sustained national or international acclaim - Procedural — something about the filing itself, not the substance (a missing form, a signature, a translation certification) The reason this matters: an insufficiency objection needs stronger or different evidence for the same claim. An absence objection needs evidence that currently doesn't exist anywhere in your file. Treating an absence objection like an insufficiency one — polishing what you already submitted instead of finding something new — is a common way to resubmit and still miss the actual ask. If you're staring at an RFE and can't tell which of the four you're looking at, the officer's exact requested language ("submit evidence that...") is usually the fastest way to sort it — it tells you whether they're asking for more of something or something new.

Published material about you vs. published material by you

These are two different criteria and petitions mix them up constantly: - Published material about you — profiles, feature articles, interviews focused on your work, written by someone else, in a professional or major media outlet. - Authorship of scholarly articles — articles you wrote (or co-wrote), published in a professional or major trade venue. A press release you wrote about your own work isn't "published material about you" — it's self-authored, and it reads as promotional rather than independent coverage. Similarly, a scholarly article you authored isn't evidence about you in the "published material" sense; it belongs under authorship instead. For published-material specifically, three things need to be in the file for each piece, not just the article itself: - A title, date, and author (so it's clear it's someone else's byline) - Evidence of the outlet's actual circulation, readership, or standing — not assumed, documented - An English translation if the original is in another language And watch for passing mentions dressed up as coverage: a single sentence naming you inside an article that's actually about something else isn't the same as an article focused on your work, even if it's flattering.

O-1A and EB-1A share criteria, not a bar

A question that comes up a lot: "If I qualify for O-1A, does that mean I qualify for EB-1A?" Not necessarily, even though the two classifications share almost the same evidentiary framework (O-1A's eight regulatory criteria overlap heavily with EB-1A's ten). What's actually different: - O-1A is temporary, nonimmigrant status tied to a specific job or event; EB-1A is a path to a green card - O-1A generally needs a US employer or agent to petition on your behalf; EB-1A allows self-petitioning - The two sets of criteria overlap but aren't identical, and adjudicators can apply them somewhat differently between the classifications - O-1A has no annual numerical cap or country-of-birth backlog; EB-1A does Practically, most of the work transfers even when the standard doesn't automatically: award documentation, published material, expert letters, evidence of a leading or critical role — all of that evidence is reusable across O-1A, EB-1A, and, with different framing, EB-2 NIW. Building it once and reframing it for whichever classification you're pursuing is far more efficient than starting over for each one.

Judging the work of others: the difference between being asked and being on record

"Participation, either individually or on a panel, as a judge of the work of others in the same or an allied field" sounds broad, and in one sense it is — peer review, competition judging, thesis committees, and grant panels all count. Where petitions run into trouble isn't the definition, it's the documentation. Reviewing for a journal is real judging work. But if the only evidence in the file is "I have reviewed for [Journal]" with nothing behind it, that's a claim, not a record. What actually documents it: - The editor's invitation email, or an equivalent appointment record - Something showing the review was completed — a review confirmation, a submission receipt from the journal's system, correspondence acknowledging your report - If it's a panel (grant review, competition, thesis committee), the appointment letter and, ideally, something naming the panel's composition or scope One more distinction that matters: the judging has to be in the same or an allied field as your claimed expertise. A judging role that's real but unrelated to the field you're arguing extraordinary ability in doesn't do much work for this specific criterion, even though it's a genuinely evaluative role.

Welcome to the Merito community

This space exists for one reason: building an EB-1A, O-1A, or EB-2 NIW case is a long process, and going through it without anyone to compare notes with is harder than it needs to be. This is where petitioners can share real experiences with each other — what an RFE actually looked like, what evidence worked, what a specific criterion actually required in practice — outside of their own individual case. A few things worth knowing up front: - This isn't legal advice, and it isn't from us either. Merito is not a law firm. Nothing posted here, by us or by any member, should be treated as legal advice for your specific case — only a licensed immigration attorney can do that. - Members share real experience, not predictions. You'll see posts about what happened in someone's own case. You won't see — and shouldn't post — claims about someone else's odds of approval. Every case is different, and framing this as a probability game isn't useful to anyone here. - Human-only, by design. Answers in this community come from real people. Merito never posts AI-generated answers into the community — if you're reading a response here, a person wrote it. If you're just getting started, the Criteria Library and free tools are a good first stop for baseline understanding — this community is where the day-to-day, "here's what I actually ran into" conversation happens once you're building.

Orphaned evidence, name inconsistencies, and other things nobody's checking for you

Three quieter problems that don't come from any one criterion being weak, but still cost credibility if they're not caught: - Orphaned evidence — a document sits in the file (a reference letter, an exhibit) but nothing in the petition body actually references it or explains what claim it's supposed to support. If a piece of evidence isn't tied to a specific claim, a reviewer has no reason to connect the dots for you. - Name inconsistencies — your name appears one way on your passport, another way on an award certificate, and a third way in a reference letter. Usually harmless (nicknames, transliteration differences, maiden names), but worth a short note in the petition connecting the variants rather than leaving a reviewer to guess whether they're the same person. - Date or figure conflicts — a membership listed as "current" that actually expired according to its own documentation, or two exhibits describing the same event with different dates. These read as carelessness even when they're genuinely just an oversight, so they're worth a pass before filing. None of these are about the substance of your case. They're exactly the kind of check that's tedious to do by hand across a hundred-plus-page file and easy to automate — which is the whole premise behind having a deterministic, code-first audit layer instead of relying on a human (or an AI model) to catch them by reading closely.

Translation order timeline — what to actually expect

Posting this since I couldn't find a clear timeline expectation anywhere before I ordered mine. For context: I had 11 documents needing certified translation, mixed lengths, one language. Rough shape of how it went: quote came back same day after documents were uploaded, I approved it, and the actual certified translations were done in batches over about a week and a half rather than all at once — which worked fine for me since I was still gathering additional exhibits anyway, but would have been tight if I'd needed everything on a hard deadline. A couple of practical notes for anyone about to do this: - Upload the cleanest scan you have — a certified translation reflects exactly what's on the page, so a low-quality source scan makes the translator's job harder and can slow things down - If a document has stamps, seals, or handwritten annotations, flag that up front rather than letting the translator discover it — it usually needs to be described in the certification, not just translated - Double-check names and dates in the finished translation against the original before submitting — translation is accurate to the source, but that doesn't catch an error that was already in the original document

Reference letters: the difference between a testimonial and evidence

Read a lot of reference letters while helping a friend put their file together, and the pattern in the weak ones was consistent: they read as testimonials ("she is brilliant, dedicated, and one of the best I've worked with") rather than as evidence (specific, checkable claims about what happened and why it mattered). What separates the two in practice: - A testimonial praises; evidence describes. "He led the redesign of X system, which reduced processing time by 40% and was adopted by two other divisions" is evidence. "He is an exceptional engineer" is a testimonial, even from someone impressive. - Specificity beats seniority. A detailed, specific letter from someone with direct knowledge of the actual work is usually stronger than a glowing but generic letter from someone more senior who worked with you less closely. - Independence matters for weight, not validity. A letter from a direct supervisor is legitimate evidence, but a mix of supervisory and independent (someone who knows the work but isn't in your reporting chain) letters generally reads as more persuasive than a stack of letters that could all be characterized as "people who work for or with you and are motivated to help." The fix for a testimonial-heavy letter usually isn't rewriting the praise — it's asking the letter-writer for specific examples and outcomes to replace the adjectives with.

Building a judging record before you have a senior title

A common worry: "I'm not senior enough yet to be asked to judge anything." Judging opportunities don't require seniority in the way that worry assumes — they require field visibility and a willingness to say yes when asked, which often starts earlier than people expect. Some concrete starting points that don't depend on already having a recognized name in the field: - Reviewing for journals adjacent to (not necessarily the top venue in) your specific subfield — mid-tier and emerging journals need reviewers constantly - Volunteering for conference program committees, which are often explicitly looking for reviewers at all career stages - Asking your own advisor, mentor, or collaborators whether they know of review or judging opportunities — a surprising amount of this is word-of-mouth, not a formal application process - Looking at professional-association-run awards or competitions in your field, which often need judges from a broader pool than just senior members Each individual role is a small credit. What builds the criterion over time is accumulating several of them, ideally across more than one venue or organization, so the pattern shows field-wide recognition rather than one person deciding to ask you once.

Using Case Canvas to find the criteria I hadn't actually built evidence for

I'd been telling myself I was covering six criteria for a couple months before I actually laid everything out in Case Canvas and realized two of those six had a single piece of evidence each, not the kind of depth I thought I had. The graph view made this obvious in a way a checklist never did for me — seeing exhibits actually connected (or not connected) to a criterion node, versus mentally counting "yeah I have stuff for that one," are two very different exercises. A criterion with one thin connecting line looks exactly as thin as it is. What I did after: picked the two weakest nodes and spent two weeks specifically closing gaps for those two, instead of continuing to spread effort evenly across all six the way I'd been doing. The timeline view was also useful for a different reason — it made it obvious that most of my strongest evidence clustered in one 18-month window, which is worth knowing before you're explaining career trajectory in a personal statement.

What actually happens when you run the Officer Simulator on your own file

Sharing this because I went in expecting something closer to a chatbot Q&A and it wasn't that — it's closer to reading commentary written by someone genuinely working through your case file section by section, criterion by criterion, the way a reviewer actually would. A few things that were more useful than I expected: - Seeing exactly where the commentary paused to flag something unclear, rather than a generic "this section could be stronger" note - The split view keeping the actual document next to the commentary made it obvious which specific sentence or exhibit a given comment was about, instead of vague overall feedback - It didn't try to predict an outcome — no percentage, no "likely approval," just the reading itself. That took some adjustment (I wanted a number), but it's consistent with everything else Merito says about not doing probability estimates The thing I'd tell someone before they run it: don't do it as your very first step. Go in with at least a full draft, not scattered evidence — the commentary is much more useful once there's an actual structure for it to react to.

Reading the officer's tone isn't about mind-reading — it's in the language

RFEs vary a lot in how they're written even when the underlying objections are similar. Some are close to a checklist — "submit X, submit Y" — and some read adversarial, pushing back on specific claims already made in the petition. That difference is real and worth noticing, because it changes how much explanation your response needs versus how much new evidence it needs. A mechanically-worded RFE is usually satisfied by directly supplying what's asked for. A more skeptical, probing RFE — one that specifically questions the independence of a letter, or challenges whether coverage is really about your work — usually needs the response to address the officer's actual concern head-on, not just add more of the same kind of evidence that triggered the skepticism in the first place. This isn't about guessing what an officer is "really" thinking. It's about reading what's actually written closely enough to tell a documentation gap from a credibility challenge — they call for different responses.

How I mentally paced a 10-12 month timeline without losing momentum

The hardest part of a long timeline for me wasn't any single hard task, it was maintaining steady effort over many months without either burning out early or losing urgency in the middle stretch. Sharing what worked, since I see this come up a lot. I broke the whole process into distinct phases with their own light deadlines, even though nothing external was actually forcing those deadlines: 6 weeks gathering baseline evidence, 4 weeks on reference letters (the slowest-moving external dependency, so I front-loaded requests), 6 weeks drafting the statement and organizing exhibits, then a genuine multi-week buffer before filing for review and gap-closing. Having artificial internal deadlines, even soft ones, kept me from letting the whole thing drift with no real accountability. The middle stretch — after the initial momentum wears off, before the filing deadline creates real urgency — is where I saw myself (and others, from conversations here) losing steam most. What helped: a weekly, not daily, check-in with myself on progress, so slow weeks didn't feel like failure, just normal variance in a long process.

A plain-language note on what we will and won't do here

We want to be direct about this instead of burying it in fine print: Merito is not a law firm, has no attorneys on staff providing legal advice through this platform, and nothing in this community — including posts written by the Merito Team — is legal advice for your case. What that means in practice: - We'll share how a regulatory criterion is generally described, what categories of evidence commonly satisfy it, and what an RFE objection type typically calls for — all general, educational information, the same kind you'd find in the Criteria Library. - We won't tell you whether your specific evidence meets a criterion, what your odds are, or what you should file. That determination requires a licensed attorney who's actually reviewed your case. - If a post in this community — including a question addressed to us — reads as asking for case-specific legal judgment, expect a response that points you toward speaking with an attorney rather than an answer that tries to substitute for one. This isn't us being cautious for its own sake. It's the same line the product draws everywhere else: Merito diagnoses and helps you strengthen a case file, it doesn't predict outcomes or replace the judgment of the licensed attorney who's actually representing you.

Exhibit numbering gaps are a completely avoidable RFE trigger

This one shows up constantly and has nothing to do with the strength of your case — it's a bookkeeping problem. If your exhibits are numbered 1 through 12, but exhibit 7 is referenced nowhere in the petition, or the petition cites "Exhibit 9" and there's no exhibit 9 in the file, that gap gets flagged before a reviewer even gets to the substance. The fix is mechanical, which is exactly why it's worth doing carefully: - Every exhibit in your table of contents should be referenced somewhere in the petition body - Every exhibit cited in the petition body should exist in the file, numbered to match - If you renumber anything late in the process (adding or removing an exhibit), re-check every cross-reference — this is where gaps usually get introduced, not at the first draft It's a small thing to get wrong and a slow thing to catch by re-reading, which is exactly the kind of check that's better done systematically than by eye.

How I actually organized evidence before it went into the petition

Sharing my system since it saved me from a lot of the "wait, which exhibit was that again" chaos I hear about in other posts here. I kept one running spreadsheet with a row per piece of evidence: exhibit number, one-line description, which criterion(s) it supported, and a status column (gathered / needs translation / needs a better scan / ready). Sounds obvious written out, but the discipline of updating it every time I added or removed something is what actually mattered — I didn't let it drift out of sync with the real folder. Two things I'd do differently next time: - I didn't lock exhibit numbers early enough, so renumbering late in the process created exactly the kind of cross-reference gaps other posts here have warned about — I caught them, but it took an extra full pass I could have avoided. - I underestimated how long "needs a better scan" would take in aggregate — a handful of documents I'd been putting off re-scanning turned into a genuinely time-consuming task right before filing, when I had the least slack in my schedule. Not a fancy system, but having one consistent source of truth for exhibit status, instead of scattered folders and mental tracking, made the last month before filing much less chaotic.

A practical checklist for the week before you file

Compiling what I actually checked in the final week, since most advice I found was about building the case, not about the last-mile review before submission. - Every exhibit referenced in the petition body actually exists in the file, numbered to match, and vice versa (no orphaned exhibits, no dangling references) - Every document requiring translation has its certified translation attached, not just the original - Names are consistent across documents, or any variation is explicitly explained somewhere in the petition - Every reference letter is signed, dated, and on letterhead where applicable — an unsigned or undated letter is an easy, avoidable gap - Scans are legible at print resolution, not just readable on screen (print a sample page and check it at arm's length) - The final merits argument is actually made explicitly somewhere — not just implied by having met three criteria, but stated: here's why the totality of this evidence shows sustained acclaim - A second person who hasn't been staring at this file for months reads it start to finish and flags anything confusing That last one caught more for me than any solo re-read did — by the end, I knew my own file too well to notice where an outside reader would get lost.

Leading or critical role: two different things that both need proving

"Evidence that the alien has performed in a leading or critical role for organizations or establishments that have a distinguished reputation" bundles two separate elements that each need their own evidence, and petitions often nail one while leaving the other thin. Element one: your role was leading or critical. Not just "senior" or "important-sounding" — actual evidence that the organization depended on your specific contribution, or that you directed, originated, or were essential to a specific outcome. A title alone doesn't establish this; what you actually did does. Element two: the organization or establishment has a distinguished reputation. This needs its own independent evidence — the organization's standing in its field, awards, recognition, media coverage, ranking — not just an assumption that a well-known name speaks for itself (and for smaller or specialized organizations, it usually needs to be argued explicitly, since a reviewer may not already know the organization). A common gap: strong evidence of the role (job description, org chart position, project ownership) with almost nothing about why the organization itself is distinguished — or the reverse, strong organizational reputation evidence with a role that reads as one contributor among many rather than clearly leading or critical.

My approval, and what I'd actually credit it to

Wanted to post a real account rather than just advice, since I found these more useful than generic tips when I was in the middle of my own case. To be clear up front: this is what happened in my specific case, not a prediction for anyone else's — every case is different, and I'm not claiming this formula works universally. I filed on four criteria: awards, published material about me, original contributions, and a leading role. In hindsight, my original-contributions section was doing the most work — it had the most specific, well-documented claim (a named technical contribution with independent evidence of adoption by two other teams outside my own organization) and the most detailed reference letters tied directly to that specific contribution rather than general praise. What I'd credit most, if I had to pick one thing: spending real time on the final-merits argument explicitly, not just assuming that meeting four criteria would speak for itself. I wrote a dedicated section of my personal statement connecting all four criteria into one coherent story about sustained recognition, rather than presenting them as four separate boxes checked.

One-time peer review vs. editorial board service — do they carry the same weight?

Both count under "judging the work of others," but they're not identical kinds of evidence, and it's worth understanding why before you decide where to put your effort. A single completed peer review is real evidence — but it's one data point, and by itself it says less about sustained standing in the field than a pattern does. Editorial board service, or judging the same competition across multiple cycles, shows something a one-off review doesn't: that the field keeps coming back to you for evaluative judgment, not just that you did it once. That doesn't mean a single review is worthless — it's genuine evidence, and several single reviews across different venues can build the same kind of pattern that one ongoing role would show. The distinction matters more for deciding how much weight one piece of evidence is doing than for deciding whether to include it at all. A file with one lone peer-review confirmation and nothing else under this criterion is weaker than the same file with three or four, even if none of them individually is an ongoing appointment.