Selected work ↗WORKFORCE & SITE OPERATIONS / PRODUCT ENGINEERINGPRODUCT CASE STUDY

WorkPulse · Web + mobile

Every site. Every team.One connectedoperation.

From the first check-in to the final approval.
A shared workspace for the people doing the work
and the people keeping the business moving.

Explore the story
THE PLATFORM IN FOCUSWEB OVERSIGHT × MOBILE EXECUTION
Field work meets business oversight.Attendance · Tasks · Payroll · Site accounts

Actual application screenshots supplied for this case study. Click any screen to enlarge.

THE PRODUCTWorkPulse by Algentrix
THE EXPERIENCESAdmin web · Supervisor & worker mobile
THE SCOPEPeople · Work · Documents · Site money
THE FOUNDATIONReact · FastAPI · PostgreSQL

The work is distributed.
The context shouldn’t be.

When teams operate across sites, attendance, task updates, documents and expenses need to remain connected. WorkPulse brings those records into a shared platform while giving each person a focused way to act.

01

Make today visible.

Help owners and supervisors see who is present, where work is happening and which issues need attention.

02

Make responsibility explicit.

Connect an assignment to the worker, the site, supporting evidence and the person who reviews it.

03

Carry records into decisions.

Bring attendance into payroll review, document requirements into worker readiness, and site receipts and expenses into reporting.

02↗

Connected experiences
Web oversight & mobile workflows

05↗

Core operational areas
Attendance, tasks, payroll, documents, accounts

01↗

Shared API foundation
Scoped identity, rules & records

The whole business.
A useful next action.

A React workspace for owners, administrators and supervisors. Move from an overview to the records behind it, with access shaped by permissions, site scope and subscription features.

A shared view of workers, attendance, open tasks, payroll and site actions.

ACTUAL PRODUCT SCREEN · CLICK TO ENLARGE

Start with the exceptions.

The dashboard combines site status with pending documents, open tasks and attendance fixes. Quick actions take the operator into the work.

Review before finalising pay.

Worker readiness, advances and payments sit alongside the monthly estimate. Generate & Lock gives payroll a defined finalisation step.

Keep reporting close.

Attendance statements, daily earnings, salary slips, site financial reports and business summaries share one reports hub.

The right context.
Where work happens.

Supervisors need visibility across their sites. Workers need their current check-in, assigned tasks and personal records. The supplied mobile screens show distinct experiences built around those responsibilities.

From the team overview to an individual’s day.

01 / SUPERVISOR DASHBOARDSupervisor dashboard

Workers, pending work and documents, with a site-by-site overview.

02 / WORKER HOMEWorker home

Current site and check-in status alongside personal attendance, salary and leave.

03 / SITE-WISE ATTENDANCESite-wise attendance

Review on-time, late and absent counts across locations.

04 / STATUS-WISE ATTENDANCEStatus-wise attendance

Find the people behind each attendance status and their recorded check-in times.

05 / TASK LISTTask list

Priorities, due dates, assigned people and overdue work in one list.

Swipe or scroll through the original mobile captures. Screen values represent the captured application state.

Assigned isn’t finished.
Approved is.

A single Pole Wiring task shows the full handoff: define the work, name the people responsible, record progress and photo proof, then review and close it.

THE TASK / POLE WIRING

Define the task

Give each task a name, category, site, due date and priority.

Site contextNamed responsibilityRecorded evidence
A deliberate approval boundary.

Workers submit for review. Reviewers approve the work or request rework. Completed tasks retain the history and close further updates.

Select a step to follow the same task.

More than file storage.
A route to readiness.

Company, worker and site documents are organised around requirements, expiry and review. An action centre brings missing papers and pending decisions into view.

REQUIREMENTS

Know what is missing.

Compliance profiles give workers a defined checklist. Required and optional records remain distinct.

REVIEW & EXPIRY

Know what needs a decision.

Preview and approve or reject uploads, while approaching expiry and expired records remain visible.

READINESS

Make the next step clear.

