We have a project that is currently underwhelming me and I know there is vast room for improvement. But I think I'm failing to get the best idea for moving forward. Here's what we have:
Mission: track the law firm's attorney's registration due dates for every court each atty is registered with.
What we have: a few hundred attorneys. Dozens of courts. Every atty has a unique combination of 1) court registrations, 2) due dates
What is happening: our admins are going thru a clumsy table which shows each atty on a row, and then a due date under the respective court. See simple sample below.
the problem is that this table is painful to navigate, manage, etc. I wanted to track like a membership, but there can be differing membership(s) per person. So we could have as small as 1 membership, up to a dozen. Then I tried to organize it by atty, but really the admins need to know when it is due (more than for whom it is due)... BUT then once they know what is due, they have to know for whom so they can contact that person. Also have to know who didn't pay. And then it repeats every year.
I feel like I'm 90% to a solution, but that each solution isn't quite right. I'm hoping someone could give me an idea or an example that I could use to build a smarter method of tracking due dates, and payment dates. I would like build a chart sheet showing the next month's due dates (and for whom). BTW, the admins who would use this do NOT have the experience/skillset to manage it themselves. I have to build it so minimum modification is required moving forward.
anyone face this problem and find a graceful solution?
Mission: track the law firm's attorney's registration due dates for every court each atty is registered with.
What we have: a few hundred attorneys. Dozens of courts. Every atty has a unique combination of 1) court registrations, 2) due dates
What is happening: our admins are going thru a clumsy table which shows each atty on a row, and then a due date under the respective court. See simple sample below.
the problem is that this table is painful to navigate, manage, etc. I wanted to track like a membership, but there can be differing membership(s) per person. So we could have as small as 1 membership, up to a dozen. Then I tried to organize it by atty, but really the admins need to know when it is due (more than for whom it is due)... BUT then once they know what is due, they have to know for whom so they can contact that person. Also have to know who didn't pay. And then it repeats every year.
I feel like I'm 90% to a solution, but that each solution isn't quite right. I'm hoping someone could give me an idea or an example that I could use to build a smarter method of tracking due dates, and payment dates. I would like build a chart sheet showing the next month's due dates (and for whom). BTW, the admins who would use this do NOT have the experience/skillset to manage it themselves. I have to build it so minimum modification is required moving forward.
anyone face this problem and find a graceful solution?
| Court 1 | Court 2 | Court 3 | Court 4 | |||||
| due | paid | due | paid | due | paid | due | paid | |
| Mr. Blue | 1/1/2023 | 12/1/2022 | 5/1/2023 | |||||
| Mrs. Green | 3/1/2023 | 7/1/2023 | 6/1/2023 | |||||
| Ms. Yellow | 11/1/2023 | |||||||
| Mr. Beige | 7/1/2023 | 11/1/2023 |
