Creating a Project Charter

The quickest way to create project charters: [after creating 25+ charters in the last 3 years] I view the project initiation as a compass, not just a formality. Then, I begin with the end in mind. This method: -Aligns stakeholders -Sets clear objectives -Maps out project boundaries -Identifies potential risks -Establishes authority and accountability Here's each step of my charter creation: 1. Objective Define the core purpose: -Why is this project essential? -What business problem does it address? -Articulate the expected outcome: -Desired end state after project completion -Key performance indicators to measure 2. Scope Detail out project boundaries: -Inclusions: What's part of the project? -Exclusions: What's out of scope? Establish the deliverables: -Tangible outputs -Milestones to reach -Stakeholders Identify key players: -Who will benefit from this project? -Who has influence over its outcome? 3. Outline roles and responsibilities: -Who’s doing what? -Who holds which authority? 4. Risks & Assumptions Highlight potential pitfalls: -What might derail the project? -Assumptions made and their validation Plan for contingencies: -Risk mitigation strategies -Backup plans 5. Resources Allocate essentials: -Budgetary constraints -Required tools and technology -Team members and their skillsets 6. Timeline Breakdown of project lifecycle: -Start and end dates -Major phase completion dates -Dependencies between tasks 7. Communication Define the communication plan: -Who gets updated and when? -Preferred communication channels 8. Approval Establish authority: -Who signs off on project decisions? -Acceptance criteria for deliverables Outline the revision process: -Feedback loop -Change request protocol 9. Documentation & Archiving Detail out the documentation process: -Where are project files stored? -How to access historical data Establish a post-project review plan: -Lessons learned -Feedback collection -Continuous improvement Follow this charter framework to kick-start your projects with clarity and purpose. What are your project charter best practices?  Leave a reply in the comment section.

Most failed projects never lacked a plan — they lacked agreement. A project charter isn’t paperwork. It’s the invisible contract that aligns every stakeholder before chaos starts. It defines: - Why this project exists (purpose) - Who owns what (accountability) - How success will be measured (outcomes) I’ve seen teams skip this step because “we need to start fast. ” They end up starting twice — once to build, once to fix. But too often, teams skip this step because “ we need to start fast. ” The truth? They end up starting twice — once to build, once to fix. If you want to lead with clarity, start with alignment. Your first deliverable isn’t the Gantt chart — it’s shared understanding. Here are 3 ways to make your project charter actually work: ✅ 1. Make it outcome-driven, not output-driven. Most charters focus on what will be delivered — timelines, budgets, tasks. Shift to why it matters. Define the problem it solves and what success looks like in behavior or adoption. - Instead of “Deliver new CRM,” say “Increase user adoption by 25% within 3 months.” ✅ 2. Co-create, don’t delegate. A charter written for stakeholders dies fast. A charter written with stakeholders lives. Run a short alignment session before writing — get your sponsor, users, and leads to co-own the “why” and the “how.” - The goal: fewer sign-offs, more buy-in. ✅ 3. Keep it human-readable. If people can’t skim it, they won’t follow it. Use one page, plain language, and visuals (timeline, ownership chart, success metrics). A charter is not a report — it’s a roadmap for humans. - Ask yourself: “Could my team summarize this in 30 seconds?” If not, simplify. Because in the end — a good charter isn’t about process. It’s about clarity, ownership, and trust. 📈 Start with alignment. Delivery gets easier from there. #ProjectManagement #WGU #PMP #Leadership #ProjectCharter #Delivery

