Unit 10: Printing Project Reports

I. Orientation — Reporting and Printing in Project Management

Printing project reports is the process of converting current project information into a structured, readable output for paper, PDF, or another print destination. In project-management software such as Microsoft Project, the printed result depends on the active project data, selected report or view, date range, page settings, and printer configuration. Print Preview is used to inspect and adjust that result, while the Project Summary report presents high-level indicators of project scope, schedule, work, and cost.

• Governing principle: A project report should communicate the information required by its audience without unnecessary detail.
  • Senior management generally needs summary dates, total cost, total work, and completion status.
  • Project managers may need schedule variance, cost variance, and progress indicators.
  • Team members usually need detailed tasks, assignments, deadlines, or workload information.
• Data dependency: Reports are generated from the values stored or calculated in the project file.
  • An incorrect task duration, missing resource rate, or outdated status date can make the printed report misleading.
  • Recalculation and progress updating should therefore occur before printing.
• Snapshot convention: A printed report represents the project at a particular moment.
  • Values can change when tasks are updated, resources are reassigned, or the schedule is recalculated.
  • The print date and reporting period help readers interpret the snapshot correctly.
• Presentation convention: Page size, orientation, margins, scaling, headers, footers, and legends affect readability but do not change the underlying project data.
• Output distinction:
  1. Print Preview shows how the selected view or report is expected to appear on pages.
  2. Project Summary Report selects and organizes important whole-project information for managerial review.
• Quality objective: A suitable report must be accurate, relevant, legible, traceable to the current plan, and economical in its use of pages.
• Typical workflow:
  1. Update and validate the project plan.
  2. Open the required view or report.
  3. Define the relevant date range and visible information.
  4. inspect the output in Print Preview.
  5. Adjust page settings and verify totals.
  6. Print or export the final report.

II. Print Preview — Inspecting the Output Before Printing

Print Preview is a pre-print inspection facility that displays the expected page layout of the active project view or report. Its purpose is to detect problems such as clipped columns, unreadable scaling, excessive blank space, unsuitable page breaks, or missing page information before paper or a PDF file is produced.

A. Using Print Preview

Using Print Preview allows the user to verify both the content and physical arrangement of a project report before issuing it.

• Opening the preview: In Microsoft Project, the preview is normally reached through the File tab and the Print command.
  • The active view, table, timeline, calendar, or report influences what appears.
  • Selecting the correct view before opening Print Preview prevents irrelevant information from being printed.
• Page inspection: The preview should be checked page by page rather than judged only from the first page.
  • Page 1 may contain task names and dates correctly while later pages contain split tables or isolated chart sections.
  • Navigation controls allow movement through multi-page output.
• Zoom control: Zoom changes the on-screen preview magnification, not the actual printed scale.
  • A zoomed-out display helps assess the overall page balance.
  • A zoomed-in display helps inspect small text, gridlines, dates, and truncated field values.
• Printer selection: The selected printer determines available paper sizes, printable area, colour capability, and duplex options.
  • A report designed for A3 paper may not fit when the destination is changed to A4.
  • A PDF printer can preserve the report electronically while retaining the chosen page layout.
• Page orientation:
  1. Portrait: Better for narrow tables containing fields such as Task Name, Duration, Start, and Finish.
  2. Landscape: Better for wide Gantt charts, time-phased tables, and reports containing many columns.
• Paper size: The paper setting must match the intended output medium, such as A4, Letter, or A3.
  • A larger sheet can improve chart readability.
  • Standard office paper may be more convenient for distribution and filing.
• Margins: Margins define the unused space around the report body.
  • Narrower margins create more room for tables and charts.
  • Margins must still leave space for headers, footers, binding, and the printer’s non-printable area.
• Scaling: Scaling controls how project content is distributed across printed pages.
  • A percentage setting reduces or enlarges the output proportionally.
  • A fit-to-pages setting can constrain output to a specified number of pages wide or tall.
  • Compressing a large Gantt chart onto one page may technically fit but make task names and dates unreadable.
• Page range: Users can print all pages or a selected range, such as pages 2–4.
  • A restricted range is useful when only one section needs replacement.
  • The preview page count should be verified before entering the range.
• Date range: Time-based views may allow only a specified interval to be printed.
  • Printing from 1 April to 30 June, for example, removes irrelevant earlier and later periods.
  • The chosen range should still include milestones and deadlines needed by the audience.
• Headers and footers: Repeated page information identifies and controls the document.
  • Useful fields include project title, company name, status date, print date, page number, and confidentiality marking.
  • A page-number format such as Page 2 of 6 helps detect missing sheets.
• Legend handling: Gantt chart output may include a legend explaining bar styles and symbols.
  • The legend is valuable when readers do not regularly use the scheduling software.
  • It may be omitted when it consumes excessive space and the symbols are already understood.
