Planning Before Reasoning: A Vision-Language Dataset for Structured Stepwise Reasoning in Document Understanding

DocPlan: 133K document VQA examples annotated with query analysis, planning, extraction-and-reasoning, and answer stages

Findings of EMNLP 2026

DongJae Shin1,*, Hangyeol Yoo2,*, Yerin Nam2, Hoyeon Shin3, SeungWoo Song2, Seohyun Song3, Donghun Yang4, KyungTae Lim2

1TutorusLabs 2KAIST 3Seoultech 4KISTI

*Equal contribution

A DocPlan training example. Left: a Statista line chart of cumulative COVID-19 cases by country with the question 'Calculate the difference in the number of cases between Brazil and Russia as of day 106.' Right: the tagged answer, with a query analysis box, a plan with two sub-plans, two plan-execution blocks that extract values into markdown tables and compute 1,310,000 minus 627,646, and a final answer of 682,354. Bottom: five example questions for the same chart, one per query type (Mathematics, Coarse Perception, Fine-grained Perception, Instance Reasoning, Logical Reasoning).
Figure 2. Example of DocPlan training data. Instead of a bare question–answer pair, each instance is written as four tagged stages: query analysis (<QUERY_ANALYSIS>), definition of the plan (<DEF_PLAN> with <SUB_PLAN> sub-goals), execution of the plan (<EXEC_PLAN> with <EXTRACTED_INFO>, <THINK> and <PLAN_ANS>), and the final answer. Here the model first extracts Russia's 627,646 cases and Brazil's 1,310,000 cases on day 106, then answers 682,354. The bottom row shows the five query types generated for each image: Mathematics (MA), Coarse Perception (CP), Fine-grained Perception (FP), Instance Reasoning (IR), and Logical Reasoning (LR).

Abstract

This paper introduces DocPlan, a vision-language training dataset designed to emulate the stepwise reasoning strategies employed by human during visual document understanding. DocPlan was constructed to enable vision-language models (VLMs) to effectively learn the structured reasoning process that humans typically follow when interpreting documents. We reorganized existing document understanding datasets into 133K examples annotated with the following four sequential stages: Recognition → Planning → Extraction and Reasoning → Conclusion. To evaluate the effectiveness of DocPlan, we fine-tuned the direct prediction-based VLMs to perform stepwise reasoning generation across these stages. The experimental results demonstrated that our approach achieved up to a 13.8%p improvement in accuracy on document-based benchmarks.

Keywords Visual document understanding Document VQA Chart question answering Vision-language models (VLMs) Multimodal reasoning Stepwise reasoning Chain-of-thought (CoT) Plan-and-reason Synthetic reasoning data Interpretability

Dataset Construction

Three-step DocPlan construction pipeline. Step 1: images from DocVQA, InfoVQA, and ChartQA are given to Qwen 2.5-VL, which generates queries of five types (CP, FP, LR, MA, IR) at Basic, Intermediate, and Advanced difficulty. Step 2: generated and original queries pass through Qwen2.5-VL 72B, which writes query analysis, definition of plan, execution of plan, and final answer, and the outputs are combined into the DocPlan dataset. Step 3: origin and generated samples go through query filtering, rule-based format filtering, and model agreement among GPT-4o, Qwen2.5-VL, and Gemini 2.0 to give the filtered DocPlan dataset.
Figure 3. Construction of the DocPlan dataset in three steps: (1) query generation, (2) plan and reasoning generation, and (3) data filtering. The pipeline starts from about 28K training images of DocVQA, InfoVQA, and ChartQA and 162K queries (82K original, 80K generated), and keeps 133,623 samples after filtering.

Existing document VQA datasets mostly pair an image with a short answer, so a model trained on them learns direct prediction and can reach the right answer through wrong intermediate reasoning (Figure 1 of the paper shows such a case on ChartQA). DocPlan follows the order in which people read charts and documents (recognize the question, plan, extract values, reason, conclude) and writes it out as explicit tagged stages. It is built as follows:

  1. Image collection. All training images of DocVQA, InfoVQA, and ChartQA are reused unchanged (about 28K images; 28,954 in the final dataset).
  2. Query generation. Because original queries are mostly simple extraction questions, Qwen2.5-VL generates 80K new queries of five document-specific types adapted from MMStar (Fine-grained Perception, Coarse Perception, Instance Reasoning, Logical Reasoning, Mathematics) at three difficulty levels (Basic, Intermediate, Advanced). With the 82K original queries this gives 162K queries.
  3. Plan-and-reason generation. For every query, Qwen2.5-VL writes a query analysis, then a plan with N sub-plans (N chosen by query type and difficulty), then executes each sub-plan in turn by extracting the needed information and reasoning over it, reusing earlier intermediate answers, and finally writes the final answer.
  4. Filtering. Original queries (with ground truth) pass a rule-based tag check, then GPT-4o, Qwen2.5-VL, and Gemini 2.0 rate each sample and only samples on which the models agree are kept. Generated queries (without ground truth) are first checked by GPT-4o for validity against the image, then pass the same tag check and model-agreement filtering.

