Abstract:
The present invention provides a system and method for tagging digital documents. A method for creating digitally tagged documents includes creating a data template for a digital document, assigning signature locations and data fields in the data template, and linking the template instructions with the digital document. A system for creating digitally tagged documents includes a processor; a display; and a memory containing stored programming instructions operable by the processor to create a data template for a digital document, assign signature locations and data fields in the data template, and link template instructions with the digital document.

Description:
PRIORITY CLAIM 
     This application claims priority to and the benefit of the filing date of U.S. Provisional Application Ser. No. 60/892,161 filed Feb. 28, 2007, which is herein incorporated by reference in its entirety. 
    
    
     BACKGROUND OF THE INVENTION 
     Contracts and other legal documents requiring signatures are used daily in commerce. These documents need to be signed, stored and routed to the necessary location in a controllable fashion. As electronic documents and electronic signatures become more universally accepted and demanded there exists a need to create a signing process that is controlled electronically. Historically, electronic systems that allow for electronic document signature typically apply the signature to the entire document. Documents such as contracts are not marked up for specific signature locations, initial locations, data collection locations and other areas for signatures to appear in the proper locations. This lack of ability to mimic the paper process led to slow adoption. More recently, some newer electronic systems allow the user to place signing locations into the document but require the user to manually create the workflow and authentication steps for the document via time consuming and tedious processes, such as the insertion or creation of tag locations throughout the document where the signatures are to be placed. Therefore there exists a need for automating the process of placing exact signature locations, workflow, and recipient tasks into these documents so they can be sent for e-signature more easily, this is especially true for documents that contain multiple signing locations, multiple recipients and more complicated workflows. 
     SUMMARY OF THE INVENTION 
     Systems and methods for tagging digital documents are disclosed herein. A method for creating digitally tagged documents includes creating a data template for a digital document, assigning signature locations and data fields in the data template, and linking the template instructions with the digital document. A system for creating digitally tagged documents includes a processor; a display; and a memory containing stored programming instructions operable by the processor to create a data template for a digital document, assign signature locations and data fields in the data template, and link template instructions with the digital document. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       Preferred and alternative examples of the present invention are described in detail below with reference to the following drawings: 
         FIG. 1  is a block diagram showing components of the preferred embodiment of the present invention; 
         FIG. 2  is a flow diagram showing a preferred method for document tagging templates; 
         FIG. 3  is a flow diagram showing a preferred method of creating a document using template data; 
         FIG. 4  is a flow diagram showing a preferred method for notifying a party to a transaction that the document is ready; 
         FIG. 5  is a flow diagram showing a preferred method for signing a digital document; 
         FIG. 6  is a flow diagram showing a preferred method of using a document overlay in one embodiment; and 
         FIGS. 7-9  are screenshots of example graphical user interfaces presented by the system shown in  FIG. 1  for performing the processes of  FIGS. 2-6 . 
     
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT 
     Systems and methods for tagging digital documents includes a way for a contract or set of contracts to be “marked up” using signing templates that describe a “signing process” that the document follows in order to be executed as intended by the document originator. This process utilizes a combination of documents, which are distributed to signers, a companion file defining the intended signing events and workflow, and an application which manages and registers the events and enforces the signing flow. The companion document information may be stored inside the document file or the document file may be a component inside the companion document. 
     In the preferred embodiment there exist two types of signing process templates: overlay templates and pre-tagged documents. Overlay templates include only the signing instructions, while pre-tagged documents include all signing instructions as well as the underlying document. A party to a transaction applies an overlay template to a new document that may contain different information each time, while the sender uses a pre-tagged document for documents that contain static information such as disclosures. Templates can be used by persons sending contracts or completed by the signer via a signing server, which prompts them for input. 
     An embodiment of the present invention is a system, method and computer program product for tagging digital documents. The present invention is preferably implemented as software components that are executed on a networked system, such as system  10  shown in  FIG. 1 , which illustrates a preferred embodiment of the present invention. The present invention may be implemented as stand-alone software components, for example delivered via Application Service Provider (ASP) technology, a web server, or integrated into a larger system. In one embodiment, a web server is computer a program running on a network that is able to receive and send commands from remote sender programs. The web server is preferably able to receive inbound documents, packages and templates, and evaluate them in order to process a document management process. System  10  includes a signing server  22  coupled to multiple customer systems  28  operated by customers over a public or private network  20 . Signing server  22  includes a database  24  for storing documents, digital signatures, digital signature certificate information, document related information (such as history), and various other information related to transactions performed on the stored documents. 
     The connections between the various components of the present invention may be a wireless or non-wireless connection, or a combination of both. Customer system  28  may be a personal computer connected to a network service provider over a public switched telephone network, a cell phone or personal data assistant wirelessly connected to a network service provider, a digital pen or other device that is connectable to network  20 . 
       FIG. 2  is a flow diagram  30  showing a preferred method for document tagging templates. At block  32  a digital document is created to be signed electronically. In order to create a digital document, templates are used which are described in further detail with reference to  FIG. 3  below. At block  34  a party to the transaction is notified that a document is ready for their signature, which is further described in  FIG. 4  below. At block  36 , signing instructions are received from a party to the transaction, which is further described in  FIG. 5  below. 
       FIG. 3  is a flow diagram  32  showing a preferred method of creating a document using template data. At block  42  a data template is created for a digital document. The template includes all the information needed to direct a signing process for a particular document or documents, and may be contained within the body or associated with files such as documents. Template information preferably includes some or all of the following data: transaction owner or source ID; recipients or roles of recipients who will be a party to the transaction (roles may be defined as required or optional and may be defined as locked and not changeable by the sender); authentication required for each recipient or role (may be single or multiple and may be applied to one or all); tasks that recipients will execute such as sign, review, approve, fill in data, or print; a list of “signing tabs” assigned for each recipient (signing tabs may be locked and/or required); association of workflow instructions, for example, the order in which the tabs are to be signed, the order in which the signers are to execute the contract, and the authentication levels being requested of each recipient; the role of each recipient as to signer, approver, reviewer, or final carbon copy; the sequence of delivery to individual recipients; locations of signatures and/or initials inside the document (locations can be relative to content in the document, like “anchors” (such as next to the text “Sign:”), or can be absolute (such as 100 pixels in and 300 pixels up on page 3 of document 1)); data collection fields and checkboxes; locations of data collection fields inside the document (locations can be relative to content in the document, like “anchors” (such as next to the text “Sign:”), or can be absolute (such as 100 pixels in and 300 pixels up on page 3 of document 1)), which data collection fields may include, for example, data that is presented to the signer to review and modify before execution of the document. 
     Templates may preferably be in, but not limited to any of the following forms: template only—contain signing instructions and no documents; pre-tagged document—a document or documents that includes signing instructions and the documents that are to be signed; and/or envelopes-a grouping of pre-tagged documents and standalone documents, or with associated templates. Template information can be stored in a variety of forms, such as XML or within the data structures of existing document types. 
     At block  44  signature locations and data fields are assigned in the data template. Signature fields are located where a party is asked to sign the document. Once the area is located a tab is entered to direct a party to the transaction to that location. Locations where a party is to initial are assigned as well as data fields such as date signed and printed name of the signer. In one embodiment the data fields are automatically entered by the system to ensure that the correct date is entered. At block  46  the template data is bound to the document. The template information as entered by the party and the document to be signed are merged. At block  48  the digital document, including the template, are sent to all of the parties to the transaction for signing. 
       FIG. 4  is a flow diagram  34  showing a preferred method for notifying a party to a transaction that the document is ready. At block  52  a digital document is received. At block  54  signatures are requested on the digital document. At block  56 , the digital document is linked to a signing server. The signing server is configured to secure the document and once signed and dated to store the document in its original form to create a legally defensible position that the document was signed and not altered in any way. 
       FIG. 5  is a flow diagram  36  showing a preferred method for signing a digital document. At block  62 , a party to the transaction is authenticated when accessing the signing server. Authentication ensures that it was the person who is party to the transaction that signed the documents. Authentication may include, for example, email invitations, access codes given through “out of band” communications, and/or personal history questions. At block  64 , the digital document is displayed to the party having signature locations and data fields. As shown in  FIG. 8 , for example, a document is displayed to the party and the area where a signature is requested is displayed with a tab that preferably states “sign here.” At block  66 , signing commands are accepted by the party. The party enters a digital signature onto the document which results in a signing command. At block  68 , all parties are notified that signatures have been received and an executed document is available. 
       FIG. 6  is a flow diagram showing a method of using a document overlay in one embodiment. A document overlay is a template that is used for documents that do not usually change; for example, in an IRS form that only changes yearly. At block  72  a previously defined overlay for a digital document is selected to match the digital document of choice. At block  74  the defined overlay to the selected digital document is bound to the digital document. At block  76 , the digital document is transmitted to the recipient. 
       FIGS. 7-9  are screen shots of example graphical user interfaces presented by the preferred system shown in  FIG. 1  for performing the processes of  FIGS. 2-6 .  FIG. 7  shows a tab overlay for a digital document. A navigation pane  82  shows a series of documents that are envelopes, pre-tagged documents, or tab overlays. A document list  84  shows the documents to be signed; in this example loan origination disclosures are shown. A properties pane  86  shows the document, the creation date, and recipients. In this case the role of each recipient is defined and determines where each recipient would sign. 
       FIG. 8  shows a document review pane  92 , which displays to a party to the transaction, the document that they are signing. The recipients pane  93 , identifies the recipients and when selected shows where each recipient is requested to sign. The tabs pane  94  shows a list of tabs that are of interest to the recipient. Tabs include, but are not limited to, signature, initials, optional initials, name, company, title and/or date signed. A date signed tab is shown in area  95 ; the date signed is locked and is preferably entered by a signing server. A signature tab is shown in area  96 : after review of the document a party may enter their signature. The current page of the document is shown in area  98 , whereas the second page is shown in area  97 . Additional pages would be shown as necessary. 
       FIG. 9  shows a screenshot of an exemplary portion of the preferred template development process of the present invention. A document pane  101  shows a user the document to be edited. A recipient/signer box  102  allows a user to define which recipient will sign in each area. A tabs box  104  shows a series of tabs that can be added to the document, including user designed custom tabs. A tab  106  is added to the document in preparation for sending the document to the recipient and asking the recipient to sign in that area. 
     While the preferred embodiment of the invention has been illustrated and described, as noted above, many changes can be made without departing from the spirit and scope of the invention. Accordingly, the scope of the invention is not limited by the disclosure of the preferred embodiment. Instead, the invention should be determined entirely by reference to the claims that follow.