Now that you’ve learned the key product areas to audit when inheriting an established instance, the next step is to create/update documentation on your instance configuration and tech stack. Whether creating it via spreadsheet or a project management application, your documentation will be a great resource to track progress and record details, as well as keep your instance structured and sustainable.

Data

Area	Review Focus
Input	Which systems feed data into Marketo Engage? Are they loading data into programs or the database? If programs, which ones? Action Item: Create a data dictionary/field mapping table between systems.
Output	Which systems receive data from Marketo Engage?

Documentation

Area	Review Focus
Data Dictionary	Is there a separate data dictionary explaining the fields available? If not, consider creating one in a folder accessible to your Marketing Operations team.
Organization	Do you have robust documentation of how your Marketo Engage instance is organized and why? Action Item: Create documentation that contains folder structure, naming convention, and channels used in your instance.
Changelog	Do you have a changelog where you can document what's changing in your instance and why? Action Item: Create a changelog and document changes made to your instance configuration.
Playbooks	Does your organization have a User or Admin Playbook? If so, update those accordingly.
Conversations with Internal Stakeholders	What are the internal expectations of your company's Marketing team? Do they match what Marketo Engage is delivering? Which teams are stakeholders in your Marketo Engage instance? Action Item: Document the goals and expectations of your key stakeholders and update them as you check in with your counterparts throughout the year.