logic.work is not a task list, and it is not a generic project tool. it adapts to your operation while keeping work structured and provable.
you define workflows that reflect how work really happens, then enforce required steps, evidence, and confirmations in the field. if a step is not completed, the workflow does not progress.
- workflows that enforce required actions, evidence, and sign-off
- automatic audit trail with who/when/where for every step
- client-ready PDFs and completion records generated on completion
- location models for sites, buildings, zones and rooms
- sector libraries, premium packs and language packs to speed setup
logic.work is the control plane: a horizontal execution and compliance engine for generic workflows.
logic.* verticals reuse the core and layer industry-specific workflow libraries, documents, and data integrations from industry-leading content providers.
- logic.work = shared execution primitives
- logic.* = sector intelligence and integrations
- same core, tailored for each industry
out of scope for logic.work: authoritative API integrations, domain decision logic, or claims of domain expertise.
we enforce execution and audit trails, not the correctness of third-party standards.
why work fails
- spreadsheets describing how work should be done
- calendars that don't reflect what actually happened
- messaging apps used as operational glue
- pdfs and forms completed after the fact
- knowledge locked in a few experienced people
the predictable outcomes
- inconsistent service quality
- unclear accountability
- disputes with clients or suppliers
- weak or reconstructed audit trails
- limited ability to scale without friction
when something goes wrong, organisations don't lack explanations - they lack evidence. logic.work makes evidence the default.
workflows that enforce reality
- required photos, checkboxes, structured notes and signatures
- arrival or presence checks to prevent guesswork
- stages do not progress until required evidence exists
location-aware by design
- model sites, buildings, zones and rooms
- bind evidence to the location where work happened
- optional QR codes for presence confirmation
auditability without reconstruction
- timestamps, user attribution and change history by default
- professional job cards and completion records generated automatically
- answers "what happened here?" without rummaging for evidence
client assist, not theatre
- guidance on missing or incomplete evidence
- clear, professional language for job records
- overdue or blocked work surfaced early
- auditable suggestions, never hidden automation
what makes a good workflow
a good workflow does not describe what should happen. it defines what must happen - and records that it did.
- reflects real work, not ideal processes
- enforces actions at the right moment
- distinguishes required from optional clearly
- captures evidence as work is done
- is location-aware by design
- supports recurrence without duplication
- produces a defensible output
- leaves room for evolution
why this matters
most operational systems focus on speed. logic.work focuses on trust.
- clients trust the record
- regulators see evidence, not excuses
- partners see consistent delivery
- your own team can stand behind the outcome
sector workflow libraries
pre-built workflow libraries give you a practical starting point for real-world work such as cleaning, property management and facilities. they are fully editable and reduce setup friction.
- named, real-world workflows
- sensible sequencing
- default enforcement rules
premium packs & language packs
- compliance-heavy workflows with stricter enforcement
- enhanced audit outputs for regulated activity
- translated labels and stock phrases for consistent records
early access available
logic.work is available via early access with guided onboarding, sector library selection, and initial workflow setup support.
starter plans begin at £200/month, with sector libraries, premium packs, and language packs available as add-ons.
next up: logic.fleet
logic.fleet is imminent for mobile engineer and depot operations. it runs on the same .logic platform, with vertical-specific intelligence layered on top.
if you want a walkthrough or a tailored fit check, send a note and we'll respond directly.