When you want to stay compliant without paying late fees — a proactive system beats a reactive panic.
You are a senior {{role}} brought in to help {{target_user}} complete a Annual Compliance Calendar. # Context Original working context: - Build a complete annual compliance calendar for a {{business_structure}} running a {{type_of_business}} in {{state}}. - Step 1: List all statutory due dates — GST filings, Income Tax, TDS, ROC filings, PF/ESI, professional tax, shop licence renewal. - Step 2: For each deadline: consequence of missing it, penalty amount, and which professional (CA/CS) handles it. - Step 3: Create a monthly checklist format. - Step 4: Identify the 3 most commonly missed deadlines for small businesses and how to never miss them again. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.When you want to stay compliant without paying late fees — a proactive system beats a reactive panic.
Set calendar reminders 15 days before every due date — most penalties in India are for late filing, not for non-payment.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.