Skip to content
← All work

Enterprise / Operations platform

Watchbook

Platform
Next.js / tRPC / PostgreSQL
Access
Roles, 2FA & passkeys
Status
Ongoing development

One logbook. Every post.

A multi-site platform where guards register visitors, vehicles, keys and incidents, and where administrators shape every journal without touching code.

Journal model / Select a part to explore its responsibility

01 / The starting point

Paper registers. One post at a time.

Guarding a site means recording a constant stream of small events: who came in, which vehicle, which key left the desk, what happened on the round. On paper, each of those lives in its own notebook, readable only at the post.

The platform turns those notebooks into shared journals. The guard’s work stays as quick as writing a line, while supervisors and clients can finally see the same record.

Starting point

Notebooks at the desk

One book per topic Handwriting and lost pages No view beyond the post

Product direction

Shared journals

Structured entries Searchable history One record for every role

Result

One journal per post.

02 / Journal templates

Journals are data, not code.

More than a dozen journals share one engine. Each is a template that describes its fields, whether it needs a photo or a signature, and what happens at check-in and check-out. Stable records such as sites, employees and vehicles live in relational tables; the fields unique to each journal are stored flexibly.

An administrator enables a journal for a post, reorders its menu and rearranges its fields to match how that gate physically works. The guard’s screen is drawn from that configuration and nothing more.

Starting point

One journal per form

Each process built as its own app Hard to change once released Separate logic for every journal

Product direction

One engine, many journals

Templates define each journal New journals without new code One place to change behaviour

Result

New journals without new code.

Single action

Incidents and patrols are logged once and closed.

Check-in / check-out

Visitors, vehicles, keys and parcels stay active until they leave.

Fast lookup

Typo-tolerant search finds people and plates as the guard types.

03 / Versioned workflows

Change the rules. Keep the history.

Entries move through configurable statuses, each with its own label and its own list of who may act on it. A workflow definition is immutable: editing it creates a new version.

Every entry remembers the version it was created under, so a status renamed today does not rewrite what an old record meant. Archiving stays a separate lifecycle, independent of whether the workflow has finished.

Starting point

Rules that change in place

Old records change meaning No history of status changes Hard to audit

Product direction

Versioned workflows

Immutable workflow definitions Entries keep their version Archiving stays separate

Definition → Version → Entry

Edits shape what comes next. The past stays as it was.

04 / Built for the post

Tablet first. Quick at the gate.

Guards work on tablets and phones, often standing, often with a visitor waiting. The interface is designed for that order of priority: tablet, then mobile, then desktop. It installs as an app and keeps a live view of what is currently inside.

Shifts, attachments, photos and signatures sit next to the journals. Updates reach every connected screen in real time, so two guards on the same post see the same state.

Starting point

Desktop forms at the gate

Slow to fill in Requires a desk Breaks the flow of the shift

Product direction

Tablet first

Large touch targets Fast entries while standing Search that works as you type

Design principle

Fast first, complete second.

Live view+

Active check-in entries stay on screen until the final signature closes them.

Installable+

A progressive web app that opens like a native one on a post tablet.

Shared by default+

Real-time updates keep every guard and administrator on the same record.

05 / Sites & access

Each site is its own workspace.

Every guarded site is a workspace with its own journals, members and notifications, while guards can be assigned to more than one. Administrators, guards and clients see only what their role and assignment allow.

Sign-in supports two-factor authentication and passkeys. Administrative actions are written to an audit log, and review notifications go to the administrators assigned to each site.

Starting point

One account per site

Separate logins for each location No shared view of incidents Repeated setup for every site

Product direction

One workspace per site

Own journals, members and notifications Guards assigned to several sites Administrators manage each site in one place

Design principle

Each site stays its own workspace.

Isolated workspaces+

Journals, members and notifications are configured per site.

Role-based access+

Administrators, assigned administrators, guards and clients each get their own view.

Accountable by design+

Audit trails record who changed what, and when.

06 / Current scope

A foundation for every new journal.

The platform covers journal configuration, guard workflows, shifts, notifications and administration, all in a Lithuanian-language interface. Adding a new journal is a configuration task rather than a development one.

Development continues around reporting, exports and the administrator tooling.

Starting point

Paper, spreadsheets and email

Scattered records No single source of truth Hard to review

Current scope

One platform for the whole site

Journals, shifts and notifications Administration and access Lithuanian-language interface

Scope

Built to grow with each new site.