Skip to content
JGG.
Selected work
In beta testing

DocumentScribe

Reusable report content that adapts to the person writing it.

My role
Creator & developer
Context
Independent product · in beta testing
DocumentScribe’s public walkthrough importing a sample inspection PDF
The public interactive walkthrough uses sample data. It demonstrates the reporting flow; it is not a customer account.

The problem

Inspection and audit reports repeat familiar language, but each job has its own details. After building Playchek Inspector, I realized the pattern could be generalized. DocumentScribe makes that reusable content editable and adaptable instead of forcing every report into fixed boilerplate, for many businesses at once.

The workflow · architectural overview
  1. 01Select reusable content
  2. 02Resolve & edit
  3. 03Export the report

Engineering decisions

Resolve variables into editable content

Snippets can include variables that resolve into report text. The operator can edit that result rather than being locked into the original template.

Learn from the editing workflow

Edits can become new reusable snippets. This makes the content library part of the reporting workflow, rather than a separate collection that has to be maintained by hand.

Share a core, allow configuration

React and Supabase support a shared application with configurable forms, branding and report layouts. Document export connects the authoring workflow to a deliverable.

Where it stands

Almost finished and in beta testing with real users; the Playchek owner is a tester and has already identified use cases he wants it for. These notes describe the implementation direction rather than measured business results.

The public product site provides the current introduction. Application source and account content are private; no customer data is included here.