Help for PunchScope — Timesheet CSV Review 0.3.5 preview, updated 19 October 2026. Installed Chrome validation and publication remain pending. This is a local review of one business's CSV, not a wage calculation, pay approval or misconduct decision.
Prepare one source file
- Use Try ISO sample or Try Clockify sample for fictional examples. Export or save anything you need before starting another review.
- Enter a business name or reference. Choose CSV delimiter to match a comma, semicolon or tab file, then select UTF-8 CSV/TSV text with a header row. The import limit is 5 MiB and 50,000 data records; XLSX workbooks need exporting first.
- Minimize the file before opening. PunchScope retains the complete text and every original cell, including columns you do not map. Exclude unrelated pay, health, address, message or secret data.
- Confirm the exact employee/grouping ID and optional name column. Leading zeros, case and spaces remain significant; IDs are not merged or normalized. An Email/User suggestion is only a mapping suggestion, not proof of employee identity.
The preview targets Chrome 144 or later. Split local dates require native Temporal in the page and worker; no replacement timezone library is bundled. Required browser APIs must be available before the relevant operation can run.
Confirm how dates are interpreted
For ISO timestamps with explicit offsets, map separate start/end timestamp columns. Values need an explicit offset or Z, such as 2026-10-15T09:00:00+01:00. A local date/time without an offset remains explained and unresolved; the tool does not guess its zone or date order.
For Clockify Detailed — split dates and times, map four distinct columns: Start Date, Start Time, End Date and End Time. Choose exactly DD/MM/YYYY, MM/DD/YYYY or YYYY-MM-DD, enter the exporter's source IANA timezone and confirm that every row uses it. Check the profile used to export the file; the reviewing computer's timezone is not substituted. Only 24-hour HH:mm or HH:mm:ss is supported, and both dates are required.
For Shared Date + local clocks — explicit +1d end marker, map Date, Clock In and Clock Out separately from the employee ID. Choose the exact source date format, enter one verified source IANA timezone for every row and record how that zone was verified in Timezone context basis (1–300 characters). Confirm both the source zone and the date/marker semantics. Missing or unknown zone/context blocks analysis; the file, reviewing computer and Hours column do not supply it.
In this mode, Date anchors Clock In. A bare HH:mm or HH:mm:ss Clock Out uses that same date. Only the literal suffix +1d — one ASCII space followed by +1d — means the next calendar date. Clock In accepts no marker. The calendar date advances before timezone resolution, rather than adding 24 elapsed hours. An unmarked reversed interval stays negative; other suffixes, missing values and invalid dates remain unresolved. This is an explicit format choice, not a PHIT preset or provider-wide compatibility claim.
Use Preview date interpretation to compare originals with derived calendar dates, offsets and UTC endpoints before confirming. Repeated or nonexistent daylight-saving times remain unresolved; no earlier/later occurrence or unmarked overnight end date is invented. Mixed-zone exports and 12-hour times are outside this preview. Clockify still requires both original dates; the shared-date mode uses only the confirmed same-date/exact-marker policy. A fresh provider-generated Clockify export has not yet been validated for this release.
Choose minimum/maximum elapsed minutes, check the source and settings confirmation, then select Find review exceptions. Elapsed duration includes everything between supplied endpoints; paid breaks, contractual rules, missing scheduled shifts and payable-hours reconstruction are outside the checks.
Review alongside the source
Select a row to inspect original cells, interpreted times and explained flags. Checks include missing/unsupported timestamps, reversed or zero intervals, duration outside your range, exact repeated complete rows, outer ID whitespace and overlaps for the exact chosen identifier. Duplicate rows stay visible. Touching intervals are not overlaps. When overlap examples are capped, every participant is still flagged; displayed pairs are not a complete list.
Choose Checked, Follow-up needed or Unresolved, add a note and select Save row review. Follow-up needs a note. These are human review records, not payroll or disciplinary decisions. Rows with no automatic flags still need your judgment; keep uncertain rows unresolved.
Search and filters change the view, not the export scope. Undo review reverses recent row decisions, up to the last 100 entries in this page. This is not an immutable history of every edit. Save or discard a row draft before saving a workspace or moving on when prompted.
Download the review
Export decisions offers Reviewed CSV, Unresolved CSV and Audit JSON. Checked and Follow-up needed rows go to the reviewed output; remaining retained rows go to unresolved, including those without flags. Filters do not hide rows from these outputs. Blank CSV records outside quoted fields are counted and skipped. Explicit quoted-empty or delimiter-only records remain review rows; the audit keeps the original CSV text.
CSV includes original columns and row notes/times; formula-like cells receive a leading apostrophe. Audit JSON retains original text, file details, settings, results and current decisions. The optional reviewer reference is saved/restored and included in audit/history JSON, not added as a dedicated row-CSV column or verified signature. There is no review ZIP.
Every output is readable staff data. Saved-copy encryption does not protect downloads, the open page or original files. Keep and share them deliberately. Audit/history downloads are records for inspection; there is no file-import restore flow for them.
Save deliberately
Save locally… asks for a long unique passphrase and confirmation; choose Encrypt and save. Use at least 12 characters. Exact characters, spaces and case matter; paste from a password manager is allowed. The phrase/key are not stored or exported, and there is no developer recovery key.
One encrypted browser-profile copy holds the source, business, settings, reviewer and current decisions/notes/times. It has an 8 MiB limit including overhead; the separate raw capture/compatible legacy reader is bounded at 10 MiB. Neither is the import limit or a promise of remaining browser quota. Save failure keeps the older copy rather than truncating evidence. Keep original files and check the success message before assuming a save exists.
Later edits need another save. There is no autosave, startup restore, sync or localhost saving fallback. A conflicting Save/Delete from another cooperating tab stops replacement; start the action again. Cancel is available before a submitted storage write, but a write already submitted must finish before its result is known.
Restore, start fresh or export history
Restore saved checks the captured copy and prepares a choice before replacing current work. Encrypted copies need the exact phrase. Valid matching v2 source/business/settings/engine/results can retain bound decisions/reviewer, including from explicitly opened older plaintext-v2. Each v2 decision needs its own valid saved timestamp with an explicit offset; missing times are rejected rather than filled with now.
A valid schema-v1 save or valid changed engine/interpretation/results can open only as a fresh unreviewed copy, or be exported as history. Fresh opening discards historical row decisions; valid reviewer metadata may remain. Malformed data is rejected for active use. Successful replacement clears the current row Undo stack and cannot be undone as a workspace action. Failed, cancelled or declined restore preserves current work.
Older plaintext stays plaintext until a successful encrypted save replaces it or you delete it. Opening does not itself change the save. Export saved history instead downloads the original historical model without current Temporal re-audit or replacing open work. Its decisions are unverified historical evidence. Encrypted history still needs the phrase and a supported authenticated wrapper; history does not restore or unlock another copy.
Start again… clears current work/reviewer/Undo and leaves the browser save. Privacy & saved data → Delete saved workspace… removes that separate copy without its phrase and cannot be undone. Neither removes originals, downloads, backups or sent email. If the phrase is lost, you can inspect any readable archives or start anew from the original CSV, but cannot recover the encrypted workspace or its decisions through an audit/history import.
Questions
Contact AK Frames at akframesltd@gmail.com using only a minimized fictional example. Do not send a phrase, private staff file or full audit. Email is voluntary and separate from local processing; the Website and support privacy notice describes website/email handling. This preview has no checkout or paid restriction; no commercial offer is established by these draft pages.
Looking for another detail?