A worker with missing required documents is directed to My Documents before continuing field work.

One document workflow across three kinds of records.

01 / DOCUMENTS ACTION CENTREDocuments action centre

Surface missing requirements, approaching expiry and pending approvals.

02 / COMPANY DOCUMENTSCompany documents

Track required and optional uploads, approaching expiry and expired documents.

03 / WORKER DOCUMENTSWorker documents

Review completion against a worker compliance profile and approved uploads.

04 / SITE DOCUMENTSSite documents

Keep drawings, work orders, BOQ and other site records together.

05 / DOCUMENT REVIEWDocument review

Preview worker uploads and approve or reject the submitted document.

06 / READINESS GATEReadiness gate

Direct workers to missing required documents before continuing field work.

Every receipt. Every expense.
Connected to a site.

Record customer payments and advances alongside site expenses and supervisor cash. Bring the amount, location, funding source and supporting bill into the same operational record.

Money left / surplus reflects the recorded receipts minus site spend for the selected period. It should be read in that context, rather than as an independently verified accounting profit.

Separate responsibilities.
A shared foundation.

WorkPulse’s modular FastAPI backend connects the tenant experience to shared operational records. A separate platform console manages companies, subscription plans, features and operator access.

TENANT WEBReact + TypeScriptVite · Shared UI components
MOBILE EXPERIENCEWorkers & supervisorsAttendance · Tasks · Documents · Accounts
TENANT API /apiFastAPIPermissions · Site scope · Subscription features
Layered domain modules
OPERATIONAL DATAPostgreSQLSQLAlchemy · Alembic
Company-scoped records
01 / ACCESS

Access follows the work.

Tenant OTP authentication, permission checks and site authorisation govern operational access. Platform authentication uses password and MFA with a separate token audience.

02 / STRUCTURE

Domains stay understandable.

Attendance, tasks, payroll, documents and site accounts use domain modules with API contracts, services and persistence layers.

03 / DELIVERY

Built to evolve.

Shared web primitives, database migrations, API automation and frontend tests provide foundations for continued product development.

Connected records.
Clearer decisions.

The product outcome is a connected operational foundation: owners can review the business, supervisors can coordinate sites, and workers can act on their own tasks and records.

A shared view of the day.

People, sites, attendance and pending work can be reviewed through the same operational context.

A traceable task handoff.

Assignment, activity, submitted proof and approval remain part of one task history.

Readiness made visible.

Missing, expiring and pending documents have a defined route to upload, review and resolution.

Financial records with context.

Payroll review and site accounts retain the worker or location behind each operational decision.

These are implemented product capabilities. This case study does not claim measured time savings, revenue gains or cost reductions. Numbers in screenshots are captured application data, not impact metrics.

THE DETAILS MATTER

Useful answers.
No guesswork.

Who is WorkPulse designed for?

Indian small and medium businesses managing people across shops, branches and field locations. The supplied examples show site-based construction and electrical work.

Do workers and supervisors see the same experience?

They share the operational foundation, but their screens and actions reflect their responsibilities and permissions. A worker can review personal attendance and assigned work; a supervisor can coordinate the sites within their access scope.

How does a task become complete?

The assigned worker records work and submits it for review. An authorised reviewer approves it or requests rework. Approval moves it to Completed and closes further activity.

What connects attendance and payroll?

The backend includes attendance-based earnings and payroll review. The web console brings worker readiness, advances and payments into the monthly workflow before generation and locking.

Are these actual product screenshots?

Yes. All 23 application images were supplied for this case study. They show the captured product state and are not evidence of customer growth or measured business impact.

See the workflow.
In your language.

Three walkthroughs of attendance, tasks and the work happening across sites.

01 / HINDIहिन्दी
02 / ENGLISHWALKTHROUGH
03 / MARATHIमराठी

LET’S BUILD WHAT’S NEXT

Your operations.
Connected by design.

A web and mobile product built around your people,
your workflows and the decisions that matter.

Discuss your project ↗

Product screen

Actual application screenshot supplied for this case study. Escape closes the preview.