Make the next action, responsible person and completion requirements visible throughout the job.
A schedule alone cannot tell the team whether a customer has approved the work, who owns the visit or what still needs to happen before completion.
Field-service operations / Custom application
Fieldnote
Keep office and field teams on the same work order.
A service operations workspace connecting the office and the field: requests, estimates, dispatch, technician handoffs and completion records.
Puzinski’s contribution
End-to-end workflow design, responsive application screens, data modeling, API implementation and validation for office and technician actions.
Inspect at full size ↗Fieldnote / Dispatch board / Desktop
Treat approval, assignment and completion as separate transitions. Use a time board for dispatch and a chronological agenda on phones.
A useful fit for
Home services, maintenance teams, installation businesses and service companies coordinating office and field work.
Implemented scopeThe work
The work
it brings together.
One work order carries customer approval, ownership, appointment context and a documented closeout from office to field.
- 01Request and estimate capture
- 02Dispatch board and mobile agenda
- 03Technician assignment and conflict checks
- 04Required completion checklist
- 05Customer and job activity history
- Create the work order
- Approve its estimate
- Assign an available technician
- Record and complete the visit
The phone experienceA clear decision.
A clear decision.
At each step.
Gate assignment on approval, check real scheduling overlaps and keep closeout requirements on the work order.
Create a request
Customer, service area, date, time window, estimate and scope are collected in a focused work-order form.
Close with a record
Required checks, a field note and the completed status are retained together in the work history.
Try the workflow
Explore Fieldnote.
Enable JavaScript to try the browser walkthrough. The screens, scope and product decisions are available above.
Interactive walkthrough · changes stay on this device. Use sample details. “Reset walkthrough” clears this example’s progress.
The structure behind the interfaceConnected by
Connected by
design.
Approvals and technician time must be checked before assignment. A completed badge is meaningful only when the required closeout work is accounted for.
Office & field interfaces
A dispatch board, work orders, customer context and technician closeout views.
Validated actions
Role-aware actions, estimate approval, actual time-interval checks and required completion checks.
Persistent record
Versioned state writes preserve work notes and activity; stale concurrent updates are rejected.
Observed acceptance checks
- Assign a technician with an overlapping visit
- The conflicting assignment is rejected.
- Close a job with unfinished checks
- Completion is blocked until all required checks are complete.
- Submit a stale concurrent change
- One stale write is rejected rather than overwriting the newer state.
Product decisions & tools
- One view for dispatch
- A populated time board makes workload and visit windows visible together. On phones, it becomes a chronological agenda instead of a compressed calendar.
- Approval before assignment
- Approval, ownership and completion are separate transitions. Users see the actions available for the current work order and workspace role.
- Context travels with the job
- Customer details, scope, estimate, required checks and activity history remain on the same record through the office-to-field handoff.
- Implementation
- React · TypeScript · Server-side role checks · PostgreSQL · Versioned writes
A product built around your businessLet’s shape
Let’s shape
your first release.
Tell us the users, the key tasks, the existing tools and what a useful first version needs to do. We’ll clarify the scope, data, review points and delivery requirements.