Australia pre-filing checklist: forms, deadlines, service and proof

Task definition: Pre

At Task definition: Pre, perform an adversarial check of the proposed position. Assume the recipient disputes the topic markers pre, filing, checklist, forms, deadlines, service, proof and asks for the source of every date, amount, obligation, and procedural assertion. The response must come from the source document, relevant agreement or decision, correspondence, calculations, official forms, proof of delivery, and any record needed to verify dates or amounts, not from repetition. Re-test what event created the issue, which rule governs, which facts remain disputed, what evidence is reliable, which deadline applies, and what outcome is legally and practically available and consider using a generic template, relying on stale guidance, treating assumptions as facts, filing with the wrong body, or asking for an outcome outside the recipient's authority. The finished section should still support a verified legal-document plan with current sources, evidence references, a controlled chronology, explicit assumptions, and a measurable requested result after that challenge.

Use Task definition: Pre to separate law, evidence, inference, and request. In the “Australia pre-filing checklist: forms, deadlines, service and proof” file, the evidence set is the source document, relevant agreement or decision, correspondence, calculations, official forms, proof of delivery, and any record needed to verify dates or amounts; the legal control comes from current legislation, official procedural guidance, the governing agreement or decision, and the rules of the body that will receive the document; and the decision question is what event created the issue, which rule governs, which facts remain disputed, what evidence is reliable, which deadline applies, and what outcome is legally and practically available. Mixing those layers is especially dangerous because using a generic template, relying on stale guidance, treating assumptions as facts, filing with the wrong body, or asking for an outcome outside the recipient's authority. Keep each layer explicit so a reviewer can identify whether a weakness is factual, legal, procedural, or merely drafting.

Governing source: Filing

At Governing source: Filing, perform an adversarial check of the proposed position. Assume the recipient disputes the topic markers pre, filing, checklist, forms, deadlines, service, proof and asks for the source of every date, amount, obligation, and procedural assertion. The response must come from the source document, relevant agreement or decision, correspondence, calculations, official forms, proof of delivery, and any record needed to verify dates or amounts, not from repetition. Re-test what event created the issue, which rule governs, which facts remain disputed, what evidence is reliable, which deadline applies, and what outcome is legally and practically available and consider using a generic template, relying on stale guidance, treating assumptions as facts, filing with the wrong body, or asking for an outcome outside the recipient's authority. The finished section should still support a verified legal-document plan with current sources, evidence references, a controlled chronology, explicit assumptions, and a measurable requested result after that challenge.

Governing source: Filing should also account for sequence. For “Australia pre-filing checklist: forms, deadlines, service and proof”, a correct fact stated at the wrong procedural moment can still damage the result. Align the chronology, any notice or filing step, and the requested action with current legislation, official procedural guidance, the governing agreement or decision, and the rules of the body that will receive the document. Use the source document, relevant agreement or decision, correspondence, calculations, official forms, proof of delivery, and any record needed to verify dates or amounts to verify the sequence. The section is complete only when it shows how the verified facts move from the present stage toward a verified legal-document plan with current sources, evidence references, a controlled chronology, explicit assumptions, and a measurable requested result without triggering using a generic template, relying on stale guidance, treating assumptions as facts, filing with the wrong body, or asking for an outcome outside the recipient's authority.

Chronology: Checklist

Use Chronology: Checklist to separate law, evidence, inference, and request. In the “Australia pre-filing checklist: forms, deadlines, service and proof” file, the evidence set is the source document, relevant agreement or decision, correspondence, calculations, official forms, proof of delivery, and any record needed to verify dates or amounts; the legal control comes from current legislation, official procedural guidance, the governing agreement or decision, and the rules of the body that will receive the document; and the decision question is what event created the issue, which rule governs, which facts remain disputed, what evidence is reliable, which deadline applies, and what outcome is legally and practically available. Mixing those layers is especially dangerous because using a generic template, relying on stale guidance, treating assumptions as facts, filing with the wrong body, or asking for an outcome outside the recipient's authority. Keep each layer explicit so a reviewer can identify whether a weakness is factual, legal, procedural, or merely drafting.

