A paperwork playbook for migration agentsSorted

It's Thursday afternoon at a five-person migration practice. A partner visa client has sent their passport scan for the third time, because nobody can find the first two. A case officer is typing the same address history into Form 80 that she typed into the service agreement on Monday, and will type into ImmiAccount tomorrow. Nothing is wrong, exactly. It's just slow, and every retype is a chance for a typo the department will notice before you do.

This playbook maps the paperwork in a typical Australian visa case, from first consultation to lodgement, and shows where a practice can collect information once and reuse it everywhere. It's written for principals and case officers at registered migration practices. US immigration paralegals will recognise the same pattern with different forms.

This is general information about practice workflow, not legal or migration advice, and it doesn't replace the Code of Conduct or the department's instructions.

What does the paperwork in a typical visa case look like?

A typical case runs through five stages: intake, appointment and agreement, forms, the online application, and signatures and records. The same core details, such as name, date of birth, passport, addresses and relationships, appear in nearly every document. The practical goal is to capture them once and have every later document draw from the same source.

The rest of this playbook takes each stage in turn.

How do you collect client details once?

Build one structured record per client at intake, covering identity, passport, contact details, address history, employment, education, relationships and travel. Fill every later document from that record. When a form uncovers something missing or wrong, fix the record first. One source of truth turns five retypes into one check.

What belongs in the record:

• Full name exactly as on the passport, plus any other names used
• Date and place of birth, citizenships
• Passport number, issue and expiry dates, issuing country
• Contact details and current address
• Address history (Form 80 asks for the last 10 years, or 30 for refugee and humanitarian applicants)
• Employment and unemployment history with no gaps
• Education history
• Relationship details and family members
• Travel history
• Scans: passport bio page, photos, identity documents

Where does this record live? Often in your case-management tool or CRM. AppliFlo connects to client data through GlobalyOS (one-click Connect), HubSpot (read-only), CSV or Excel upload, a REST API and an MCP server. An Agentcis connection is on the roadmap, not live today.

What appointment and agreement documents do you need?

Before giving immigration assistance, a registered migration agent must give the client the Consumer Guide and have a written service agreement signed by the client and the agent. To act with the department, the agent lodges Form 956, one per matter. Form 956A is only for appointing an authorised recipient who isn't also the agent.

The Code of Conduct requirements

The Migration Agents Code of Conduct (compilation of 11 April 2024 (opens in a new tab)) sets the paperwork rules. Among them:

• Consumer Guide (s 38). An agent must not give immigration assistance unless a copy of the Consumer Guide has been given to the client.
• Service agreement (s 42). It must be in writing and signed by the client and the agent, and include the client's name, date of birth, email and residential address, the agent's name, MARN and contact details, the services, a statement that the Consumer Guide was given, what happens to the client file at the end, and the fee terms.
• Initial consultation (s 43). Advice at a first consultation can be given without a service agreement.

Notice how many of those agreement fields are client-record fields. Fill them from the record, and the agreement is ready in minutes.

Form 956 and Form 956A

Form 956 (opens in a new tab) (design date 08/22) can only be used by a registered migration agent, a legal practitioner or an exempt person. It says plainly that "A separate form 956... must be completed for each matter." Registered migration agents are registered with OMARA (opens in a new tab), and the form notes exempt persons "must not charge a fee", with penalties of up to 10 years' jail if they do.

Form 956A (opens in a new tab) appoints or withdraws an authorised recipient: someone who receives the department's letters but doesn't give immigration assistance. Our guide to Form 956 vs 956A covers which to use.

Getting them signed

Send the service agreement and Form 956 together, pre-filled from the client's record, with roles for the client and the agent. With AppliFlo Sign, you can set signing in order (client first, then agent) or in parallel, add reminders, and every signed PDF gets a PAdES seal, a certificate of completion and an audit trail of who signed, when, and from which IP address. Check the department's current instructions on how Form 956 must be signed and provided.

How do you fill Form 80, 1221, 888 and statutory declarations from the record?

Fill each form from the client record, then review it against the client's documents and have the client confirm and sign it. Personal particulars, address history and employment history flow straight in. Questions about character, relationships and personal circumstances must be answered by the client in their own words; a record can't and shouldn't answer those.

The common forms in Australian visa work:

