Johannesburg, 22 Aug 2016
For financial institutions looking to automate common business processes, there are two major technology choices to be made: A Business Process Management system (BPMs) and a document assembly platform. The BPM handles data routing, rights management, stage approvals, credit checks, etc., while the document assembly platform handles data-gathering and document production. Because workflow requirements across banks - even across lines of business within a bank - vary so dramatically, it's difficult to offer advice on overall workflow design. However, the document assembly requirements of workflows within banks tend to be more standardised.
With this in mind, here are eight mission-critical issues to consider when transforming your real-world business processes into automated workflows:
1. Inline document preparation
Virtually none of the major BPM systems have document assembly capability (at least, not adequate capability for complex documents, such as loan agreements). Consequently, BPM vendors may just assume that you'll be generating documents using some dark, offline process and then passing the finished documents into the workflow for routing and approval. But the idea of document-centric workflows that don't actually have the ability to generate documents seems . . . well, like somebody's missing the point. At any rate, that's why you need an enterprise-grade document assembly platform to work in unison with your BPMs - to gather all necessary information for the documents themselves and to generate the documents from within the workflow. Anything less is tantamount to a duct tape-and-super-glue kluge for what could otherwise be an elegant solution.
2. BPM integration
There are lots of lightweight, template-building utilities on the market which may be an upgrade from the native document assembly functionality in your BPM. Such lightweight applications are typically designed for merging simple variables into word processor documents and controlling the inclusion of language blocks with simple business logic. But such applications may not allow for server/cloud deployment (critical with a BPM integration) and, those that do, may not have the type of flexible APIs necessary to integrate with a robust BPM. In contrast, enterprise-grade document assembly platforms, such as HotDocs, allow for either on-premises server deployment or a cloud-based (hosted) deployment. Likewise, such systems will have powerful APIs, enabling you to integrate interviews (wizard-like, interactive data-gathering sequences) into a workflow wherever they're needed.
3. Data Gathering
Virtually all BPMs have utilities for creating simple, data-gathering forms. And in many types of workflows, these simple forms may be adequate. However, in any workflow that includes complex document assembly (such as loan origination workflows), BPM forms are not likely to get the job done. Automating the assembly of complex documents requires ultra-sophisticated data-gathering forms, which can only be designed and created after the documents themselves have been automated. Put another way, you won't know which questions need to be asked to generate the document(s) until you've merged variables and business logic into the documents themselves. The variables you merge into the document serve as question fields in the data gathering forms. And here's the key point - since you have to use the document assembly platform to create interviews that are sophisticated enough to gather data for your complex documents, you might as well use the document assembly platform to generate all data-gathering forms in all of your workflows.
4. Safeguards in the data-gathering sequence (interview)
One of the key benefits of any type of business process automation is the codification of best practices. In the case of document-centric workflows, adherence to best practices doesn't just improve efficiency; it also safeguards you from making costly mistakes. As was already mentioned, elite document assembly platforms have, arguably, the most powerful interviewing capability available, a by-product of the need to generate data-gathering sequences for sophisticated legal instruments. Such platforms will allow you to design wizard-like interviews that lead workflow users through the process of gathering all the necessary data. Question fields can include validation logic and help resources can be attached to individual questions. Workflow designers may even want to call outside Web services to help loan officers get the correct answer in each field. One global bank tests each answer as it's entered into a field against the bank's own internal guidelines and policies. Answers are colour-coded based on how closely they comply with policy. Given correct and complete business logic in document templates, the key to generating perfect transactional documents is correct data entry. Safeguards in the interviewing sequence are the key.
5. Word processor documents and PDF forms
Depending on the types of documents involved in your workflows, documents generated out of your workflow may include text-based documents (word processor documents) as well as PDF forms (graphical forms with fields and checkboxes). When choosing a document assembly platform, make sure it can handle the complex automation issues of both types of documents. One key functionality to look out for is component sharing, which means variables used in the automation of, say, a text-based lending agreement can be used in any other document template as well, including PDF forms. This approach allows you to update a component (variable) in a single place and have it updated globally, throughout all documents and PDF forms. Furthermore, it allows for bank staff (loan officers, for example) to enter an answer a single time and have it appear throughout all documents and forms.
6. Integration with enterprise data storage
One of the early stages in your workflow should be a check of enterprise storage systems to see if you already have existing, relevant data relating to the transaction at hand. Given that you'll likely want to use a document assembly platform to create data-gathering interviews, make sure that the platform you choose can integrate with your existing data storage systems. You should be able to populate fields in your workflow interviews as well as write new data (entered during the interviewing process) back out to data storage systems.
7. Data routing and approval (Instead of document routing and approval)
Given that most BPMs don't have sophisticated document assembly capability, most BPM vendors assume that you'll be generating documents outside the workflow. In this scenario, it follows that the finished documents will be passed into the workflow, where they can be routed for various stages of approval. But gathering all the data necessary to generate documents within the workflow (as well as for any other data needs within the workflow) facilitates a much more efficient approach - routing data for approval, rather than documents. In the Safeguards section above, we mentioned a bank that uses an automated workflow for loan origination. The workflow colour codes answers in an interview according to an answer's compliance with bank policy. The complete answer set is then routed from relationship managers (the staff members that interface with customers and actually gather loan data) to a loan approval committee. The committee can then quickly review the colour-coded answer set, rather than spend hours reading complex loan documents. This approach has allowed the bank to reduce the origination process for commercial loans from three days to under an hour.
8. Planning for the future
The workflows that you're envisioning now may be simple or complex, incorporating your current wish list of features and functionality. But there's a good chance that what you're envisioning today may be rudimentary compared to what you may want or need a year or two down the road. Don't get drawn in by the siren's song of simplicity. Choose a BPM and a document assembly platform that have the features and functionality to handle virtually any level of technological sophistication. That way, you won't have to abandon a technology investment a couple of years down the road and make yet another investment that will actually be adequate for your long-term needs. The ability to scale is key.
Share