the system of the present invention involves two major components , as shown in fig1 : a local area network , i . e . lan , 10 located at a central office 12 , and remote workstations 14 located at remote sites 16 . at the central office 12 a document server 15 and local workstations 18 are connected on the lan 10 . also present on the lan 10 are a high - speed scanner 24 and an archive storage unit 26 . the archive storage unit 26 can be a &# 34 ; jukebox &# 34 ; type optical storage unit , which can store millions of electronic documents on a series of optical disks that are selected using a jukebox type disk changer mechanism . on the network is a remote gateway server 20 , which may be an isdn gateway server . server 20 connects the lan to the remote workstations , e . g . over isdn lines 22 . fig2 illustrates the program controlled procedure for sending work to an employee at a workstation 14 at remote a site 16 . this procedure is under the control of a program stored on the document server 15 at the central office . according to this procedure , the documents are digitally scanned ( step 100 ) using the high - speed scanner 24 . the scanned images are compressed and stored as image files ( step 102 ), in order to drastically reduce their size . the uncompressed image file for a scanned image of a document that has considerable &# 34 ; white space &# 34 ;, such as a form , can occupy more than 10 times the storage space of the image file when in compressed form . the compressed image files are loaded onto a network device , such as the document server 15 . if a large number of images are scanned at once , or if they are to be stored for an extended period of time , they may be stored in another network device , such as the archive storage unit 26 . as new documents are received by the document server 15 , a program executing on the document server , known as a document router , evaluates the characteristics of each document and compares them against a set of predetermined criteria called &# 34 ; routing rules &# 34 ;, which have been established and represented in a database ( step 104 ). these rules could consist of any information that would allow the selection of certain documents which are suitable for a particular remote user ( employee ) or group of workers to process . for example , the files may be selected according to type , such as a medicaid form , location of the client , date of the form , or any other criteria . associated with each rule is a named &# 34 ; destination &# 34 ; which describes a user or group of users or a computer program assigned to perform business data processing for a given document . fig3 illustrates the document router program of step 104 in fig2 in further detail . for the first document received by the document router ( step 200 ), a first rule and its associated destination is obtained from the rules database ( step 202 ). the rule is compared with the data characteristics of the document ( step 204 ). for instance , a sample rule might be : &# 34 ; document type is a medical claims form and the total claim amount field is greater than $ 1 , 000 &# 34 ; with an associated destination of supervisor . if the rule condition was evaluated to be true ( step 205 ) for a given document , then the document would be assigned a destination of &# 34 ; supervisor &# 34 ; ( step 206 ) and the program would exit ( step 210 ) back to the routine of fig2 . if the rule condition is not true , the next rule in the rules database would be obtained ( step 208 ). it would then be compared to the document characteristics ( step 204 ). this loop would continue until a destination was determined , based on finding a match between the rule and the document characteristics . if after the last rule in the rules database has been compared ( step 207 ), there is no rule in the database that is a match , a default destination is assigned ( step 209 ) and the program exits . returning to fig2 associated with each possible destination are a set of page selection and clipping extraction definitions for each possible type of document . the particular pages and clippings associated with the destination are extracted from the document ( step 105 ). the clipped document files are then held on the document server until remote users , who are associated with the various destinations , sign on and request documents to work on ( step 106 ). when the remote user login is complete , the files assigned to a destination associated with a particular user are then transferred from the document server to the remote workstation for processing ( step 108 ). when this transfer is complete , the user connection to the document server is terminated ( step 110 ). another portion of the program that operates the system according to the invention is stored at the remote workstation 14 . this program is illustrated by fig4 . according to the program , the image files are first received over an isdn line ( step 300 ). since the image files received at the remote workstation 14 are in compressed form , each image file is decompressed automatically in order for the remote user to view the image and perform work relevant to the image ( step 302 ). once the first image file is decompressed , the remote user can begin work on that file . while working on each image file ( step 304 ), the remote user occupies very little of the workstation processor time . for example , while the user is typing data that is relevant to the first image into the workstation , the majority of the processor time is spent waiting for the next character to be typed . this time can be utilized , in part , for decompressing the next image file ( step 306 ) so that the next image will be available for viewing when the remote user finishes working on the first image . when the user finishes work relevant to the first image , the user switches to the second image which has already been decompressed and can thus appear on the screen almost instantaneously ( step 308 ). since the second image is stored in ram after its decompression , the speed with which the user can switch to the second image is limited only by the monitor refresh time . by anticipating the need for the second image while the user is working on the first image , the user can continue work from the first image to the second without interruption . the idle time of the user is thereby greatly reduced . after the user switches to the second image , the user can being work related to the second image ( step 310 ). while the user performs work related to the second image , the third image file is decompressed ( step 312 ) and the data created during the processing of the first image is stored ( step 214 ). therefore , the delay time is reduced when switching images by eliminating at least two sources of delay : ( 1 ) delay in decompression of the next image , and ( 2 ) delay in saving the data related to the previous image . when the user finishes work on the second image , he switches to the third image ( step 316 ). this process continues while the worker goes through the files in the inventory at his workstation . for a group of n images , as the user works on the next - to - the - last image ( n - 1 ) ( step 318 ), the last image ( n ) is decompressed ( step 320 ), and the data related to second to the last image ( n - 2 ) is stored ( step 322 ). after work is performed relating to all images , an isdn connection can be established between the remote workstation and the isdn gateway to communicate to the central office the data developed by the remote user related to the images using the automatic transfer program described previously . the images themselves will not need to be transmitted back to the network unless they have been changed in some way at the remote workstation , because the central office network retains copies of the images . it should be noted that the present invention is effective in part because of the anticipation of workflow . this is most possible , and the benefits of the invention are greatest , where work may progress in a predictable fashion . as an example , a clerk who processes credit card applications for a particular region of the country by entering the data written on the application into a mainframe application can be assigned a continuous stream of new applications by the document router . the system can anticipate that when one application is processed , the operator will ask for the next one assigned . because of this , the system can prepare the next document by ensuring that it has been transferred from the server , decompressed , and is ready for viewing by the time the remote workstation operator actually needs it . it may also be a requirement of the program to prioritize documents , e . g ., to present first the most important or critical documents or the oldest documents . thus , the program anticipates which document and which portion of the document will be needed next . the anticipated document is decompressed in ram at the workstation before it is needed and while the user is working on a previously requested or anticipated document . naturally there may still be occasions where the user wishes to view a document out of the anticipated sequence . in such a case the document is available , but the user must wait for the images of the documents in the file to be transferred and decompressed , perhaps in the anticipated order . the process of transferring documents to a remote user workstation is largely hidden from the remote workstation operator by a program stored on the remote workstation which executes in the background while the user is processing documents in the foreground . the logic for this program is depicted in fig5 . this program maintains a count of the current inventory of documents to process on the remote workstation . associated with this inventory are three user - configurable threshold values used to determine if an automatic call to the central office is required . in ascending value , they are termed the &# 34 ; empty &# 34 ;, &# 34 ; low &# 34 ;, and &# 34 ; high &# 34 ; thresholds . in addition , there is a user - configurable table called the &# 34 ; call schedule table &# 34 ; which has the following format , as an example : ______________________________________rowno . day time state comment______________________________________1 2 - 6 9 : 00 - 18 : 00 empty peak rate only when empty2 2 - 6 18 : 00 - 9 : 00 low off - peak if low3 2 - 6 10 : 00 - 11 : 00 none block weekday peak even hours4 2 - 6 12 : 00 - 13 : 00 none block weekday peak even hours5 2 - 6 14 : 00 - 15 : 00 none block weekday peak even hours6 2 - 6 16 : 00 - 17 : 00 none block weekday peak even hours7 7 - 1 0 : 00 - 0 : 00 low anytime weekend if low______________________________________ the first column , called &# 34 ; day &# 34 ;, of this table is a numeric range code for the day of the week with sunday coded as day &# 34 ; 1 &# 34 ; for example , &# 34 ; 2 - 6 &# 34 ; in the table stands for monday through friday . the second column , called &# 34 ; time &# 34 ;, is a time of day range indicated with military time format . the third column , called &# 34 ; state &# 34 ;, is one of the values none , empty , or low . the value &# 34 ; none &# 34 ; is used to indicate that automatic calling is not permitted for the given period . the value &# 34 ; empty &# 34 ; is used to indicate that automatic calling is only permitted if the current inventory is below the empty threshold value . finally , the value &# 34 ; low &# 34 ; is used to indicate that automatic calling is permitted if the current inventory is below the low threshold value . the comment field is used to describe the purpose of that row in the table . the call management program works by periodically checking to see how many unprocessed documents are in its current inventory ( step 400 ). this period is user - configurable and would typically be set for 5 minute intervals . it then evaluates the state of the inventory by comparing it against the empty threshold ( step 402 ). if the current inventory is below this threshold , then the state of the inventory is set as &# 34 ; empty &# 34 ; ( step 404 ). if the inventory is not below this threshold , then it &# 39 ; s level is compared against the low threshold ( step 406 ). if the current inventory is below this threshold , then the state of the inventory is considered &# 34 ; low &# 34 ; ( step 408 ). if the inventory is not below this level , then the program exits to wait until the next period begins . ( step 410 ). if the inventory state is either empty or low , the program will proceed to scan each row of the call schedule table ( step . 412 ). the processing for each row can be described as follows : if the current day is not within the day range of the row , proceed to the next row ( step 414 ). if the current time is not within the time range of the row , proceed to the next row ( step 416 ). if the current day is within the day range ( yes at step 414 ) and the current time is within the time range for a row ( yes at step 416 ), then if the current inventory state is less than or equal to the state level of the row ( step 418 ), proceed to the next row . if the current inventory state is greater than the state level of the row ( step 418 ), then the program will exit and wait ( step 410 ) until the next period to repeat this procedure . if all the rows of the table have been processed successfully ( step 420 ), then proceed with automatic calling of the lan gateway ( step 422 ). in the example call schedule table , row nos . 1 through 6 are configured to control call scheduling from monday through friday as follows : calls may be placed from 9 am - 10 am , 11 am - 12 pm , 1 pm - 2 pm , 3 pm - 4 pm , 5 pm - 6 pm from monday through friday if the remote workstation is empty . calls may be placed 6 pm - 9 am from monday through friday if the remote workstation is low on work . the effect of rows 1 and 2 is to defer calling during peak rate hours until it is absolutely required . for instance , if the remote workstation becomes low on work at 5 : 30 pm , the call schedule table will defer calling until either the workstation is empty or until 6 : 00 pm . the effect of rows nos . 3 through 6 is to block calling during office hours which start with an even number . presumably , other remote workstations are configured for the converse situation , i . e ., to block calling during office hours which begin with an odd number . the last row no . 7 indicates that calls may be placed anytime on saturday or sunday if the remote workstation becomes low on work . this kind of configuration permits scheduled , efficient sharing of a limited number of host phone lines . the workstation will then automatically call the lan gateway using a pre - stored phone number , user id , and security password to establish a data connection . it will then receive files which have been assigned to the remote workstation operator ( step 424 ) until the inventory level equals the &# 34 ; high threshold &# 34 ; ( step 426 ). it will also transmit any modified data from processed documents back to the document server ( step 428 ) for access by other users and for re - assignment by the document routing program . when this data transfer has been completed , the call is automatically terminated ( step 430 ) and waits for the next inventory check ( step 432 ). the procedures described above provide many advantages over a manual calling process . first , the call schedule table can be configured to automatically call when the phone rates are lowest . this obviously reduces the overall cost of operating a remote workstation . second , utilization of the lines into a lan gateway can be maximized by scheduling remote workstation access . for instance , given one ( 1 ) incoming line for the lan gateway and four ( 4 ) remote workstations , it is beneficial for the remote workstations to coordinate their calling to minimize retries and possible work starvation situations by configuring the call schedule table such that each workstation is permitted to call the lan gateway in a different 15 minute interval , this increased utilization of the lan gateway permits fewer lan gateway phone lines to be configured for a given number of remote workstation users , again reducing the costs of operation . third , the whole process of connection to the central site is hidden from the remote workstation operator , simplifying workstation operation and increasing productivity . while the invention has been particularly shown and described with reference to preferred embodiments thereof , it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention .