I'm thinking about defining a few classes for the interview I'm working on. 1) DiscoveryRequest 2) Interrogatory - inherits from Discovery 3) InterrogatoryList? 4) DocumentRequest - inherits from Discovery 5) DocumentRequestList? The objects should have a few properties: "Checked" to indicate if it should be shown in the template, "Name", and "Description" to be used in the interview when showing a summary of the discovery that the system recommends the user to select. For Interrogatorys, they should each have a Priority. There should be a method for the InterrogatoryList class that displays only the 30 highest priority interrogatories to comply with discovery limits. In the interview, I'd like to pre-define the 85 discovery requests with the name and description (I think as a source file?). I'll also have a list that links each discovery request to a true/false interview variable. There can be a many-to-many relationship between the claims and the discovery request that's relevant to the claim. I'm building the table with two columns right now in Google Sheets, but my plan was to convert it to a format usable in DocAssemble. The example on the website for a custom object doesn't define any properties, only the methods. I looked at the classes you've already defined in /docassemble_base/docassemble/base/util.py and it looks like again, mostly it's just the methods you've defined. I only have a thought for one method so far. Is there any real benefit for me to define a new class for this example use? Would it make more sense to just use the built-in DAObject and specify the properties as I go along? Quinten Steenhuis Senior Attorney Network Administrator Greater Boston Legal Services 197 Friend St Boston, MA 02114 (617) 603-1553 F: (617) 371-1222 Qsteenhuis@GBLS.org