hi @juliaweist, just picking our conversation from March 10. You mentioned its better to use only one or the other procedure for Condition (e.g. remove the condition page from procedures and only use the condition screen within Object screen or vice versa). We are in the process of tidying up the screens on Providence and working out what is best for our workflow and have come across this issue again for audit, valuation, conservation - they all appear as individual fields within Object > Condition and Object > Valuation, but they are also under New > Procedure > Audit for example. You said several of your museum users take the standalone approach. I feel the inputting from the procedures menu makes sense, especially from a reporting/display point of view, but can't get my head around why it would be useful to use it within the object editor when the containers become so complex and require more playing around with templating when it comes to pulling up a report. Do you have any examples of users using the other approach e.g. condition/audit/valuation functions within the object editor, and how the condition boxes look? All of the data inputed into condition, conservation, audit & valuation will be entered multiple times over the years for an individual object so feel like this gets messy/hard to navigate within the individual object page. Same goes with artwork movements, but I understand this is still a work in progress for the CA team?