Worklog / Guide
Work-record field guide

Choose CSV, spreadsheet or PDF for a time report

Match machine-readable handoff or human review to the recipient.

Use a structured export for calculations or system transfer and a readable report for human review. Choose the format by the receiving task, not by which download button is easiest to find.

Explore this collection →

Documentation reviewed · 23 Sep 2026No hands-on merchant testing

Separate presentation from data interchange

A PDF can preserve a reviewable layout but is usually a poor contract for field-by-field import. CSV is plain delimited data whose types must be agreed separately. A spreadsheet can include typed cells and formatting, but those conveniences can also hide transformations. Check whether the recipient needs a visual record, machine-readable rows, or both.

Compare a single known record in each format

Use a fictional contributor ID 00042, a 90-minute duration and a project label containing a comma. Inspect whether each format preserves identity, unit and complete text. Time Doctor documents CSV, XLS and PDF custom exports; format availability alone does not establish that every layout contains the same fields. Record the exact report settings alongside the chosen file.

Make the CSV contract explicit

Specify the delimiter, encoding, header names, date convention, duration unit and quote handling. Let an appropriate parser handle quoted fields rather than splitting text at every comma. A value such as “Research, phase 2” should remain one field. Check row counts before and after opening the file. Keep an untouched original so any change introduced by a spreadsheet can be traced.

Keep the review copy and import copy related

If the recipient needs both a PDF and a CSV, label them with the same batch identity and reconcile their totals at the same granularity. Do not assume files downloaded at different times contain the same corrections. If an automated importer requires a particular schema, use its specification and a small test; a visually neat spreadsheet is not evidence of import readiness.

Continue this work-record check

Use the linked guide for the next decision in this workflow. Keep your original records separate from experiments and record any unresolved requirement before changing a live process.

Sources and boundaries

Primary documentation supports the dated product facts. Proposed checks and fictional examples are our editorial method, not observed product results.