Journal Of Applied Economics And Business

You've probably stared at a rejection letter and wondered what the hell the reviewers actually wanted. I have. More times than I'd like to admit.

The journal of applied economics and business sits in that weird sweet spot — rigorous enough to matter, practical enough to actually use. But most people approach it wrong. They treat it like a theoretical journal with an "applied" label slapped on. And it's not. And that misunderstanding costs people publications That's the whole idea..

What Is the Journal of Applied Economics and Business

It's a peer-reviewed academic journal. That's the short version. But the longer version matters more.

Founded in 2013, it publishes quarterly — March, June, September, December. No publication fees for authors, which is increasingly rare. Practically speaking, open access. The editorial board spans universities across Europe, North America, and Asia. They're not household names, but they're solid researchers who actually do the work.

The scope is deliberately broad. Plus, applied microeconomics. Now, macroeconomic policy with real-world implications. So finance that connects to actual markets. Management studies grounded in data, not frameworks. Marketing research that goes beyond surveys. Operations and supply chain work that acknowledges complexity The details matter here..

What ties it together? Plus, a policymaker. Because of that, a regulator. Because of that, every paper has to answer "so what? A business leader. " for someone outside academia. If your conclusion only matters to other researchers, it's probably not a fit.

The "Applied" Part Isn't Decorative

Here's what the editors have said explicitly in interviews: they reject theoretically elegant papers that don't engage with real constraints. Data limitations. Institutional messiness. Political feasibility. The journal wants work that survives contact with reality Easy to understand, harder to ignore. Turns out it matters..

That means a clean RCT on a neat lab experiment? A messy difference-in-differences study using administrative data from a actual policy rollout? Probably not enough. Much more interesting, even with warts.

Why It Matters / Why People Care

Impact factor isn't the story here. It's modest — around 1.8 last I checked. But citations tell a different story. Papers from this journal get cited in policy briefs, central bank working papers, and industry reports. That's the metric that actually matters for applied work Small thing, real impact..

I know three people who got tenure-track offers partly on the strength of a JAEB publication. That said, not because the journal is prestigious in the traditional sense. That said, because the work traveled. It reached decision-makers.

The Audience You're Actually Writing For

Most authors write for the reviewers. Wrong audience.

The real audience is the mid-level economist at a finance ministry who needs to justify a policy design. That said, the strategy director at a logistics company evaluating a new routing algorithm. The competition authority analyst building a market definition case.

These people don't care about your identification strategy's elegance. They care: does this help me make a better decision tomorrow?

Write for them. The reviewers will follow Small thing, real impact. Simple as that..

How It Works — Getting Published

The process is standard on paper. Which means submit, desk reject or send to review, revise, accept or reject. But the unwritten rules are what matter.

Desk Rejection: The Silent Killer

Roughly 60% of submissions never reach reviewers. Here's the thing — i've seen the numbers. The editor-in-chief has mentioned this at conferences.

Top reasons for desk rejection:

• Pure theory with no empirical application
• Empirical work with no clear policy or business implication
• "Applied" papers that use only publicly available cross-country macro data with no institutional context
• Papers that could belong in a top field journal but aren't good enough for one — so the author shops down

People argue about this. Here's where I land on it.

That last one stings. But it's real. Editors can smell a paper that failed at JEEA or JFE and got lightly rewritten.

The Review Process: What Reviewers Actually Look For

Three things, in order:

1. Credibility of the setting. Is this a real decision context? Do the constraints make sense? If you're studying firm entry, do you understand the licensing process? If you're studying wage setting, do you know the collective bargaining structure?

2. Robustness that isn't performative. Don't show me 47 specifications. Show me the three that matter and explain why the others don't. Reviewers here hate kitchen-sink robustness tables.

3. A discussion section that doesn't hedge into meaninglessness. "Our results suggest X, but future research should..." — stop. Tell me what changes. What should the minister do differently? What should the CEO stop doing?

The Revision Round

If you get R&R, you're in good shape. But the revision letter matters more than the revised manuscript Worth keeping that in mind..

Address every comment. Even the stupid ones. Especially the stupid ones. If a reviewer misunderstood something, that's on you for not being clear enough. Fix the clarity. Don't argue.

But — and this is crucial — you don't have to do what every reviewer suggests. You do have to respond thoughtfully. So "We considered this approach but concluded X because Y" is a perfectly valid response. Reviewers respect it. Editors respect it.

Common Mistakes / What Most People Get Wrong

Mistake 1: Confusing "Applied" with "At Heoretical"

I see this constantly. A paper builds a beautiful model, calibrates it to some data, calls it applied. The editors reject it.

Applied means the research question comes from the world, not the literature. Because of that, the model serves the question. Not the other way around.