Ensuring Compliance in Greenfield Projects: A Must-Know Checklist from BOCW Act, 1996 As HR professionals, especially those managing large-scale greenfield projects, it’s crucial to be well-versed with the Building and Other Construction Workers (Regulation of Employment and Conditions of Service) Act, 1996 (BOCW Act). This Act is not just a legal requirement but a commitment to the safety, health, and welfare of construction workers. Here’s a quick compliance checklist to ensure you’re on the right track: 1. Applicability: Covers any construction with a cost over Rs.10 lakhs and employing 10+ workers. 2. Key Registrations: • Establishment must be registered within 60 days (Sec.7) • Building workers must be registered as beneficiaries (Sec.12) 3. Worker Welfare Provisions: • Accommodation to be provided free of cost near the site (Sec.34) • Clean drinking water must be marked and available (Sec.32) • Crèche facilities where 50+ female workers are employed (Sec.35) • Canteen mandatory for sites with 250+ workers (Sec.37) 4. Working Conditions: • Max. 48 hours/week, 9 hours/day with intervals (Sec.28) • Overtime to be paid at twice the regular wage (Sec.29) 5. Safety & Reporting: • Appoint safety officers and set up committees (Sec.38) • Report serious accidents within 4 hours (Sec.39) • Intimate commencement of work 30 days in advance (Sec.46 Rule 249) 6. Maintenance of Records: Wage registers, muster rolls, service certificates, and more to be maintained and submitted annually (Sec.30). 7. Penalties: Non-compliance can attract imprisonment up to 2 years with fines (Sec.47-49). Let’s ensure we build with compliance and care – respecting not only timelines but the people who make the projects possible. #HRCompliance #GreenfieldProjects #ConstructionWelfare #BOCWAct1996 #HRLeadership #StatutoryCompliance #WorkplaceSafety #LabourLaw #HRBestPractices #EmployeeWelfare

GOING BACK TO THE BASICS: INTERNAL AUDIT CHARTER!! 👉Formal policy document that highlights the internal audit function’s mandate, organizational position, reporting relationships, scope of work, and types of services offered by internal audit (IIA). 👉 Prepared by the Chief Audit Executive and Approved by the Board. 👉Applicable standard: Standard 6.2 of the Global Internal Audit Standards. 👉At a minimum must highlight: ✅ Purpose of Internal Auditing. ✅Commitment to adhering to the Global Internal Audit Standards. ✅Mandate of Internal Audit including scope and types of services to be provided by Internal Audit. ✅Organizational position of Internal Audit and reporting relationships. 👉Provides the organization a blueprint for how internal audit will operate and helps the Board to clearly signal the value it places on internal audit’s independence. (IIA) 👉Helps to ensure alignment of expectations by all parties (Board, Management and Internal Audit). 👉Helps provide Internal audit the needed authority to achieve its tasks (could range from unfettered access to records, physical properties and personnel relevant to internal audit). 👉Is NOT a secret document. Must be shared with everyone across the business to ensure appreciation and alignment.

RERA registration becomes mandatory when: • Project land exceeds 500 sq. metres • The development consists of more than 8 apartments or plots • Ongoing projects lacked Completion Certificate (CC) or Occupancy Certificate (OC) at the time of RERA implementation. The registration process is far more than a procedural filing. Before registration, developers must complete extensive legal, technical, financial, and regulatory due diligence to establish the legitimacy and viability of the project. The pre-registration framework typically includes: • Commencement Certificate (CC) • Approved layout and sanctioned plans • 30-year legal title verification and ownership validation • Encumbrance disclosures and CERSAI verification • Development agreements and consent documentation • Escrow account setup under the 70:30 RERA framework • Litigation disclosures and financial declarations The registration process is structured around multiple statutory forms: • Form A – Primary project registration application • Form B – Affidavit-cum-declaration confirming title, project timelines, escrow compliance, and legal undertakings • Form 1 – Architect certification • Form 2 – Structural Engineer certification • Form 3 – Chartered Accountant certification validating project costing and fund utilization • Form 4 – Completion certification issued upon project completion and linked with OC issuance Under MahaRERA, projects undergo a multi-level scrutiny mechanism covering: • Technical verification of approvals and sanctioned plans • Legal scrutiny of title flow and encumbrances • Financial validation of escrow structure and project costing • Administrative verification of PAN, Aadhaar, CTS, and survey details. The 70:30 escrow discipline has fundamentally changed construction finance practices across the industry. At least 70% of customer collections must be deposited into a dedicated project account and utilized strictly in proportion to construction progress. The compliance lifecycle continues even after registration through: • Quarterly Progress Report (QPR) filings • Escrow monitoring • Financial disclosures • Society formation • Conveyance execution • 5-year structural defect liability under Section 14(3) Today, most banks, NBFCs, and institutional lenders require valid RERA registration before major construction finance disbursement, project-level funding activation, retail home loan approvals, and sales-linked financing. In many ways, RERA registration has evolved into the foundational gateway for institutional capital, buyer confidence, and market credibility.

