Submitting Timesheets

How to submit a timesheet

How the desktop tracker builds your weekly timesheet, what to review before submitting, and what changes after submission.

Updated

Anastasis timesheets are mostly automatic. The desktop tracker logs your time, takes activity screenshots, and fills the weekly timesheet for you. Your job at the end of the week is to review the draft, add any required context, and submit it for client approval.

Where the data comes from

While the tracker is running, it logs:

  • Time — minute-by-minute, with break detection.
  • Screenshots — periodic captures of your active screen as evidence.
  • Activity summaries — application names and rough categories (browser, code editor, email, etc.). Not keystrokes, not page contents.

All of this syncs to your timesheet automatically. By the end of the week, the timesheet is a draft you only need to review.

Reviewing the draft

From the contractor portal, open Timesheets for your active engagement.
Confirm the week range at the top (e.g., Apr 22–28).
Scan each day’s row: hours, work summary, evidence count, status. Rows in Ready state are good to submit.
Open any row marked Adjustment or Exception. Add a short note if the portal asks for one before you submit.
Optional: add daily notes for context the client will appreciate (“rolled out new resident-onboarding template; queue empty by Thursday”).
When every row is Ready (no unexplained adjustments), click Submit for approval.

Before you submit

If you worked offline, took a client call from your phone, or forgot to start the tracker, handle it before submission. Depending on the engagement setup, the portal may ask for:

  • Date and hours.
  • Short description of the work.
  • Reason for the exception — “tracker not running,” “offline client call,” “phone-based work.”

What the dashboard shows

Before you submit, the dashboard shows four totals:

  • Tracker total — hours auto-generated from verified sessions.
  • Exceptions — time or evidence that needs extra context.
  • Evidence — total screenshots and activity summaries the client will see.
  • Ready rows — how many of the week’s rows are submission-ready.

Submit is gated on every row being Ready (or every adjustment being explained).

After you submit

  • The timesheet status moves from DRAFT to PENDING.
  • Your client is notified and reviews each row in their Approvals queue. They can approve, decline, or send the timesheet into dispute/review.
  • If your client takes no action by Monday at 11:59 PM for the prior week, the submitted timesheet auto-approves.
  • Once a timesheet is approved, it moves to APPROVED and is queued for the weekly billing cycle. Your client’s card is charged on Tuesday; your payout targets Friday — see payment timeline.

Resubmitting after rejection

If a client declines your timesheet, it returns to REJECTED state with their reason attached. Make the corrections, then submit again. A resubmission goes back to PENDING.

What if you forgot to start the tracker

The tracker runs in the background. If you notice it wasn’t running (no screenshots for a stretch you definitely worked), the timesheet will show that gap. Before you submit, either:

  • Add the required exception context if your engagement setup allows it, or
  • Discount the missed time and submit only what the tracker captured.

Be specific. “Client called from job site, took notes on phone” is stronger than “forgot.”

Related