Projects E-signature
Agreements
Programs were paying for a separate e-signature service, then copying signed documents into the chart by hand. Now the paperwork lives where the record does.
Try it
Sign the admission agreement the way a parent does, from the link in their email. Nothing is sent anywhere.
What it does
- Template studio
- Upload the PDF the program already uses. Place the fields once. Publish. Each facility keeps its own library.
- Packets from the record
- Pick the documents a family needs to sign. Roles that repeat across documents collapse into one signer. Send by email, sign in the app, or hand over a tablet.
- Signing on a phone
- A disclosure, the fields, a typed or drawn signature, and a six-digit code when the sender wants one. Progress saves as they go.
- Filing
- When the last signature lands, the PDF is stamped, a certificate of completion is attached, copies go out by email, and the agreement is filed in the record. Nobody touches it.
Screens
Click any screen to enlarge. All data is demo data.
The template library. Status is a control: a template can only go Active once it has a document and a placed field. 
Building a packet from a client's record: pick the documents. 
Recipients. The Parent role appears in both documents, so it is filled once. 
Every packet lives on the client's record, next to everything else. 
A completed packet: signed copies, recipients, certificate, audit trail.
How it was built
Three merge reports and two endpoints in TypeScript on BlueStep. The browser renders pages with pdf.js and the server stamps signatures with pdf-lib. A scheduled sweep sends reminders and expires stale links.
It shipped to eight organizations by script, with a read-only audit after each one, so nothing failed silently.