PDF-Based Templates for Brelly Docs
under review
J
Jake Kretzschmar
THE REQUEST:
Add the ability to upload an existing PDF and use it as the foundation for a Brelly Docs template.
The goal is to take an existing contract, authorization, inspection form, report, or any other professionally formatted PDF and convert it into a reusable Brelly Docs template by placing configurable fillable fields on top of the document.
CURRENT ISSUE:
Brelly Docs allows documents to be created, but I do not see a way to upload an existing PDF and build fillable fields on top of it.
Many companies already have professionally designed documents with company branding, logos, legal language, formatting, spacing, and layouts that they do not want to recreate from scratch.
EXPECTED BEHAVIOR:
A user should be able to upload a PDF into Brelly Docs and then place configurable field blocks anywhere on the document where information needs to be inserted.
Each field should allow configuration such as:
- Field name or token name.
- Position on the page.
- Width and height.
- Font family.
- Font size.
- Font style.
- Text alignment.
- Underline or other basic formatting.
- Required or optional status.
- Auto-filled or manually entered values.
CLAIM DATA TOKENS:
Where information already exists within the claim, the user should simply be able to select that field from a list and place it on the PDF.
Examples include:
- Policyholder first name
- Policyholder last name
- Loss address
- Claim number
- Policy number
- Insurance company
- Date of loss
- Email address
- Phone number
- Contractor or company name
- Estimate amount
- Deductible
- Mortgage company
- Any other claim information already stored in Brelly
This could function as a token selector or drag-and-drop field library similar to other document automation platforms.
CUSTOM FIELDS:
Not every document contains information that already exists within the claim.
For those situations, users should be able to create custom fields that are completed manually when generating the document.
Examples include:
- Custom dollar amounts
- Special instructions
- Scope descriptions
- Payment terms
- One-time notes
- Any other document-specific information
SUGGESTED WORKFLOW:
- Upload an existing PDF.
- Choose "Create Template."
- Place fillable field blocks where information belongs.
- Assign each field to either a Brelly claim data token or a custom manual-entry field.
- Save the completed layout as a reusable template.
- Generate future documents using automatically populated claim data along with any required manual inputs.
- Export the completed document as a PDF.
WHY THIS MATTERS:
Many businesses already have documents that are exactly the way they want them, including branding, formatting, legal language, and spacing.
Recreating those documents inside Brelly Docs is unnecessary and may never perfectly match the original.
Allowing users to upload an existing PDF and simply place intelligent fillable fields on top of it would make Brelly Docs dramatically more powerful while requiring very little redesign of existing company documents.
This would be valuable for:
- Contracts
- Work authorizations
- Direction-to-Pay forms
- Certificates of completion
- Inspection forms
- Claim intake forms
- Customer agreements
- Internal company forms
- Any recurring document containing variable claim information
FINAL NOTE:
The closest comparison would be a PDF form designer such as those found in document automation platforms.
The uploaded PDF remains the visual foundation of the document. The user simply overlays configurable fields that either pull data directly from the claim or are completed manually when generating the document.
This would allow companies to convert their existing documents into intelligent, reusable Brelly Docs templates without rebuilding them from scratch.
Photo Viewer
View photos in a modal
T
Tobias Patch
updated the status to
under review
Jake Kretzschmar - actively discussing. Will update when this goes into the pipeline.
Gibby Cornejo
You're always on point with your suggestions, Jake! I've notified the team about this.