The Holiday Project Index: A Starting Point for the Colleague Covering

The holiday handoff says "everything is in the shared folder." The folder contains several drafts, an old slide deck and a note whose title is "final." The material may be there, but its roles are not explained.

An index is a map to those explanations. It need not duplicate the documents or tell a covering colleague how to operate unfamiliar systems. It can simply identify which document answers which kind of question.

Key takeaways

• An index explains where to start, not how to operate a system.

• Give each linked document a short purpose statement.

• Separate current context from historical background.

• Leave open questions visibly open for the returning team.

Step 1: Give each document a job

A fictional workshop project has three documents: an agenda draft, a background note and a list of unresolved wording questions. The index can explain those jobs in one line each.

The descriptions should say what the documents contain, not claim they are complete. "Questions discussed so far" is different from "all possible questions answered."

Step 2: Use labels the covering reader can understand

Google's audience guidance points out that project proximity affects what a reader knows. A colleague covering for a few days may know the organization well but not the project's local nicknames.

Write the index for that difference. Explain the document's purpose rather than relying on a filename that made sense only in last month's conversation.

Step 3: Keep the index from becoming another copy

If the agenda already lives in a named document, the index can point there instead of copying its content. The index's useful addition is the explanation of what the link is for.

A note beside an old document can say "background, not the current draft" when that is known to be true. If the current version is not clear, record that as a question rather than select one by appearance.

This is deliberately different from standing operating orders. It contains no restart instructions, account details or authority to change systems. It gives a colleague a starting point for understanding the work while the usual contributors are away.

Sources for the definitions and writing principles discussed here: Google, Technical Writing One: Audience, last updated March 28, 2025. The examples and suggested discussion formats are illustrative.

Frequently asked questions

Is the index the same as a handoff note?

It is narrower. A handoff explains the work; the index points to where those explanations live.

Must it cover the whole project history?

No. A small index can distinguish the present draft, useful background and open questions without reproducing every past conversation.

Should the index tell the colleague what systems they may change?

Not this index. Operational authority and procedures belong in their appropriate workflow, not in a document-navigation aid.

A practical next step

Open a fictional project folder as though you were covering it for a colleague. Add one line explaining which document to read first and why. Book a Decision-Clarity Call for help making technology work easier to explain.