Data Governance Charter: A Blueprint for Data Management A Data Governance Charter is a foundational document that outlines the core strategy, and processes related to the exercise of control and authority over an organization's data assets. It serves as a roadmap for how data will be managed, protected, and utilized to achieve organizational goals. In essence, a Data Governance Charter is a critical document that empowers organizations to effectively manage their data as a valuable asset. Ø Key Components of a Data Governance Charter o  Purpose and Scope: Clearly defines the charter's objectives and the data assets it covers. o  Governance Structure: Establishes the data governance organization, including roles, responsibilities, and decision-making authority.  o  Data Stewardship: Defines data stewardship roles and responsibilities for data owners and custodians. o  Data Quality: Outlines standards and processes for ensuring data accuracy, completeness, and consistency.  o  Data Security: Specifies data protection measures and compliance with relevant regulations.  o  Data Retention and Disposal: Establishes guidelines for data lifecycle management. o  Metrics and Reporting: Defines key performance indicators (KPIs) to measure data governance effectiveness. Ø Benefits of a Data Governance Charter o  Improved data quality: Ensures data accuracy and reliability. o  Enhanced decision-making: Provides access to trusted data for informed decisions. o  Reduced risk: Protects sensitive data and mitigates compliance risks. o  Increased efficiency: Streamlines data management processes. o  Enhanced organizational performance: Aligns data with business objectives.

Every successful pharmaceutical product starts with a decision: is this project worth pursuing? The initiation phase is where that decision is made and in our industry this phase is critical. A poorly evaluated project at this stage can lead to costly failures down the line. So, what does a PM actually do during the initiation phase in pharma? 💼 Supporting the business case 💼 The business case outlines why a project should move forward. While it's often driven by commercial or strategic teams, the PM plays a key role in coordinating input from cross-functional SMEs and ensuring departmental alignment 📑 Coordinating feasibility assessments📑 Before committing major resources, it’s essential to assess if the project is viable. The PM ensures that feasibility assessments are completed on time and include the right experts: ❓ Do preclinical or early data support the intended mechanism of action? ❓Can the drug be developed and manufactured with current capabilities? ❓Will agencies likely support the development path? ❓Is the return on investment justifiable given the risks? All findings are documented and presented to governance bodies for informed decision-making 🙋♂️Identifying and engaging stakeholders 🙋♂️ The PM maps out key internal and external stakeholders R&D, regulatory, clinical, manufacturing, commercial, and others and starts aligning expectations early. In pharma, this may also include regulators, external experts, and even patient advocacy groups, depending on the project phase 📑 Preparing the project charter 📑 Once the project receives a green light, the PM develops the project charter that authorizes the project and sets its foundation. This outlines: ❗ Project objectives and high-level scope ❗ Key deliverables and success criteria ❗ Timeline and major milestones ❗ Budget estimates ❗ Roles and responsibilities of the core team ❗ Project sponsor or governance body The Charter becomes a reference for alignment, governance, and accountability. Why Initiation phase matters ❓ In pharmaceutical development, a well-executed initiation phase builds the foundation for everything that follows. It ensures that strategic, technical, and operational aspects are considered before moving into detailed planning and execution. Taking the time to do this right can reduce risks and significantly increase the chance of delivering a safe, effective, and commercially viable drug.

