BASICS | Practical Templates Appendix

This appendix provides procedurally orthodox templates that mirror the Basics doctrine. Each template is narrow, factual, and designed to sit inside an existing legal process. No pseudo‑legal language is used. Templates may be adapted to jurisdiction and matter type. These templates are a guide only and should include recommended inclusions (depending on the seriousness/stage of the matter).

Notes
– To: The intended recipient should have a name, find the wo/man who is the head of that agency.
– Re: Quote EXACTLY the claim with identifiable reference

Jump to:

  1. Request for Reasons and Particulars
  2. Conditional Acceptance of an Allegation or Demand

  3. Request to Confirm Statutory Authority and Scope

  4. Request for Proof of Standing

  5. Objection to Jurisdiction

  6. Request for Proof of Service

  7. Recording a Procedural Defect

  8. Escalation After Non‑Response

  9. Standard Sign-off Block

  10. Based on these basic principles
  11. Inspired by these two videos

Template 1 — Request for Reasons and Particulars (General)

To: [Decision-maker / Review Officer]

Re: [Matter reference, notice number]

This request relates solely to the decision / notice dated [date].

To enable proper consideration of the matter and to preserve my rights, please provide:

  1. The statutory provision relied upon to make the decision or issue the notice;

  2. The identity of the authorised decision-maker and confirmation of their authority or delegation;

  3. The evidence relied upon to support the decision;

  4. Confirmation that procedural fairness requirements were met;

  5. Details of available review or appeal rights and applicable timeframes.

This request is made within the relevant statutory framework.

 

Template 2 — Conditional Acceptance of an Allegation or Demand

To: [Issuing authority]

Re: [Matter reference]

I acknowledge receipt of the above notice.

I conditionally accept the allegation / demand, subject to confirmation that it has been lawfully issued, is supported by proper authority, and complies with statutory and procedural requirements.

To that end, please provide the particulars and full disclosure of all evidence and material relied upon, whether directly or indirectly, in support of the claim.

Nothing in this correspondence is to be taken as an admission of liability or a waiver of rights.

 

Template 3 — Request to Confirm Statutory Authority and Scope (Regulator)

To: [Regulatory body]

Re: [Regulatory request / correspondence dated]

Before responding substantively, please confirm:

  1. The specific statutory power under which the request is made;

  2. Whether compliance is mandatory or voluntary;

  3. The consequences of non‑compliance;

  4. Whether the request is administrative, civil, or enforcement in nature;

  5. The authorised officer responsible for the decision.

This request is made to clarify the legal basis and scope of the request.

 

Template 4 — Request for Proof of Standing

To: [Applicant / Issuer]

Re: [Proceeding or notice]

Please provide particulars establishing standing to bring or issue the above action, including:

  1. Identification of the applicant;

  2. The interest or loss relied upon;

  3. Authority to commence or pursue the action on behalf of any other entity.

This request is made prior to engaging on substantive issues.

 

Template 5 — Objection to Jurisdiction (Procedural)

To: [Court / Tribunal / Authority]

Re: [Matter reference]

The Respondent objects to jurisdiction on the basis that:

  • standing has not been established;

  • statutory authority has not been identified; and/or

  • the pleadings fail to disclose a proper basis for jurisdiction.

The Respondent seeks that these threshold issues be determined prior to any consideration of substance.

 

Template 6 — Request for Proof of Service

To: [Issuing authority]

Re: [Notice reference]

Please provide proof that service of the above notice was effected in accordance with the applicable statutory requirements, including the date, method, and address for service.

 

Template 7 — Recording a Procedural Defect

To: [Authority / Court]

Re: [Matter reference]

For the record, the following procedural issue is noted:

  • [e.g. failure to provide reasons / failure to identify authority / missed statutory timeframe].

This correspondence records the issue without waiving any rights or remedies.

 

Template 8 — Escalation After Non‑Response

To: [Authority / Review body]

Re: [Matter reference]

