PunchScope support

Support for PunchScope — Timesheet CSV Review 0.3.5 preview, updated 19 October 2026. Installed Chrome validation and publication remain pending.

The CSV will not open

Export UTF-8 CSV/TSV text, choose the matching comma/semicolon/tab delimiter and include a header row. Use clear column names and check the numbered choices when names repeat. Quote delimiters or line breaks correctly. Different field counts are flagged and all supplied cells are retained, rather than silently dropped. XLSX is not accepted directly. The limit is 5 MiB and 50,000 data records.

PunchScope keeps every original cell, including unmapped columns. Prepare a smaller, minimized copy before opening; remove unrelated pay, health, address, message or secret content. Reducing a displayed filter does not remove data from saves or outputs.

Dates, grouping or overlaps look wrong

Check the exact chosen employee/grouping identifier. Spaces, case and leading zeros distinguish IDs; no names or email addresses are silently merged. An Email/User suggestion needs your confirmation.

ISO mode requires explicit offsets or Z in both timestamp columns. Clockify split-date mode requires four distinct start/end date/time columns, one exact date format, 24-hour times and the confirmed exporter profile's IANA timezone. Both original dates are needed in Clockify mode.

For Shared Date + local clocks — explicit +1d end marker, map Date, Clock In and Clock Out separately from the employee ID. Choose the exact date format and one verified source IANA timezone for every row, record a Timezone context basis (1–300 characters), and confirm the zone and date/marker semantics. Unknown or missing context blocks analysis; do not substitute the reviewing computer's zone or infer one from Hours.

Date anchors Clock In. Bare Clock Out uses that same date; only the literal suffix +1d (one ASCII space then +1d) means the next calendar date. Clock In cannot carry a marker. Calendar-day advancement can span a different elapsed duration at daylight-saving changes; it is not an extra 24 hours. Unmarked reversed intervals stay negative, and unsupported suffixes, invalid dates, repeated/nonexistent local times and missing values stay unresolved. This is not a PHIT preset or provider-wide support. Mixed-zone and 12-hour files remain outside the preview.

Use Chrome 144 or later. Split-date interpretation needs native Temporal in the page and worker. Check the original-versus-derived preview; do not mark an unresolved time as correct simply to proceed. Native timezone rules can change with the browser, and current release compatibility with a fresh Clockify-generated export remains unverified.

Elapsed duration is not paid time. A flag, Checked or Follow-up needed does not establish wages, payroll approval or misconduct. Touching intervals do not overlap. Repeated rows remain in the source, and bounded pair examples do not list every overlap.

Saving fails or another tab changed the copy

Save the row review or discard its draft first. New saves require a long unique phrase of at least 12 characters and confirmation. Exact spaces, case and Unicode characters matter; paste from a password manager is allowed. The phrase/key are not stored or exported.

The encrypted browser copy is limited to 8 MiB including overhead, separate from the 10 MiB raw capture/compatible older-save bound and 5 MiB import limit. Extensive notes or legacy content may fit reading but not encrypted saving. Chrome quota errors can still occur. Failure keeps the previous save; there is no evidence truncation or plaintext fallback.

Save/Delete need the installed extension's local storage, WebCrypto and Web Locks. A localhost preview has no save/restore/history/delete fallback. If required APIs are unavailable, use a supported environment; do not assume that every export remains available, because bound exports also require cryptography.

If another cooperating tab saved or deleted the copy, close the dialog and start the action again. Cancel works before a storage write is submitted; a submitted write must finish. There is no autosave, startup restore or sync, so check the save result before closing.

Unlocking, matching and fresh opening

An unlock error can mean the wrong exact phrase or changed/corrupt saved data. A failure leaves the current review and save in place. There is no developer recovery key or phrase reset that decrypts it. Keep the encrypted copy if you may remember the phrase; replacement/deletion does not recover it.

Valid matching v2 saves, including explicitly opened plaintext-v2, can retain bound decisions/reviewer after source/settings/business/engine/result checks and separate final consent. Missing or invalid v2 decision timestamps are rejected; the tool does not invent them. A valid v1 save or valid engine/interpretation/result drift offers a fresh unreviewed copy or history, not reinstated Checked rows. Fresh opening may retain valid reviewer metadata.

Successful matching or fresh replacement clears row Undo; it is not an undoable workspace action. Failed, cancelled or declined restore keeps current work and drafts. Older plaintext remains readable in storage until a successful encrypted save replaces it or you delete it; outside backups remain separate.

History, readable outputs and deletion

Export saved history writes the original captured model without current Temporal re-audit. Historical decisions remain unverified; this is not an active restore or proof of reviewer identity. Encrypted history still needs the phrase and a supported authenticated wrapper. Unsupported or over-limit values can be rejected; values beyond the raw capture bound cannot be read or deleted through these bounded controls.

CSV/current audit/history downloads remain readable and can include complete source content and review notes. Reviewer metadata is in saves/audit/history, not a dedicated row-CSV column. Formula prefixes and fingerprints do not encrypt files. There is no audit/history file-import restoration, review ZIP or forgotten-phrase recovery. A fresh CSV import does not restore earlier decisions/settings/reviewer.

Start again… clears current work/reviewer/row Undo. Delete saved workspace… separately removes the browser copy without its phrase and cannot be undone. Neither retracts original files, downloads, backups or email. The page's last 100 row Undo entries are not a full edit history or included as such in the save/audit.

Contact AK Frames

For product or privacy questions, email akframesltd@gmail.com. Include the PunchScope and Chrome versions, exact error, action, file size/row count and selected date/grouping settings. A few fictional rows that reproduce the problem are preferable to a private file. Crop screenshots to remove staff details.

Never send a phrase, credentials, real employee records, complete staff audit or unrelated sensitive information. Email is optional; your sender details, content and attachments go to AK Frames and the email providers handling delivery/storage. The extension does not send or attach work automatically. Local clearing/deletion does not remove emailed copies; the existing Website and support privacy notice covers that separate channel.

This preview has no account, licence activation, checkout or subscription recovery flow. These draft pages make no response-time, price, refund or compensation promise.