Generating and sending the supplement package
Build the package for the items and round you intend to request. Then inspect the saved PDF and choose how to deliver it. Generating a package, sending an email, and recording external delivery are separate actions.
Build and open the saved package
- Check the selected round and included items. Finish any required response decisions or other steps shown beside the package action. You can prepare with current documents, or use Add supporting details for an item that needs more explanation. Extra uploads are optional; both current original estimates and required claim checks still apply.
- Choose Review supplement and review the selected scope, current documents and support warnings. Review any listed items without extra support and any confirmation shown, then choose Create supplement only when the proposed scope is what you intend. Cancel, Escape or closing a preview does not create or send a package.
- Wait for generation to finish successfully. A preview visit, cancelled preview, queued job, or failed generation is not a completed package.
- Open the saved version and choose Download PDF. Check the round, version, included items, and request amount in that PDF. Current selections shown elsewhere on the page may have changed since it was saved.
If you make a permitted package edit, use the available update action and wait for the new saved version. Saving your source review does not change an already generated PDF, its wording, or its amounts. Original parsed-source corrections are locked once there is a saved package; see the correction limits before trying to fix a source value.
Before you send
Always review the generated PDF before sending it to a carrier. Check these details in the actual saved version:
- Claim and scope: correct property, insured, claim number, round, and requested items. Deferred items and prior approvals should not be presented as new active requests.
- Amounts: quantities, units, rates, line totals, prior allowances, and the amount requested for this round. Compare unexpected values with the source documents.
- Sources: readable evidence, relevant references, and attachments matching the items they address. Open supporting documents as well as the package.
- Wording: the cover letter and item explanations accurately describe the claim and response. Check for unsupported statements, placeholders, and unexpected blanks.
- Recipient: the intended carrier address, email subject, message, and attachment list in the send dialog.
The support checklist in Before you send describes current workspace information. Its score does not certify the saved PDF or predict carrier acceptance. If it is loading or unavailable, inspect the PDF and sources; missing checklist information is not a readiness result. Package creation does not mean a founder or expert reviewed it.
Send from ClaimOps
- Choose Send to Carrier for the saved package. If sending is unavailable, follow the displayed reason. Complete email verification if prompted.
- Check or enter the recipient. Review the subject, message, and attachments; a suggested address still needs your review.
- Optionally choose Send a test copy to myself. Inspect that test in your own inbox. A test copy is not a carrier submission.
- Choose Send Email when you intend to send to the displayed recipient. Follow its result in Submission History.
Queued means the send is still processing. Sent records the completed send; it does not mean the carrier read or approved it. Failed needs attention: read the error, check the address and attachments, and use the available retry action after resolving the issue. If the result is unclear, refresh history before starting another send.
A successful internal send creates its submission record. Do not also mark it submitted manually to duplicate that record.
Deliver it yourself and record what happened
Download the PDF and any supporting attachments, then deliver them through your email or the carrier's portal. Open in my email app can fill in the subject and message, but it does not automatically attach the PDF. Attach the downloaded files yourself and check them before sending.
After you have delivered the package, use Already sent it? Mark as submitted. This records your report of external delivery; it does not send an email or verify its recipient. Keep your own sent-email or portal receipt, including the address and date.
Choose a follow-up for the actual situation
On the claim Overview, use the follow-up guidance for No response, Information requested or Partial approval. It opens the relevant existing notes, schedule or response controls. Selecting guidance does not contact the carrier, record an outcome or start a new round.
If the carrier asks for information, keep the request in negotiation notes and review the specific items and sources it asks about. Selecting this guidance or saving notes does not pause scheduled emails. Use the schedule's explicit Stop or Reschedule controls when appropriate. An unavailable schedule needs Retry; it does not mean no emails are scheduled. External delivery does not itself establish an automated follow-up schedule.
If something is unavailable or looks wrong
For a processing or generation error, use the retry action shown and wait for a successful saved version. For wrong scope or amounts, stop before sending and inspect the relevant source, item selection, and round decisions. Use edits or round reopening only where the app permits them; saved and submitted versions retain their history.
If the issue cannot be resolved, email contact@claimops.io with the claim, round, package version, and specific error or amount. When the carrier responds, follow the carrier-response workflow.