Documentation
Reading the gap analysis report, and preparing a response before the notice
Read · 3 min
On Pro and Enterprise, a completed draft job also produces a pre-filing gap analysis. It runs after verification and redraft, so it reads the draft your team will actually see, not an early pass.
The report is organized by criterion, using the statutory heading rather than an internal catalog label. For each one Petria records a risk level of low, medium, or high, the named defect from the officer template, the matter-specific weakness, and what would close it. High is reserved for a criterion you are actually claiming where the primary corroborating exhibit is missing from the inventory. A criterion that is fully supported can still carry notes without carrying risk. Above the per-criterion rows sits an overall risk score and a list of the criteria that pushed it up. "Claimed" matters here: Petria assesses the criteria this petition is actually relying on, taken from the locked criteria package or the draft's own structure, rather than running the full statutory catalog, so a criterion you never claimed should not be generating gaps against you.
What would close it is written to point at exhibit labels and at concrete missing evidence, not at a rewrite of the petition or general best practice. Treat those items as a shopping list for the client, and expect fewer of them on a criterion that is already well covered. On Enterprise, a criterion marked Revised in the petition was already redrafted in loop 2, so the report does not ask you to do that rewrite again; Needs evidence means a missing exhibit, not more argument.
The report is not always called an RFE report, because the follow-up it anticipates depends on the program: US petitions, including asylum, anticipate an RFE, a USCIS Request for Evidence; Canadian LMIA anticipates an AIR, an ESDC Additional Information Request; Canadian refugee claims anticipate an RPD or RAD procedural direction or request for further evidence; other IRCC programs anticipate a refusal or request for additional documents. Read it beside the verification report, not instead of it. Verification asks whether the draft is grounded in the record you uploaded. Anticipation asks what an adjudicator might still push on. A draft can verify cleanly and still carry real rubric risk. This is decision support before filing, not a validated prediction of what the agency will do. You decide what to strengthen, and on Enterprise a second loop can redraft against these findings. If the gaps are real, the usual answer is more evidence rather than more argument.
Once a Pro or Enterprise draft job finishes and gap analysis is available, the matter offers to create a linked response matter, the same mechanism you would use after a notice arrives, run early. The idea is narrow: gap analysis has told you where an adjudicator is most likely to push, so rather than waiting to find out, you can open a response matter now, draft against those points, and have the argument on file before anything is received. In the US that is an RFE response; in Canada it is an RFR or additional documents response, depending on the program.
The response matter is created as a child of the original petition, and that linkage matters: a response matter linked to a petition Petria drafted can reuse the arguments from that original run. If the original was filed by another firm or drafted outside Petria, create the response matter as an external original instead and upload the prior petition as evidence. Uploads for a response job look different from a first filing: include the notice itself when you have one, the original petition, and any new evidence gathered since. Label them plainly, and keep exhibit labels consistent with the original matter where you can, so verification can tie new material back to earlier sections.
Response jobs run on their own monthly quota, separate from full draft jobs, and they are a Pro and Enterprise feature; every response job counts against that bucket, including ones linked to a Petria original. Two behaviors differ from a draft job. Response jobs read and triangulate the notice against the record as a dedicated step, so the response is organized around what was actually asked. And a response job produces a filing packet PDF assembling the notice, the response, and the exhibits, in addition to the Word deliverables. Gap analysis does not run on a response job, since the anticipation work was already done on the petition you are responding to. Only one linked response matter is offered per petition; if one already exists, the matter panel points you to it rather than creating a second.