Think about it. Breaking Logical Relationships!
The most common mode of workflow management in-house involves the use of key enterprise level systems (with a network of Microsoft office document attachments used to fill in the gaps between them – to organize, compile, layout and communicate using attachments).
Execution of a High-Volume Print / Fulfillment Project
However, when it comes to execution of a high-volume print/fulfillment project, the Word documents and spreadsheets typically used are not optimal for the task of volume production execution. These types of files are under-powered for the task at hand and it is so easy to “break” logical relationships between the member database records and their intended content – making it easy to send the wrong stuff to the wrong people.
Constant Barrage of Government Changes
Now add to that the constant barrage of government changes or list changes smack in the middle of the project plus the flurry of 500 emails exchanged between team members and you have a recipe for a profit draining disaster. Now let’s program an enterprise system to handle all this and was it lost on the plan that they can focus on making money through what they do best which is providing health insurance instead of writing software?
Valuable Staff Resource Hours Could be Better Spent in Other Areas of Plan Administration
Successfully implementing an integrated communication management platform devours valuable staff resource hours that could be better spent in other areas of plan administration. One Health Plan reported 10-12 hours of lost time for the completion of one letter run to only 150 members due to decentralized communications.