𝐏𝐫𝐨𝐣𝐞𝐜𝐭 𝐂𝐡𝐚𝐫𝐭𝐞𝐫 𝐢𝐧 𝐏𝐫𝐨𝐣𝐞𝐜𝐭𝐬 𝐈𝐧𝐭𝐫𝐨𝐝𝐮𝐜𝐭𝐢𝐨𝐧 A Project Charter is a formal document issued by a sponsor to authorize a project's start and grant the project manager authority to use organizational resources. It outlines high-level project information and ensures alignment and accountability from day one. 𝐏𝐮𝐫𝐩𝐨𝐬𝐞 𝐚𝐧𝐝 𝐒𝐢𝐠𝐧𝐢𝐟𝐢𝐜𝐚𝐧𝐜𝐞 -Authorization & Control -Empowers the project manager -Defines scope, schedule & budget -Acts as a change control baseline -Communication & Agreement -Aligns all stakeholders -Prevents scope creep -Documents objectives, assumptions & risks -Strategic Relevance -Links project to business goals -Supports long-term organizational improvement -Insight: The charter should be kept visible and current to remain effective. 𝐑𝐞𝐬𝐩𝐨𝐧𝐬𝐢𝐛𝐢𝐥𝐢𝐭𝐲 𝐟𝐨𝐫 𝐂𝐡𝐚𝐫𝐭𝐞𝐫 𝐂𝐫𝐞𝐚𝐭𝐢𝐨𝐧 Though the project sponsor issues the charter, the project manager often helps develop it, gathering input from stakeholders & aligning it with strategic goals. In public projects, tools like risk assessments may guide its development. 𝐖𝐡𝐲 𝐈𝐭’𝐬 𝐄𝐬𝐬𝐞𝐧𝐭𝐢𝐚𝐥 Every project needs a charter to: -Establish direction and authority -Define roles and responsibilities -Prevent miscommunication & risk escalation Example: Outdated charter timelines in a project caused contractor delays and claims due to misaligned expectations. 𝐊𝐞𝐲 𝐂𝐨𝐦𝐩𝐨𝐧𝐞𝐧𝐭𝐬 A. Overview Project name, author, sponsor, manager, date B. Purpose & Background Business case and strategic need C. Goals & Objectives Broad goals and measurable targets D. Scope Inclusions, exclusions, and deliverables E. Deliverables Major outputs like structures, manuals, plans F. Timeline Key milestones and start/end dates G. Budget Summary of expected costs with estimation types H. Constraints Real limitations (e.g., regulatory, financial) I. Assumptions Factors accepted as true during planning J. Risks Potential events that could impact success K. Success Factors Critical elements that must be met (e.g., timely decisions) L. Organization & Resources Team structure and required resources M. Communication Plan Reporting, stakeholder updates, and escalation N. Contingency & Management Reserves Budget buffers for known/unknown risks O. Optional Items Quality metrics, stakeholder list, reporting plan 𝐓𝐚𝐢𝐥𝐨𝐫𝐢𝐧𝐠 𝐟𝐨𝐫 𝐏𝐫𝐨𝐣𝐞𝐜𝐭 𝐂𝐨𝐦𝐩𝐥𝐞𝐱𝐢𝐭𝐲 Use tools like the Project Complexity & Risk Assessment Tool for government or large-scale projects. While charter depth may vary, its core elements stay consistent across all project types. 𝐂𝐨𝐧𝐜𝐥𝐮𝐬𝐢𝐨𝐧 The Project Charter is critical for: -Authorizing project execution -Aligning stakeholders & expectations -Managing change and complexity -Supporting strategic, operational, and financial success A well-maintained charter lays the foundation for project discipline, control, and delivery of value.

What to Consider before Developing a Project Charter. A well-developed project charter serves as the blueprint that defines a project’s purpose, direction, and authority before any work commences. Developing one goes beyond just filling out a template. Before drafting a charter, a project manager should take time to assess several key factors to ensure it’s grounded in the right context, purpose, and strategy. · Business Need and Strategic Alignment: Understand the why. What business problem, opportunity, or change drives this project?  What value will it deliver, and how does it connect to the broader organizational goals? · Identity and Engage Stakeholders Early: The best charters are built collaboratively. Involve sponsors, decision-makers, and key influencers early. Understand their expectations and level of influence. When people co-own the “why,” they support the “how", ensuring buy-in. · Clarify Scope and Boundaries: Understand the major deliverables and assess dependencies, potential risks, and limits around budget, time, and resources. This helps outline clear assumptions and expectations from the start. · Define Success Criteria: Be clear about what success looks like and how it will be measured. Tie acceptance criteria to clear business outcomes because success that can’t be defined can’t be achieved. Taking time to reflect on these factors helps the project manager build clarity, alignment, and confidence before developing the charter and committing resources or authority. So, over to you: Are there other factors you consider before drafting a project charter in your organization? #ProjectCharter #ProjectManagement #PMBOK #Leadership #ProjectInitiation WinTECH Community PMI North Saskatchewan Chapter