Mistake 2: The "Policy Implication" Paragraph

You know the one. Last paragraph of the conclusion. "These findings have important policy implications for..." followed by vague hand-waving And it works..

Reviewers hate this. Editors hate this. If your policy implication is real, it should shape your entire framing — from the introduction through the research design to the heterogeneity analysis. Not tacked on at the end.

Mistake 3: Ignoring Institutional Detail

"We control for country fixed effects" is not institutional knowledge. It's a statistical crutch Small thing, real impact..

The best papers in this journal — the ones that get cited in policy circles — they use institutional detail. In practice, they exploit a specific reform's staggered rollout. Here's the thing — they put to work a regulatory threshold. They interview practitioners to interpret a weird coefficient.

Mistake 4: Writing for the Wrong Journal Tier

JAEB isn't a dumping ground. If your paper is incremental but clean, it might fit. It's a destination for a specific kind of work. Now, if it's ambitious but messy, it might fit. If it's neither — if it's just "safe" — it won't And that's really what it comes down to. Nothing fancy..

Practical Tips / What Actually Works

Before You Write: The One-Page Test

Can you explain your paper on one page to a smart non-economist? The main finding. Worth adding: the setting. In practice, the research question. The actionable takeaway Worth keeping that in mind. Surprisingly effective..

If you can't, you're not ready to submit. This journal rewards clarity. The editors have explicitly said they prioritize papers where the contribution is obvious without reading the appendix Took long enough..

Structure Your Paper Like a Policy Brief — Then Add the Rigor

Introduction: the problem, why it matters, what you do, what you find, what changes. Day to day, background: only the institutional context the reader needs. Not a literature review. Which means data: be honest about limitations. Which means reviewers here check. Here's the thing — methods: justify every choice. "Standard in the literature" is not a justification. Results: lead with the main finding. Tables in appendix.

This is the bit that actually matters in practice.

Results: lead with the main finding. Tables in appendix. Figures in the main text.

Open the Results section with a concise, headline‑style statement of the primary causal effect—e.g.In practice, , “We find that a 10 % increase in the minimum wage reduces employment by 1. Worth adding: 8 percentage points in the restaurant sector. ” Follow this with a brief narrative that explains the intuition behind the number, then dive into the robustness checks. All auxiliary regressions, sample variations, and placebo tests belong in the appendix; the main text should only reference them (“see Appendix Table A.3 for full specifications”). Figures that illustrate dynamics, heterogeneity, or counterfactual simulations belong in the main body, while detailed data visualizations can be tucked away in the appendix Easy to understand, harder to ignore..

Discussion & Policy Context

