Suppose a two-attorney family practice opens an adjustment of status matter for a married couple on eImmigration. The matter starts as case work. eImmigration's case management page describes a case creation wizard that opens the case, gathers its forms, builds the workflow and assigns the legal team. No form has been filled in yet.
Intake is where the two jobs first meet. The client completes a questionnaire, and an intake review notifies staff when it's finished. The answers are form data, and the notice is a case task.
Then comes the step the forms label describes. According to the form management page, a client record entered once generates the I-485, I-765 and I-131 together, and an address changed in one place updates everywhere. The checks for this step alone are in how to evaluate USCIS form automation.
After that the work is mostly case management again. A library of 120+ immigration process templates guides staff through the tasks for the case type. Through the client portal, the client uploads documents, reviews and signs, and sees the case status. Filing is the second place the jobs meet. The packet goes out by mail, or through the e-filing feature for forms the agency accepts online. Once the packet is filed, reminders and alerts run on the same record. Expiring documents such as an I-94, a passport or a visa are monitored up to 180 days ahead.
So the forms job comes up each time a filing needs it: at intake, at preparation, and again if a response or renewal follows. The case job runs the whole time, from the day the matter opens until it closes. A forms-only tool leaves the assignments, deadlines and filed copies to be kept somewhere else. With two separate products, data has to cross from one system to the other at intake, at filing and whenever a shared detail such as an address changes.