The ChronoCards ArcGIS Pro add-in logs metadata about activity within ArcGIS Pro and sends it to the ChronoCards dashboard. The add-in runs in the background and does not interfere with your work.

For the cloud-hosted version, you only need to install the ChronoCards add-in within ArcGIS Pro. This usually does not require you to have admin access to your computer. If using Portal for authentication, you will also need to create a "developer credentials" item in your Portal.

Most teams using the cloud-based application can be onboarded in about 5 minutes! All you have to do is install the add-in, login with ArcGIS Online or Portal, and you’re ready to go!

The ChronoCards add-in for ArcGIS Pro uses your stored credentials within Pro (either ArcGIS Online or Portal) to authenticate with the ChronoCards server. You use this same AGOL or Portal account to login to the ChronoCards dashboard.
If using Portal, your Portal must be accessible by the ChronoCards server. We can provide a single IP for whitelisting if needed.

After an introductory call, if needed, we can run a 1-2 week technical fit trial with your team to ensure that ChronoCards works as expected with your systems and processes.

No. We log actions taken in Pro as they happen, but do not prevent anything from running within Pro and only send events in a non-blocking manner.

Yes. When the ChronoCards add-in is installed in ArcGIS Pro, by default it will log all activity. You can temporarily or permanently disable this by going to the add-in in the top ribbon in Pro or by going to the add-in’s settings page.

The cloud-based version of ChronoCards requires a stable internet connection to run properly and communicate with the ChronoCards server. The on-prem version can run without making any external network requests and thus can work without internet.

Check the docs for an updated list of events we catch.

Here are some examples of how custom tools look in the logs.

Yes, ChronoCards is fully compatible with Utility Network.

Yes, version information is saved alongside relevant items in your log.

The fastest way to get support is to submit a ticket from within the ChronoCards web app. We aim to respond to each ticket in less than 48 hours, and typically respond within an hour on the same business day. We are also available for phone and/or videocall support during Mountain Time business hours by appointment.

Check the versions release page for an updated list of supported ArcGIS Pro versions. We typically stay up to date with the latest released version.

The ChronoCards web application is updated roughly once per month, and the ChronoCards add-in for ArcGIS Pro is updated roughly once per quarter.

By design, in our cloud-based platform does not replicate or store any of your GIS data-- we log metadata about actions taken involving that data. For example, if you edit a feature class in SDE we log the name of the feature class and the object ID of the feature edited. We store the names and paths to layers, APRX files, geoprocessing tools, etc but none of the actual data is ever sent to us at any time. We do not share any data we collect with anyone.

ChronoCards is primarily a cloud-based application, but we offer an on-prem version for larger organizations. If you think you’d need an on-prem installation, get in touch and we can go through the options. Typically this is only needed if you have data storage or security concerns, or if the ChronoCards server will not be able to access your Portal instance due to IT security controls.

The ChronoCards cloud platform is hosted on Azure and all data resides within the United States.

Yes. As long as you are able to load the add-in into ArcGIS Pro and login with your Portal/AGOL account, ChronoCards should function as normal.

ChronoCards is licensed annually via a named users from your organization's Portal or ArcGIS Online account. You can link a subset of your Portal/AGOL users to ChronoCards, or your entire organization, but all users must use the same method of authentication (Portal or AGOL).

ChronoCards can link ArcGIS Pro activity to the specific person and their exact Pro session. It is much more granular, GIS-specific, and analyst-focused than Monitor (which focuses more on the infrastructure).

ChronoCards is always logging in the background (unless disabled), so you don't need to explicitly record a task or set time aside to document. ChronoCards logs the work that you might not think is important at the time, but ends up being impossible to recreate later if you don't have a log to rely on. If you know you have a discrete task that you're going to replicate 1,000 times, Tasks or Workflow Manager could be a good fit. If you want to work as you normally do, ChronoCards will automatically document your work in the background without imposing any extra work on you.