The Discussion is not a second Results section; it is where you connect the dots. , a regulatory threshold that triggers a licensing requirement), explain how that feature was leveraged to sharpen identification. g.Then address each robustness check explicitly: why a difference‑in‑differences design is appropriate, how the staggered timing of the reform helps identify causality, and what the placebo tests tell us about parallel trends. If you used institutional detail (e.Start by reiterating the research question and why the finding matters for the real‑world setting you described in the Background. Finally, discuss any limitations—data gaps, potential measurement error, or omitted variables—and suggest how future research could extend the analysis That's the part that actually makes a difference..

Writing the Policy Implication Section the Right Way

Instead of a tacked‑on paragraph, weave policy relevance throughout the paper. That's why in the Discussion, translate the numbers into actionable guidance—e. Now, in the Background, highlight the institutional mechanism that policymakers can manipulate. In the Methods, justify why your design yields credible estimates for policy evaluation. , “Given the estimated employment loss, a gradual phase‑in of the reform could mitigate adverse effects while preserving its intended benefits.In the Introduction, frame the problem in terms of a concrete policy debate. In the Results, present the quantitative effect that directly informs the debate. Now, g. ” This integrated approach ensures reviewers see policy relevance as an organic part of the study, not an afterthought.

Handling Reviewer Comments Efficiently

1. Separate substantive feedback from stylistic notes. Address substantive critiques (identification concerns, omitted variables, alternative specifications) first; stylistic edits can be handled later.
2. Create a “response table.” List each comment, quote the reviewer’s concern, describe your revision, and reference the new figure/table where the change appears. Editors love seeing a clear, side‑by‑side comparison.
3. Never ignore a reviewer’s suggestion. Even if you think the suggestion is unnecessary, explain why you chose to keep the original approach and provide additional robustness checks to reassure the reviewer.
4. Proofread the response carefully. A typo in your rebuttal can undo weeks of careful revisions. Use track changes or a separate document to keep the manuscript clean.

Final Checklist Before Submission

• One‑page summary can be read and understood by a non‑economist.
• Research question originates from a real‑world problem, not a literature gap.
• Institutional detail is central to identification (reform timing, regulatory thresholds, interviews, etc.).
• Methods are justified beyond “standard in the literature.”
• Results lead with the headline finding; tables are in the appendix; figures are in the main text.
• Discussion links findings back to the original policy question and addresses robustness.
• Policy implications are woven throughout, not just appended.
• Language is clear, jargon is minimized, and the narrative flows like a policy brief.
• Formatting follows the journal’s guidelines (word count, references, footnotes, etc.).
• Author notes include clear contributions and disclosure statements.

Conclusion

Writing for a journal that prizes applied relevance demands more than a clean model and a tidy regression output. It requires you to start with a problem that matters

Putting It All Together: A Mini‑Template for an Applied‑Relevance Manuscript

Below is a compact, reusable skeleton that you can adapt to the specific requirements of the target journal. Each heading corresponds to a logical flow that reviewers expect, and each bullet contains the essential content you must supply. Feel free to trim or expand sections, but keep the overall architecture intact The details matter here..

1. Title & Subtitle

• Title: Concise, descriptive, and includes the policy context.
• Subtitle (optional): Highlights the analytical contribution (e.g., “Evidence from a phased‑in carbon tax”).

2. One‑Page Policy Summary (Front Matter)

• Problem statement: One sentence that a minister could read and understand.
• Policy question: Explicitly phrased as a decision‑maker’s query.
• Key finding: The headline quantitative result.
• Implication: How the finding would guide implementation.

3. Introduction

• Motivation: Ground the research in a real‑world dilemma (e.g., “The 2023 Renewable Energy Incentive Reform aimed to reduce industrial emissions by 15 % within five years, but early labor market data suggested a 3 % rise in unemployment in affected regions.”).
• Gap in knowledge: Why existing literature does not answer this particular question.
• Contribution roadmap: Briefly outline the empirical design, main result, and policy takeaway.

4. Institutional Context (Identification)

• Policy design: Describe the reform’s mechanics, timing, and geographic variation.
• Identification strategy: Explain the quasi‑experimental or natural‑experiment lever (e.g., staggered rollout, regression‑discontinuity, difference‑in‑differences).
• Justification: Cite institutional details that guarantee plausibly exogenous variation.

5. Data & Sample

• Sources: Administrative records, survey modules, or proprietary databases.
• Sample construction: Inclusion criteria, any cleaning steps, and sample size.
• Variable construction: Definitions, measurement error considerations, and any interaction terms.

6. Methodology

• Estimation equation: Present the core specification with clear notation.
• Robustness checks: List alternative specifications, placebo tests, or falsification designs.
• Diagnostic tools: Discuss over‑identification tests, weak‑instrument tests, or balance checks.

7. Results

• Primary coefficient: Report point estimate, confidence interval, and statistical significance.
• Magnitude translation: Convert the coefficient into an intuitive metric (e.g., “A 1‑percentage‑point increase in the reform’s intensity reduces employment growth by 0.12 percentage points”).
• Supplementary tables/figures: Place robustness results in an appendix; keep the main text focused on the headline finding.

8. Discussion / Policy Translation

• Interpretation: Explain what the number means for the original policy question.
• Actionable guidance: Offer concrete steps (e.g., “Phase‑in the reform over three years, coupled with targeted upskilling programs, can preserve the emissions‑reduction goal while limiting employment loss”).
• Limitations & extensions: Acknowledge any remaining identification concerns and suggest avenues for future work.

9. Conclusion

• Synthesis: Recap the problem, method, and central finding in a single, non‑technical sentence.
• Broader relevance: underline how the study advances the dialogue between empirical economics and policy design.
• Future outlook: Briefly note how the evidence can inform subsequent reforms or evaluations.

Final Tips for a Seamless Submission

1. Narrative cohesion – Treat each section as a paragraph in a longer story: problem → data → method → result → implication.
2. Avoid “method‑only” language – Whenever you introduce a statistical technique, immediately tie it back to the institutional quirk that makes it credible.
3. Keep the policy thread visible – Even when describing robustness checks, phrase them as “we examine whether alternative specifications alter the policy‑relevant estimate.”
4. Proofread for jargon – Replace technical acronyms with plain language wherever possible; remember that reviewers may come from diverse disciplinary backgrounds.
5. Check alignment with journal guidelines – Word limits, reference styles, and mandatory sections (e.g., “Data Availability Statement”) are non‑negotiable.

Conclusion

Writing for a journal that prizes applied relevance demands more than a clean model and a tidy regression output. It requires you to start with a problem that matters, embed the institutional quirks that make the data plausible, and then walk the reader through a logical chain that ends with a number they can act on.