For the proposal coordinator or manager at a 10–250-person federal contractor bidding on a recurring cadence — strongest in construction, A&E, facilities, and professional services in the NAVFAC, USACE, and GSA ecosystems: Long Pole is where each pursuit's Past Performance Questionnaires are worked. It keeps a register of every past-client reference on every pursuit, captures the solicitation's own return terms per pursuit, holds a state on every reference, and runs a deadline board counted against proposal close — so the coordinator's last two weeks of a pursuit are not spent chasing officials by hand.
How it works
- Add a pursuit — agency, solicitation number, and the proposal close date and time
- Capture the solicitation's own PPQ terms for that pursuit — the form it names, the route each questionnaire must take, and the deadline it sets
- Add each past-client reference — contact, project, route (return-to-bidder, or direct-to-contracting-officer blind), and the date the questionnaire went out
- Track every reference through Requested → Sent → Opened → Promised → Returned — the blind route records a Blind-confirmed date only, never form content
- Keep every reminder your team makes in the reminder log — date, channel, note
- Work the deadline board — days-to-close on every pursuit, At-risk flags inside 5 days, dashboards sorted by nearest close
A register for every pursuit
Every pursuit gets its own reference register: the pursuit (agency, solicitation number, close date and time), and under it each past-client reference — contact, project, the route that reference's questionnaire must take, and the date it went out.
The register is kept on the solicitation's own terms. Each solicitation names its own PPQ form, its own return route, and its own deadline, so those terms are captured per pursuit and the register is worked against them — not against a generic template.
Every reference, in a state, against the close
Each reference sits in exactly one state — Requested, Sent, Opened, Promised, or Returned — and every reminder the coordinator's team makes is kept in the reminder log, so the state on the board is the team's own record, in one place.
The deadline board counts days-to-close on every pursuit and flags a pursuit At-risk inside 5 days of close. Dashboards are sorted by nearest close, so the pursuit that closes first is the one worked first.
The blind route — a Blind-confirmed date, never the form
Some solicitations require a reference's questionnaire to go straight to the contracting officer — a blind return the bidder is not allowed to see. That route is part of the register like any other, with one settled rule that is the product's compliance shape:
The blind route records a Blind-confirmed date only — never form content. Long Pole never holds a blind questionnaire's content, and the bidder never sees a blind PPQ through Long Pole. What the bidder holds instead is the printable blind receipt ledger: the record that each blind questionnaire went out and was confirmed, by date — the bidder's proof the PPQ went in.
The scope — the register, the board, and the proof
Long Pole's work is the register, the states, the deadline board, and the receipt ledger. It does not promise that a reference will return a questionnaire — returning one is the reference's act, on the solicitation's terms — and it makes no promise about the outcome of any pursuit or any contract.
Where it stands — the honest state
Long Pole is forming its first bidder pilot group now. The door below is a bidder pilot application — applying starts a pilot conversation; it does not create an account, and it is not a sign-up for a running service.
Long Pole sends nothing today. Live email delivery and reminder sending to government references do not exist yet — the coordinator's own team makes every contact today, and Long Pole's work is the register, the states, and the deadline board. Sending belongs to a future sending layer, designed around professional-tone controls for messages addressed to officials; that layer is gated work — it has not been built, and it has not been run.
Ingestion of arbitrary agency PPQ forms is not proven, and it is not claimed. Agencies issue their own questionnaire forms in their own formats, and reading an arbitrary agency PDF form automatically has not been verified — it stands as an engineering verification still to be performed. Today, a pursuit's PPQ requirements are set up in the register directly: the pursuit, its references, and the form, route, and deadline the solicitation names, entered by the bidder's own team.
Amendment-driven deadline tracking is part of the product's design: when an amendment moves a proposal close, the pursuit's deadline moves with it and the board recounts against the new close. It goes live only with real pursuits inside a working deployment — no pursuit is running in Long Pole today.
No price has been set. A price range exists in our market research as a hypothesis; it has not been validated and it has not been decided, so no price is shown here and there is nothing to buy on this page.
One rule does not change in the pilot or after it: the blind route records a Blind-confirmed date only — never form content.
Bidder pilot application
This is a bidder pilot application — an application to join Long Pole's first bidder pilot group, not an account sign-up and not a purchase. Tell us who to reach, your company, and how many pursuits your team typically has active at once. If you like, tell us how many references a typical pursuit carries, and how your team chases PPQs today. We will be in touch about the pilot group.