Patial v Kailash Lawyers Pty Ltd (No 2)

This decision is a procedural appeal judgment from the Federal Court of Australia. It does not resolve the underlying commercial or insolvency dispute between the parties. Instead, it explains why the Court dismissed the appeal on the hearing date.

The appellant was Prateek Patial. The respondent was Kailash Lawyers Pty Ltd. The appeal came from an earlier decision identified as Kailash Lawyers Pty Ltd v Patial [2025] FedCFamC2G 1432, but the published reasons in this case do not describe that earlier dispute in any detail. That is an important limit on how far this case can be used as a precedent for broader business issues.

What the reasons do show clearly is the procedural history. On 11 March 2026, Goodman J made orders listing the appeal for hearing on 11 May 2026. Those orders also set deadlines for the appellant to file written submissions and an appeal book. The appellant was present in court when those orders were pronounced, and the entered orders were sent to both parties.

The appellant then failed to meet the timetable. He did not file written submissions by 9 April 2026. He also did not file appeal books by 28 April 2026. A few days before the hearing, on 4 May 2026, he emailed the judge's Associate and others, including the respondent's solicitor, asking for clarification about whether the appeal was still on foot and seeking directions about finalising the appeal book. In that email, he said he remained committed to complying with the Court's directions and procedures.

The Court responded by listing the matter for case management at 9:00 am on 6 May 2026. The appellant did not appear at that case management hearing either. At that hearing, counsel for the respondent said that, to preserve the hearing date, the respondent had prepared appeal books itself. The Court then made further orders requiring the respondent to file and serve those appeal books and its written submissions, and giving the appellant a final short opportunity to file his own submissions and any additional documents. The Court expressly confirmed that the appeal hearing would proceed on 11 May 2026.

When the appeal was called on for hearing at 10:16 am on 11 May 2026, the appellant again did not appear. The Court stood the matter down until 10:30 am in case he was merely late. When the hearing resumed, counsel for the respondent applied for dismissal under r 36.75 of the Federal Court Rules 2011 (Cth).

The key legal point in the judgment is narrow but important. The Court applied r 36.75 of the Federal Court Rules 2011 (Cth). The reasons specifically refer to r 36.75(1)(a)(i). The Court said the preconditions for exercising the discretion under that rule were plainly met because two things had happened. First, the appellant was absent when the appeal was called on for hearing. Second, the respondent applied for dismissal.

That means this was not a decision about whether the appellant's arguments were legally strong or weak. It was a decision about whether the appeal should continue at all when the appellant had not turned up and the respondent asked the Court to dismiss it. The Court then had to decide whether, as a matter of discretion, dismissal was the appropriate course.

The reasons show that the Court did not look at non-attendance in isolation. It considered the broader procedural context. The appellant had already failed to file written submissions. He had failed to file appeal books. He had failed to attend the case management hearing that had been convened after his own email seeking clarification and directions. He was plainly on notice that the hearing remained listed for 11 May 2026. The Court also noted that he had not notified the Court or the respondent that he did not propose to appear.

For businesses, the significance of r 36.75 in this case is practical. If you are the appellant in a Federal Court appeal, your absence at the hearing can trigger a dismissal application. If there is also a history of missed deadlines or non-attendance, the risk of dismissal becomes much more serious.

Goodman J dismissed the appeal and ordered the appellant to pay the respondent's costs of the appeal as agreed or taxed. The Court's reasoning was short and direct.

First, the Court found that the threshold requirements for r 36.75(1)(a)(i) were satisfied. The appellant was absent when the appeal was called on for hearing, and the respondent had applied for dismissal.

Second, the Court exercised its discretion to dismiss the appeal. The reasons identify the circumstances that supported that result. The appellant had failed to file written submissions. He was plainly on notice that the appeal was listed for hearing on 11 May 2026. The Court said that was clear from the 11 March 2026 orders and from the appellant's own 4 May 2026 email, and it was confirmed again in the 6 May 2026 orders. Despite that notice, the appellant failed to appear not only at the hearing itself but also at the case management hearing on 6 May 2026. That case management hearing had been convened following the appellant's own request for clarification. The Court also noted that the appellant had not told the Court or the respondent that he did not propose to appear.

The result is important because it shows the Court was not dealing with a single accidental omission. The reasons describe repeated non-compliance and repeated non-attendance. That pattern mattered to the exercise of discretion.

It is also worth noting what the Court did not decide. The reasons do not analyse the merits of the appeal. They do not explain whether the appellant had an arguable substantive case. They do not resolve the underlying dispute between the parties. The published judgment is therefore best understood as a procedural dismissal decision with a costs consequence.

