假期交接如何避免四處搜尋資訊
Holiday handover without the information hunt
Bala Madhusoodhanan 提供 Holiday Handover and Cover Planner,整合電郵(包括 Sent Items)、Teams 討論、日曆承諾及相關文件,整理假期交接建議。
Work is scattered. Accountability must not be
Preparing for leave can become a reconstruction exercise. A decision may sit in a Teams thread, a promise in Sent Items, a deadline in a meeting invitation and an approval in a project update. A handover written from memory can miss the connection between them.
The difficult part is not listing everything you touched. It is identifying what remains open, what will matter during your absence and whether someone has actually agreed—and is authorised—to take it forward.
A useful handover is not “here is everything I did”. It is “here is what needs to happen without me, with the evidence and the remaining gaps”.
Consider a few illustrative risks, not findings about a particular team: a broad contact has been named but a specific approval is still assigned to the absent person; a delegate can attend a workshop but cannot make its decision; or a calendar leave marker ends before the intended last day away. These are continuity questions, not simply summarisation tasks.
Approach:
The Holiday Handover and Cover Planner is designed to connect recent email—including Sent Items—Teams discussions, calendar commitments and relevant documents. Its configurable defaults are a three-week lookback, a two-and-a-half-week outlook and a two-week absence; actual leave dates still need establishing.
Instead of treating an old status email as the current truth, the instructions call for substantive source reading and reconciliation of later replies. They distinguish business cover from technical support, coordination from approval authority, and a suggested contact from someone who accepted a defined cover period.
The intended output is a practical decision aid: priority actions before departure, a topic-by-topic cover matrix, upcoming commitments and a visible list of assumptions or missing evidence. The design also checks leave markers and automatic replies where the environment exposes those settings.
That makes the output a proposal to review, not an assignment of responsibility. People still need to agree the cover, and approval authority must still be verified.
| For Cowork users | For users without Cowork |
|---|---|
| The accompanying holiday-handover-cover-planner-v1.0.0.zip contains the generic skill and guidance, without your work results or colleague details. In a compatible personal-skills environment, attach it and ask for validation and installation. “Plan my holiday handover. Review recent work and propose cover; do not change anything.” Skill | Use the prompt below in an already approved, Work IQ-connected assistant available to you. It supplies the planning instructions without a Cowork skill installation. It does not reproduce Cowork’s execution engine or guarantee identical retrieval. If the assistant cannot inspect a source or setting, the requested result is an explicit gap—not an invented finding. Prompt |
Work IQ supplies permission-aware work context; access remains limited to the signed-in user’s authorised data.
Review the evidence before you delegate.
- Check the dates. Confirm the final day off and first working day back; do not silently resolve conflicting leave markers.
- Check the latest evidence. Open the key citations, especially for blockers, deadlines and approvals. A mention is not proof that a task remains open.
- Agree the cover. Verify the scope with the named person and check decision authority separately. Free/busy does not equal agreement.
- Look at the gaps. A source the assistant could not read belongs in a manual follow-up list, not under an assurance that everything was reviewed.
- Keep changes separate. Review any proposed handover wording before sending it. Request specific calendar or automatic-reply changes only after dates and contacts are agreed.
The aim is simple: leave colleagues with a clearer route forward—not a longer reading list, and not an assumption that responsibility has transferred.
來源:DEV Community · dev.to
