Hi Ian,
The team has reservations about this.
First, we worry that it would open the door to similar status indicators on other data fields. Why wouldn't we have "intentionally blank: evidence lacking" for all names, dates, and family relationships? Why does it make sense for locations but nowhere else?
Some people might also ask for other "intentionally blank" indicators. Right now, we only use them for privacy.
One small objection to all status indicators and the addition of new ones: they add complication. The more of these little things we have, the more complex the UI. It all takes a few more seconds to understand. Seconds add up and discourage new users.
Adding to confusion: Why do we have different approaches for other required fields? We require that one date field be included, and to use "Unknown" for last names. Some like Peggy McMath and Jim have suggested considering "Unknown" for locations instead of the new status indicator. Others have made good arguments against using Unknown for names.
Another important consideration, raised by Regan and others: would the new indicator be understood and used correctly? We are saying it should only have a very, very limited usage. There is a good chance it would be used incorrectly more than it would be used correctly.
Even many of the advanced members commenting on the proposal don't quite agree on the proper usage of the "Uncertain" status indicator. If we add an "Evidence Lacking" indicator, it's likely that a lot of members would use these instead of entering uncertain information. The way we encourage uncertain information has always been controversial. Our rationale for it is subtle. It's something that many genealogists are not comfortable with. If we now offer "Evidence Lacking" as an option, we might be shooting ourselves in the foot.
Finally, this doesn't feel urgent. The team is rushing to push out changes that have been discussed for years before we lock down for the redesign. Even if there were no open questions to consider, it would be months before it could be implemented.
Ian, I am sorry to be a wet blanket here, as I often am.
Chris