Home>Case Studies>Project hours from weekly timesheets to billable reports, in one intranet
EngineeringHR & AdminIntranet Systems

Hours that belong toreal work, every week.

How a process engineering firm runs assigned project work, weekly timesheets and approvals, and the company intranet beside them, from one role-based system whose hours feed project, department and billability reports.

A weekly timesheet grid by project and day, with a submitted status
ClientQuanta Process & Project Services
IndustryProcess and project engineering
UsersEngineers, managers and HR
ScopeProjects, timesheets and reports, plus HR intranet
EngagementWeb intranet
01

The situation

A process engineering firm runs many live jobs at once. Hours are split across clients, departments and tasks, and the same week has to be filled by the engineer, seen by a manager, and later counted for the project.

Spreadsheets made that path fragile: who is assigned, which task is billable, which week is still a draft, and how many hours a project has already used. Quanta Process needed one intranet for that work, and for the company information that sits beside it.

Which task is billable, which week is still a draft, and how many hours a project has already used.

02

What we built

We treated the project and the week as the two units of work. A project holds the client, departments, tasks and hour budget. A timesheet holds one employee’s week, and people can log time only against project tasks they are assigned to, so every hour in a report belongs to a real job.

Submitting a week locks it and writes a status history, so a later approval or rejection never overwrites the path. The same hours then feed project, employee, department and billability reports, each with a date filter and Excel export.

Inside the intranet

One employee’s week, from assignment to the report.

Projects and assignment

  • Clients, departments and a task master
  • Projects with allocated hours by department
  • Employees assigned to project tasks
  • Project grid or list views with status

Weekly timesheets

  • Monday to Sunday entry against assigned tasks
  • Time off for company holidays and annual leave on the same sheet
  • Save as draft or submit, with submission locking the week
  • Approve or reject, with a status history for every change

Reports and company life

  • Project hours, employee, department and billability reports
  • Pending-timesheet reminders and submission notifications
  • News, events, HR documents, quick links and holidays
  • Role-based dashboards for admins, managers and employees

What it looks like

Screens from the staging environment, populated with test data.

Admin dashboard with users, clients, departments and project status
Project details, with hours used against allocated hours by department
Employee timesheets awaiting review, with status
A submitted timesheet, with daily totals and the task breakdown
03

What changed

01

Hours belong to real work

A timesheet offers only the projects an employee is assigned to, so the hours that reach a report already sit against a live job.

02

Budgets visible on the project

Used and pending hours sit beside each project’s department allocations, so progress is read from the system rather than a separate spreadsheet.

03

Billable time separated from the rest

Billability on each task, and the overhead and business development flags on projects, let reports separate chargeable work from everything else.

04

How it was built

A web application with role-based screens, so an employee sees their own timesheets and the HR pages while administration and reports stay with the roles that own them.

ApplicationLaravel 11 on PHP 8.2
InterfaceBootstrap 5, grid and list views, Excel export on reports
AccessRoles and permissions on routes and menu items
RecordsClients, projects, tasks, assignments, weekly timesheets and status history

Is your team still filling timesheets in a spreadsheet?

Tell us how projects, hours and billability reach your management today. We will tell you honestly what an intranet would change, and what it would not.