From equipment issue to reviewed, completed work.

The operational problem

Asset lists, task messages, and inspection notes often live in separate places. The result is a broken history: who did the work, which checks were completed, and who approved it?

Who uses it

Maintenance managers and assigned technicians. A read-only role can inspect records without changing them.

The complete workflow

1. 01Inspect the sample equipment and create recurring maintenance plans.
2. 02Generate due work orders and assign them to a technician.
3. 03Start the work, record checklist results and temperature, add notes and optional photographs.
4. 04Submit for review. A supervisor can approve or return the work with a reason.
5. 05Inspect the complete asset and decision history.

Decisions that matter

• Required checklist results and completion notes are validated before submission.
• Technicians cannot approve their own work; server-side role checks govern each transition.
• A plan occurrence is generated once, even when the scheduler is run again.
• Image evidence is stored separately from structured application records.

What you can inspect

Open your own demonstration workspace, change roles, complete the workflow, refresh the page, and inspect the saved activity history. Export the current workspace to review the records.

Implemented technology

React and TypeScript, built with Vinext, running on Cloudflare Workers. D1 stores workspace records and server-side sessions; R2 stores maintenance images. Workflow transitions and permissions are checked by the server.

Current limits

This demonstration runs scheduled-work generation on demand. It is not a certified safety system, and its example inspection procedure is synthetic.

Demonstration roles are deliberately selectable. They illustrate server-enforced permissions within an isolated sample workspace, not a production employee or supplier identity system.

Public project brief