Professional Documents
Culture Documents
[SYSTEM/APPLICATION NAME]
Single Report
Design
Specification
SYSTEM/APPLICATION NAME REPORT DESIGN SPECIFICATION
A Report Design Specification is a required deliverable for all business intelligence and
management information reports.
Template This Report Design Specification template includes data input fields that support internal
Flexibility controls and processes, policies and risk mitigation principles, governance drivers, and/or
project management control standards and proven best practices. It provides the
minimum basic fields required to successfully complete a Report Design Specification
document deliverable in meeting PMO requirements for all system development projects
requiring reporting. The amount of detail included in the template will depend on the size,
complexity and type of project, as well as the kinds of systems involved and information
required.
The project development leads/teams are empowered to utilize this template as necessary
to best serve the needs of the project and business owner. Each data input field provided
in this template should be considered for applicability and relevance to the project at hand.
Multiple Report Design Specification documents may need to be created for the entire
library of reports.
Template 1. This Template Guidelines section is for reference purposes only. It should be printed
Completion and deleted prior to completing the final document.
2. To input text within a text field (), place the cursor inside the field and just start
typing.
3. Enter the required information on the Title Page and add additional fields as needed.
4. Complete the document utilizing suggested text where applicable and entering
text/fields where shown within <blue text> brackets. Note that the blue text is NOT to
be included in your final document. Its purpose is to either provide guidance for
SYSTEM/APPLICATION NAME REPORT DESIGN SPECIFICATION
VERSION HISTORY
Version # Date Revised By Reason for change
1.0 9/17/09 Aaron Demenge PMO Review
DOCUMENT APPROVALS
Approver Name Project Role Signature/Electronic Approval Date
SYSTEM/APPLICATION NAME REPORT DESIGN SPECIFICATION
TABLE OF CONTENTS
1.0 Overview...........................................................................................................................1
1.1 What business question will this report answer?.....................................................................................1
1.2 Who are the report users?....................................................................................................................... 1
1.3 What are the key parameters or business rules?.....................................................................................1
1.4 What is the report layout?........................................................................................................................ 1
6.0 Appendix............................................................................................................................4
SYSTEM /APPLICATION NAME REPORT DESIGN SPECIFICATION
1.0 OVERVIEW
Provide an overview of the requested report. Include examples of existing reports if appropriate.
2.2 Metrics
2012 Regents of the University of Minnesota. All rights reserved. Revised August 22, 2017 Page 1
SYSTEM /APPLICATION NAME REPORT DESIGN SPECIFICATION
Time
Net Plan
Net Actual
Variance
Details
Sequence
SKU Style
Description
Prices MSRP
List Price
Sale Price
2.3 Totals
<Define any totals calculations to be displayed.>
2.4 Drill-Downs
<Define any drill-down linkages to be displayed.>
Define the single overarching business question the report is suppose to answer
Gather examples or create mock ups of expected report information
Ensure ETL designs document are in the overall project Technical Specification Design document
Validate metric definitions
Document universe of related reports to view individual reports/requests in context
Create the report specific design document
Review and get business user sign off
2012 Regents of the University of Minnesota. All rights reserved. Revised August 22, 2017 Page 2
SYSTEM /APPLICATION NAME REPORT DESIGN SPECIFICATION
6.0 APPENDIX
Existing Reports Examples or Mock-ups
2012 Regents of the University of Minnesota. All rights reserved. Revised August 22, 2017 Page 3