At Chronology: Checklist, perform an adversarial check of the proposed position. Assume the recipient disputes the topic markers pre, filing, checklist, forms, deadlines, service, proof and asks for the source of every date, amount, obligation, and procedural assertion. The response must come from the source document, relevant agreement or decision, correspondence, calculations, official forms, proof of delivery, and any record needed to verify dates or amounts, not from repetition. Re-test what event created the issue, which rule governs, which facts remain disputed, what evidence is reliable, which deadline applies, and what outcome is legally and practically available and consider using a generic template, relying on stale guidance, treating assumptions as facts, filing with the wrong body, or asking for an outcome outside the recipient's authority. The finished section should still support a verified legal-document plan with current sources, evidence references, a controlled chronology, explicit assumptions, and a measurable requested result after that challenge.

Evidence: Forms

For Evidence: Forms, write from the remedy backwards. The intended destination is a verified legal-document plan with current sources, evidence references, a controlled chronology, explicit assumptions, and a measurable requested result; therefore every factual paragraph about pre, filing, checklist, forms, deadlines, service, proof should either establish an element, answer an expected objection, support a calculation, or prove a procedural step. Verify the position against current legislation, official procedural guidance, the governing agreement or decision, and the rules of the body that will receive the document. Material that does none of those jobs should be shortened, moved to an exhibit note, or removed from the operative document.

Evidence: Forms should also account for sequence. For “Australia pre-filing checklist: forms, deadlines, service and proof”, a correct fact stated at the wrong procedural moment can still damage the result. Align the chronology, any notice or filing step, and the requested action with current legislation, official procedural guidance, the governing agreement or decision, and the rules of the body that will receive the document. Use the source document, relevant agreement or decision, correspondence, calculations, official forms, proof of delivery, and any record needed to verify dates or amounts to verify the sequence. The section is complete only when it shows how the verified facts move from the present stage toward a verified legal-document plan with current sources, evidence references, a controlled chronology, explicit assumptions, and a measurable requested result without triggering using a generic template, relying on stale guidance, treating assumptions as facts, filing with the wrong body, or asking for an outcome outside the recipient's authority.

Deadline: Deadlines

A useful general analysis changes when the facts change. At Deadline: Deadlines, compare the chronology for “Australia pre-filing checklist: forms, deadlines, service and proof” with the source document, relevant agreement or decision, correspondence, calculations, official forms, proof of delivery, and any record needed to verify dates or amounts, then ask what event created the issue, which rule governs, which facts remain disputed, what evidence is reliable, which deadline applies, and what outcome is legally and practically available. This comparison should expose contradictions before they become pleadings, notices, or demands. Pay particular attention to using a generic template, relying on stale guidance, treating assumptions as facts, filing with the wrong body, or asking for an outcome outside the recipient's authority. Where two records conflict, preserve both versions and explain which fact is still disputed rather than silently selecting the more convenient account.

For Deadline: Deadlines, write from the remedy backwards. The intended destination is a verified legal-document plan with current sources, evidence references, a controlled chronology, explicit assumptions, and a measurable requested result; therefore every factual paragraph about pre, filing, checklist, forms, deadlines, service, proof should either establish an element, answer an expected objection, support a calculation, or prove a procedural step. Verify the position against current legislation, official procedural guidance, the governing agreement or decision, and the rules of the body that will receive the document. Material that does none of those jobs should be shortened, moved to an exhibit note, or removed from the operative document.

Recipient: Service

Use Recipient: Service to separate law, evidence, inference, and request. In the “Australia pre-filing checklist: forms, deadlines, service and proof” file, the evidence set is the source document, relevant agreement or decision, correspondence, calculations, official forms, proof of delivery, and any record needed to verify dates or amounts; the legal control comes from current legislation, official procedural guidance, the governing agreement or decision, and the rules of the body that will receive the document; and the decision question is what event created the issue, which rule governs, which facts remain disputed, what evidence is reliable, which deadline applies, and what outcome is legally and practically available. Mixing those layers is especially dangerous because using a generic template, relying on stale guidance, treating assumptions as facts, filing with the wrong body, or asking for an outcome outside the recipient's authority. Keep each layer explicit so a reviewer can identify whether a weakness is factual, legal, procedural, or merely drafting.

The practical output of Recipient: Service should move the matter toward a verified legal-document plan with current sources, evidence references, a controlled chronology, explicit assumptions, and a measurable requested result. Do not fill space with a standard legal template. Instead, test each sentence against the topic phrase pre, filing, checklist, forms, deadlines, service, proof, the selected Australia forum, and the governing source. The controlling material should include current legislation, official procedural guidance, the governing agreement or decision, and the rules of the body that will receive the document. If an assumption remains unresolved, identify it openly and state what record or official source would resolve it.

