Time entry
A timer that survives reloads, manual entries and a weekly project-by-day grid.
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.
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.
What Timesheets does for you.
A timer that survives reloads, manual entries and a weekly project-by-day grid.
People submit their week; their manager approves or sends it back, and approved weeks lock.
Billable and non-billable hours, utilisation, budget burn and amounts by client, project and person.
A suggested path for Timesheets. What you can do depends on your access in the app.
Add clients, projects, tasks and rates, or import them from Boards.
Start a timer or fill the weekly grid, then submit.
Approve the weeks and bill the approved time.
Live host, inventory, governance, health checks, verification, dependencies and history.
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.
Plans and tasks belong to Boards; bookings belong to Timeslots; cron jobs belong to Scheduling; the quote itself belongs to Quotations.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
timesheets.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.