AppliFlo's library includes 54 official government forms prepared for filling, including Australian visa forms, and it can read any other PDF, Word file or scan you upload, find the fields and fill them from the client's record. Fields it isn't sure of are flagged for a person to check, and form memory learns your corrections. Using an official form or saved template doesn't use AI pages.

For statutory declarations, the Attorney-General's Department says all three ways of making a Commonwealth declaration are equally valid, and that witnessed declarations can be signed in wet ink or electronically (AGD (opens in a new tab)). The right method depends on the client and the declaration.

How do you fill ImmiAccount pages without retyping?

Fill each ImmiAccount page from the client's record, review it against the client's documents, and only then move to the next. Upload documents into the right slots as you go. Stop at the final declaration so the client confirms the answers before you lodge. This keeps speed in the typing and judgment with the people accountable.

The page-by-page routine:

1. Sign in to ImmiAccount yourself and open the application.
2. Fill the current page from the client record.
3. Check names, dates and numbers against the passport and documents, not the record.
4. Read any error messages and fix the field they point to.
5. Attach documents in the correct slots.
6. Click Next yourself. Repeat.
7. At the final step, review the whole application with the client, confirm the declaration, then lodge and pay.

AppliFlo for Chrome, coming soon to the Chrome Web Store, does steps 2, 4 and 5 for you. It fills portal pages page by page from the client's record, including uploads such as passport scans and photos. It maps the portal's own error messages to each field. Sensitive details like tax file numbers and bank details fill only after you confirm, site by site. Its AI sees field labels, never the client's values. And on the final step it stops: it never lodges and never pays. Our post on why the form filler stops before Submit explains why.

How do you keep a defensible client file?

Keep everything that shows what the client agreed to, what was lodged, and that the client got a copy: the signed service agreement, signed forms, the lodged application and receipt, your written records of oral advice, and the signing audit trails. The Code requires a client file kept for 7 years after the last action on it.

What the Code requires (same compilation (opens in a new tab)):

• Lodgement notice and copies (s 39). Tell the client in writing when an application is lodged and give them a copy.
• Records of oral communications (s 55). Make a contemporaneous written record of oral advice and instructions.
• Client file (s 56). Keep a file including the application, service agreements, written communications, records of oral communications, invoices and receipts. It can be electronic, and you must take reasonable steps to keep it for 7 years after the last action.

A defensible file checklist:

• Consumer Guide given (and noted in the agreement)
• Signed service agreement, with certificate of completion and audit trail
• Form 956 or 956A as signed and provided
• Each signed form, sealed, with its certificate
• Lodged application and acknowledgement
• Written notice of lodgement and copy sent to the client
• File notes of oral advice and instructions
• Invoices and receipts

With GlobalyOS connected, signed copies from AppliFlo go back to the client's record automatically. Our guide to the audit trail and certificate of completion explains what to keep from each signing.

Where does AppliFlo fit next to your case-management tool?

AppliFlo isn't a case-management system. It sits beside one and handles the document work: filling PDF and Word forms and official government forms, filling online portals page by page, drafting agreements in Docs, and collecting sealed signatures. Your CRM keeps clients, deadlines and checklists; AppliFlo turns that data into finished, signed paperwork.

When we reviewed their public websites in November 2026, the main tools in this space covered different ground. Docketwise is built for US immigration law firms and auto-populates USCIS forms from a client intake questionnaire; we didn't see online portal filling. Agentcis is a CRM for education and migration agencies with document checklists; we didn't see visa form filling or e-signatures. Check each vendor's current features before deciding.

Pricing is on the pricing page; a free plan exists, and filling for clients from your CRM is part of the paid plans. For a closer look at how this works for a practice, see AppliFlo for migration agencies and the broader visa and immigration page.

Common paperwork mistakes in migration practices

The costliest mistakes are retyping errors across forms, reusing old answers for character or relationship questions, one Form 956 used across several matters, missing signatures or copies, and files scattered across inboxes. Each is avoidable with one record, a review habit and a fixed file structure.

• Different spellings across documents. One record, filled everywhere, fixes this.
• Address history that doesn't match between Form 80 and the application. Fill both from the same history.
• One 956 for two matters. The form requires a separate one per matter.
• Copying last year's answers. Circumstances change; ask again.
• Lodging without the client's final review. It's their declaration.
• Forgetting the lodgement copy. The Code requires you to give the client one.

If you're new to the forms themselves, start with our guide to Australian visa forms and the Form 80 guide. Forms and editions change, so check the current version on the Home Affairs form listing before filling.