New York is asking how its NY.gov ID login should work. Read your own portal's support inbox with the same questions
"I changed my phone and now I can't get the code." Every public portal gets that email. New York just asked the market how its statewide login should handle it, and the list of topics works for any agency or county with a sign-in page.

New York's Office of Information Technology Services launched NYS Digital Access in November 2026, with a discovery RFI on modernizing NY.gov ID; responses are due December 30, 2026, and it is not a procurement. Its topics, from sign-in and multi-factor authentication to account recovery, identity verification, fraud, language access and migration, make a good test for any public portal. Read your own support inbox against them before you write requirements or talk to a vendor.
New York asked a good set of questions
New York's Office of Information Technology Services launched an initiative this month called NYS Digital Access. It's about NY.gov ID, the single sign-in that New Yorkers use for services such as unemployment benefits, tax filings, DMV records and public assistance, according to StateScoop's coverage. The state posted a discovery request for information and opened a survey for residents who use the login today. GovTech reports that RFI responses are due December 30.
It's not a purchase. ITS says plainly that the RFI is "for strategic discovery and planning purposes only" and not a solicitation or product selection. What makes it worth reading, even if you'll never answer it, is the list of things the state wants to understand: account creation, sign-in, multi-factor authentication, identity verification, fraud protection, account recovery, language access, agency integration, support, and long-term operation.
Acting CIO Jenson Jacob put the point well: "Large-scale modernization requires more than technology selection. It requires a practical understanding of implementation realities, migration, agency readiness, support, operations, integration and sustainability."
If you run a county portal, a licensing site, a benefits application or any public service with a login, that list applies to you. And you don't need an RFI to start answering it.
The answers are already in your inbox
The requirements for a public login are already written. They're sitting in the support inbox.
Here are five emails that almost every public portal receives in some form. These are composites, not real messages, but anyone who has worked a help desk will recognize them.
"I changed my phone number and now I can't get the code." That's account recovery, and it's the email that tells you whether your multi-factor setup was designed for real life. People change numbers, lose phones and share family devices.
"It says you couldn't verify my identity. What do I do now?" That's identity verification. The interesting part isn't the check. It's what happens after it fails, how long a person waits, and whether anyone at the agency can see why.
"My mother doesn't read English well and can't get past the sign-up page." That's language access, and it often stops at the marketing pages. The error messages and the code-entry screens are where people actually get stuck.
"I made a new account and now my history is gone." That's agency integration, and it usually means two accounts for one person. Somebody has to find and merge them, and that somebody is usually staff, by hand.
"Someone logged into my account and changed my direct deposit." That's fraud protection, and it's the email nobody wants. It's the reason for a second check on sensitive changes, and a notice to the old phone or email when contact details change.
Decision guide
What the email says, and what to ask a vendor
| Consideration | The email | The question for a vendor |
|---|---|---|
| Recovery | I changed my phone and can't get the code | Show me recovery for someone who lost their only second factor |
| Identity | It says you couldn't verify me | What happens next, and how long does a person take to review it? |
| Language | My mother can't read the sign-up page | Which steps are translated, including the error messages? |
| Two accounts | I made a new account and lost my history | How are duplicate accounts found and merged, and by whom? |
| Fraud | Someone changed my direct deposit | Which changes trigger a second check or a notice to the old contact? |
The requirements for a public login are already written. They're sitting in the support inbox.
Turn each email into a vendor question
Sort a month of support tickets into those five piles, plus "other." Count them. You now have something better than a feature wish list: a ranked list of where real people fail, in their own words.
Then turn each pile into a question you'd ask a vendor, and ask them to show you rather than tell you. For recovery, ask to watch someone recover an account after losing their only second factor. For identity checks, ask what the failure screen says and how a person reviews the case. For language access, ask which screens are translated, including the errors. For duplicates, ask how they're detected and who merges them. For fraud, ask which changes trigger a second check and who gets notified.
A vendor demo almost always shows the happy path, a new user signing up smoothly. Your inbox is a list of unhappy paths. Make those the demo.
Plan for two logins at once
The part of New York's announcement that deserves the most attention is the plan itself. ITS describes the phases as discovery, target-state planning, procurement, implementation, pilot, phased migration, legacy retirement and ongoing operations. Read that list again and notice what sits in the middle: a long stretch where the old login and the new one both exist.
That period is where public login projects get hard. Residents get emails telling them to move. Some do, some don't, some create a second account by mistake. Help desk scripts have to cover both systems. Every connected service has to know which login a person used. And the date you retire the old one depends on how many people are still on it, which you can only manage if you're counting.
Whatever you're replacing, write the migration plan before you pick the product. Decide how a resident moves, what happens to people who never respond, and how you'll know when it's safe to turn the old system off.
Sequence of work
The phases New York has named
- Discovery
RFI and resident survey; responses due December 30, 2026.
- Target-state planning
Decide what the new login must do.
- Procurement
Separate, if authorized; the RFI is not a solicitation.
- Pilot and phased migration
Old and new sign-in live side by side.
- Legacy retirement
The old system is switched off.
Count before you change anything
There's one more thing worth doing early, and it's dull: count. Before anyone writes requirements or talks to a vendor, find out how many accounts exist, how many people signed in during the last year, and how many support tickets each of the five piles produces in a typical month. Note how long each kind takes to resolve, and how many need a person at the agency to step in.
Those numbers do three jobs. They tell you which problems are worth paying to solve. They give vendors something concrete to respond to, so their proposals can be compared on the same footing. And they become the baseline for the migration, the only way to know later whether the new login actually reduced the recovery emails, or just moved them to a different inbox.
If the numbers are hard to get, that's a finding too. A login nobody can measure is hard to replace safely.
If you're about to write your own requirements
If you're an agency or county with a login project coming, three things are worth doing this month. Sort your support inbox, as above. Read New York's RFI topics as a checklist, since a large state has already done the work of listing what matters. And if you have experience with this kind of system, consider responding to New York by December 30. Discovery RFIs are exactly where practical lessons are wanted.
We help public agencies scope and build resident-facing services, starting from how people actually use them, in our government and public sector work. If your login is the thing your help desk talks about most, talk to us.
Related work: Sutton|Place
We build alongside the people doing the work.
Bring us the problem you’re thinking about.