AWRA OpsHub Search

AWRA Help Center

Copy link
Help Workflow Support
01 Projects & Tasks Overview Projects & Tasks

Time, Budget & Flexibility

Know what work costs, and shape the module to how your team actually works — time tracking and budgets, plus labels, checklists, watchers, saved views, recurring tasks, templates and per-project statuses.

Logging Time (Effort, Not Attendance)

On a task, log hours per day with an optional note; the worker defaults to your own employee record. Set estimated hours to compare against actuals ("X logged of Y estimated"). This is effort — how long work took, and whether it's billable — and it is deliberately separate from HR attendance, which is presence (clock-in/out). They live in different systems so you never keep two conflicting timesheets.

Project Budgets

Give a project a budget in hours and/or amount. A burn bar shows logged effort against it, turning from green to red as you approach or pass the budget. Delivery analytics rolls up effort per employee and shows a billable / non-billable split.

Flexibility

FeatureWhat it does
LabelsA colored tag catalogue; tag tasks and filter by label.
ChecklistsBreak a task into sub-items with a live progress bar.
WatchersFollow a task to get notified on comments and status changes.
Saved viewsSave your favourite "my tasks" filter combinations as named views.
Recurring tasksRepeat daily/weekly/monthly; completing one spawns the next until an optional end date.
Project templatesSave a project as a blueprint and clone its tasks, milestones, checklists and statuses.
Custom statusesGive a project its own board columns; mark which count as done or cancelled.

Permissions

Managing labels and per-project statuses is a project-config permission; tagging tasks and editing checklists use task-edit; logging time has its own permission; and saved views are personal to each user. If something is missing, it is usually a permission difference — see the Permissions Guide. Back to the Projects Overview.

Need help with this topic?

Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.

Open support guide