Feature · Timesheet Approvals

    The Draft → Pending → Approved workflow

    Not a status label on a card — the actual gate between a tracked minute and everything that reads it.

    The short answer

    Every time entry in Flocci Timesheets moves through DRAFT → PENDING → APPROVED or REJECTED. New entries default to Draft. Only Approved entries are admitted into reports, analytics aggregates and payroll, and that filter is enforced in the query layer rather than in the interface.

    What it does, precisely

    • Members submit their own Drafts and Rejected entries, by id list or by date range.
    • Editing a Rejected entry resubmits it automatically — no second manual submit.
    • Rejection carries a written reason back to the member.
    • Bulk approve and bulk reject, with unauthorised entries filtered out silently rather than failing the batch.
    • Approval locks the entry against further edits or deletion, permanently.
    • Solo self-managed mode: a one-member workspace lands submissions directly as Approved.

    What this does not do yet

    There is no multi-stage approval chain (reviewer, then a second reviewer). Approval is a single review step by an authorised reviewer.

    Timesheet Approvals — common questions

    What does “enforced in the query layer” mean?
    It means reports, analytics and payroll build their queries with the Approved filter applied at the data layer, not by hiding rows in the interface. There is no screen, export or API shape in which unapproved hours are counted.
    Can an approved entry be unapproved?
    No. Immutability after approval is the property that makes the record defensible; corrections are made forward as new entries so the history of what was approved stays intact.
    What happens in a one-person workspace?
    Solo self-managed mode applies: with exactly one active member, submissions land Approved immediately with the submitter recorded as approver, leave requests are created Approved, and the approval surfaces are hidden. Inviting a second member restores the queue automatically.

    See it on your own data in under a minute.

    Create a workspace, start a timer, submit it. Nothing about that path costs a credit.