Tuesday, June 02, 2015

The Receipt for Service II

I've got a problem with the Receipt for Service implementation. Just in terms of bureaucracy and system design, county employees are asked to dual-task, do the work to support what the customer wants or needs plus as a separate operation record the history of the encounter. The extra work isnot likely to please the employee and the fact it's separate increases the likelihood it won't get done, undermining the validity of the statistic

A separate problem arises when it's the producer/farmer herself going online to do the work, as for example the new NRCS process.  How are those transactions going to be tracked?

No comments: