Institute an Audit Log in Your AMS
Audit logs (or change logs) track the changes made to the data in your system. They can track what was changed, when it was changed, and who changed it. If you're not sure if your database has this feature, ask your developer or re-seller. One note: To institute an effective audit log, your users must have individual user log-in names, and they must use them every time they log into the database. If everyone uses the same login, your change log will be useless.
The best way to resolve data entry problems is to go to the source. By using the audit log, you can learn the source of the mistakes, address the issue immediately and eliminate the problem. Also, an audit log can serve as invaluable record history. For example, by looking at your audit log, you can see at a glance that a certain member lowers his sales volume come dues time, but after paying the lower dues amount, raises his published sales volume again. Armed with this knowledge, you can be prepared the next time he calls to change his volume and insure he pays the correct dues amount.
|
