daily-report-formatter
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseDaily Report Formatter
施工日报格式化工具
The daily construction report is not an administrative formality. It is the
contemporaneous record that proves schedule performance, justifies delay claims,
documents crew deployment, and provides the audit trail when a dispute arises
six months after project completion.
Reports written retroactively from memory are worthless in a dispute.
Reports written from informal field notes at the end of the day are what this
skill produces.
施工日报并非只是一项行政流程，它是能够证明工期执行情况、支撑延误索赔、记录人员部署的同期记录，并且在项目竣工六个月后出现纠纷时，可作为审计追踪的依据。
仅凭记忆事后补写的报告在纠纷中毫无价值。本技能的作用就是将当日的非正式现场记录整理为规范的施工日报。
What You're Working With
处理对象说明
The user will provide one of the following:
- A text message or WhatsApp thread from the site superintendent
- A voice-to-text transcript from the field
- A bullet list of what happened on site
- A partially filled form or template with gaps
- A verbal description in the chat
If the date is not provided, ask for it. A daily report without a date is
not a daily report.
If the project name is not provided, use a placeholder and flag it.
用户会提供以下任意一种输入内容：
- 现场主管发来的短信或WhatsApp对话
- 现场语音转文字的转录内容
- 当日现场情况的要点清单
- 填写不完整的报告模板
- 聊天中的口头描述
若用户未提供日期，需主动询问。没有日期的日报不能称为“日报”。
若用户未提供项目名称，需使用占位符并标记此缺失信息。
Step 1 — Extract Raw Data
步骤1 — 提取原始数据
From whatever the user provides, identify and extract:
- Date and weather — temperature range, conditions, wind, precipitation
- Crew deployment — each trade, crew size, hours on site, superintendent name
- Equipment on site — lifts, heavy machinery, vehicles
- Work completed — what was actually installed or completed, with quantities
- Work planned for tomorrow — what the crew intends to accomplish next day
- Delays or issues — anything that reduced productivity or stopped work
- Safety incidents — any near-miss, first aid, or recordable incident
- Visitors — inspector, owner rep, engineer of record, utility representative
- Materials delivered or received — what arrived, quantity, condition
- Open items or RFIs — anything that needs resolution
If the input is thin on any of these, do not fabricate. Use the placeholder
notation: [NOT REPORTED — confirm with superintendent].
从用户提供的任意内容中，识别并提取以下信息：
- 日期与天气 — 温度范围、天气状况、风力、降水情况
- 人员部署 — 各工种、人数、现场工作时长、主管姓名
- 现场设备 — 升降设备、重型机械、车辆等
- 当日完成工作 — 实际安装或完成的内容及工程量
- 明日工作计划 — 班组次日的工作安排
- 延误与问题 — 任何导致生产力下降或停工的事件
- 安全事件 — 未遂事件、急救事件或可记录的安全事故
- 现场访客 — 监理、业主代表、注册工程师、公用事业方代表
- 材料收发 — 送达材料的名称、数量、状态
- 未结事项或RFI — 任何需要解决的事项
若某项信息缺失，不得编造内容，需使用占位符并标记：[未记录 — 请向主管确认]
Step 2 — Classify the Day
步骤2 — 当日类型分类
Before drafting, classify the day type. This affects how the report is written
and what language is used in the delay section.
Full Production Day: All planned work executed as planned. No significant
delays. Normal crew and equipment deployment.
Partial Production Day: Work completed but at reduced rate due to weather,
crew reduction, equipment issue, or material shortage.
Weather Delay Day: Work stopped or significantly impacted by weather.
Important: document the specific weather condition, the time at which work
stopped, and the crew time that was lost. This documentation supports a
force majeure or excusable delay claim.
Administrative / Inspection Day: No significant installation work but
on-site activity for inspection, punch list, commissioning, or meetings.
Standby / Idle Day: Crew on site but unable to work due to a condition
outside the EPC's control (material not delivered, access not provided,
owner-caused delay, utility delay). This is the highest-priority day to
document carefully — idle crew costs are the basis of a cost recovery claim.
起草报告前，需先对当日类型进行分类。分类结果将影响报告的表述方式及延误部分的措辞。
全日施工日： 所有计划工作按要求完成，无重大延误，人员及设备部署正常。
部分施工日： 完成了部分工作，但因天气、人员减少、设备问题或材料短缺导致生产力下降。
天气延误日： 因天气原因导致施工暂停或严重受影响。注意：需记录具体天气状况、停工时间及人员损失时长。此类记录是不可抗力或可原谅延误索赔的重要依据。
行政/检查日： 无重大安装工作，但现场开展了检查、整改、调试或会议等活动。
待命/闲置日： 人员在现场但因EPC可控范围外的情况无法工作（如材料未送达、现场无法进入、业主原因延误、公用事业方延误）。此类日期的记录最为关键——闲置人员成本是成本补偿索赔的核心依据。
Step 3 — Draft the Daily Report
步骤3 — 起草施工日报
Produce the report in the following format.
DAILY CONSTRUCTION REPORT
Project: [Project name and address]
Report No.: [Sequential number if known — otherwise leave blank]
Date: [Date]
Prepared By: [Superintendent name if provided / left blank if not]
Report Type: [Full Production / Partial Production / Weather Delay /
Administrative / Standby-Idle]
WEATHER CONDITIONS
| Morning | Afternoon | |
|---|---|---|
| Temperature | ||
| Conditions | (Clear / Cloudy / Rain / High Wind / Other) | |
| Wind Speed (est.) |
Weather impact on work: [None / Reduced productivity / Work stopped — describe]
CREW ON SITE
| Company | Trade / Scope | Crew Size | Hours | Superintendent |
|---|---|---|---|---|
| [EPC name] | [General supervision / electrical / civil] | |||
| [Sub name] | [Racking / civil / electrical / commissioning] |
Total on-site person-hours: [sum]
EQUIPMENT ON SITE
| Equipment | Quantity | Used / Standby |
|---|---|---|
| [Scissor lift / boom lift / forklift / etc.] |
WORK COMPLETED TODAY
[Write in plain, specific language. Include quantities. Bad: "Installed modules."
Good: "Installed 240 modules on Roof Section B, Rows 1-12, Grid Lines A-D.
Module installation on this section is now 100% complete."]
Scope: [Description of work completed]
Quantities: [Modules installed: X | Conduit run: X LF | Trenching: X LF | etc.]
Percent complete (overall project): [X% if known]
WORK PLANNED FOR TOMORROW
[What the crew intends to do next. Specific. Referenced to drawing areas
where possible.]
DELAYS AND ISSUES
[If no delays: "No delays or issues to report."]
[If delays exist — use the following structure for each:]
Issue [#]:
- Description: [What happened]
- Cause: [Weather / Material not delivered / Design issue / Owner-caused / Equipment failure / Other]
- Duration: [Hours of lost productivity, or full-day stoppage]
- Responsible party: [If known — state factually, not accusatorially]
- Action taken: [What was done to mitigate]
- Open: [Yes — resolution pending / No — resolved on site]
Note on standby time: If crew was idle due to a condition outside the
EPC's control, state specifically: "Crew of [X] was on site and available
for work from [time] to [time]. Work could not proceed due to [reason].
Idle time of [X] person-hours is a direct cost to [EPC name] for which
cost recovery will be requested under [contract clause reference if known]."
SAFETY
Safety orientation conducted: [Yes / No]
Safety incidents today: [None / describe if applicable]
Near-misses or observations: [None / describe if applicable]
PPE compliance: [Full compliance observed / Issues noted — describe]
SITE VISITORS
| Name | Company / Role | Purpose of Visit | Time on Site |
|---|---|---|---|
[If no visitors: "No site visitors."]
MATERIALS RECEIVED
| Material | Quantity | Supplier | Condition | PO / Delivery Reference |
|---|---|---|---|---|
[If nothing received: "No material deliveries today."]
OPEN ITEMS
| Item | Description | Assigned To | Due Date | Status |
|---|---|---|---|---|
| RFI-[###] | [Brief description] | [EOR / Owner / Utility] | Open |
[If no open items: "No new open items. Refer to open issues log."]
PHOTOS
[List photo references or note: "Photos available in project photo log for [date]."]
PREPARED BY:
Name: ___________________
Title: ___________________
Signature: ___________________
Date: ___________________
需按照以下格式生成报告。
施工日报
项目：[项目名称及地址]
报告编号：[已知则填连续编号，否则留空]
日期：[日期]
编制人：[若提供则填主管姓名，否则留空]
报告类型：[全日施工/部分施工/天气延误/行政/待命-闲置]
天气状况
| 上午 | 下午 | |
|---|---|---|
| 温度 | ||
| 状况 | （晴/多云/雨/大风/其他） | |
| 估计风速 |
天气对施工的影响：[无/生产力下降/施工暂停——说明详情]
现场人员
| 公司 | 工种/工作范围 | 人数 | 工作时长 | 主管 |
|---|---|---|---|---|
| [EPC公司名称] | [总协调/电气/土建] | |||
| [分包商名称] | [支架安装/土建/电气/调试] |
现场总人工时：[合计]
现场设备
| 设备类型 | 数量 | 使用状态（使用中/待命） |
|---|---|---|
| [剪叉式升降车/曲臂式升降车/叉车/等] |
当日完成工作
[需使用简洁明确的表述，并包含工程量。反面示例：“安装了组件。” 正面示例：“在B区屋顶1-12排、A-D轴线区域安装了240块组件，该区域组件安装工作已100%完成。”]
工作范围：[已完成工作描述]
工程量：[组件安装：X | 导管铺设：X延英尺 | 管沟开挖：X延英尺 | 等]
项目整体完成率：[若已知则填X%]
明日工作计划
[需明确具体工作内容，尽可能关联图纸区域。]
延误与问题
若无延误：“无延误或问题需报告。”
若有延误——每项问题需按以下结构记录：
问题[#]：
- 描述：[事件详情]
- 原因：[天气/材料未送达/设计问题/业主原因/设备故障/其他]
- 时长：[生产力损失时长，或全天停工]
- 责任方：[若已知，需如实陈述，勿带指责语气]
- 已采取措施：[为缓解问题所做的行动]
- 状态：[是——待解决/否——现场已解决]
**待命时间说明：**若因EPC可控范围外的情况导致人员闲置，需明确说明：“[X]名人员于[开始时间]至[结束时间]在现场待命，因[原因]无法开展工作。共计[X]人工时的闲置时间为[EPC名称]的直接成本，将依据[若已知则填合同条款编号]申请成本补偿。”
安全情况
已开展安全培训：[是/否]
今日安全事件：[无/若有则说明详情]
未遂事件或观察发现：[无/若有则说明详情]
个人防护装备（PPE）合规情况：[完全合规/存在问题——说明详情]
现场访客
| 姓名 | 公司/职务 | 来访目的 | 停留时间 |
|---|---|---|---|
若无访客：“无现场访客。”
材料接收
| 材料名称 | 数量 | 供应商 | 状态 | 采购订单/送货单号 |
|---|---|---|---|---|
若无材料送达：“今日无材料送达。”
未结事项
| 事项编号 | 描述 | 责任人 | 截止日期 | 状态 |
|---|---|---|---|---|
| RFI-[###] | [简要描述] | [注册工程师/业主/公用事业方] | 待解决 |
若无未结事项：“无新增未结事项，请查阅未结事项日志。”
现场照片
[列出照片编号，或备注：“[日期]的现场照片可在项目照片日志中查看。”]
编制人：
姓名：___________________
职务：___________________
签字：___________________
日期：___________________
Step 4 — Flag High-Priority Items
步骤4 — 标记高优先级事项
After producing the report, review it and flag anything that requires
immediate PM or project director attention:
- Any safety incident (even minor)
- Any standby / idle time due to owner or utility-caused delay
- Any material delivery that arrived damaged or with quantity shortfall
- Any inspector visit that resulted in a comment, correction notice, or failed inspection
- Any verbal instruction from owner's rep that is not in writing
For each flagged item, add a note:
ACTION REQUIRED: [Specific action needed and who should take it]
生成报告后，需复查并标记所有需要项目经理或项目总监立即关注的事项：
- 任何安全事件（即使是轻微事件）
- 因业主或公用事业方原因导致的人员待命/闲置时间
- 任何送达时损坏或数量短缺的材料
- 任何导致监理提出意见、整改通知或不合格结论的监理到访
- 业主代表给出的任何口头指示（未形成书面记录）
对每一项标记事项，需添加备注：
需采取行动：[具体行动要求及责任人]
Step 5 — Offer Follow-Through Documents
步骤5 — 提供后续支持文档
After delivering the report, offer to:
- Draft an RFI if any field condition was noted that requires engineering clarification
- Draft a change order if any owner-directed scope change was documented
- Draft a delay notice letter to the owner if a standby day was documented (a formal delay notice protects the right to claim schedule extension)
- Create a weather delay log if multiple weather delays have been reported
交付报告后，可主动提供以下服务：
- 若记录的现场状况需要工程师澄清，可协助起草RFI
- 若记录了业主提出的工作范围变更，可协助起草变更令
- 若记录了待命闲置日，可协助起草给业主的延误通知函（正式的延误通知函是保障工期延长索赔权的关键）
- 若已记录多次天气延误，可协助创建天气延误日志
Examples
示例
Worked examples showing input field notes and the resulting formatted report:
- Fresno Commerce Center — Full Production Day — Racking milestone completed, two subs on site, owner's rep verbal scope comment, material delivery. Illustrates day classification, missing-data placeholders, scope milestone language, person-hours math, and verbal-instruction flagging.
以下为输入现场记录后生成格式化报告的示例：
- 弗雷斯诺商务中心——全日施工日 ——完成支架安装里程碑，两家分包商在场，业主代表提出口头工作范围意见，材料送达。示例展示了当日类型分类、缺失数据占位符、工作范围里程碑表述、人工时计算及口头指示标记。
Domain Notes — What Field Notes Usually Miss
行业提示——现场记录常遗漏的内容
When the user's input is sparse, these are the items most commonly omitted:
- Exact crew count by trade (not just "the racking crew")
- Quantity of work completed (not just "installed racking")
- Whether an inspection was passed, failed, or deferred
- Name of utility or owner rep who visited
- Specific weather times (work stopped at 2pm vs. weather all day)
- Whether open items from yesterday were resolved
Ask for these specifically if the input does not include them.
当用户提供的信息较为简略时，以下是最常被遗漏的内容：
- 各工种的具体人数（而非仅“支架安装班组”）
- 完成工作的工程量（而非仅“安装了支架”）
- 检查结果是合格、不合格还是延期
- 到访的公用事业方或业主代表姓名
- 具体的天气影响时间（比如下午2点停工 vs 全天受天气影响）
- 昨日未结事项是否已解决
若输入信息未包含上述内容，需主动向用户询问。