An ITAT appeal workflow begins before anyone opens Form 36. The team must first establish what order was received, when and how it was communicated, whether the proposed grievance is appealable, and which record can support each proposed ground. If those questions remain loose, a polished upload can still carry the wrong dates, an incomplete record, or grounds that do not match the order.
This guide treats the appeal as a controlled legal operation. It does not decide whether an appeal should be filed. That judgment belongs to qualified professionals applying the current Income-tax Act, the Income Tax (Appellate Tribunal) Rules, applicable notifications, and the facts.
What should happen when the impugned order arrives?
Open a matter record on the day the order is received. Preserve the native electronic file, the email or portal communication, envelope or dispatch evidence if relevant, and a readable working copy. Do not overwrite the original with an annotated PDF. Record who obtained it, from where, and when.
Create an intake sheet with these fields:
| Field | Evidence to retain | Review question |
|---|---|---|
| Order authority and provision | Complete signed order | Is this the operative order? |
| Assessment year and PAN | Order and prior proceedings | Do identifiers agree throughout? |
| Communication date | Portal, email, dispatch, or service record | What event starts the proposed calculation? |
| Amounts and issues | Computation and order | Can each figure be reconciled? |
| Earlier grounds and submissions | Form 35, pleadings, evidence | Which issues were actually raised? |
| Proposed challenge | Counsel instruction | Is each ground tied to a finding or omission? |
The Income Tax Appellate Tribunal describes its institutional role and publishes notices. The legislation should be checked in an official source such as India Code. Save the version used and the research cut-off date because portal instructions, rules, and legislation can change.
How should the team assess appealability and scope?
Prepare an issue map, not a draft ground list copied from another appeal. For every proposed issue, identify the challenged finding, the material facts, the governing provision, the earlier submission, the evidence already on record, and the relief being considered. Mark new facts, new evidence, and issues not dealt with below for specific professional review.
A useful triage uses four statuses:
- Proceed for analysis: source material is complete enough for counsel to assess.
- Evidence gap: a document, ledger, notice, or service record is missing.
- Procedural question: maintainability, limitation, jurisdiction, or admission requires research.
- Out of scope: the complaint is commercial or factual but does not yet identify an appealable error.
Keep the assessment separate from client advocacy. A strong file records adverse findings and weak points openly. The AI legal research guide explains why a generated answer is only a research lead. Use the complete statute, rules, and authorities for verification.
How do you build a reliable appeal record?
Create one document register before drafting. Give each item a stable identifier and record its date, description, source, page count, confidentiality, legibility, and status. The register should distinguish the lower-authority record from documents obtained later.
The core working folders can be simple:
01-order-and-servicefor the impugned order and receipt evidence.02-lower-recordfor the assessment order, prior appeal, grounds, facts, and submissions.03-appeal-draftfor reviewed versions of Form 36, grounds, and applications.04-filing-setfor only the approved upload files.05-acknowledgementsfor portal receipts, fee evidence, defect communications, and responses.06-hearingfor paper books, authorities, synopsis, and hearing notes.
Use permissions appropriate to tax and personal information. Teams evaluating systems can review Gotham's security approach, then test deployment, access, retention, and export controls against their own duties.
How should Form 36 and the grounds be prepared?
Treat Form 36 as structured data backed by the record. One preparer enters information; another compares every identifier, date, section, amount, and address against the source documents. Never resolve a mismatch by choosing the value that looks familiar. Log it and obtain a decision.
Draft grounds only after the issue map is reviewed. Keep grounds precise enough to identify the error and relief, while leaving argument and evidence discussion for the appropriate submission. Check numbering, internal references, party descriptions, assessment year, and whether any general ground has a defined operational purpose.
The ITAT's required-documents page generates a list according to appeal type and subtype. It may identify Form 36, grounds, the first appellate order, earlier grounds, fee challan, limitation certificate, authorisation, or other material. Use the live matrix for the actual filing rather than treating this article as a document prescription.
What is the safest way to complete ITAT e-filing?
Begin at the official ITAT e-Filing portal. Confirm the current login method, authorised user, contact details, jurisdiction inputs, and portal guidance. The ITAT e-Filing help page links practice material and filing checklists. Read the current items, including later notices, before relying on an older saved procedure.
Run a pre-upload check:
- The approved document list matches the selected appeal type and subtype.
- Signed documents were executed in the required manner.
- Every PDF opens, is oriented correctly, and remains searchable where practicable.
- File names are meaningful and contain no unnecessary personal data.
- Page counts match the document register.
- Form data agrees with the final PDFs.
- The fee and authorisation evidence have been professionally verified.
- Limitation and any condonation material have received specific approval.
- A second person has checked the complete submission preview.
After submission, save the acknowledgement and timestamp outside the browser session. The portal's Appeal Dashboard can be used to view filing details, address defects, or file later documents. A generated form, draft, or screenshot should never be mistaken for proof that submission finished.
How should defects and portal failures be managed?
Maintain a filing event log. Record the time, action, screen or reference number, operator, result, and stored evidence. If a portal error appears, capture the full screen without exposing credentials, record the attempted action and time, and escalate under the current official channel. Do not improvise a deadline position from a technical failure.
When a defect communication arrives, classify it:
| Defect class | Example operational response | Closure evidence |
|---|---|---|
| Identifier mismatch | Compare source records and obtain approved correction | Corrected filing plus acknowledgement |
| Missing enclosure | Confirm required item and approved version | Upload receipt and updated register |
| Signature or authority | Refer to counsel and authorised signatory | Accepted replacement or registry record |
| Legibility or format | Recreate from controlled source | Visual check and portal receipt |
| Limitation concern | Immediate professional review | Filed response and supporting evidence |
Keep the original communication, response, attachments, and proof of closure together. A status of “sent” is not closure; the responsible professional should confirm what the registry or portal reflects.
When is the appeal file ready for hearing preparation?
Do not wait for listing to reconstruct the file. After filing, reconcile the filed set against the document register, record any admitted or pending applications, and convert the issue map into a hearing plan. For each ground, link the order passage, record page, statutory material, authority proposition, and person responsible for verification.
Use the court filing readiness checklist for a broader quality-control model and Gotham's legal corpus when evaluating source discovery. Every cited proposition still needs source-level verification by the legal team.
The matter can move to hearing preparation when the acknowledgement is preserved, defects are tracked, the filed version is immutable, deadlines and listing monitoring have named owners, and counsel can trace every ground to the source record. Teams that want to make this process repeatable can explore legal workflows or contact Gotham to discuss controlled intake, review, and evidence capture.
