One of MasterFile’s unique design points is its single file database architecture and browsing metaphor. This architecture makes MasterFile simple to understand and ideal for small project and case files — or even just a few documents that need to be organized, secured and shared. In this post we look at how MasterFile’s unique browsing metaphor and issue/topic categorizations let you customize it to use in creative ways you might not have thought of — without any programming.

One of MasterFile’s unique features is the ability to let you set out and substantiate your argument or thesis, point by point. Why? Because setting out and proving the facts related to the issues with concrete argument, substantiated by key extracts from evidence is what it’s all about. In this post we cover how, based on what we’ve learned and refined from actual cases argued with MasterFile.

Documents are at the heart of your work and being able to efficiently load existing documents and e-mail, and manage work-product, is essential. MasterFile’s unique document repository is designed to manage both evidence which is generally static and work product such as correspondence, pleadings, reports, etc. that is often also revised.

Work flow: loading a case’s documents into MasterFile and keeping it up to date as you create work product or receive more evidence is the focus here. You’ll find the concepts useful for both litigation and transactional case files.