Skip to content

Free contractor tool

Supplement Tracking Log Generator

See what was requested, what evidence exists and who owns the next response.

Enter your details

One submitted item does not make the whole supplement submitted

A supplement file can contain several items moving through different stages. Start with stable item references and the current status of each one. Requested, drafted, submitted, reviewed and paid do not mean the same thing. A log that applies one status to the whole file can hide a missing photo behind another item’s submission confirmation.

Use anonymized identifiers when preparing a draft in this tool. Describe each item, its inspection photo reference and the next owner in the supplied details. The generator organizes the record; it does not contact an insurer, confirm receipt or retrieve a payment status.

Reconcile status at the item level

Suppose D-1 has submission confirmation, F-2 is waiting for a photo reference and V-3 has received a response that needs review. Those rows have different next actions. A single status of pending for the whole file hides both the missing photo and the received response. Give each item a reference, a source record, its last confirmed status and a next owner.

Amounts need the same discipline. Requested, submitted, accepted and paid totals answer different questions. A revised request should not be added to its previous version as if it were a second item. Keep the version relationship visible so the team can reconcile what changed.

A revised amount replaces its earlier request

In a fictional item record, D-1 was submitted at $600, then revised to $750 with a new supporting document. The current request is $750, not $1,350. Preserve the $600 submission in the history, label the $750 revision and retain separate evidence for its receipt. If a documented response accepts $500, record $500 as accepted while leaving payment unknown until a payment record supports it.

Use the meeting preparation brief when the difference needs a specific evidence discussion. Refer to D-1 and its current version so the participants examine the same item. A file total becomes useful only after each row’s amount type and version have been reconciled.

Use the log to prepare the next follow-up

Filter by the action owner and unresolved state. A field lead should see the missing observation or photo they need to provide; an estimator should see the response that needs review. Avoid repeatedly marking a row urgent without identifying the action that can move it. The generator organizes supplied details but does not confirm insurer receipt or payment. Update the working log when that evidence arrives, keeping the date and reference with the status it supports.

Fictional supplement register

Track each item, not one status for the whole file

Different items can be at different stages
ItemEvidence on fileActual statusNext owner
D-1 · deckingSubmission confirmationSubmitted; response pendingEstimator follows up
F-2 · flashingDraft scope; photo reference missingDraftField lead supplies the reference

A response arrives for D-1

Attach the response to D-1 and update that row. It does not change F-2’s submission status.

The missing photo arrives for F-2

Add the reference and route the draft for the next review. Receiving a photo is not evidence of submission.

Build a log that preserves evidence and ownership

  1. Use an internal alias

    Work with a demo or anonymized job label here. Keep the link to the real claim only in the approved internal record.

  2. Separate the line items

    Enter amount and source for each item. Specify partial approvals explicitly instead of assigning the whole item to approved.

  3. Record submission and response evidence

    Include actual receipt and response dates. If a receipt is missing, mark submission unverified rather than pending by default.

  4. Assign the next action

    Name an internal role and a supplied review date. Missing deadlines remain unknown; do not use a generic carrier turnaround estimate.

Review only the open work

Scan the items without a final recorded outcome. Each should show the last evidence received, the missing answer and the next owner. Requested, submitted, reviewed and paid amounts need separate labels.

Reconcile a partial response without losing the balance

Suppose a fictional item requests $1,200 and the written response allows $800. Record requested: $1,200; allowed in that response: $800; unresolved difference: $400. Keep paid blank until payment evidence exists. An allowed amount and a payment are different events.

Use the blank item-level supplement register (CSV) to retain the response reference, date, next question and owner. Keep revisions on the same item ID so a revised request does not get counted as another item.

If the missing record is a photo, prepare its location and observation with the photo caption tool. If the question needs discussion at a meeting, carry the specific item into adjuster meeting preparation.

Questions about supplement tracking log

Does the log prove a supplement was submitted?

No. Link the actual submission receipt. A generated row alone is not evidence of delivery.

How should I record partial approval?

Keep the submitted amount and the approved, denied and unresolved portions separately. Preserve the dated response and any revisions.

What should I do with a denial?

Record the exact source, reason and date, then assign the question to an authorized reviewer. Do not presume an appeal is required or will succeed.

How long should I wait for a response?

Use the actual process, documented deadlines and authorized reviewer’s instructions for the job. This generator cannot establish a carrier timeline.