Remedy: Proof

For Remedy: Proof, write from the remedy backwards. The intended destination is a verified legal-document plan with current sources, evidence references, a controlled chronology, explicit assumptions, and a measurable requested result; therefore every factual paragraph about pre, filing, checklist, forms, deadlines, service, proof should either establish an element, answer an expected objection, support a calculation, or prove a procedural step. Verify the position against current legislation, official procedural guidance, the governing agreement or decision, and the rules of the body that will receive the document. Material that does none of those jobs should be shortened, moved to an exhibit note, or removed from the operative document.

The practical output of Remedy: Proof should move the matter toward a verified legal-document plan with current sources, evidence references, a controlled chronology, explicit assumptions, and a measurable requested result. Do not fill space with a standard legal template. Instead, test each sentence against the topic phrase pre, filing, checklist, forms, deadlines, service, proof, the selected Australia forum, and the governing source. The controlling material should include current legislation, official procedural guidance, the governing agreement or decision, and the rules of the body that will receive the document. If an assumption remains unresolved, identify it openly and state what record or official source would resolve it.

Quality control: Pre

At Quality control: Pre, perform an adversarial check of the proposed position. Assume the recipient disputes the topic markers pre, filing, checklist, forms, deadlines, service, proof and asks for the source of every date, amount, obligation, and procedural assertion. The response must come from the source document, relevant agreement or decision, correspondence, calculations, official forms, proof of delivery, and any record needed to verify dates or amounts, not from repetition. Re-test what event created the issue, which rule governs, which facts remain disputed, what evidence is reliable, which deadline applies, and what outcome is legally and practically available and consider using a generic template, relying on stale guidance, treating assumptions as facts, filing with the wrong body, or asking for an outcome outside the recipient's authority. The finished section should still support a verified legal-document plan with current sources, evidence references, a controlled chronology, explicit assumptions, and a measurable requested result after that challenge.

Treat Quality control: Pre as an evidence checkpoint. For “Australia pre-filing checklist: forms, deadlines, service and proof”, assemble the source document, relevant agreement or decision, correspondence, calculations, official forms, proof of delivery, and any record needed to verify dates or amounts. Then label each item by date, source, author or issuer, and the proposition it proves. The principal failure mode in a general file is using a generic template, relying on stale guidance, treating assumptions as facts, filing with the wrong body, or asking for an outcome outside the recipient's authority. A document that names the risk but cannot point to the underlying record is not ready for filing, service, negotiation, or escalation.

Task definition: Filing

A useful general analysis changes when the facts change. At Task definition: Filing, compare the chronology for “Australia pre-filing checklist: forms, deadlines, service and proof” with the source document, relevant agreement or decision, correspondence, calculations, official forms, proof of delivery, and any record needed to verify dates or amounts, then ask what event created the issue, which rule governs, which facts remain disputed, what evidence is reliable, which deadline applies, and what outcome is legally and practically available. This comparison should expose contradictions before they become pleadings, notices, or demands. Pay particular attention to using a generic template, relying on stale guidance, treating assumptions as facts, filing with the wrong body, or asking for an outcome outside the recipient's authority. Where two records conflict, preserve both versions and explain which fact is still disputed rather than silently selecting the more convenient account.

A useful general analysis changes when the facts change. At Task definition: Filing, compare the chronology for “Australia pre-filing checklist: forms, deadlines, service and proof” with the source document, relevant agreement or decision, correspondence, calculations, official forms, proof of delivery, and any record needed to verify dates or amounts, then ask what event created the issue, which rule governs, which facts remain disputed, what evidence is reliable, which deadline applies, and what outcome is legally and practically available. This comparison should expose contradictions before they become pleadings, notices, or demands. Pay particular attention to using a generic template, relying on stale guidance, treating assumptions as facts, filing with the wrong body, or asking for an outcome outside the recipient's authority. Where two records conflict, preserve both versions and explain which fact is still disputed rather than silently selecting the more convenient account.

Primary sources to verify

• Federal Register of Legislation
• Federal Court of Australia
• AustLII
• ACCC