• Content validation: Visual correctness does not guarantee data correctness.
  • Confirm that task filters, hidden columns, grouping, outline levels, and selected tables match the reporting purpose.
  • Check that summary tasks, milestones, deadlines, and critical tasks appear where required.
• Worked example: A Gantt Chart preview occupies six pages horizontally because the timescale covers the entire project year.
  • Set the print date range to the current quarter.
  • Change the orientation from portrait to landscape.
  • Remove nonessential columns and use moderate scaling.
  • Recheck that task names, milestone dates, and Gantt bars remain readable before printing.

B. Applications and Limitations

Print Preview improves output control, but its value depends on careful inspection and suitable report design.

• Waste reduction: Previewing prevents repeated printing caused by incorrect orientation, blank pages, or clipped information.
• Professional presentation: Consistent headers, page numbers, margins, and scaling make reports easier to distribute and archive.
• Layout diagnosis: Unexpected page counts often reveal an overly wide table, an excessive date range, or unused columns.
• Device variation: Output can change when another printer driver, paper size, font, or PDF renderer is selected.
• Readability limitation: Fitting more information onto fewer pages reduces text and chart size; page economy must not override comprehension.
• Interactivity limitation: A printed page cannot provide live filtering, drill-down, recalculation, hyperlinks, or expandable task outlines.
• Currency limitation: Preview reflects current saved or calculated data, but the printed copy becomes outdated as soon as the plan changes.

III. Project Summary Report — Presenting Whole-Project Status

The Project Summary report provides a consolidated view of major project indicators rather than task-by-task detail. It supports rapid assessment of whether the project is progressing within its planned scope, schedule, work, and cost constraints.

A. Using The Project Summary Report

Using The Project Summary Report enables managers and stakeholders to examine headline project values in a compact, printable form.

• Report access: In Microsoft Project, summary information is commonly available through the Report tab and project overview reports; exact report names and locations depend on the software version.
• Project identity: The report should clearly display the project name and relevant reporting date.
  • Without these identifiers, printed reports from multiple projects or periods can be confused.
• Schedule indicators: Typical summary values include project start, current finish, duration, and percentage complete.
  • The finish date is generally calculated from task relationships, calendars, constraints, and resource scheduling.
  • A delayed critical task can move the project finish even when many noncritical tasks are complete.
• Work indicators: Work represents scheduled effort, commonly measured in hours or days.
  • For a basic fixed assignment, work is related to duration and assignment units:
    
    TEXT

    Work = Duration × Assignment Units

  • Work is total resource effort, Duration is scheduled working time, and Assignment Units is the assigned resource capacity, such as 100% for one full-time resource.
• Cost indicators: Summary cost may include resource charges, fixed costs, and other values recorded in the plan.
  • A task with 20 hours of work at ₹500 per hour contributes ₹10,000 before other fixed or usage costs.
  • Missing resource rates cause reported costs to be incomplete.
• Baseline comparison: When a baseline has been saved, current performance can be compared with the approved plan.
  
  TEXT

  Schedule Variance = Current Finish − Baseline Finish
  Cost Variance = Current Cost − Baseline Cost

  • A positive schedule variance indicates lateness when dates are interpreted as elapsed time beyond the baseline.
  • A positive cost variance in this form indicates that current cost exceeds baseline cost.
• Progress interpretation: Percentage complete must be read with schedule and cost information.
  • 70% complete does not by itself prove that the project is on time or within budget.
  • High completion on low-value tasks can conceal delays in critical or expensive work.
• Filtering and reporting period: The summary should correspond to the agreed status date and reporting cycle.
  • Weekly reports may emphasize recent movement.
  • Monthly governance reports may emphasize baseline variance, forecast finish, and total cost.
• Printing process: After generating the report, use Print Preview to inspect page count, orientation, chart labels, totals, headers, and footer dates before selecting Print.
• Worked example: A project baseline finish is 30 September, while the current calculated finish is 8 October.
  • The schedule variance is eight calendar days under the stated subtraction convention.
  • If current cost is ₹540,000 against a baseline cost of ₹500,000, cost variance is ₹40,000.
  • The summary therefore communicates both schedule delay and projected overspending.

B. Applications and Limitations

The Project Summary report is most effective as a decision-oriented overview supported by detailed reports when investigation is required.

• Management use: It gives sponsors a compact picture of completion, forecast finish, total work, and total cost.
• Meeting use: It provides a consistent evidence base for status meetings, stage reviews, and approval discussions.
• Comparison use: Periodic copies show movement in finish date, completion, work, and cost across reporting dates.
• Aggregation limitation: Project totals can hide individual late tasks, overallocated resources, and local cost overruns.
• Baseline limitation: Variance values are meaningful only when a valid baseline was saved and maintained under change-control procedures.
• Data-quality limitation: Incomplete actual work, outdated task progress, missing rates, or incorrect calendars produce unreliable summary values.
• Interpretation requirement: Significant variances should be investigated through detailed task, resource, cost, and critical-path views before corrective action is approved.