A takedown is not submitted until somebody sends it

The most dangerous word in a takedown workflow may be a status label. Mark a notice “submitted” too early and the case history now asserts an event that did not happen. A reviewer may assume the clock is running. A colleague may wait for a response that cannot arrive. The draft itself can be perfect and the operational record can still be false.

This is why Brand Protector treats preparation and transmission as separate events. The system does not infer filing from a completed draft, a signature, or a copied block of text. It records a direct submission as submitted only on a path that actually transmits the notice. A login-gated form remains prepareduntil an operator records that the filing happened.

One button can hide two different workflows

Some destinations accept a notice through an API or a system email. Brand Protector can transmit on those configured paths after the review gate clears. Other destinations require a person to sign in, inspect a prefilled form, paste the prepared material, and submit it on the destination’s site. The product can prepare that second path, but it cannot truthfully claim to have completed the final click.

That difference also changes the declaration shown at review. Direct API and email paths use the sworn-attestation wording. A form-paste path uses review-and-authorization wording: the reviewer confirms the facts and authority before taking those facts to the platform’s own declaration. The server derives the declaration from the stored submission method, so the browser cannot select an easier statement.

The two questions should never collapse into one:

• What did the authorized signer confirm? The answer belongs in the attestation record, with the exact declaration and time.
• Who transmitted the notice, and when? The answer belongs in the filing record, and may not exist yet.

Why a signature does not prove transmission

Review is a gate, not a delivery receipt. On a direct path, the system attempts the configured transmission before it writes the submitted state. On a form-paste path, review produces a filing-ready package and a status that says exactly that. The submitted timestamp and filer fields remain empty.

When the operator finishes the external form, Brand Protector provides a separate action to record the filing. That action is only available for a prepared notice. It stores the actual operator and time, accepts an optional reference, advances the case to submitted, and adds the filing event to the audit trail in the same transaction. It cannot be used to rewrite a notice that is still a draft or one already recorded as submitted.

The status should answer the next person’s question

Imagine opening the case after a handoff. “Submitted” should answer: yes, somebody sent this. “Prepared” should answer: the package is ready, but the external action is still outstanding. The useful interface does not make the second state sound like failure; it makes the next action unmistakable.

Brand Protector keeps that wording consistent wherever the lifecycle appears. Form-paste and mailto packages say they are ready to file or send and explicitly say they have not yet been submitted. Direct API and system-email paths can enter the submitted state after transmission. If a new submission method is added, the status mapping must handle it explicitly rather than falling through to a flattering default.

What to demand from any takedown record

Ask a vendor to show the transition, not a slide about automation. Start with a destination that requires login. Approve a draft, stop before using the external form, and inspect the case. Then complete the filing and inspect it again. You should be able to tell which facts came from review, which came from transmission, and which came from a later human record.

• Can a completed review appear as submitted before delivery?
• Does the record name the event that actually changed the status?
• Can an operator add a platform reference without inventing one?
• Does a failed direct transmission leave a submitted timestamp?
• Can an old case be silently rewritten after the fact?

A takedown tool is not merely a document generator. It is also the memory of what your team asserted and did. The honest design is the one that is willing to stop at “prepared” until the evidence supports a stronger word.