When a badge application is wrong, it doesn't fail quietly. Philadelphia's signatory handbook states the rule most offices follow: "If any portion of the application is incomplete or incorrect, the badging operator will reject the application, and the applicant will be instructed to return to the authorized signer to revise the rejected application." San José adds the second cost: turned-away applicants "will have to schedule a new appointment." A single missing field turns into a bounced packet, a re-booked appointment, and a start date that slips a week.

The reasons are remarkably consistent from airport to airport. Here are the twelve that appear again and again, with each airport's own words.

01Names that don't match across documents

The most widely named error in the country. Denver states it twice on one page: "Names on the documents must match the name on the fingerprinting and badging application. If names do not match, all legal documents containing name changes are required." Houston is blunter about the consequence: names on each ID "must match exactly, or the vetting process may be stopped." Oakland requires "identical spelling of names and name placement"; Dulles requires the legal name to "match exactly on both documents"; Charlotte lists "wrong IDs (names not matching)" among its turn-away reasons; Philadelphia requires legal name-change documentation when they differ.

Catch it early: compare every document's name against the application before the packet goes anywhere — maiden names, middle names, and hyphenation included.

Sources: DEN new-employee badging · Houston Airport System badging · OAK authorized signer information · MWAA Dulles Pass & ID · CLT credentialing · PHL Authorized Signer Handbook 2025 — links in Sources.

02The wrong ID documents — or photocopies of the right ones

Phoenix Sky Harbor's signatory guidebook says the quiet part out loud: "The PHX SBO turns applicants away each week for failing to remember to bring the correct ID Verification/Right to Work documents." Every week. Denver requires two documents from the federal I-9 acceptable-documents list — one proving identity, one proving work authorization — "none of which can be digital or photocopies." Salt Lake City will "only accept original documents." Oakland won't fingerprint, train, or badge anyone without both forms of ID.

Catch it early: verify the two-document combination against the I-9 list — one identity, one work authorization — and confirm they're originals.

Sources: PHX Authorized Signatory Guidebook (p.25) · DEN · SLC badging FAQ · OAK · SJC Authorized Signatory Responsibility Agreement · DTW badge office.

03Expired, damaged, or altered documents

Phoenix requires documents that are "original, valid, undamaged, and unexpired." Houston: "All documents must be an original, unexpired & clearly legible." Philadelphia's appendix is in capital letters: applicants "MUST PRESENT TWO (2) FORMS OF UNEXPIRED GOVERNMENT IDENTIFICATION." A license that expires between the application date and the appointment date fails on the day it matters.

Catch it early: check expiry dates against the appointment date, not the day the packet was assembled.

Sources: PHX AS Guidebook (p.24) · PHX Know Before You Go · Houston · PHL handbook Appendix D · MWAA Dulles.

04Any portion incomplete — the whole application bounces

Palm Beach's handbook repeats the same sentence for new badges, renewals, and expired media alike: "If any portion of the application is incomplete, or incorrect, the application will not be accepted, and the applicant will be instructed to return to the authorized signatory." There is no partial credit. Yuma's signatory training names it as the delay driver: "Delays can be caused by applications that are incomplete or not properly filled out."

Catch it early: treat "one blank field" as "rejected packet," because that is how the badging office will treat it.

Sources: PBI Authorized Signatory Information Handbook · PHL handbook · SJC · OAK · Yuma NYL Authorized Signatory Training.

05Missing legal names, aliases, or personal details

Phoenix publishes a section literally titled "Learn common errors": if items are missing, "applications may be denied or subject to lengthy delays." The list: the legal name (not a nickname), all first, middle, and last names, every alias including maiden names, a full current mailing address, and an email address. Its background-check page adds that TSA "requires all applicants to provide a social security number and all aliases," and that "lack of detail or information on the part of the applicant affects the badging process and may result in badging delays." Philadelphia's handbook agrees: "Enter all legal names on the application. Nicknames are not permitted."

Catch it early: the alias section is where vetting stalls — a maiden name on one document and not on the application is error 01 and error 05 at once.

Sources: PHX AS Guidebook (pp.25–26) · PHX background checks · PHL handbook.

06Handwritten or illegible forms

Kahului's application says it three ways on one form: "Handwritten applications will be rejected. Complete all applicable sections. Incomplete forms will be rejected" — and, later, "Type or print legibly or application will be rejected." Houston requires every document "clearly legible." If the badging office can't read it, the badging office won't process it.

Catch it early: anything a tired reviewer would squint at, redo before it ships.

Sources: OGG (Hawaiʻi DOT) New Badge Application, rev. 2025 · Houston.

07The wrong form revision — or the wrong kind of signature

Minneapolis–St. Paul set a hard cutover: paper applications must use the March 2026 revision, and "beginning May 4, 2026, all previous versions will no longer be accepted." Detroit accepts "only the original copy of a completed Badge Application" — and for federal seal applications, "actual signatures are required. Digital or computer-generated signatures will not be accepted." An old PDF saved on a company shared drive fails silently, months after it went stale.

Catch it early: pull the form from the airport's site each time, and check the revision block before anyone writes a word on it.

Sources: MSP MyMSPConnect badging · DTW badge office.

08The wrong appointment — or no application in the system at all

