MCA compliance preparation for startup founders.

MCA compliance preparation, not portal automation

Founders often search for MCA compliance when they are not sure what information is needed before an official filing. Draft answers that intent by focusing on preparation: company facts, board approvals, registers, due-date context, and evidence storage. It does not log in to government portals or claim that a filing is complete just because a draft or checklist exists.

• Maintain company identifiers, registered office details, director records, capital information, and relevant dates before starting a filing task.
• Prepare draft resolutions, minutes, and internal notes that support common MCA workflows.
• Record the SRN, challan, acknowledgement, signed form, or professional note after the official filing step happens elsewhere.
• Keep a clear no-auto-submit guardrail for MCA, GST, income-tax, and other government systems.

Form-readiness examples for startup teams

Different MCA tasks need different supporting context. A founder preparing auditor appointment work may need board approval, auditor details, and proof of acceptance. A commencement declaration workflow may require incorporation and bank context. Annual filing preparation may require financial statements, board documents, AGM dates, and register updates. Draft makes those preparation questions visible before the user reaches the official portal.

• ADT-1 preparation: keep auditor appointment context, board record, professional details, and evidence together.
• INC-20A preparation: collect incorporation data, bank or subscription proof context, and declaration support before review.
• AOC-4 preparation: keep financial statement evidence, board approvals, and filing notes linked to the company workspace.
• MGT-7 or MGT-7A preparation: keep annual return inputs, shareholding context, director information, and proof records organized.

Deadline context that founders can understand

MCA compliance anxiety often comes from not knowing whether a task is urgent, optional, already done, or waiting on a professional. Draft presents the work as a preparation queue with plain-language status. Founders can see what is pending, what is blocked by missing information, what has been drafted, and what has proof after the official step is finished.

• Use incorporation date, AGM context, financial year, and company profile data to organize the preparation calendar.
• Separate pending preparation, ready for review, externally filed, and evidence stored states.
• Keep notes for who is responsible: founder, operations lead, CS, CA, or another advisor.
• Avoid overpromising: a reminder in Draft is not legal advice and a completed task still depends on official facts and professional review.

Evidence packs for future proof

MCA work does not end when a form is submitted. Startups later need proof for investors, banks, auditors, vendors, and internal governance. Draft gives teams a place to store the reviewed output and the official trace, so the next person can understand what happened without rebuilding the history from downloads and email attachments.

• Store SRNs, challans, receipts, signed documents, board packs, register exports, and supporting PDFs by company.
• Link generated drafts to the workflow that created them so a reviewer can trace the preparation path.
• Keep a simple evidence checklist for each MCA task rather than relying on one large shared drive.
• Make future due diligence easier by preserving both the document and the context around it.

How MCA preparation connects to the rest of Draft

A filing task rarely stands alone. It may depend on a board resolution, register data, director details, a letterhead, or a company stamp. Draft links these pieces across modules so founders can prepare more complete material for a CS or advisor before touching the official MCA portal.

• AI Drafter prepares board approvals and supporting documents from structured company data.
• Statutory Registers keep member, director, charge, loan, and related party information close to filing work.
• Asset Studio creates stamps and letterheads for operational paperwork where appropriate.
• Documents Vault stores reviewed records and official evidence after completion.

Founder questions