Quick Rendering
Once the interview is complete and you confirm the collected values, CoQuill renders your finished document immediately. No queue, no cloud processing, no waiting.
Word documents
Section titled “Word documents”Templates authored as .docx files produce polished Word documents. CoQuill uses docxtpl under the hood, which means every font, table, header, and style in your original document is preserved exactly. Only the placeholders change.
Your formatting stays intact — bold text stays bold, tables keep their borders, and page breaks remain where you put them.
When Microsoft Word or LibreOffice is available on your machine, CoQuill also produces a .pdf alongside the .docx automatically. If neither is installed, you receive the .docx with a note explaining how to convert it manually.
HTML and PDF
Section titled “HTML and PDF”Templates authored as .html files produce two outputs: the rendered HTML file and a PDF generated from it via WeasyPrint. You get both automatically, no extra steps required.
This is ideal for invoices, proposals, and any document that needs to look good on screen and in print.
Markdown
Section titled “Markdown”Templates authored as .md files produce a rendered Markdown file, with an optional PDF when WeasyPrint is available. Markdown is the lightest format to author — no Word styling to manage, no CSS to write — and the output is version-control friendly.
This works well for meeting notes, internal records, and any document where readability matters more than pixel-perfect layout.
Interview transcript
Section titled “Interview transcript”Every document assembly session saves a human-readable transcript.md alongside your rendered output. The transcript records the full interview: questions asked, answers given, any clarifications or corrections, and a summary table of all confirmed values.
This gives you a clear audit trail — you can see exactly what was discussed and what values ended up in the document, without re-reading the chat history.
Output lands in one place
Section titled “Output lands in one place”Every rendering job creates its own folder inside output/, named with the template, a key variable value, and the date:
output/ Bonterms_Mutual_NDA_acmepteltd_2026-03-01/ Bonterms_Mutual_NDA_acmepteltd_2026-03-01.docx Bonterms_Mutual_NDA_acmepteltd_2026-03-01.pdf ← when Word or LibreOffice availableFor HTML templates, you get both files in the same folder:
output/ invoice_acmepteltd_2026-03-01/ invoice_acmepteltd_2026-03-01.html invoice_acmepteltd_2026-03-01.pdfEvery job folder also includes interview_log.json (the raw interview data) and transcript.md (the human-readable record):
output/ Bonterms_Mutual_NDA_acmepteltd_2026-03-01/ Bonterms_Mutual_NDA_acmepteltd_2026-03-01.docx Bonterms_Mutual_NDA_acmepteltd_2026-03-01.pdf interview_log.json transcript.mdNo files are overwritten. Each job is isolated, so you can render the same template repeatedly for different clients or dates without losing previous output.