Timesheet validation

Timesheet validation chains two steps:

1. Internal validation — a member submits their period, a manager approves (or rejects) the lines.
2. Client signature — once the projects are validated internally, you send a signature request to the client via a magic link; they sign without an account, and an evidential two-logo PDF is emailed to both parties.

Until a step is cleared, the next one stays blocked. Nothing unlocks on its own: a contest or a rejection must be explicitly reopened.

Enable the feature

Validation is off by default and configured per workspace.

1. Open Workspace settings → Timesheets (Owner or Admin).
2. Turn on Timesheet validation.

A Timesheets entry then appears in the sidebar, and the Validations tab becomes available on every client page.

Step 1 — Internal validation

Submit your period (member)

1. Go to Timesheets → My timesheets.
2. Pick the period and the client, then click Preview: Tickr groups your entries by project and by day.
3. Click Submit. The covered entries are locked (not editable) until the submission is reopened.

Validate (manager)

Reserved for the Project lead, Admin and Owner roles.

1. Go to Timesheets → To validate.
2. For each line (one project): Approve or Reject (a reason is required on reject). The Approve all button validates the whole submission at once.
3. The member sees the outcome and, on a rejection, fixes it and resubmits.

Every state change is journaled (who, what, when) and visible in the submission’s history.

Deadlines and reminders (optional)

Under Timesheets → Closings, a manager can set a submission deadline for a period. Tickr automatically emails a reminder to members who haven’t submitted yet, within the two days before the deadline.

Reopen a submission

The owner of a submission can reopen it (Reopen button): its status returns to Reopened and the entries become editable again. They fix and resubmit. Reopening is always explicit.

Step 2 — Client signature

Set the issuer identity (one-time)

The PDF and the emails show your identity (the “issuer”).

1. Workspace settings → Identity (Owner or Admin).
2. Fill in legal name, address, and upload your logo (PNG, JPEG or WebP, 512 KiB maximum).

Set the client identity and its contacts

1. Open the client page from Clients, Identity tab.
2. Fill in the client’s legal name, address and logo.
3. Add one or more contacts (name + email): these are the people who can receive the signature request.

Send a signature request

1. On the client page, open the Validations tab.
2. Pick the period (the current month by default). Tickr lists the ready projects — a project is ready when all of its lines have been validated internally. Non-ready projects are greyed out (“X/N validated”).
3. Tick the projects to include and set the document options:
   • Show task detail;
   • Show amounts (hidden by default).
4. Pick the recipients: address-book contacts and/or ad-hoc emails.
5. Click Send request.

Tickr creates the request, freezes an immutable snapshot of the recap (logos and figures are frozen at that moment) and emails the magic link. A copyable link is also shown in the app — handy if the email fails to send: you can pass it on manually.

Client side: sign or contest (no account)

The contact receives an email with a link to a public page (/approve/…), with no sign-in.

1. They review the recap (per project, expandable by task if the option is on; hours only, unless amounts are shown).
2. To approve: they enter their name and tick the attestation box.
3. To contest: they enter a reason.

On approval, Tickr generates the two-logo evidential PDF (issuer + client logos, recap, attestation, signature date and IP) and emails it to the contact and to you. The PDF stays downloadable from the client page history.

Contest → reopen → resend

1. On a contest, you’re notified by email; nothing is unlocked automatically.
2. An Owner or Admin reopens the affected lines (Reopen lines button on the contested request) — the M1 entries become editable again.
3. The member fixes and resubmits, the manager re-validates.
4. You resend a request: a new link is generated and the old one stops working.

Reminders, expiry, manual resend

• A request with no response is reminded automatically (up to twice); each reminder regenerates the link (the old one is invalidated).
• A link expires after 30 days; the request then moves to Expired.
• On a sent request, the Resend button regenerates the link and re-sends it to the original recipients — and shows a copyable link.

Who can do what

Action	Required role
Enable the feature, set the issuer identity	Owner / Admin
Submit your own timesheet	Any member
Approve / reject lines, manage closings	Project lead +
Manage a client’s identity and contacts, send / resend a request	Project lead +
Reopen the lines of a contested request	Owner / Admin
Sign or contest	Client contact (no account)

Good to know

• The snapshot sent to the client is frozen: editing entries afterwards does not change a request that has already been sent.
• The signature link is a secret: anyone who has it can sign. Only share it with the intended contact.
• Rejecting internally or contesting on the client side deletes nothing — the fix always goes through an explicit reopen.