ITIL Reporting Pitfalls Part 3: (Snap)Shots in the Dark

About this Resource

The first paper in this series focused on an issue that purely resided in the reporting area. The second paper looked at a problem that is as much a process issue as it is reporting. In this, the third and final part of the series, we look at the flaws of Snapshot Reporting; why they are not auditable, recreateable and are capable of potentially undermining the entire ITIL framework.

Snapshot Reporting: A Short Definition

A Snapshot Report is a type/style of report that is used to capture data as it is at the single point in time when the report was refreshed and tends to rely on the values in status fields as opposed to defined date ranges.

Reading that description may make Snapshots sound harmless enough, but misusing them can lead to a range of pitfalls as the reporting suite grows and evolves.

This often means that organizations do not realize there is a very real risk until the flawed solution is already entrenched. By this time a suite of Snapshot Reports can have expanded, building one pitfall on top of another…

Login to continue reading about ITIL Reporting pitfalls.

Already a Member? Sign in here

Related Resources

ITIL Reporting Pitfalls Part 3: (Snap)Shots in the Dark
  • Register to Download

  • The email address is already in use, please login
  • Checking your email address . . .

  • Please add your Job Title

  • Please add your Industry

  • Please add an Interest

  • Please add your Country

  • * Minimum 6 characters long, including lower and uppercase letters, a number and symbol (!/=+_-@ )

  • Please complete missing fields
  • Passwords need to be minimum 6 characters long, including lower and uppercase letters, a number and symbol.

DEMO Search