Make project labels useful on a time card

Give labels one job

A project label should help you recognize what a shift belongs to. Use a short, repeatable name for that purpose. Put one-off context in notes instead of turning each label into a sentence. This keeps the repeated part stable while leaving room for details such as a review session or a change in location.

Small differences can complicate review

Do not silently rewrite user text

A tool should preserve the text you entered rather than guessing that similar labels mean the same project. When importing a spreadsheet, inspect the preview for inconsistent spelling or surrounding whitespace. Make any cleanup deliberately so an exported record does not unexpectedly change the identity of a task.

Keep split sessions understandable

Two shifts on one day can share a label or use different labels. The day total still adds their net minutes, but the labels help explain why there are separate records. For example, a morning planning session and an afternoon build session may be easier to review as separate rows with concise notes than as one long undifferentiated span.

Use notes sparingly and privately

Record enough context to understand the shift later. Avoid adding personal or sensitive details that the time card does not need. A note is included wherever you choose to export or share it, so review the output fields before sending a copy to someone else.

A CSV field can contain commas, quotes and Unicode text. Those characters must be preserved safely, not stripped until the note changes meaning. After importing or exporting, review a representative note as well as the numeric total.

A short review habit

1. Choose one spelling for recurring labels.
2. Use notes for details that apply to only one session.
3. Review imported labels before creating the new project.
4. Check whether the intended recipient needs notes in the reading copy.