GitHub Education verification rejected for online MBA student at FACPRISMA #204288
|
Hello GitHub Education Support, I am requesting a manual review of my GitHub Education application for FACPRISMA – Faculdade de Ensino Superior Ltda. My application was rejected because of a name-match issue and campus proximity. I believe my documents already address both points. My GitHub billing information and official enrollment declaration show the exact same name: Rogério Limas Moreira. I am enrolled remotely in the MBA em Inteligência Artificial at FACPRISMA. I live in São Paulo, Brazil, while the institution is located in Montes Claros, Minas Gerais, because the program is offered in distance-learning modality. My official enrollment declaration states that the institution is accredited to offer higher-education courses in “modalidade a distância” and confirms my current enrollment. I have attempted verification with both my digital enrollment declaration and digital student ID card. Both include a QR code linking to the institution’s website, where my enrollment and course attendance can be verified. I am autistic, and repeated automated rejections without a specific explanation are difficult for me to navigate. I would appreciate either a manual review or clear guidance on the exact missing requirement. For privacy reasons, I have not posted personal documents publicly, but I can provide redacted documents or additional verification through a secure support channel. Thank you for your help. |
Replies: 2 comments 1 reply
|
Look, your letter's already pretty solid, it just has a bit of repetition and your strongest point ends up buried near the bottom. You explain the name match twice up top once in the paragraph, once in the bullet one is enough. And the location point, that it's a fully online program and that's why you're in one state and the institution's in another, is exactly what answers their second rejection reason, so it's worth moving that closer to the start instead of leaving it near the end. I'd also open by asking directly for the manual review, so whoever reads it knows right away what you're asking for before getting into the details. And the autism disclosure I'd keep, but as one sentence it already does its job of explaining why you need something more specific than another automated rejection, no need to expand on it. Here's the rewrite, flowing as one piece: Hi GitHub Education team. I'm writing to request a manual review of my application, which was rejected for two reasons I believe my documents already address. The name on my billing information and on my enrollment declaration is the same, Rogério Limas Moreira, so it matches exactly. As for campus proximity: I'm enrolled remotely in the MBA em Inteligência Artificial at FACPRISMA, an institution accredited for distance-learning modality. I live in São Paulo, and the institution is based in Montes Claros, Minas Gerais, a different state, precisely because the program is fully online my enrollment declaration states this. I've already tried verifying with my digital enrollment declaration and my student ID card, both with a QR code linking to the institution's verification page. I'm autistic, and repeated automated rejections without a clear explanation are hard for me to work through, so I'd really appreciate a manual review or specific guidance on what's missing. I'm happy to share redacted documents through a secure channel if needed. Thank you for your help. |
|
Beyond polishing the letter, there are two mechanical fixes that address the two rejection reasons directly — both are about what the automated checks can read, not how the request is worded:
When you have the EAD-stating declaration in hand, submit one clean application: printed document photographed by camera, name block filling the frame. And if that still bounces, the manual-review request you want goes through https://support.github.com/contact/education with your application ID — moderators in this forum can't trigger one, but that queue can, and "remote modality + accented name" is a combination they've adjudicated plenty of times. |
Beyond polishing the letter, there are two mechanical fixes that address the two rejection reasons directly — both are about what the automated checks can read, not how the request is worded: