Did JobKeeper save Australia's economy from COVID-19?

When COVID-19 struck, Australia’s Treasury didn’t have the luxury of years of work, refinement and debate to develop JobKeeper – it had to perform battlefield surgery, writes UNSW Business School's Richard Holden

To the critics, the Treasury has just marked “its own homework”. It has produced a 60-page report entitled Insights from the first six months of JobKeeper. And it finds the A$89 billion program it designed and delivered held up pretty well last year at the time Australia needed it most.

As with the Labor government’s economic rescue programs during the global financial crisis, there are critics claiming it was wasteful, this time from the Labor side of politics. But they have exceedingly short memories. In the first week of March 2020, Australia had 93 COVID-19 cases and three deaths. The prime minister said he was “going to the footy” and “looking forward to it”, at a time when medical experts were calling for people to do no such thing and a quarter of Italy was locked down. Italian tourists were coming in freely. We were sleepwalking into a calamity.

Was JobKeeper enough to stave off the economic after effects of COVID-19 in Australia_.jpeg
JobKeeper provided six months of financial support to almost every single business in Australia during the COVID-19 pandemic. Image: Shutterstock

The way we were

On March 10 last year, I wrote that we needed to close our international border totally and immediately and spend about $100 billion to support workers and business while we shut down the economy and got health measures in place. On March 20 the borders were closed. Treasury forecast that if we had to lock down as hard as Italy or Spain our economy (GDP) would collapse by 24 per cent. That wouldn’t be a mere recession or even a depression. It would be economic and financial Armageddon. The government needed to plug an unimaginable hole quickly. And it did.

JobKeeper provided six months of financial support to businesses that expected their revenues to drop. At the time, that was almost every business in the country. It was designed to be easy to understand and to get money onto business and household balance sheets immediately. Most importantly, it was designed to give recipients certainty in a time of calamitous uncertainty. These are facts. They are undisputed.

Read more: Business insolvency rates show post-Jobkeeper fallout yet to emerge

What the critics say now

From the safety of the present day, critics point out that JobKeeper excluded certain industries and workers: short-term casuals and universities among them. And they say $19.7 billion went to businesses whose revenues increased in the three months they received the payment.

It would have been better, they say, not to spend the money on businesses that turned out to have rising revenues, and it would have been good to include short-term casuals and universities. JobKeeper should have included a “clawback” provision, they say. They are right. It would have been better had it been designed in that way. But they are taking insufficient account of what things were like at the time.

The Australian Treasury building in Canberra.jpeg
The Treasury developed the JobKeeper program within a matter of days before its announcement on 30 March 2020. Image: Shutterstock

What things were like then

The context for the development of JobKeeper was a once-in-a-century event, with a government in power whose entire political brand had been railing against “debt and deficits”. Economists were concerned the government might do too little, or nothing at all. There are three things worth noting:

  • Treasury had to act incredibly quickly, in a matter of days. I like an academic seminar as much as the next person, but Treasury didn’t have the luxury of years of work, refinement and debate. It had to perform battlefield surgery.
  • A key reason so many businesses were able to increase revenues after JobKeeper began was that it was so effective. A smaller scheme, with more requirements and red tape, would have meant fewer workers and businesses would have received support, leaving the whole economy worse off.
  • The more carve-outs and exclusions from JobKeeper the less effective it was likely to be. Fine-tuning rules creates uncertainty. It provides scope for gaming (getting around the rules). If we want public programs to have force, they need to be simple.

The real choice in March 2020 was JobKeeper as it was or no JobKeeper at all.

If we want public programs to have force, they need to be simple..jpg
Australia's economic JobKeeper experiment proves public programs must be simple to be effective. Image: Shutterstock

We saved the patient

In early March 2020, the Australian economy was critically ill. Doctors Josh Frydenberg (Treasurer) and Steven Kennedy (Treasury Secretary) saved the patient. That’s what matters. Did they use ECG machines, blood bags, gauze and stitches? You bet. Did it cost economic resources? Probably, although had the worst had happened even more resources might have been used. 

Insurance can look wasteful after the fact, but that doesn’t make it unwise. I am glad they erred on the side of too many stitches rather than too few. They provided the only thing that can really help in times of extreme uncertainty, which is a certainty.

Richard Holden is a Professor of Economics at UNSW Business School, director of the Economics of Education Knowledge Hub @UNSWBusiness, co-director of the New Economic Policy Initiative, and President-elect of the Academy of the Social Sciences in Australia. His research expertise includes contract theory, law and economics, and political economy. A version of this post first appeared on The Conversation.


You are free to republish this article both online and in print. We ask that you follow some simple guidelines.

Please do not edit the piece, ensure that you attribute the author, their institute, and mention that the article was originally published on Business Think.

By copying the HTML below, you will be adhering to all our guidelines.

Press Ctrl-C to copy