[{"data":1,"prerenderedAt":462},["ShallowReactive",2],{"document-issue-tracking-sheet-D13471":3},{"document":4,"label":23,"preview":11,"thumb":24,"thumb600":25,"description":5,"descriptionCustom":6,"apiDescription":5,"pages":8,"extension":10,"parents":26,"breadcrumb":30,"related":36,"customDescModule":172,"customdescription":6,"mdFm":173,"mdProseHtml":461},{"description":5,"descriptionCustom":6,"label":7,"pages":8,"size":9,"extension":10,"preview":11,"thumb":12,"svgFrame":13,"seoMetadata":14,"parents":16,"keywords":15},"[COMPANY NAME] DETAILED ISSUE TRACKING SHEET Date: _________________________",null,"Issue Tracking Sheet","1",513,"doc","https://templates.business-in-a-box.com/imgs/1000px/issue-tracking-sheet-D13471.png","https://templates.business-in-a-box.com/imgs/250px/13471.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#13471.xml",{"title":15,"description":6},"issue tracking sheet",[17,20],{"label":18,"url":19},"Business Plan Kit","/templates/business-plan-kit/",{"label":21,"url":22},"Administration","/templates/business-administration/","Issue Tracking Sheet Template","https://templates.business-in-a-box.com/imgs/400px/13471.png","https://templates.business-in-a-box.com/imgs/600px/13471.png",[27,17,20],{"label":28,"url":29},"Templates","/templates/",[31,32,33],{"label":28,"url":29},{"label":21,"url":22},{"label":34,"url":35},"Project Management","/templates/project-management/",[37,41,46,50,54,58,62,66,70,74,78,82,86,100,116,129,141,157],{"label":38,"url":39,"thumb":40,"extension":10},"Bug Tracking Sheet","/template/bug-tracking-sheet-D13460","https://templates.business-in-a-box.com/imgs/250px/13460.png",{"label":42,"url":43,"thumb":44,"extension":45},"Employee Absence Tracking","/template/employee-absence-tracking-D626","https://templates.business-in-a-box.com/imgs/250px/626.png","xls",{"label":47,"url":48,"thumb":49,"extension":10},"Telephone Tracking Log","/template/telephone-tracking-log-D682","https://templates.business-in-a-box.com/imgs/250px/682.png",{"label":51,"url":52,"thumb":53,"extension":45},"Balance Sheet","/template/balance-sheet-D353","https://templates.business-in-a-box.com/imgs/250px/353.png",{"label":55,"url":56,"thumb":57,"extension":45},"Time Sheet","/template/time-sheet-D630","https://templates.business-in-a-box.com/imgs/250px/630.png",{"label":59,"url":60,"thumb":61,"extension":45},"CUE Sheet","/template/cue-sheet-D14094","https://templates.business-in-a-box.com/imgs/250px/14094.png",{"label":63,"url":64,"thumb":65,"extension":10},"Call Sheet Template","/template/call-sheet-template-D13875","https://templates.business-in-a-box.com/imgs/250px/13875.png",{"label":67,"url":68,"thumb":69,"extension":10},"Casting Sheet","/template/casting-sheet-D13914","https://templates.business-in-a-box.com/imgs/250px/13914.png",{"label":71,"url":72,"thumb":73,"extension":10},"Fact Sheet","/template/fact-sheet-D13971","https://templates.business-in-a-box.com/imgs/250px/13971.png",{"label":75,"url":76,"thumb":77,"extension":10},"Prospecting Sheet","/template/prospecting-sheet-D1419","https://templates.business-in-a-box.com/imgs/250px/1419.png",{"label":79,"url":80,"thumb":81,"extension":10},"Term Sheet","/template/term-sheet-D473","https://templates.business-in-a-box.com/imgs/250px/473.png",{"label":83,"url":84,"thumb":85,"extension":10},"Board Resolution to Issue General Release","/template/board-resolution-to-issue-general-release-D68","https://templates.business-in-a-box.com/imgs/250px/68.png",{"description":87,"descriptionCustom":6,"label":87,"pages":88,"size":9,"extension":45,"preview":89,"thumb":90,"svgFrame":91,"seoMetadata":92,"parents":94,"keywords":93,"url":99},"Risk Register","2","https://templates.business-in-a-box.com/imgs/1000px/risk-register-D14096.png","https://templates.business-in-a-box.com/imgs/250px/14096.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#14096.xml",{"title":93,"description":6},"risk register",[95,98],{"label":96,"url":97},"Legal Agreements","business-legal-agreements",{"label":96,"url":97},"/template/risk-register-D14096",{"description":101,"descriptionCustom":6,"label":102,"pages":88,"size":9,"extension":10,"preview":103,"thumb":104,"svgFrame":105,"seoMetadata":106,"parents":108,"keywords":107,"url":115},"DISCIPLINARY ACTION POLICY PURPOSE The purpose of this Disciplinary Action Policy is to establish a clear framework and guidelines for addressing employee misconduct, policy violations, and performance issues in a fair and consistent manner. This Policy aims to promote a positive work environment, ensure compliance with company policies, and provide opportunities for employee growth and improvement. SCOPE This Policy applies to all employees at [COMPANY NAME], including full-time, part-time, temporary, and contract workers. It covers a wide range of infractions, including but not limited to misconduct, violation of company policies, insubordination, unethical behavior, harassment, discrimination, poor performance, and any actions that may negatively impact the workplace or the organization's reputation. PRINCIPLES OF DISCIPLINARY ACTION Fairness: All disciplinary actions will be conducted in a fair and unbiased manner, providing employees with an opportunity to present their side of the story and defend themselves against allegations. Consistency: Disciplinary actions will be applied consistently throughout the organization, ensuring that similar infractions are treated similarly. Progressive Approach: Whenever possible, a progressive approach to discipline will be followed, with escalating consequences for repeated or severe infractions. However, the organization reserves the right to skip progressive steps in cases of serious misconduct. Confidentiality: Disciplinary matters will be treated with strict confidentiality, only shared with individuals who have a legitimate need to know, while maintaining compliance with applicable privacy laws. DISCIPLINARY PROCEDURES Investigation: Before initiating any disciplinary action, a thorough and impartial investigation will be conducted to gather facts and evidence regarding the alleged misconduct or performance issue. The investigation may involve interviews, document review, and any other relevant means of gathering information.","Disciplinary Action Policy","https://templates.business-in-a-box.com/imgs/1000px/disciplinary-action-policy-D13486.png","https://templates.business-in-a-box.com/imgs/250px/13486.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#13486.xml",{"title":107,"description":6},"disciplinary action policy",[109,112],{"label":110,"url":111},"Human Resources","human-resources",{"label":113,"url":114},"Company Policies","company-policies","/template/disciplinary-action-policy-D13486",{"description":117,"descriptionCustom":6,"label":117,"pages":8,"size":9,"extension":45,"preview":118,"thumb":119,"svgFrame":120,"seoMetadata":121,"parents":123,"keywords":122,"url":128},"Task List","https://templates.business-in-a-box.com/imgs/1000px/task-list-D13044.png","https://templates.business-in-a-box.com/imgs/250px/13044.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#13044.xml",{"title":122,"description":6},"task list",[124,126],{"label":18,"url":125},"business-plan-kit",{"label":21,"url":127},"business-administration","/template/task-list-D13044",{"description":130,"descriptionCustom":6,"label":131,"pages":8,"size":9,"extension":10,"preview":132,"thumb":133,"svgFrame":134,"seoMetadata":135,"parents":137,"keywords":136,"url":140},"PROJECT STATUS REPORT PROJECT SUMMARY Report Date: Project Name: Prepared By: STATUS SUMMARY ","Status Report","https://templates.business-in-a-box.com/imgs/1000px/status-report-D13043.png","https://templates.business-in-a-box.com/imgs/250px/13043.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#13043.xml",{"title":136,"description":6},"status report",[138,139],{"label":18,"url":125},{"label":21,"url":127},"/template/status-report-D13043",{"description":142,"descriptionCustom":6,"label":142,"pages":143,"size":9,"extension":45,"preview":144,"thumb":145,"svgFrame":146,"seoMetadata":147,"parents":149,"keywords":148,"url":156},"Project Plan","6","https://templates.business-in-a-box.com/imgs/1000px/project-plan-D12775.png","https://templates.business-in-a-box.com/imgs/250px/12775.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#12775.xml",{"title":148,"description":6},"project plan",[150,153],{"label":151,"url":152},"Sales & Marketing","sales-marketing",{"label":154,"url":155},"Marketing Plan","marketing-plan","/template/project-plan-D12775",{"description":158,"descriptionCustom":6,"label":159,"pages":160,"size":9,"extension":10,"preview":161,"thumb":162,"svgFrame":163,"seoMetadata":164,"parents":166,"keywords":165,"url":171},"BOARD MEETING MINUTES [YOUR COMPANY NAME] Organization Name: Date: Location: Time: Board Members Present: [LIST NAMES] Board Members Absent: [LIST NAMES] Guests: List names and affiliations if any. Meeting Called to Order by: [NAME AND TIME] Approval of Previous Meeting Minutes: Motion by: [NAME] Seconded by: [NAME] Outcome: [APPROVED/AMENDED] [Agenda Item Title] Presenter: [NAME] Discussion Summary: Summarize the key points of discussion, including any differing views or debates. Action Items: Detail specific tasks decided upon, who is responsible, and any deadlines. Decisions Made: Summarize any decisions made, including vote outcomes if applicable. [Agenda Item Title] Presenter: [NAME] Discussion Summary: Summarize the key points of discussion, including any differing views or debates. Action Items: Detail specific tasks decided upon, who is responsible, and any deadlines. Decisions Made: Summarize any decisions made, including vote outcomes if applicable. Financial Report: Presented by: Summary: ","Board Meeting Minutes","3","https://templates.business-in-a-box.com/imgs/1000px/board-meeting-minutes-D13904.png","https://templates.business-in-a-box.com/imgs/250px/13904.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#13904.xml",{"title":165,"description":6},"board meeting minutes",[167,168],{"label":151,"url":152},{"label":169,"url":170},"Market Analysis","market-analysis","/template/board-meeting-minutes-D13904",false,{"seo":174,"reviewer":185,"legal_disclaimer":172,"quick_facts":189,"at_a_glance":191,"personas":195,"variants":220,"glossary":247,"fields":278,"how_to_fill":322,"common_mistakes":353,"faqs":370,"industries":395,"comparisons":412,"diy_vs_pro":426,"related_template_ids_curated":439,"schema":448,"classification":450},{"meta_title":175,"meta_description":176,"primary_keyword":177,"secondary_keywords":178},"Issue Tracking Sheet Template (Free Word)","Free issue tracking sheet template to log, assign, and resolve project or operational issues. Download in Word, edit online, or export as PDF. Free Word and PDF download.","issue tracking sheet template",[179,180,181,182,183,184],"issue log template","issue tracker template word","project issue tracking template","issue tracking sheet free download","issue register template","issue management log",{"name":186,"credential":187,"reviewed_date":188},"Bruno Goulet","CEO, Business in a Box","2026-05-02",{"difficulty":190,"legal_review_recommended":172,"signature_required":172},"easy",{"what_it_is":192,"when_you_need_it":193,"whats_inside":194},"An Issue Tracking Sheet is a structured log used to record, assign, prioritize, and monitor the resolution of problems, defects, or action items that arise during a project or business operation. This free Word download gives you a ready-to-use table you can edit online and export as PDF to share with your team or stakeholders in minutes.\n","Use it whenever a project, process, or system produces recurring problems that need to be formally captured and followed through to resolution — from software bugs and construction punch-list items to client complaints and audit findings.\n","Issue ID, date logged, description, category, priority rating, assigned owner, target resolution date, current status, and resolution notes — giving every issue a complete lifecycle record from discovery to closure.\n",[196,200,204,208,212,216],{"title":197,"use_case":198,"icon_asset_id":199},"Project managers","Tracking open issues across project phases to prevent scope creep and delays","persona-project-manager",{"title":201,"use_case":202,"icon_asset_id":203},"IT and software teams","Logging bugs, defects, and system errors for triage and resolution","persona-it-manager",{"title":205,"use_case":206,"icon_asset_id":207},"Operations managers","Monitoring recurring process failures and assigning corrective actions","persona-operations-director",{"title":209,"use_case":210,"icon_asset_id":211},"Quality assurance professionals","Recording non-conformances and tracking remediation to closure","persona-qa-specialist",{"title":213,"use_case":214,"icon_asset_id":215},"Client services teams","Documenting client-reported problems and ensuring timely follow-through","persona-customer-success",{"title":217,"use_case":218,"icon_asset_id":219},"Small business owners","Keeping a single visible list of open problems for a lean team to action","persona-small-business-owner",[221,224,228,232,236,239,243],{"situation":222,"recommended_template":38,"slug":223},"Tracking software bugs and defects during development or QA","bug-tracking-sheet-D13460",{"situation":225,"recommended_template":226,"slug":227},"Managing open items after a project audit or review","Audit Finding Log","finding-your-creative-spark-D13108",{"situation":229,"recommended_template":230,"slug":231},"Recording customer complaints and resolution steps","Customer Complaint Log","customer-complaint-resolution-policy-D13644",{"situation":233,"recommended_template":234,"slug":235},"Tracking punch-list items at a construction project close-out","Punch List Template","pricing-list-D13029",{"situation":237,"recommended_template":87,"slug":238},"Logging risks that have not yet materialised as active issues","risk-register-D14096",{"situation":240,"recommended_template":241,"slug":242},"Assigning and tracking action items from a meeting","Action Items List","disciplinary-action-policy-D13486",{"situation":244,"recommended_template":245,"slug":246},"Managing a broad set of tasks across a project team","Project Task List","task-list-D13044",[248,251,254,257,260,263,266,269,272,275],{"term":249,"definition":250},"Issue ID","A unique sequential identifier assigned to each logged issue so it can be referenced consistently across communications and reports.",{"term":252,"definition":253},"Priority Level","A rating — typically Critical, High, Medium, or Low — that determines the urgency with which an issue must be resolved.",{"term":255,"definition":256},"Issue Owner","The named individual responsible for driving an issue to resolution, not necessarily the person who will fix it.",{"term":258,"definition":259},"Target Resolution Date","The agreed deadline by which the issue must be resolved or escalated, used to track overdue items.",{"term":261,"definition":262},"Status","The current state of an issue in its lifecycle — typically Open, In Progress, Pending Review, or Closed.",{"term":264,"definition":265},"Root Cause","The underlying reason an issue occurred, as distinct from its symptom — identifying root cause prevents recurrence.",{"term":267,"definition":268},"Workaround","A temporary fix or process change that allows work to continue while the permanent resolution is developed.",{"term":270,"definition":271},"Escalation","The formal process of raising an unresolved issue to a higher authority or different team when it cannot be resolved within the original scope.",{"term":273,"definition":274},"Resolution Notes","A brief written record of what action was taken to close an issue, retained for audit trail and future reference.",{"term":276,"definition":277},"Issue Register","Another name for an issue tracking sheet, commonly used in formal project management frameworks such as PRINCE2 and PMI.",[279,283,287,292,297,302,307,312,317],{"name":249,"plain_english":280,"sample_language":281,"common_mistake":282},"A unique reference number assigned to each issue, usually sequential (e.g., ISS-001, ISS-002).","ISS-047","Reusing or skipping issue IDs makes cross-referencing in emails and reports unreliable and complicates audit trails.",{"name":284,"plain_english":285,"sample_language":188,"common_mistake":286},"Date logged","The calendar date the issue was first identified and entered into the log.","Recording the date work began on the issue instead of the date it was discovered — this understates how long issues sit unresolved.",{"name":288,"plain_english":289,"sample_language":290,"common_mistake":291},"Issue description","A concise statement of what the problem is, including where it occurred and what impact it is having.","Payment gateway returning error code 502 on checkout for orders over $500, blocking approximately 15% of daily transactions.","Writing vague descriptions like 'checkout problem' — without specifics, the assigned owner cannot begin work without a follow-up conversation.",{"name":293,"plain_english":294,"sample_language":295,"common_mistake":296},"Category","A label grouping the issue by type — e.g., Technical, Process, Resource, Communication, or Quality — to enable trend analysis.","Technical / Payment Processing","Skipping the category field entirely and only filling it in during reviews — uncategorised logs cannot be aggregated to spot recurring patterns.",{"name":298,"plain_english":299,"sample_language":300,"common_mistake":301},"Priority","A rating indicating urgency and business impact, guiding the order in which issues are addressed.","Critical — blocking live transactions; resolution required within 4 hours.","Marking every issue as High or Critical. When everything is critical, teams lose the ability to triage and the highest-impact issues get lost in the noise.",{"name":303,"plain_english":304,"sample_language":305,"common_mistake":306},"Assigned owner","The full name and role of the person responsible for resolving or coordinating resolution of the issue.","[FIRST NAME LAST NAME], Senior Developer","Assigning issues to a team or department rather than a named individual — shared ownership produces no ownership in practice.",{"name":308,"plain_english":309,"sample_language":310,"common_mistake":311},"Target resolution date","The agreed deadline for the issue to be resolved or formally escalated if it cannot be closed by that date.","2026-05-09","Leaving this field blank for lower-priority issues. Without a deadline, Low and Medium issues accumulate indefinitely and are never actioned.",{"name":313,"plain_english":314,"sample_language":315,"common_mistake":316},"Current status","Where the issue stands in its resolution lifecycle at the time of the last update.","In Progress — fix deployed to staging; awaiting QA sign-off before production release.","Setting status to Closed before a fix has been verified in the production environment — premature closure masks recurring issues.",{"name":318,"plain_english":319,"sample_language":320,"common_mistake":321},"Resolution notes","A brief record of the action taken to resolve the issue, including the root cause identified and any preventive measures applied.","Root cause: third-party payment API timeout threshold set to 3 seconds for large payloads. Fix: increased timeout to 10 seconds and added retry logic. Deployed 2026-05-08.","Leaving resolution notes empty after closing an issue. Without a record of what was done, the same fix must be rediscovered the next time the issue recurs.",[323,328,333,338,343,348],{"step":324,"title":325,"description":326,"tip":327},1,"Set up your issue ID sequence","Choose a consistent prefix and numbering format before logging the first issue — for example, ISS-001 or [PROJECT CODE]-001. Apply it to every row from the start.","A project-code prefix (e.g., ALPHA-001) keeps issues from different projects separate if you manage multiple logs in one file.",{"step":329,"title":330,"description":331,"tip":332},2,"Log the date and write a specific description","Enter the date the issue was first identified, then write a description that states what failed, where, and what the business impact is. Aim for two to three sentences.","Include a quantified impact wherever possible — '15% of orders affected' is far more actionable than 'intermittent checkout error'.",{"step":334,"title":335,"description":336,"tip":337},3,"Assign a category and priority","Select the most relevant category from your predefined list and set a priority level — Critical, High, Medium, or Low — based on the business impact and urgency.","Define priority criteria in a legend at the top of the sheet before the team starts logging, so ratings are applied consistently across reporters.",{"step":339,"title":340,"description":341,"tip":342},4,"Name a single owner and set a target date","Assign the issue to one named individual — not a team — and agree on a specific target resolution date at the time of logging.","For Critical issues, set the target date to the same day. For Low priority, a maximum of two weeks prevents the backlog from growing indefinitely.",{"step":344,"title":345,"description":346,"tip":347},5,"Update status at each review cycle","Change the status field at every team check-in or status meeting — Open, In Progress, Pending Review, or Closed. Add a one-line update note with each status change.","Colour-code the status column — red for Open/overdue, amber for In Progress, green for Closed — so the state of the log is visible at a glance without reading every row.",{"step":349,"title":350,"description":351,"tip":352},6,"Complete resolution notes before closing","Before changing status to Closed, record what action was taken, the root cause identified, and any preventive measures put in place to stop recurrence.","A two-sentence resolution note takes 60 seconds to write and saves hours of re-investigation when a similar issue surfaces months later.",[354,358,362,366],{"mistake":355,"why_it_matters":356,"fix":357},"Assigning issues to teams instead of individuals","When an issue is owned by 'the dev team' or 'operations', no single person feels accountable and issues stall indefinitely between handoffs.","Name one person as owner for every issue at the time of logging. That person coordinates resolution even if others do the actual work.",{"mistake":359,"why_it_matters":360,"fix":361},"Leaving the target resolution date blank","Issues without deadlines migrate to the bottom of everyone's priority list and accumulate into a backlog that never gets actioned.","Set a target date for every issue regardless of priority. For Low items, a two-week default is better than no date at all.",{"mistake":363,"why_it_matters":364,"fix":365},"Closing issues before verifying the fix","Premature closure means the same issue resurfaces, teams lose confidence in the log, and recurring problems cannot be identified as patterns.","Require a verification step — QA sign-off, user confirmation, or a defined observation period — before any issue is marked Closed.",{"mistake":367,"why_it_matters":368,"fix":369},"Inflating every issue to Critical or High priority","When priority ratings are not calibrated, teams cannot triage effectively and the highest-impact issues compete for attention with minor inconveniences.","Define written criteria for each priority level — for example, Critical means production is down or revenue is directly blocked — and apply them consistently.",[371,374,377,380,383,386,389,392],{"question":372,"answer":373},"What is an issue tracking sheet?","An issue tracking sheet is a structured log used to record, assign, prioritize, and monitor problems or action items until they are resolved. Each row captures a single issue with its ID, description, owner, priority, deadline, and status — giving teams a single shared reference for everything that is open, in progress, or closed.\n",{"question":375,"answer":376},"What is the difference between an issue and a risk?","A risk is a potential problem that has not yet occurred — something you are monitoring and trying to prevent. An issue is a problem that has already materialised and requires active resolution. Risks are tracked on a risk register; issues are tracked on an issue log. A risk that is not mitigated in time typically becomes an issue.\n",{"question":378,"answer":379},"What fields should an issue tracking sheet include?","At minimum: a unique issue ID, the date logged, a specific description of the problem, a priority rating, the name of the assigned owner, a target resolution date, the current status, and resolution notes. Optional fields include category, root cause, workaround, and linked documents or ticket numbers.\n",{"question":381,"answer":382},"How often should the issue log be reviewed?","Weekly reviews are standard for most project teams. High-velocity teams — software development, incident response — review daily or at every stand-up. The key is a fixed cadence: irregular reviews allow overdue issues to drift without accountability. Set a recurring calendar event and update every status field at each session.\n",{"question":384,"answer":385},"Can I use an issue tracking sheet instead of dedicated software like Jira?","Yes, for teams of up to about 15 people or projects with fewer than 50 concurrent issues, a well-maintained spreadsheet or Word log works effectively. Dedicated tools add workflow automation, notifications, and integrations that become valuable at higher volumes. Start with a template and migrate to software when manual updates become the bottleneck, not the exception.\n",{"question":387,"answer":388},"Who should have access to the issue tracking sheet?","All team members who may log or resolve issues should have edit access. Stakeholders and clients who need visibility but should not modify the log should receive read-only access or a filtered export. Restricting access too tightly means issues go unlogged; unrestricted editing without governance leads to accidental deletions and inconsistent entries.\n",{"question":390,"answer":391},"How do I handle issues that cannot be resolved within the target date?","Update the status to reflect the delay, document the reason in the notes column, set a revised target date, and escalate to the appropriate authority if the issue is blocking other work. Never simply extend the date silently — an audit trail of date changes and escalation decisions is what separates a managed backlog from a neglected one.\n",{"question":393,"answer":394},"What is the difference between an issue tracking sheet and an action items list?","An action items list captures discrete tasks assigned at a meeting or during planning — things that need to be done. An issue tracking sheet records problems that have arisen and need to be investigated and resolved. Issues often generate action items as part of their resolution, but not every action item stems from a problem.\n",[396,400,404,408],{"industry":397,"icon_asset_id":398,"specifics":399},"Technology / Software","industry-saas","Used to log bugs, API failures, and performance degradations during development, testing, and production support cycles.",{"industry":401,"icon_asset_id":402,"specifics":403},"Construction","industry-construction","Tracks punch-list defects, subcontractor non-conformances, and safety observations from site inspections through to sign-off.",{"industry":405,"icon_asset_id":406,"specifics":407},"Healthcare","industry-healthtech","Documents equipment malfunctions, process deviations, and patient safety incidents requiring formal corrective action under regulatory frameworks.",{"industry":409,"icon_asset_id":410,"specifics":411},"Professional Services","industry-professional-services","Captures client-reported problems, deliverable gaps, and internal process breakdowns across concurrent client engagements.",[413,416,419,422],{"vs":87,"vs_template_id":414,"summary":415},"risk-register-D13530","A risk register tracks potential problems that have not yet occurred, recording likelihood, impact, and mitigation plans. An issue tracking sheet records problems that have already materialised and require active resolution. The two documents are complementary — a risk that is not mitigated typically moves from the risk register to the issue log.",{"vs":241,"vs_template_id":417,"summary":418},"action-items-list-D13527","An action items list captures tasks assigned during a meeting or planning session — things that need to be done. An issue tracking sheet records problems that have arisen and must be investigated and resolved. Issues frequently generate action items, but an action item is not inherently the result of a problem.",{"vs":245,"vs_template_id":420,"summary":421},"task-list-D13454","A project task list outlines planned deliverables and work packages that form part of the project scope. An issue tracking sheet captures unplanned problems that threaten scope, schedule, or quality. Task lists drive forward progress; issue logs manage deviations from that progress.",{"vs":423,"vs_template_id":424,"summary":425},"Change Request Form","D{CHANGE_REQUEST_FORM_ID}","A change request form proposes and authorises a deliberate modification to scope, schedule, or budget. An issue tracking sheet records problems that require investigation and resolution within the existing baseline. Issues sometimes trigger change requests — for example, when a defect cannot be fixed without modifying scope — but the two documents serve distinct governance functions.",{"use_template":427,"template_plus_review":431,"custom_drafted":435},{"best_for":428,"cost":429,"time":430},"Project teams, small businesses, and operations managers who need a simple, shared issue log with no tooling overhead","Free","5 minutes to set up; under 2 minutes per issue entry",{"best_for":432,"cost":433,"time":434},"Teams adding custom categories, escalation workflows, or SLA columns for client-facing issue management","$0–$100 (internal configuration time)","1–2 hours",{"best_for":436,"cost":437,"time":438},"Organisations requiring integration with project management platforms, automated notifications, or regulatory audit trail requirements","$500–$5,000+ (system configuration or developer build)","1–4 weeks",[238,242,246,440,242,441,442,443,444,445,446,447],"status-report-D13043","project-plan-D12775","board-meeting-minutes-D13904","charter-agreement-D13440","change-management-plan-D12880","quality-assurance-policy-D13756","incident-report-D12621","financial-report-D12767",{"emit_how_to":449,"emit_defined_term":449},true,{"primary_folder":451,"secondary_folder":452,"document_type":453,"industry":454,"business_stage":455,"tags":456,"confidence":460},"production-operations","project-management","worksheet","general","all-stages",[452,457,458,459,453],"quality-assurance","operations","issue-tracking",0.85,"\u003Ch2>What is an Issue Tracking Sheet?\u003C/h2>\n\u003Cp>An \u003Cstrong>Issue Tracking Sheet\u003C/strong> is a structured log used to record, assign, prioritize, and monitor the resolution of problems, defects, or failures that arise during a project or ongoing business operation. Each row in the sheet captures a single issue from the moment it is discovered through to verified closure — including who is responsible, when it must be resolved, and what action was taken. Unlike informal email threads or verbal task assignments, a centralised issue log gives every team member and stakeholder a single, up-to-date reference for what is open, what is being worked on, and what has been fixed.\u003C/p>\n\u003Ch2>Why You Need This Document\u003C/h2>\n\u003Cp>Without a formal issue log, problems get reported once in a meeting or email, fall out of circulation, and resurface weeks later — often with greater impact. Teams lose time reconstructing what was agreed, who owns it, and whether it was ever actually resolved. A single missed issue can delay a project milestone, breach a client SLA, or allow a recurring defect to compound into a larger failure. This template gives you a ready-to-use structure that takes under five minutes to deploy, keeps every open issue visible to the whole team, and builds an audit trail of resolutions that supports post-project reviews and continuous improvement.\u003C/p>\n",1781185976767]