virtual-triplets's Review of DocreviewpadReviewed on 8/9/18 3:32 PM
I purchased DocReviewPad (DRP) primarily for use in document productions. My main uses are discovery (requests for production), public records requests, and EEOC/OCR complaints. With all of these, I typically receive a numbered list of requests. With DocReviewPad, I can easily assign issue codes to match the request numbers. It works a whole lot better than sorting on a large table (or more often on the floor), especially when individual documents fall under multiple categories. The app is very good for reviewing documents and assigning issue codes. It falls short, though, in a number of usability features, which I will discuss below. If this was priced like most PDF readers, like PDF Expert, I would give it five stars. But at its premium price it needs more. Here are the specific shortcomings I see, in no particular order. - You can only access the user guide from the opening window. So if you are viewing a document and need help on a specific feature, you have to back out of the document and the case before viewing the help document, then navigate back to the document page you were working on. - There is no easy way to delete a page or range of pages from a document. The quickest way I have found is to extract the pages, which moves them into another document, then delete that document. It seems like a delete function would be easy to add. - Similarly, rotating pages is more difficult than it should be. You can rotate one page or all pages in a document. Frequently, though, I get documents that have a mix of orientations. Getting them all correct is so difficult that I use a separate PDF reader to fix orientations before importing into DRP. Which brings me to . . . . - Add a thumbnail viewer. Take a look at the thumbnail viewer on PDF Expert (which is 1/9 the cost of DRP). It shows all pages in a grid (it shows 3 rows of 4 pages on an iPad Pro 12.9 inch in landscape mode). From that view you can select non-contiguous pages and rotate or delete them as a group. You can also drag and drop to rearrange page order. Something like that is desperately needed in DRP. - Add a report that is organized by issue code. When I have all of my documents coded for production, I need to list in my written response the bates numbers that correspond to each of the issue codes. As far as I have been able to figure out, the reports are always sorted by document first. A lot of the time, I combine everything into one big document when I produce it, so that report format is counterproductive. Basically what I want is a report like: Issue Code 1 Bates 001-005 Bates 018-053 Issue Code 2 Bates 101-298 Bates 333-345 There could also be an option to include the document names - the key feature is top-level sorting by issue codes. - More flexibility in bates numbering. Give us the option to specify how many digits (I don’t like a lot of leading zeroes when there will only be a few hundred or a few thousand pages). Let us specify separators other than a hyphen. I prefer spaces, because I prefer the way it looks when specifying a range: Bates-001 to 005 versus Bates 001-005.
ienjoyed's Review of DocreviewpadReviewed on 5/26/18 1:46 AM
The sexy new web-based app, LogikCull (LC) is a current darling on the legal discovery scene, but DocReviewPad (DRP) is LogikCull Plus - we just didn’t recognize this app for the gem it is until there was something with which to directly compare. —— Both apps allow you to code a document with all of the same basic discovery codes, e.g., “Relevant, Responsive, Confidential, Privilege, etc.,” useful in marking whether a set of documents will be part of a production set. Additionally, both apps allow adding custom codes for signifying that a document is relevant because of something case specific, e.g., “Credibility,” “Witness?” “Hidden Asset,” “Key Date,” etc. However, LC only allows adding any custom tag to the entire document. By contrast, DRP allows analysis by page, when necessary. This is essential when your custom code refers, for example, to a key sentence you will want to easily find in the future despite it being buried deep in a huge journal, report or business record. Next, DRP does better Bates stamps, because they are customizable and visible (useful for taking side notes) while using the app rather than only upon download of a production or other document set. DRP also allows export of whole docs or individual pages either clean or marked-up, by email, to DropBox, to TrialPad, etc., and has the option of sending a summary of the page-by-page coding with the export. Both Apps allow you to make comments, but there is less necessary notetaking if the coding in DRP serves as both a placekeeper and a notation device. For example, once you have gone through and quickly marked thousands of pages with a tag noting “Witness,” or “Liar!”, when you later pull up all pages marked with “Witness,” you can easily determine who will need to be deposed or brought to trial without having to take notes while doing the initial document analysis. Months later, having this ability to find specific pages where the key data is located is a game changer. Next, DRP is much cheaper than LC (more below),* and finally, allows for maintaining all the files, e.g., pleadings, orders, correspondence, discovery, depo transcripts, photos, etc., in organized sub folders (important to our firm), instead of having to bring the documents in piecemeal if they are not part of the initial upload into LC — *Fraction of the cost: LogikCull is “Free,” but do not be fooled. Storage of documents while your case is ongoing is charged monthly by the gig, currently $40 per gig per month - and you are charged over and over for the same gig of data for every month you need the case to remain on the LogikCull server. While DRP may seem expensive at over $100 per subscription, in comparison to $100s to $1000s per month for LC data storage, even for a small firm, clearly DRP could make expensive improvements and people in the know would pay more for a ‘pro’ upgrade that fixes DRPs ‘little app’ disadvantages, as follows: — Downsides to DRP (improvements please!): 1) As compared with LC, which allows a full team of users to log in to see the data, DRP is a single user app, and to allow other users to view the analysis, the entire file must be uploaded as a report, or as a packet of data through iTunes (ugh). The actual analysis reports are easily emailed or stored in DropBox, etc., but the report is not the full value of having the documents in analysis mode in the app, as more twists and turns occur during the discovery period in your case. 2) DRP is only on iPad for now - a major negative. While the initial document analysis on iPad is fresh and fast, and frankly is a winner, being able to work with the results of the analysis on a computer with a 27 inch screen would be much more useful. The main reason members of our Mac-only firm looked away from DRP and tried LogikCull (and NViva, MaxQDA, DeDoose, Scrivener, and others) is because DRP is iPad only. ==Summary: Great features that are under-appreciated simply because of the limitations of transfer and the iPad platform itself. Our firm is still looking for perfection, but is hoping DRP continues to push for perfection with us.