For business owners, this case is a reminder that litigation has two separate dimensions. One is the underlying legal dispute. The other is the procedural machinery that keeps the case alive. A party can believe strongly in its legal position and still lose because it does not comply with orders, prepare the required documents, or attend hearings.

That is especially relevant in owner-managed businesses, where the same person may be dealing with customers, staff, cash flow and a court matter at the same time. In practice, procedural failures often happen because no one is managing the case as a disciplined project. Deadlines are missed. Court books are left too late. Emails are sent instead of formal steps being taken. Hearing dates are assumed to be flexible when they are not.

This case also shows that the other side may continue preparing the matter even if you do not. Here, the respondent prepared appeal books in order to maintain the hearing date. That did not save the appellant. Instead, it reinforced the procedural contrast between the parties and contributed to a costs order after dismissal.

Businesses should also be careful not to overread the decision. It is not a broad statement about insolvency law, legal services disputes, or corporate governance. The published reasons simply do not contain enough detail for that. Its value lies in the procedural lesson: if you are in an appeal, the Court expects active prosecution or active defence. Silence, delay and non-attendance can end the matter.

If your business cannot comply with a timetable, the safer course is to act early. Get advice, consider whether a formal application is needed, and communicate in the proper way before the hearing date arrives. Waiting until the last moment, or failing to appear after asking the Court for clarification, creates obvious risk.

The judgment is useful because it identifies the exact procedural events that led to dismissal. Those events are the practical warning signs businesses should watch for in their own matters.

First, there were clear court orders made on 11 March 2026. Those orders listed the appeal for hearing on 11 May 2026 and set a timetable for submissions and the appeal book. The appellant was present when those orders were made, and the entered orders were sent to the parties. That meant there was little room for later uncertainty about the timetable.

Second, the appellant missed the filing deadlines. Written submissions were due by 9 April 2026 and were not filed. Appeal books were due by 28 April 2026 and were not filed. In an appeal, those are central documents. Without them, the hearing cannot proceed in the ordinary way.

Third, the appellant's 4 May 2026 email mattered because it showed he knew the matter was listed for hearing on 11 May 2026 and was seeking clarification and directions shortly before that date. The Court later relied on that email as part of the basis for finding that he was plainly on notice of the hearing.

Fourth, the appellant did not attend the case management hearing on 6 May 2026, even though that hearing had been listed after his own email. The Court then made further orders that day, including a final short timetable for the appellant and an express confirmation that the hearing on 11 May 2026 would proceed.

Fifth, the appellant did not appear when the appeal was called on for hearing on 11 May 2026. The Court allowed a short adjournment in case he was running late. When he still did not appear, the respondent applied for dismissal under r 36.75.

For businesses, these events show the kinds of conduct that can shape a procedural outcome. Courts look at the whole pattern: notice, missed deadlines, attendance, communications, and whether the party has told the Court if it does not intend to appear.

If your business is involved in an appeal, a simple control system can reduce the risk of the kind of outcome seen here. Start with the orders. Make sure someone in the business has the current sealed orders, understands what each order requires, and has entered every date into a calendar that will actually be monitored.

Next, separate legal responsibility from administrative responsibility. Even if external lawyers are acting, someone inside the business should still track deadlines, hearing dates and document status. If the business is self-represented, this becomes even more important. Appeals involve formal documents and strict timetables. They are not well suited to ad hoc management.

Then focus on hearing readiness. Confirm whether the hearing is in person or by another method, who will appear, what documents must be filed beforehand, and whether the appeal books are complete. If there is any problem, address it before the hearing date. The published reasons in this case show how damaging it can be to leave matters unresolved and then fail to appear.

Finally, keep costs in mind. Here, the appeal was dismissed and the appellant was ordered to pay the respondent's costs of the appeal as agreed or taxed. Procedural default can therefore create a double loss: the case ends, and the business may also have to pay the other side's costs.

The key dates in the published reasons are straightforward. Orders listing the appeal and setting the timetable were made on 11 March 2026. The appellant's written submissions were due on 9 April 2026. The appeal books were due on 28 April 2026. The appellant sent an email seeking clarification on 4 May 2026. The Court listed the matter for case management on 6 May 2026, and the appellant did not appear. The appeal hearing took place on 11 May 2026, when the appellant again did not appear and the appeal was dismissed. The reasons were published on 13 May 2026.

The status of the case, based on the published reasons, is that the appeal was dismissed and a costs order was made against the appellant. The reasons do not indicate any further procedural step beyond that order.