Event Planning: a Tokeny case study
Generate planning proposals with schedules, materials, and staff assignments based on event type and budget. Follow the recorded task, execution screenshots, actual files and verification notes.
By the Tokeny team · Windows · Tokeny 1.7.8 · gpt-6-sol
Prepare the inputs
Create a separate workspace in Tokeny, download and unpack the sample inputs, then select a model that supports tools. The sample uses synthetic data or the public sources named in the article.
- event.md
Send the task to Tokeny
The original task was executed in Chinese. Copying these instructions reproduces the same task; the results below include an English report.
为 30 人的社区读书交流活动制定执行方案，预算 3000 元，时长 2 小时，含流程、分工、物料、预算、应急安排与报名表模板。 交付文件：event-plan.docx、budget.xlsx、runbook.csv。 验收要点： - 流程总时长 120 分钟 - 预算不超过 3000 - 有分工与应急事项 这是使用合成演示输入或指定公开资料的真实操作案例。请先读取工作空间输入，再实际生成文件并自检。所有写入、脚本与临时服务限于当前工作空间；临时服务只监听 127.0.0.1，执行后关闭；不触达外部收件人、不发布、不付款、不更改系统设置，不调用子智能体。需要公开资料时可读取给定 URL。只启用完成任务必需的工具。另写 report.md（中文）和 report.en.md（英文），简洁、完整，包含输入、处理步骤、真实结果、检查方式和局限；失败或未验证部分如实记录，不能宣称成功。最终回复用中文列出产物、关键结果与待核实项。 排版检查：Word 主标题仅出现一次，标题为黑色且与后续正文或表格保持同页；表格的标题、表头和第一条数据保持同页，单行不要跨页拆分；Excel 表头和长文字不能被窄列截断，合理设置列宽、换行、行高；HTML 在 390px 视口不能整页横向溢出。临时网络服务请用系统分配端口（0），记录实际端口，不使用固定端口，避免并发案例互相访问。报告没有固定字数要求，不要为字数反复改写。
Follow-up instructions after review (1)
独立重算和 Microsoft Word 原生分页发现以下问题，请只补修必要部分并更新两份报告： 1. budget.xlsx 的 G3 错写成 =D2*F2，后续金额也整体错行，导致 G3/G12/G13 为 #VALUE!。G3:G11 必须各自使用本行 D*F（如G3=D3*F3），逐行实际核对数值，合计1837、余量1163。不要只断言硬编码数组的总和。 2. event-plan.docx 第2页末“五、预算摘要”与整张预算表分开；第3页末“七、报名表模板”后只剩表头，内容在第4页。请让各标题、说明、表头、第一条数据同页，小型预算表与报名表优先完整同页，必要时在标题前分页；保留重复表头和不拆行。 3. Word物料表“预算（元）”下饮水写2，实际36瓶×2=72。请统一此列为金额小计，写72并核对所有物料小计与Excel一致，保留1837总额。 不要重做其他正确内容；实际检查修改后文件，报告如实保留验证范围。
The recorded run used an isolated demonstration workspace. Review the commands and file paths before approving operations in your own workspace.
What actually ran
The task was submitted through the Tokeny input box. An online model read the inputs and executed tools. This run covers the local sample task and its actual files. Results and checks are recorded below.
Results and verification
Input
Read event.md: date TBD; indoor community activity room; 30 adults; 4 volunteers; no commercial performance; check-in, a themed sharing, group discussion, and closing cleanup are required; venue fee is CNY 800. ENVIRONMENT.md was also read to confirm the Windows environment and available Python document/spreadsheet dependencies.
Processing steps
- Converted the requirements into a 120-minute agenda, roles, materials, budget, contingency actions, and a registration template.
- Used Python to generate
event-plan.docx,budget.xlsx, andrunbook.csv. - Rechecked the total minutes and budget from structured data; configured Word tables with repeating headers and non-splitting rows; configured Excel widths, wrapping, row heights, and frozen headers.
- Reopened the generated files to check existence, readability, and required fields.
Actual results
- The agenda has 8 segments totaling 120 minutes.
- Corrected
budget.xlsxso every formula inG3:G11uses the same-rowD*F, then checked the row values: 800, 72, 120, 180, 100, 35, 80, 150, 300; total CNY 1,837 and remaining CNY 1,163 under the CNY 3,000 limit. - The plan includes volunteer roles, materials, contingencies, and a registration form template.
runbook.csvincludes a 30-minute setup block plus all 120 minutes of live execution.
Verification method
- Extracted DOCX text and checked that the main title appears once and required sections exist; checked table header repetition and row non-splitting properties.
- Reopened the workbook with openpyxl, read every formula in
G3:G11, recomputed each amount from the same-row D×F values, and checked total CNY 1,837, remaining CNY 1,163, widths, and wrapping. - Reopened the CSV as UTF-8-SIG and checked the header, 9 execution records, and Chinese text readability.
Limitations
- The event date, book title, facilitator name, venue evacuation route, and emergency contact are still TBD and must be completed before execution.
- No live venue rehearsal was performed; equipment availability must be retested on site. No external sources were used and no messages were sent.
- Added page-break controls before “V. Budget Summary” and “VII. Registration Form” and preserved repeating headers and non-splitting rows; structural checks are complete. The local Office rendering script could not run, so final page placement still requires a Microsoft Word check. The official DOCX validator could not run because
defusedxmlis unavailable in the environment; available XML parsing and structural checks were used instead.
Download and inspect the outputs
The archive contains the files created during this run. Use these checks when adapting the example to your own data.
- Reconcile the reported results against the downloadable sample inputs.
- Open the generated files and check the contents relevant to your task.
- Review the limitations and any unverified steps in the report.