On [date], a request for [reasons / particulars / authority] was made.

As no response has been received within the applicable timeframe, please advise whether the matter will be withdrawn, reviewed, or otherwise addressed.

This correspondence is made to preserve procedural rights.

 

Use Notes (Not for Sending)

  • Each template must be tied to one matter only.

  • Replace placeholders precisely; do not broaden scope.

  • Use correct service methods for the forum.

  • Retain copies and proof of service.

These templates are procedural tools. They do not argue merits and do not rely on declaration, consent theories, or silence as agreement.

 

Standard Sign-off Block (Correspondence)

The following sign-off block may be used consistently across all templates in this appendix where correspondence (not formal execution of deeds or affidavits) is intended:

Authored by:

______________________________
John Henry
pp / agent for JOHN HENRY DOE

Date: ___ / ___ / ______

This formulation records authorship and stated capacity only. It does not assert authority beyond the document itself and is suitable for procedural notices, requests, and correspondence.

 

BASICS

Procedural Notices, Standing, and Jurisdiction

This document consolidates the content into a single, clean reference. It preserves the original substance and structure, while adding limited clarification where appropriate to improve usability and internal coherence. No new doctrines are introduced.


1. Threshold Questions (Before Anything Else)

Before engaging on substance, the following threshold questions must be capable of being answered:

  • Under what enactment is jurisdiction asserted?
  • Is the action administrative, civil, regulatory, or criminal in nature?
  • Is the proceeding in personam or in rem?
  • Who is the proper applicant with standing?

These are not notices. They are threshold challenges.

If these questions are not answered, the matter cannot lawfully advance.


2. Standing

Most enforcement actions collapse on standing if it is tested early.

Standing questions include:

  • Who is the applicant?
  • What loss have they suffered?
  • Are they the proper party?
  • Is the action brought by the correct legal person?

No standing = no jurisdiction.

Courts must deal with standing, pleadings, and jurisdiction before reaching substance.


3. Authority and Delegation

Where an action is taken by an official or agency, you may require:

  • The instrument of delegation
  • Proof of decision‑maker authority
  • Evidence relied upon
  • A record of reasons

This does not invite debate. It forces process.


4. Statutory Compliance Checks

Every statutory action has mandatory procedural steps. Common examples include:

  • Timeframes
  • Service requirements
  • Opportunity to be heard

You do not argue ideology. You ask:

  • Has the relevant statutory section been complied with?
  • On what date was notice served?
  • Where is proof of service?

Failure at this level creates real leverage.


5. Identify the Arena

Before issuing notices or correspondence, identify the legal arena:

  • Administrative
  • Civil enforcement
  • Regulatory
  • Criminal

Different arenas operate under different rules and remedies.

No notices should be issued until this is clear.


6. Ask, Don’t Assert

Assertions trigger dismissal. Questions compel answers.

All communications should be framed as:

  • Requests for clarification
  • Requests for particulars
  • Requests for evidence

Courts and agencies are obliged to respond to these if they wish to proceed.


7. Enforce Procedure

Track and preserve the following:

  • Deadlines
  • Service
  • Form
  • Authority
  • Evidence

Most actions fail on procedure before substance when procedure is properly enforced.


8. Preserve Credibility

To remain effective:

  • Avoid pseudo‑legal language
  • Avoid moral declarations
  • Avoid grand theory
  • Stick to recognised legal concepts

This keeps doors open and signals competence rather than ideology.


9. Escalate Only When Leverage Exists

Escalation without leverage is noise.

Escalation becomes effective only where there is:

  • Missed deadlines
  • Absent or defective authority
  • Defective service
  • Lack of standing

That is what creates outcomes.


10. Why Notices Fail

Notices commonly fail because they:

  • Attempt to create law instead of using it
  • Assert instead of testing
  • Declare instead of compelling
  • Assume silence has legal meaning

Law responds to structure, not volume.

One precise procedural step in the correct jurisdiction is more effective than many unanswered notices.


