Request an engagement

Tell us the contest, the date, and the artifact.

Intake screens for the same-race conflict rule before anything else. If the race identifier matches an engagement we already hold, or the declaration below states a conflict, we refuse in writing and log it, and no contract is opened.

Section 01 · the contest

Principal type Select the principal type. We cannot screen the conflict rule without it. Country Country is required. Election Name the election. Do not name a candidate or a party. Contest date T is the contest date; T−8 weeks is the earliest workable start. A contest date is required. T−8 weeks is the earliest workable start. Jurisdiction scope National, or the jurisdictions in scope. Race identifier (if known) The contest's registry key, lower-case with hyphens: country, office, jurisdiction code, year — e.g. co-alcaldia-11001-2027. It is checked against every engagement we hold before anything else. Left blank, intake screens the race by hand. Use lower-case letters, digits and hyphens, e.g. co-alcaldia-11001-2027. Mandate Select a mandate so we can quote against the artifact list.

Section 02 · conflict declaration

An opposing party in this race has engaged us, or may have, through another principal.The declaration is recorded at intake and cross-checked before a contract exists. Leave unticked to declare the race clear. Conflict position, in your words Relationships, coalitions, or subcontracts we should know about.

Declare the conflict position. An unanswered declaration is treated as a conflict.

Section 03 · you

Contact name A named contact is required. Engagements are not opened to a shared inbox. Email Enter a working email address. Organisation Organisation is required for the intake screening record. Correspondence language All three are equal; none is the default.

I consent to these fields being processed for intake.The consent timestamp is recorded alongside the fields. Consent is required before we can hold these fields.

Sending stores the request and screens the race identifier · the email route stays open

Before you send

Nothing is submitted yet. The fields above are held in this page only; nothing leaves the browser until you send the request or build the email.

Validation

Six fields need an answer before intake can screen the conflict rule. The errors are shown inline, under the field they belong to, and nothing was sent.

Fallback route

If the submission backend does not answer, the button opens a prefilled email to [email protected] with the fields above, and you send it from your own account so you keep a copy.

Received

The request is logged for intake screening. Quote the reference below in any correspondence; we reply with scope, refusal conditions, and a price against the published floor.

reference issued by the intake backend

Intake screening within two working days

Refusal

Request withheld at intake

The race identifier matches an engagement we already hold for a principal in this race.You declared a conflict in this race. We do not act for opposing principals in the same race, so no contract is opened and no scope is discussed.

Basis: Same-race dual-engagement exclusion, screened at intake · matched on the race identifier, against every engagement we holdyour declaration
What would change it: A different race, or the same race after the existing engagement has closed and its artifacts are frozen.
Logged: Logged at intake · reason code same_race_exclusionRefused at intake · reason code same_race_exclusion · the log entry did not confirm; intake records it by handLogged when you send the request · reason code same_race_exclusion

What we hold

Only the fields above, the timestamp of consent, and the intake screening result. No tracking, no third-party analytics, no marketing list.

Security and data handling →

Tell us the contest, the date, and the artifact.

Intake form