1. [Project Name] project - Business Case Summary
[Note: Hints & Tips are provided through out this template & are shown in blue italic. Please delete these when you no longer require them, and in advance of submitting for approval consideration.]
Project ID : [Project ID Number – as provided by PMO]
Short Name: [Project Name]
Department/ School/ Faculty: [Department / School / Faculty Name]
Dean/ Chief Officer approver: [Name & Title of approver]
Project Sponsor: [Sponsor Name / Role in TCD]
EOG Champion: [EOG Champion Name / role in TCD]
Project Manager: [Name, role in TCD ]
Project Type/ Category: [Operational/ Change Management/ Legislative/ External/ New Build /Refurbishment /IT / Audio Visual / Infrastructure]
Total Estimated Operational Costs: [€€€ - over X years]
Level of Funding Secured: [€€€ - total of funding secured as per Financial Plan or Funding Model]
Total Project Cost: [€€€ –total project estimated cost including as per Financial Plan]
Approved Project Spend: [€€€ Total Project Spend Approved to date]
Seeking approval to spend: [€xxx – to get to Stage [?]
Document Version [e.g V0.1 must match filename]
Issued Date: [ DD/MM/YY]
Prior sign off, Review and Information Prior to submission into the approval & prioritisation process, key stakeholders in other business areas directly involved in delivery of this proposal or on whom the project is dependent, should review or approve this submission primarily from the perspective of their relevant business area / project role.
[Note: Please review the table below & complete / update / delete key stakeholder details, as appropriate for your project]
Key stakeholder/Dependency area
Role
Action
Review Date
Finance Rep / Contact name
Verify Financial plan and Funding details
Approve
 DD/MM/YY
ISS Rep / Contact name
Verify IS costs
E & F Rep / Contact name
Verify E & F costs
Disability Services Rep / Contact name
HR Partner / Contact name
Review
Space Allocation

2. [Project Name] Background & Objectives
Background / Problem to be resolved
Project Objectives / Purpose
[Note: provide a brief outline of the background of why the project is being considered, the severity of the problem the project has been set up to solve, and other information that will support the readers understanding of the requirement and its priority.]
The background to this project is…..
[Note: What is this project trying to achieve? Provide a brief overview of project objectives/ purpose including information on timeline for delivery, quality to be met, risk and benefit performance goals, and the impact of the project in the medium term (5-15 years).
The objectives / purpose of the project should be consistent with the TCD strategy/business plans. The project objectives should be Specific, Measurable, Achievable, Realistic and Time-constrained (SMART).]
The Project Objectives /Purpose are

3. [Project Name] Alignment to TCD Strategic Plan
TCD Strategy.
List specific areas where this proposal aligns with the TCD strategy
CSFs and KPIs necessary for this proposal to be successful
[Note: This slide should clearly show the alignment of project proposal against College strategy. See the Business case template document for further information.
In this Column, extract and list the sections from the TCD strategy that this proposal aligns to. The current TCD Strategy can be found on the TCD website here
For example A2.3 Student Services, Tutorship and Registry of the TCD strategy states—“further develop appropriate IT platforms for
on-line delivery of relevant student services”
TCD Strategy Item A
TCD Strategy Item B
[Note: State how this proposal meets the specific TCD Strategy sections listed in the first column. Be as specific and detailed as required to prove the alignment]
TCD strategy item A alignment is as follows:-
Xxx
TCD strategy item B alignment is as follows:-
[Note: CSF:- Things which must go well in order that the specific TCD Strategy and this proposal are aligned successfully. Think of specific TCD roles, departments, services and day to day activities that must be involved. Use action verbs only.
KPI: Something that measures TCD progress towards the proposals Success Factors and TCD Strategic objective
For example, for the strategy example given in the first column, sample CSF and KPIs might be
“CSF:- x, y, z staff hired for the opening Trinity Academic Medical Centre and completed by dd/mm/yyyy aligned Vs the target number.
KPI: Number of candidates presented by the hiring system per month.” ]
Aligned CSFs are as follows:-
xxx
Aligned KPIs are as follows:-

4. [Project Name] Project Scope
Key areas In-Scope
Key areas Out-of-Scope
[Note: List the key areas that are in the scope of the project delivery.]
Xxx
[Note: List the key areas that are outside of the scope of the project delivery.]
xxx
Interfaces / Key Communications (to internal / external people / business areas, processes, external organisations, technology)
[Note: Provide details of the key interfaces that the project will have with
people
processes
technology
internal TCD business areas / departments or
external organisations.]
The following key interfaces have been identified:-
xxx xx

5. [Project Name] Risks, Assumptions, Issues, Dependencies
[Note: Use RAID log to assist when completing Key Risks/Issues below]
Prty No.
RAG
Status
Description
Potential Impact
Avoidance/Mitigation Action
Risk Owner
Action by
Date Closed
R01
00002
Open
Planning permission will not be granted
Project will not meet delivery date
ensure contingency in schedule for planning
Project Manager 
A01
Assumption ROI will be met in agreed timeframe
College loan will not be paid back in agreed time
Monitor ROI forecast during project & post project
Sponsor
D01
Dependency on internal completion of Project Z prior to delivery
Impact on capital projects portfolio
Monitor delivery/project schedule of project Z to ensure it does not delay impact on approved schedule
PMO/Sponsor
[Risk ID as per RAID log ]
[Provide the RAG status of the risk]
[Provide a brief description of the key risk as identified in RAID log]
[State the recommended mitigation strategy to manage the risk]
[Provide owner as per RAID log]
Resolution date
actual date closed
[assumption ID as per RAID log]
[Provide the RAG status]
[Provide a brief description of the assumption identified in RAID log]
[State the recommended mitigation strategy to manage the assumption]
[Provide owner as per RAID log]
[Issue ID as per RAID log ]
[Provide the RAG status of the issue]
[Provide a brief description of the key issue as identified in RAID log]
[State the recommended mitigation strategy to manage the issue]
[Dependency ID as per RAID log ]
[State the recommended mitigation strategy to manage the dependency]

6. [Project Name] Options
Option 1 – xxx
Option 2 – xxx
[Note:Include brief Summary of Option 1]
Xxx
xxx
Pros:
[Note: List the advantages linked to implementation of Option 1]
Advantage 1
Advantage 2
Advantage 3
Cons:
[Note: List the disadvantages linked to implementation of Option 1]
Disadvantage 1
Disadvantage 2
Disadvantage 3
[Note: Include brief Summary of Option 2]
[Note: List the advantages linked to implementation of Option 2]
[Note: List the disadvantages linked to implementation of Option 2]
[Note: This slide should outline the potential solution options considered.]

7. [Project Name] Options
Option 3 – xxx
Option 4 - xxx
[Note:Include brief Summary of Option 3]
Xxx
xxx
Pros:
[Note: List the advantages linked to implementation of Option 3]
Advantage 1
Advantage 2
Advantage 3
Cons:
[Note: List the disadvantages linked to implementation of Option 3]
Disadvantage 1
Disadvantage 2
Disadvantage 3
[Note: Include brief Summary of Option 4]
[Note: List the advantages linked to implementation of Option 4]
[Note: List the disadvantages linked to implementation of Option 4]
[Note: This slide should outline the potential solution options considered.]

8. [Project Name] Recommendation
Recommendation - Go with Option 2
[Note: Provide clear recommendations on the preferred option and why it is being recommended. Include high-level details on the likely organisational impact, the fit with current TCD strategic plans & initiatives, and any technical considerations]
The recommendation is to select Option X, because xxx
Benefits (Quantifiable & Non-Quantifiable)
[Note: Summarise the estimated benefits (quantifiable and non-quantifiable) for resources, technology, etc, for the proposed option.
Examples of non-quantifiable benefits include drive the plan to increase Outreach activities or enhance College’s reputation, visibility and connectivity (national and international).
Not all projects will have quantifiable benefits. Quantifiable benefits can be measured as either € savings or € increased revenue. Examples of quantifiable benefits include an increase in students (income to College of €€€€to €€€€ over X years); resource savings of XXX, increased revenue in College catering outlets, reduce risks associated with current environment.
Non-quantifiable Benefits will include:
XXXX
Quantifiable Benefits will include:
XXX
REPLACE WITH APPROPRIATE INFO
[Note: Take info from Financial Model / Business Case – whatever is most relevant]

9. [Project Name] Benefits/Funding Model
Note: Example of Benefits Model include best case and worst case scenarios/ Increases in student/researcher numbers which result in worst and best case income generation.
Please insert key Benefits/Funding Model info as agreed with FSD/ Finance Partner.
REPLACE WITH APPROPRIATE INFO
Notes on Finanicals/Benefits:
CRG require confirmation that funding and approval to proceed (by Dean/Chief Officer) is in place before approval is sought via Governance/CRG.
Fund Raising/ Payback/ROI details to be provided.

10. [Project Name] Project Cost Estimates (summary)
[Note: Include Summary Details from Project Financial Plan; additional information may also be included (graphs, numbers)]
REPLACE WITH APPROPRIATE INFO

11. [Project Name]– On-going Operational Costs
[Note: Include On-going Costs Details from Project Financial Plan]
REPLACE WITH APPROPRIATE INFO

12. [Project Name] Resources & Milestones
Key Resources Required
[Note: Outline the key resource skills & level of experience required to deliver the project, providing an indication of the likely grade of resource within TCD who would normally be expected to have the skills / experience, or whether an external resource is likely to be required / is proposed. ]
Below is a list of the key resources currently identified as being required to support the success of the programme delivery:-
Resource A (Grade x) is required as they have xxx skills required to complete deliverable X1 for this project.
Resource B (Grade y) is required as they have xxx skills required to complete deliverable X2 for this project.
[Note: The content below is provided as an example of what might be included. Update the content below by adding / updating / removing, as appropriate for the specific project. ]
Key Stages/ Milestones / Deliverables
Target Start
Target End
Approval & Prioritisation – Full Business Case submitted for approval
dd/mm/yy
Approval & Prioritisation – Project Approved by EOG
Initiation & Strategic Planning - xxxx
01/06/14
Detailed Planning & High level Design– xxxx
Detailed Design– All required design documents created and approved by Steering
Stage Gate Approval – All confirmed costs & timeline for project delivery approved by CRG
Execution – Configuration, templates, content & other development deliverables completed
Testing – system available for TCD internal access / testing (non-project)
Handover & Implementation– Project Delivery Date
Closeout - xxxxx
REPLACE WITH APPROPRIATE INFO

13. [Project Name] Proposed Steering Committee
Role on Committee & any specific responsibilities
Title
[Chair Name]
[Sponsor Name]
[PM Name]
[Steering Member 2]
[Steering Member 3]
[Steering Member …]
Chair
Project Sponsor
Project Manager
Finance representative
E & F representative, if appropriate
ISS representative, if appropriate
Xxx representative
xxx
Xxx
Project Steering Committees are required for all projects with a budget of €500k or more. If the project budget is less than €500k, CRG may request, during the approval and prioritisation process, a programme or project to form a Steering Committee if CRG believe the project requires one due to the level of risk.

14. Appendices – Additional / Supporting information
Project Risk Indicator (PRI)
Include Relevant Additional Project Financial information(e.g. from Financial Plan)
[Include other additional information / detail that might support your proposal]

15. A. Project Risk Indicator (PRI) – to be completed
Very Low (1)
Low (2)
Medium (3)
High (4)
Very High (5)
Score
Team size
<3
3-7
8-12
12-17
>17
# of cross functional areas involved 1
2-5
6-9
10-12
>13
Estimated Duration (Elapsed Months)
< 4
4-11
12-18
19-24
>24
Technology and / or Business Process – Known or New
In house expertise
Very Familiar
Somewhat Familiar
New to TCD
New to industry/ Leading edge
Complexity of solution
Well defined. No problems expected
Known. Some minor problems expected
Known but some medium / major problems expected
More than 1 approach available
Solution unknown or vaguely defined
Dependency on external suppliers / organisations
long standing
Reasonable relationship
Used before, but not regularly
Used before, but not recently
No previous relationship
Risk to Reputation
Reputational risk Unlikely to happen, Negligible impact
Reputational risks occasionally occur, Minor impact to reputation
Reputational risks are likely as not to occur, Notable impact to reputation
Reputational risks are likely to occur, Substantial impact to reputation if they do
Reputational risks certain to occur, Threatens the reputation of the project or TCD
TCD Resource Impact
In house skills present and project is easily absorbed within current workload
In house skills present with some occasional impact on current workloads
In house skills present but the project will impact current workloads and require backfill
Up skilling required, resources will have to be dedicated to the project
In house and external resources dedicated to the project and from more than one department
Funding/Finance
Funding exists with current budgets
Most Funding in place or requires minor budgetary allocation
Funds not in place. Project will impact departmental budgets
Funding sources not clear, will impact TCD budgets
Funding will be difficult, funding complexity mix high and possibly not attainable
Project Scoring:
Low
Medium
High
<19
19 – 31
> 32
 The overall Project risk is therefore indicating as (Low, Medium High)

16. B. Project Financials
REPLACE WITH APPROPRIATE INFO

17. B. Project Financials
REPLACE WITH APPROPRIATE INFO