Charlotte publishes its turn-away list plainly: "booking the incorrect appointment type, no application in portal, wrong IDs (names not matching) or no IDs, Disqualifying Questionnaires (DQ) not answered." The applicant physically shows up; the paperwork didn't. That's still a rejection — with a parking receipt.

Catch it early: confirm the portal application exists and the DQ is answered before the appointment is booked, not the morning of.

Source: CLT credentialing.

09Training not finished before the appointment

Also on Charlotte's turn-away list: "incomplete online Non-Movement Driver training (DR) training." Where training gates the appointment, an unfinished module is as disqualifying as a missing document — it just fails later in the visit.

Catch it early: track training completion as part of the packet, not as a separate errand.

Source: CLT credentialing.

10A signatory signature on an incomplete form

This one bites the signer, not the applicant. Eagle County's booklet: "NEVER sign an incomplete or blank form" — with the consequence spelled out: a violation notice, "loss of Authorized Signatory privileges & possible civil penalties... assessed to the Authorized Signatory by the TSA along with badge suspension." Oakland warns that "repeated failures could result in the loss of Authorized Signer authority."

Catch it early: the signatory signature is the last thing added to a packet, never the first.

Sources: EGE Authorized Signatory Booklet · OAK.

11Requesting the wrong access or privileges

Oakland's example is concrete: "ramp driving privileges will not be extended to an applicant unless the application correctly requests that privilege" — an omission discovered on the employee's first shift. Phoenix warns in the other direction: "Do not authorize or request more access or privileges than are operationally necessary." Too little bounces the employee; too much draws the auditor.

Catch it early: map the job title to the access level once, in writing, and check every application against it.

Sources: OAK · PHX AS Guidebook.

12Missing the 30-day clock

Clearing the background check starts a timer. Phoenix: applicants "have 30 calendar days from notification to complete training and obtain their badge. Failure... means they must start the process over, at full cost." Houston: not badged within 30 days of fingerprint results, "the applicant must repeat the application and fingerprint process." The same clock runs on renewals — at Salt Lake City, a badge expired more than 30 days means "a new application must be submitted and fingerprinting is required." A packet that was perfect in March can still fail in May by sitting in a queue.

Catch it early: the paperwork being right isn't enough — it has to be right on time, twice: at submission and inside the clearance window.

Sources: PHX AS Guidebook ("The 30-day rule") · Houston · CLT · SLC · PBI handbook · DTW.

What a rejection actually costs

The published clearance times make the arithmetic plain. Philadelphia: CHRC and STA clearances "usually take 3–5 days," up to 30 for some applicants. Salt Lake City: "anywhere from 5 to 14 days." Phoenix says that with an engaged signatory, "the majority of applicants can be badged within seven to ten days." Every bounced packet re-enters that queue from the back — plus a new appointment at offices that book out days or weeks in advance. The error itself takes minutes to fix. The bounce costs a week.

The pattern behind the twelve

The industry's own research reached the same conclusion. The National Safe Skies Alliance's credentialing efficiency toolkit (PARAS 0036) found that "duplicate manual data entry in the credentialing processing is time-consuming and prone to user error," that error-checking at intake — "fillable online forms can provide basic error checking and ensure the data is readable" — is the first fix worth making, and that airports that supported their authorized signatories "experienced fewer issues." When San Antonio reworked its intake process, prep time per appointment fell from 60 minutes to 15 and "data entry errors were reduced by 80%."

In other words: almost everything on this list is checkable before the packet reaches the badging office — names compared, dates verified against the appointment, blanks caught, the right form revision confirmed. The offices that check at intake bounce less. The rest do the same inspection anyway — after the queue, at the counter, one turned-away applicant at a time.

This inspection is what AkamaiForms does.

It reads every application packet the minute it lands in your badging office's Microsoft 365 mailbox — checks the names against each document, the dates against the calendar, every field against your airport's own rules — and drafts the correction letter the same minute, naming exactly what's wrong. A person approves everything. The applicant fixes it all in one round instead of three.

Watch the 3-minute demo Talk to the team

Sources

  1. Phoenix Sky Harbor (PHX), Authorized Signatory Guidebook (Apr 2023) and Know Before You Go; Background Checks.
  2. Philadelphia (PHL), Authorized Signer Handbook 2025.
  3. Charlotte (CLT), Credentialing.
  4. Denver (DEN), Badging & Security for New Employees.
  5. Houston Airport System (IAH/HOU), Badging.
  6. Salt Lake City (SLC), Badging FAQ.
  7. Oakland (OAK), Authorized Signer Information.
  8. MWAA / Washington Dulles (IAD), Dulles Pass & ID Office.
  9. San José (SJC), Authorized Signatory Responsibility Agreement.
  10. Palm Beach (PBI), Authorized Signatory Information Handbook.
  11. Eagle County (EGE), Authorized Signatory Booklet.
  12. Kahului (OGG), Hawaiʻi DOT, New Badge Application (rev. 2025).
  13. Minneapolis–St. Paul (MSP), MyMSPConnect Badging.
  14. Detroit (DTW), Airport ID Badges.
  15. Yuma (NYL), Authorized Signatory Training.
  16. National Safe Skies Alliance, PARAS 0036: Airport Credentialing Efficiency Toolkit (2022).

Quotes are reproduced verbatim from the linked documents as published at the time of writing (July 2026). Requirements vary by airport and change — the linked source is always the authority.