Scenarios
What Drumtap catches, told in six trade-subvertical stories.
These are synthetic, illustrative trade-subvertical scenarios—not substantiated customer records or historical portfolio evidence. They show the kind of GC pay-app situation, supplied evidence comparison, and owner-reviewed next step Drumtap is designed to organize.
Private beta waitlist
Join the private beta waitlist.
Leave your email to signal interest while we prepare private-beta access. Joining records interest only; it does not create or activate an account, grant paid access, start a subscription, or charge you. We will share timing and final terms before access opens.
The stories below are illustrative trade-subvertical scenarios — not named real customers, not GC logos, and not evidence of a recovery outcome. They describe the kind of review-ready comparison Drumtap is built to draft.
Drywall
A drywall sub files a pay app with an expired conditional waiver template version on a tenant buildout.
A drywall sub files the monthly pay app through the GC portal as normal. The pay app packages the original conditional waiver, but the GC swapped the waiver template two cycles back — the sub is still on the old version. The portal rejects the submission the same day it clears AP.
In this synthetic scenario, the owner supplies the AP rejection notice through Drumtap’s signed, feature-flagged intake or upload flow. Drumtap processes that supplied notice, waiver template, and signed change order, then organizes the rejection evidence for owner review before any possible refile.
Illustrative next step: the owner reviews a refile packet against the supplied records and decides whether to upload it; no acceptance or payment outcome is asserted.
Electrical
A one-truck electrical sub on T&M gets the labor rate rounded down and the material markup line dropped on the next pay app.
A one-truck electrical sub runs time-and-materials on a remodel. The GC portal accepts the hours the sub submitted but rounds the labor rate down to the original bid number and quietly drops the material markup line. The invoice the sub sent and the pay app the GC approved stop matching in QuickBooks the same day.
In this synthetic scenario, the owner supplies the AP email, T&M sheet, and material receipt through the signed, feature-flagged intake or upload flow. Drumtap processes those supplied records and matches the discrepancy line-by-line for owner review; the labor-rate round-down and missing markup line remain separate review findings.
Illustrative next step: the owner reviews the rate and markup evidence and may send a focused question; payment or recovery is not guaranteed.
Plumbing
A plumbing sub emails the pay app to AP but it never lands on the pay cycle — AR ages while the books say it is submitted.
A plumbing sub emails the pay app directly to the GC AP inbox because the portal upload timed out. The AP clerk processes the portal queue first and the emailed pay app slips a cycle. AR keeps aging while QuickBooks shows the invoice as "submitted" — the books never see the missing cycle back.
In this synthetic scenario, the owner supplies the forwarded AP timestamp and portal submission history through the signed, feature-flagged intake or upload flow. Drumtap compares those supplied records across the reported pay cycles and shows the gap between what the sub sent and what the AP clerk processed; it does not monitor the mailbox or retrieve portal history live.
Illustrative next step: the owner reviews the submission timeline and prepares a possible refile; the scenario does not claim acceptance, payment, or recovery.
Mechanical
A six-worker mechanical sub carries retainage across three pay apps outside the contract release schedule.
A six-worker mechanical sub sees three pay apps in a row marked "approved" in the GC portal. The retained amount does not release on the schedule the contract calls for. AR keeps growing while QuickBooks shows the invoice as approved.
In this synthetic scenario, the owner supplies the AP email, contract retainage clause, and pay-app history through the signed, feature-flagged intake or upload flow. Drumtap compares those supplied records and ties each retained line back to the clause for owner review.
Illustrative next step: the owner reviews the contract clause and pay-app history before deciding whether to send a retainage question; no release is promised.
Roofing
A roofing sub gets a rejection for a missing tear-off SOV line bundled under the old reroof line on a re-roof.
A roofing sub files the re-roof pay app against the original SOV. The new tear-off scope landed under a separate CO that the sub did not sequence onto the same line. The GC portal rejects the submission for the missing tear-off line and bundles it back under the original reroof SOV line.
In this synthetic scenario, the owner supplies the rejection note, change order, daily logs, and tear-off photos through the signed, feature-flagged intake or upload flow. Drumtap organizes those supplied records and rebuilds the missing-line evidence for owner review before any possible refile.
Illustrative next step: the owner reviews the change-order and tear-off evidence before deciding whether to refile; no acceptance or payment result is asserted.
Concrete
A concrete sub is short-paid on a foundation pour because a change-order delta never makes it onto the SOV.
A concrete sub pours the foundation per CO-02 but the GC portal SOV still runs the original pour quantity. The AP email short-pays the next cycle to the original line — the CO-02 delta disappears into the SOV rather than getting billed as a separate change-order line.
In this synthetic scenario, the owner supplies the AP email, signed CO-02, and pour photo log through the signed, feature-flagged intake or upload flow. Drumtap compares those supplied records, ties the delta back to CO-02, and flags it for owner review against the short-paid line.
Illustrative next step: the owner reviews the CO-02 evidence and may send a focused discrepancy question; payment or recovery is not guaranteed.
Private beta waitlist
Join the Drumtap private beta
Drumtap is preparing a private beta for trade contractors who want a clearer path from GC portal discrepancies to the next documented action. Join the waitlist for timing and next steps before access opens.