当前时间: 1970-01-01 08:00:00
分类:办公文件
评论(0)
体制内新人第一次写周报,这3个模板直接套用上周四,领导在群里发消息,让周五中午前把周报交上来。小刘懵了:周报写什么?这一个礼拜也没干什么大事啊。她打开Word,从周一写到周五——"周一接6个电话,周二整理7份文件,周三参加2个会……"她来找我。我想起自己第一次写周报的样子,我当年更惨——写了“接电话、复印、跑腿、参会”,领导在会上说:“有些人一周下来,好像什么都没干。”01 领导看周报,只看三样东西
周报是"导航",告诉领导——这周到哪了、卡在哪了、下周怎么推进。02 万能公式:动作+结果
- 进行中:完成XX方案初稿,已发科长审阅,目前还未返回修改意见
03 三个真实场景,直接套
- XX工作原定X月X日完成,目前60%,预计延迟至X月X日
04 新人最容易踩的坑(我都踩过)
改:按"事项+进度+问题"重组。比如"接电话"→"处理群众咨询XX件,已全部办结,其中XX类问题需政策明确已上报"。改:主动说小问题+解决方案。"XX部门数据延迟3天,已沟通确认下周一给齐,我将加班追赶"。改:每条工作带"下周节点"。让领导知道"这事在推进"或"这事卡住了"。05 写完3件事
下周计划加起来是否合理?别计划50小时只有40小时。写在最后
我说:“在体制内,领导回‘收到’就是最高评价——说明你没问题,他没话说了。”周报的核心就一句话:把一周的工作"翻译"成进度导航条
基本
文件
流程
错误
SQL
调试
- 请求信息 : 2026-04-22 14:20:57 HTTP/1.1 GET : https://www.yeyulingfeng.com/a/556312.html
- 运行时间 : 0.144977s [ 吞吐率:6.90req/s ] 内存消耗:4,700.07kb 文件加载:145
- 缓存信息 : 0 reads,0 writes
- 会话信息 : SESSION_ID=9f724f7d7df62ea009675b4d8ae04a01
- CONNECT:[ UseTime:0.000670s ] mysql:host=127.0.0.1;port=3306;dbname=wenku;charset=utf8mb4
- SHOW FULL COLUMNS FROM `fenlei` [ RunTime:0.001145s ]
- SELECT * FROM `fenlei` WHERE `fid` = 0 [ RunTime:0.000520s ]
- SELECT * FROM `fenlei` WHERE `fid` = 63 [ RunTime:0.000486s ]
- SHOW FULL COLUMNS FROM `set` [ RunTime:0.000874s ]
- SELECT * FROM `set` [ RunTime:0.000315s ]
- SHOW FULL COLUMNS FROM `article` [ RunTime:0.000896s ]
- SELECT * FROM `article` WHERE `id` = 556312 LIMIT 1 [ RunTime:0.000764s ]
- UPDATE `article` SET `lasttime` = 1776838858 WHERE `id` = 556312 [ RunTime:0.000967s ]
- SELECT * FROM `fenlei` WHERE `id` = 64 LIMIT 1 [ RunTime:0.000331s ]
- SELECT * FROM `article` WHERE `id` < 556312 ORDER BY `id` DESC LIMIT 1 [ RunTime:0.000707s ]
- SELECT * FROM `article` WHERE `id` > 556312 ORDER BY `id` ASC LIMIT 1 [ RunTime:0.000604s ]
- SELECT * FROM `article` WHERE `id` < 556312 ORDER BY `id` DESC LIMIT 10 [ RunTime:0.001261s ]
- SELECT * FROM `article` WHERE `id` < 556312 ORDER BY `id` DESC LIMIT 10,10 [ RunTime:0.001090s ]
- SELECT * FROM `article` WHERE `id` < 556312 ORDER BY `id` DESC LIMIT 20,10 [ RunTime:0.001075s ]
0.147600s