Specialized Matter Types

Some matters need more than the general drafting interview. An asylum brief leans on country-conditions research; an I-601A waiver turns on hardship; an RFE response is built issue by issue against the notice. DraftyAI handles each of these, but you never pick the right flow from a menu — the system routes your matter there for you.

These are destinations the workflow sends a matter into, by case type — not modes you toggle between. Internally the product calls them "perceived tools." You see one Draft action on the matter; behind it, the routing reads the output you want and the matter's case type, then opens the flow built for that work. The path is the same one every filing follows — client → matter → outline → draft → review → export — and each specialized flow is a step inside it, not a side door.

How routing decides

When you click Draft (or one of the "Produce a document" buttons) on a matter, DraftyAI parses two things: the output you asked for and the matter's case type. It then opens the flow that fits.

• A generic matter opens the Drafting Studio interview, the turn-based experience for any document.
• A specialized case type opens its dedicated flow — the branches below.
• Anything the system doesn't recognize falls through to the Drafting Studio, which never dead-ends.

You don't choose a tool. The single Draft action resolves to the right place, with your client and matter context carried over, so you generally don't re-enter what the matter already knows. The sections that follow describe what changes once you land in each branch.

RFE, NOID & NOIR — the Notice Response Builder

When the matter is a response to a USCIS notice — a Request for Evidence (RFE), Notice of Intent to Deny (NOID), or Notice of Intent to Revoke (NOIR) — the RFE response output routes you to the Notice Response Builder (/ai/notice-response-builder; the dispatch labels this destination "RFE Studio").

This flow is structured around the notice itself. You move through distinct steps:

1. Issues — the requested issues from the notice.
2. Evidence — the evidence each issue calls for.
3. Arguments — the legal arguments that answer each issue.
4. Draft — the assembled response.
5. Verification — a review pass over the draft.
6. Export — the finished documents.

Like every flow, it runs inside the matter and saves back to it. When the draft references case law or a statutory requirement, those citations are flagged for you to confirm or correct — a review aid, not a guarantee. Export offers a Response Letter and an Exhibit List as Word (.docx) documents.

Asylum, Withholding & CAT

For asylum, withholding of removal, and Convention Against Torture matters, the Petition / brief output routes to the dedicated Asylum/WOR/CAT flow (/ai/asylum). This flow has integrated web search for country conditions, so the brief can draw on current conditions and authoritative sources as you build it.

Your client, court, and jurisdiction come in from the matter, so you confirm context rather than re-type it. You build the brief with country-conditions research alongside, then review and export the same way as any other draft.

I-601A — Unlawful-Presence Waivers

When the matter is an I-601A provisional unlawful-presence waiver, the Petition / brief output routes to the I-601A Waiver flow (/ai/I-601A-Waivers). This flow is framed around extreme hardship: it works through the qualifying relative and the hardship facts that the waiver turns on.

Where the matter already holds the information, you can skip most questions; DraftyAI inserts a placeholder you edit after generation. The flow produces a draft with hardship-specific arguments for you to review, edit, and finalize.

Naturalization (N-400)

Naturalization is a specialized flow, but it produces something different from the others. When the matter is an N-400, the routing opens the Naturalization Cover Page flow (/ai/naturalization), which generates a client-specific filing checklist / cover page — not a drafted brief. In the app it carries a Free badge.

Treat it as the filing's cover sheet and checklist, assembled from what the matter knows about the client, rather than a narrative argument.

Translate a document

The Translate output routes to the Translation Studio (/ai/translation-studio). Upload the document and configure the translation; the studio exports a Word (.docx) document that includes a translator-certification block for you — or your certified translator — to complete and sign.

There's no back-and-forth drafting here: you upload, configure, and export. You remain responsible for the accuracy and certification of any translation you file with USCIS.

Improve a document

The Improve a document output routes to the Document Improvement Studio (/ai/document-studio). Bring in an existing document and the studio helps you strengthen it. The improved document saves back to the matter alongside your other drafts. As with every flow, you review and edit the result before relying on it.

Expert letters

An expert opinion letter has its own flow, the Expert Letter Builder (/ai/expert-letter-builder), which assembles a letter from the facts already in the matter.

There's an important routing nuance here: the Expert Letter Builder is not the auto-default draft for employment matters. An expert letter is one specific document, not the document most employment matters need — so routing it as the default would hijack nearly every employment matter. Instead, you reach it only through the explicit Expert letter button on the matter. The general Draft action on an employment matter goes to the Drafting Studio interview, not the Expert Letter Builder.

Affidavits & declarations

When you ask for an Affidavit/Declaration output, the matter routes to the dedicated Affidavit & Declaration flow (/ai/affidavit), which drafts the affidavit or declaration from the matter's facts. Review and export it like any other draft.

What stays the same across every branch

No matter which branch the routing opens, the rest of the workflow doesn't change:

• It runs inside the matter. Each flow launches with your client, case type, and jurisdiction already in context.
• Everything saves back to the matter. Drafts, letters, translations, and improved documents land on the matter page, grouped by type, so the matter stays the single home for the case.
• You review before you file. Drafts return as sections to read, edit, and verify; citations are flagged for your confirmation. This is a review aid, not a guarantee.
• You export to Word. Finalized drafts produce a downloadable .docx.

The specialized flow changes how the draft is built for that case type. It never changes who is responsible for the result — that's always you.

Important: you review and own every filing

DraftyAI accelerates drafting — it doesn't replace your review. Routing your matter into the right flow saves you setup and re-typing; it does not check your legal judgment. You read the generated draft, edit it as needed, confirm every authority, and are solely responsible for its accuracy and completeness before filing. The system is a research and drafting assistant, not a law firm.

DraftyAI accelerates drafting; it is not a law firm and does not provide legal advice. You review, edit, and are solely responsible for every document you file.