11. When Notices Work

Notices work only when they sit inside an existing legal process. That requires:

  • A defined matter or dispute
  • A specific decision, action, or demand
  • A recognised legal relationship (statutory, contractual, or procedural)
  • A forum capable of enforcing consequences

12. Specificity

Effective notices are:

  • Tied to one event
  • Dated
  • Referenced to one statute, clause, or power
  • Directed to the actual decision‑maker
  • Limited in scope

They say, in substance:

“In this matter, on this date, under this power, you failed to do X.”

That creates a record the system cannot ignore.


13. Umbrella Notices

Umbrella or “global” notices fail because they:

  • Assert broad theories
  • Target institutions generally
  • Allege global wrongdoing
  • Lack a live cause of action

Courts treat these as opinion, not evidence.

So‑called “bandit‑style” notices fail because they try to:

  • Impose duties globally
  • Bind people without capacity
  • Create jurisdiction by declaration
  • Collapse public law into private equity
  • Rely on silence as agreement

They sit outside process and produce no leverage or remedy.


14. The Core Rule for Notices

A notice works only when it:

  • Sits inside jurisdiction
  • Relates to a specific act or omission
  • Triggers an existing legal obligation
  • Preserves evidence or rights
  • Points toward an enforceable next step

If it does not change the procedural landscape, it is just correspondence.


15. What Actually Works (Examples)

Requests for Reasons / Particulars

A proper procedural notice may request:

  • Identification of the authorised decision‑maker
  • The statutory provision relied upon
  • Evidence supporting each alleged element
  • Proof of service
  • Confirmation of review rights and timeframes

This works because it is tied to one notice, triggers obligations, preserves rights, and creates leverage if unanswered.


16. Regulator Context

What fails:

Broad notices asserting “no consent”, “no contract”, or “breach of trust”. Regulators act under statute, not contract.

What works:

Procedural notices requiring regulators to confirm:

  • The specific statutory power relied upon
  • Whether compliance is mandatory or voluntary
  • Consequences of non‑compliance
  • The nature of the action
  • The authorised officer responsible

17. Court Context

What fails:

Declaratory notices to the court asserting lack of legitimacy, fraud, no consent, or breach of trust.

Courts do not accept jurisdictional declarations by notice.

What works:

Proper procedural filings, including:

  • Objections to jurisdiction
  • Applications for further and better particulars
  • Applications to strike out defective pleadings
  • Requests for proof of standing

18. Rewriting Ineffective Notices

Broad, emotional notices can be rewritten into enforceable instruments by:

  • Narrowing them to a specific decision
  • Requesting authority, delegation, evidence, and procedural compliance
  • Stating the purpose as assessment of validity and preservation of rights

Courts respect narrow, factual, procedural paper trails.


19. Agency: “Notice to Agent is Notice to Principal”

This phrase is frequently misused.

It is not:

  • A jurisdiction‑creator
  • A way to bypass service rules
  • A substitute for standing

It only works where:

  • A real agency relationship already exists
  • The agent is authorised to receive notice
  • The notice falls within that authority
  • Service complies with governing rules

Agency cannot be created by declaration.

Frontline staff, clerks, and call‑centre personnel are not agents for liability. Employment alone does not create agency.


20. Where Agency Rules Do Apply

The rule operates in narrow, legitimate contexts:

  • Contractual agency — where an authorised agent manages the contract and service follows agreed terms
  • Statutory agency — where legislation names the agent and service method
  • Legal representation — within a lawyer’s retainer and court rules
  • Insurance and intermediaries — where authority is express and specific

21. Final Principle

Agency must exist first. Authority must cover the notice. Service must comply with rules.

Miss any one element, and the notice does nothing.

Procedural notices do not try to change the system. They force the system to prove itself.

That is where outcomes occur.

The inspiration for this information:

Part 1

Part 2

Last Updated 7 months ago

Views: 286

Posted by Jillian