Skip to app details
Back to app library
APPNEURAL APP FAMILYPeople & HR

Timesheets

Know where the week's hours went

Track time per client, project and task with timers and a weekly grid, then approve and bill it.

01 / OVERVIEW

See where it fits in your day.

Each domain keeps clients (GSTIN, place of supply), projects with a billable default, a rate and a budget in hours or money, and tasks with their own rate; an entry's rate comes from the task, the person on the project, the project or the person, in that order. Each person runs one timer (kept in D1 across reloads and devices), adds entries as a duration or from-to with notes and tags, or fills a weekly project-by-day grid with "Copy last week". A week is submitted, then approved, sent back with a comment or reopened by the person's manager or the owner; submitted and approved weeks are locked, and a Friday 17:00 IST cron reminds people with unsubmitted weeks and days without time. Reports by client, project, person, task or day show billable and non-billable hours, amounts, utilisation against weekly capacity and budget burn, with CSV. Approved billable time is exported as unbilled lines, or sent to Quotations as a draft quote with SAC and GST, and marked billed. Projects and tasks can be imported from Boards. Employees (member role) see only their own time. POST /api/v1/entries with idempotency, webhooks, and Claude to turn a described day into draft entries and to write a weekly client update.

A LOOK INSIDEExample layout · sample content
This week's time
MON9
Sample planWebsite redesign
TUE10
WED11
Sample planClient call
THU12
Sample planMonthly report
FRI13
Illustrative weekly layout
02 / CAPABILITIES

Built around the work you do.

What Timesheets does for you.

01

Time entry

A timer that survives reloads, manual entries and a weekly project-by-day grid.

02

Approval

People submit their week; their manager approves or sends it back, and approved weeks lock.

03

Reports

Billable and non-billable hours, utilisation, budget burn and amounts by client, project and person.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Timesheets. What you can do depends on your access in the app.

01

Set up projects

Add clients, projects, tasks and rates, or import them from Boards.

02

Log the week

Start a timer or fill the weekly grid, then submit.

03

Approve and bill

Approve the weeks and bill the approved time.

YOUR NEXT MOVE

Make Timesheets part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE— items
P2VERIFIEDPUBLISHED
Overview

Purpose and boundaries

Each domain keeps clients (GSTIN, place of supply), projects with a billable default, a rate and a budget in hours or money, and tasks with their own rate; an entry's rate comes from the task, the person on the project, the project or the person, in that order. Each person runs one timer (kept in D1 across reloads and devices), adds entries as a duration or from-to with notes and tags, or fills a weekly project-by-day grid with "Copy last week". A week is submitted, then approved, sent back with a comment or reopened by the person's manager or the owner; submitted and approved weeks are locked, and a Friday 17:00 IST cron reminds people with unsubmitted weeks and days without time. Reports by client, project, person, task or day show billable and non-billable hours, amounts, utilisation against weekly capacity and budget burn, with CSV. Approved billable time is exported as unbilled lines, or sent to Quotations as a draft quote with SAC and GST, and marked billed. Projects and tasks can be imported from Boards. Employees (member role) see only their own time. POST /api/v1/entries with idempotency, webhooks, and Claude to turn a described day into draft entries and to write a weekly client update.

Actual time per client, project and task: timers, entries and a weekly grid, weekly approval, billable rates, utilisation and budget reports, and unbilled time sent on as a quote.

Plans and tasks belong to Boards; bookings belong to Timeslots; cron jobs belong to Scheduling; the quote itself belongs to Quotations.

Priority
P2
Portfolio
People & HR
Capability
People & HR
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:03:12
Semantic inventory

Every number says what it counts

—Count unavailabletrackedEntityCount · catalog-api:unavailable
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

timesheet schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

timesheets.appneurox.com DEPLOYED

timesheets.appneurox.com

Worker
timesheet-catalog
Health
HEALTHY
Last deployment
2026-11-18 14:03:12
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/timesheet-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app