The result is DocPlan with 133,623 samples (68,513 from original queries and 65,110 from generated queries). An extra trace-based “hard filtering” step with human review of 10,207 likely errors produces DocPlan-HF with 124,053 samples. Both are released on Hugging Face (DocPlan-133K, DocPlan-HF-124K; access is granted on request). VLMs are fine-tuned on the data with visual instruction tuning for three epochs and evaluated with VLMEvalKit on DocVQA and InfoVQA (ANLS) and ChartQA and ChartQAPro (GPT-4o as judge).

Main Results

  • Up to 13.8%p higher average accuracy. Training paligemma2-10B on DocPlan raises its average over DocVQA, InfoVQA, ChartQA, and ChartQAPro from 40.1 to 53.9; Llama3.2-11B-Vision goes from 52.3 to 69.2 (59.3 when trained on the original QA data without reasoning).
  • Planning beats direct prediction on the same data. Rewriting the original 82K QA pairs into the DocPlan format (+DocPlan(origin)) improves Llama3.2 by 7.1%p (59.3 → 66.4) and gemma3 by 2.4%p (58.6 → 61.0) over direct training; adding the generated queries gives Llama3.2 another 2.8%p (69.2).
  • Structured stages beat free-form chain-of-thought. With the same base models, DocPlan outperforms free-form CoT, e.g. Gemma3-4b DocVQA 82.8 vs. 53.46 and ChartQA 81.3 vs. 54.0, and Llama-Vision InfoVQA 71.2 vs. 54.83. In the stage ablation, adding the execution stage gives the largest gain (5.3%p).
  • Competitive with larger systems and transfers to held-out data. Llama-3.2-11B+DocPlan reaches 91.5 on DocVQA and 86.6 on ChartQA, above Llava-CoT (89.8 / 82.6) and zero-shot GPT-4o (85.6 / 85.7). On held-out TextVQA, Gemma3-4B-it improves from 58.14 to 62.91 (+4.77%p).
  • More interpretable reasoning traces. In a simulatability test (answering from the reasoning trace alone, without the image), Llama3.2+DocPlan scores 62.0 on average vs. 51.5 for Llava-CoT (+10.5%p); in GPT pairwise preference it wins 71.3% of comparisons on average vs. 26.1% for Llava-CoT.

Trade-offs reported in the paper: responses become much longer (e.g. Llama3.2-11B-V generates 177.5–285.3 tokens on average instead of 5.7–26.1), and accuracy on the general-domain MMMU benchmark drops after document-only fine-tuning, though less than with direct-prediction training (Llama3.2-11B-Vision: −15.0%p vs. −31.2%p).

Table 1. Accuracy of five open VLMs under different training data. Base: no fine-tuning; +origin dataset: 82K original QA pairs without reasoning; +DocPlan(origin): the 68K original queries converted to DocPlan format; +DocPlan: those plus 65K generated queries. DocVQA and InfoVQA use ANLS, ChartQA and ChartQAPro use GPT-4o-judged accuracy. Bold marks the best value per model, as in the paper. (Table 2 in the paper.)
ModelTraining dataDocVQAInfoVQAChartQAChartQAProAvg
SmolVLM2-2.2BBase80.947.666.117.853.1
+origin dataset77.045.163.318.350.9
+DocPlan(origin)75.843.870.817.151.9
+DocPlan80.144.472.718.954.0
gemma-3-4b-itBase62.030.157.421.642.8
+origin dataset83.750.376.124.158.6
+DocPlan(origin)82.752.981.027.361.0
+DocPlan82.850.481.328.960.9
Qwen2-VL-7BBase93.172.783.126.668.9
+origin dataset89.266.078.623.164.2
+DocPlan(origin)91.873.479.929.968.8
+DocPlan91.871.283.230.069.0
paligemma2-10BBase69.034.934.222.440.1
+origin dataset71.939.567.616.648.9
+DocPlan(origin)74.942.371.520.752.3
+DocPlan76.442.374.522.453.9
Llama3.2-11B-VBase83.041.074.211.052.3
+origin dataset87.859.573.416.559.3
+DocPlan(origin)90.468.379.827.166.4
+DocPlan91.568.286.630.669.2

BibTeX

@inproceedings{shin-etal-2026-planning,
    title = "Planning Before Reasoning: A Vision-Language Dataset for Structured Stepwise Reasoning in Document Understanding",
    author = "Shin, Dongjae  and
      Yoo, Hangyeol  and
      Nam, Yerin  and
      Shin, Hoyeon  and
      Song, SeungWoo  and
      Song, Seohyun  and
      Yang, Donghun  and
      Lim, KyungTae",
    editor = "Lee, Hung-Yi  and
      Dev, Sunipa  and
      Li, Jessy  and
      Elliott, Desmond",
    booktitle = "Findings of the {A}ssociation for {C}omputational {L}inguistics: {EMNLP} 2026",
    month = oct,
    year = "2026",
    address = "Budapest, Hungary",
    publisher = "Association for Computational Linguistics",
    url = "https://aclanthology.org/2026.findings-emnlp.996/",
    doi = "10.18653/2026.findings-emnlp.996",
    pages = "21022--21061",
    ISBN = "979-8-89176-462-0"
}
More projects from KAIST MLP Lab →