Prompt
I'm building an HR tool that sends offer letters and tracks signing status
Latest observation
Nov 5, 2026
OpenAI APIWeb search: off
Great use case. An HR offer-letter tool usually needs two core pieces:
- Document generation + delivery
- Status tracking + reminders
Here’s a practical way to design it.
Core workflow
- HR creates an offer letter from a template.
- The system fills in candidate-specific data.
- The letter is sent for signature via email or an e-sign provider.
- The system tracks events:
- sent
- viewed
- signed
- declined
- expired
- HR sees a dashboard with current status and next actions.
Suggested data model
OfferLetter
idcandidate_idjob_idtemplate_idstatus—draft | sent | viewed | signed | declined | expired | withdrawnsent_atviewed_atsigned_atexpires_atcreated_bycreated_atupdated_at
OfferLetterRecipient
idoffer_letter_idnameemailrole— e.g. candidate, witness, managersignature_status
AuditEvent
idoffer_letter_idtype—sent,opened,signed,reminder_sent,declinedmetadatacreated_at
Recommended status flow
A simple state machine helps prevent invalid transitions:
draft→sentsent→viewedviewed→signedsent/viewed→declinedsent/viewed→expireddraft/sent/viewed→withdrawn
Features to include
Must-have
- Template editor with merge fields
- PDF generation
- Email delivery
- Signature status tracking
- Reminder scheduling
- Dashboard and filters
Nice-to-have
- Multiple signers
- Offer approval workflow
- E-signature integration
- Candidate portal
- Version history
- Custom expiration rules
API endpoints example
POST /offer-letters— create draftPOST /offer-letters/{id}/sendGET /offer-letters/{id}GET /offer-letters?status=sentPOST /offer-letters/{id}/remindPOST /offer-letters/{id}/withdrawPOST /webhooks/esign— receive signing events
Important implementation notes
- Use webhook events from your e-sign provider if possible; don’t rely only on polling.
- Store every status change as an audit event.
- Make reminders idempotent so you don’t send duplicates.
- Protect documents with access controls and signed URLs.
- Consider compliance needs: retention, privacy, and legal hold.
Tech stack idea
- Frontend: React / Next.js
- Backend: Node.js, Python, or Ruby
- DB: PostgreSQL
- Queue: Redis / SQS for reminders and email jobs
- Storage: S3 or similar for PDFs
- E-sign: DocuSign, Dropbox Sign, Adobe Sign, or an internal signer
If you want, I can help you with:
- a database schema,
- API design,
- state machine logic,
- or a minimal MVP architecture.