Skip to content

Business workflow use case

Confirm a month of project time in one click when nothing changed.

Each employee's month on a project arrives with an 8-hour billable day on every working day; they fix the days that differ and submit.

The system creates the employee's timesheet line and a Submit task on the 1st. The employee adjusts the days on a month calendar in the Personal workspace and submits it, and a manager approves.

Use the documented operating model as a starting point, then adapt fields, approvals, reports, or connected areas when your process differs.

Pre-filled 8-hour working daysMonth calendar bookingFill Month in one stepRates and amounts hiddenSubmit from the Inbox

Before you start

Put the right records and roles in place.

Each employee needs an Employee record whose Username matches their login, and must be on the project's team; otherwise no timesheet line is generated for them. An administrator without an Employee record can walk the flow by acting as an employee.

Documented sequence

From the pre-filled month to the submitted timesheet.

Each stage identifies the action, handoff, or record change that moves the work forward.

  1. 01

    Find the month waiting — Employee

    On the 1st, a DRAFT timesheet line is created for every active project the employee is on, with an 8-hour billable day per working day. A Submit task appears in their Inbox, the home page of the Personal workspace.

  2. 02

    Adjust the days — Employee

    In My Employee Timesheets the days show as a month calendar: click an empty date to add a day, or an entry to change its hours, Billable flag or task. On an empty month, Fill Month books every weekday in one step.

  3. 03

    Submit — Employee

    The Submit task shows the placeholder number, the project-month, the total hours and the status, with no money fields. Submitting moves the line to SUBMITTED and sends it to a manager for approval.

Current scope

Once a timesheet is APPROVED it is locked against edits and deletes; a correction after approval goes through the manager.

A starting point, not a fixed package

Fit the timesheet to how your team works.

Each day carries its own hours, Billable flag and optional project task, and a manager can still book days for someone who is away on the back-office pages. Other day patterns, additional fields or a different approval route can be scoped as a Custom adaptation.

Try BusinessIntents

Decision-stage answers

Fill in your timesheet FAQs

Do employees see their billing rate or the amounts?

No. The rate, each day's amount and the timesheet's billable amount never leave the server for the Personal workspace. Employees see their total hours, recomputed as they edit.

What happens if the timesheet is rejected?

It turns REJECTED, clearly distinct from a fresh draft, and the Submit task comes straight back to the employee's Inbox. They correct the days and resubmit in the same flow.

Can someone else book time for an employee who is away?

Yes. A manager can book the days on the back-office pages, or an entitled user can act as that employee in the Personal workspace. The entry is recorded as the employee's, while the audit log keeps the real login.

Why did no timesheet arrive this month?

Either the project is not ACTIVE, or the employee was not on its team when the month was generated. The project manager can check both.

Review the real workflow

Book one real month of project time in BusinessIntents.

Use a real record or transaction to compare the documented flow with the way your team works today.

The BusinessIntents Business Suite - end-user guide.