Priority Date ... why can it be different from filing date?
-
I have an IN provisional application where my docketing department inadvertently entered 1/10/2024 as a filing date; it has no Connections to any other application. The priority date changed to 1/10/2024 once the filing date was entered.
They then realized that they'd entered the wrong filing date and changed it to 1/11/2024 and saved the record. But the priority date didn't update to match.
If a priority connection is specified, then the priority date changes to match the earliest priority date of the "Connections" and is hard-coded; you can't change it.
The priority date not updating to match the filing date for applications that don't have priority connections seems like a bug. Although maybe there's some reason I'm not seeing for this behavior. The only one I can think of is if you maybe have to import a bunch of legacy matters into AppColl and want to have key date information but don't care about specifying the priority chain. But even if that were the case, it seems like maybe the default approach should be to update the priority date field to match the filing date when the filing date is edited....
Curious to hear if this is on purpose or a bug....
-
The reason may have been to stop generating a number of tasks when the priority date changes. This allows you to manually edit what you need.
