New Job

New Job

Drop a bank's Word format and the tool builds a leak-free shell_template.docx plus the extraction prompts and master form.

The key is the format_fields namespace — the prompt and master form use it, so leave it blank unless you have a reason.

Drop a bank format .docx (or legacy .doc) here
or click to choose · a PDF is not a source
Building shell_template…
Analyzing the document — this usually takes about a minute.
0:00
elapsed

Dashboard

All jobs, most recent first.

SourceDate & timeStatusT1T2 leaksCoverage

T1 Reconstruction
render(shell, source values) ≈ source — catches loss
T2 Leaks
render(shell, empty) must contain zero case data
Coverage
value slots bound / static / flagged
Rendered via
T1/T2 go through the real production engine

Map sections → real keys

The tool finds the structure; you name the meaning. Set each answer key / narrative region, then re-run — same input + mapping → same output.

SectionKindPreviewAssign key / prefix

Edit the shell in Word

Download the shell, fix the questions / placeholders / tables in Word, and upload it back. The prompts and the reviewer form are generated from whatever shell is on disk, so your edits flow straight through. Uploading does not re-run the builder — that would rebuild the shell from the original document and discard your edits.



        

Review sheet (Excel)

One row per field in the bank's format, with the placeholder kind the tool chose. Check it, correct the new_kind / new_key columns, and upload it back to see what would change. The How placeholders work tab explains the four kinds.



        

Generate & publish



        

Download & judge

Open T1_reconstruction.docx and compare to your original. Then open T2_blank.docx — it must contain no client data.

Run log



        

Decisions — why the tool did what it did

KindWhereKeyDispositionWhy

Shell needs these variables


        

T1 — lines the shell cannot carry (over-blanking / loss)


        

T2 — leaked values (must be empty)