Start hereOpen the incident command and preserve the discovery clock
~23 days leftOpen step
Guide library
Regulation North America

HIPAA breach notification operations

HIPAA breach response: investigation, risk assessment, notice and HHS reporting

An operational playbook for health plans, providers, clearinghouses and business associates responding to suspected exposure of unsecured protected health information. It turns the Breach Notification Rule into a clocked incident workflow, with clear handoffs between the business associate, covered entity, privacy office, security team, counsel and communications.

Issuing authority
U.S. Department of Health and Human Services, Office for Civil Rights (HHS OCR)
Timing
For breaches involving 500 or more individuals, provide affected-person, OCR and required media notice without unreasonable delay and no later than 60 calendar days after discovery. Media notice applies when more than 500 residents of a single State or jurisdiction are affected. For fewer than 500 people, individual notice still follows the 60-day outer limit; the OCR report can be filed annually, no later than 60 days after calendar year-end. HHS now permits a covered entity or business associate to estimate a large breach population if the number is not yet certain and submit an addendum later. A business associate must notify the covered entity without unreasonable delay and no later than 60 days after discovery, but the BAA may impose a shorter deadline. Build earlier internal and contract-specific clocks so the covered entity has time to identify people and deliver its notices.
Reviewed
Inside this guide
6 steps · 6 templates

Who it applies to

Use this guide after a suspected impermissible use or disclosure of unsecured PHI. Determine whether the data is PHI, whether an event is a security incident, whether the breach presumption applies, and whether an exception or documented low-probability-of-compromise assessment is supportable. Covered entities and business associates both have documentation duties, but the covered entity is ultimately responsible for required individual notice. This guide does not replace the Security Rule incident response, state breach laws, 42 CFR Part 2, FTC or state consumer laws, law-enforcement coordination, contractual duties or litigation obligations. For Change Healthcare-type events, HHS says each covered entity must assess and meet its own duties even where a business associate submits a breach report on its behalf.

What you’ll produce

A preserved investigation record; a good-faith decision on whether unsecured PHI was breached; a deduplicated affected-person population; a signed notice plan allocating each duty between covered entity and business associate; delivered individual, OCR and media notices when required; an annual small-breach log; and corrective actions tied to the root cause.

OCR’s latest annual report in this research set covers calendar 2024. It records 663 large breaches affecting about 242.9 million people and 74,299 reports involving fewer than 500 people, affecting about 340,618 people. Hacking/IT incidents represented 81% of the large breach reports and affected about 241.6 million people. OCR opened investigations into every reported large breach and resolved 785 breach investigations through technical assistance, corrective action, settlement or a finding that no violation occurred. Twelve resolutions involved corrective action plans and settlements or civil money penalties totaling $7,813,831. These counts are not probabilities that a specific company will be investigated or penalized; the report also includes OCR resolution of matters from other periods. OCR highlighted risk analysis, risk management, information-system activity review, audit controls, and authentication as recurring improvement areas.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What applies to each entity, product and activity?
Have Legal or Regulatory confirm scope and applicable deadlines for each entity, activity and jurisdiction. Assign owners for incident reporting, filings and lifecycle changes where required.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the first week

  1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
  2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
  3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.

What to review each week

Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

HIPAA breach notification operations kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Open the incident command and preserve the discovery clock · Incident commander + Security operations + Privacy officer + Business associate lead [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Do the incident hotline, SOC, privacy office and business associates use one discovery timestamp and one escalation route, including nights, weekends and holidays?
  • Can the organization produce a defensible list of unique affected people and determine whether 500 or more residents of any one state are involved before notice deadlines?

Worked scenario

A managed service provider tells a hospital that an attacker accessed a file server and may have copied claims data. The hospital’s incident commander preserves logs, isolates affected systems and keeps care operations safe. Privacy maps the data to the covered entity and business associate relationship, confirms whether the records are PHI and whether the information was encrypted in a manner that made it unusable to the attacker. Security investigates initial access, systems, file paths, exfiltration evidence and backups. The Privacy Officer documents the four required risk-assessment factors and evaluates exceptions without assuming that encryption at rest resolves a live ransomware event. Data Operations reconcile member IDs to a deduplicated list of people and residential states. Legal checks the BAA’s notice deadline and each state law. The parties assign who will prepare the individual notices, submit the OCR report and provide any state-level media notice. They release notices without unreasonable delay, retain proof of mailing and portal receipt, and file an addendum when forensic work confirms the final population. The audit committee receives a root-cause report and funded remediation plan.

DATES AND TRIGGERS

Official milestones

See the deadline calendar
  • Without unreasonable delay; no later than 60 calendar days after discovery

    Notify affected individuals

    First-class mail is the default; electronic notice is permitted where the person agreed to it. State law or contracts may require faster action.

    Official reference (opens in a new tab)
  • Without unreasonable delay; no later than 60 calendar days after discovery

    Notify HHS OCR of breaches affecting 500 or more individuals

    If counts are uncertain at filing, submit an estimate and update it through an addendum.

    Official reference (opens in a new tab)
  • Within 60 calendar days after calendar year-end

    Report each under-500 breach to OCR

    File each incident separately. Early filing is allowed; do not wait for the annual deadline if prompt reporting helps.

    Official reference (opens in a new tab)
  • Without unreasonable delay; no later than 60 calendar days after discovery

    Notify prominent media when more than 500 residents of one State or jurisdiction are affected

    Compute this threshold by resident state, not by total affected people across the whole incident.

    Official reference (opens in a new tab)
  • At least 90 days after substitute notice begins

    Keep a homepage substitute notice available when contact details are insufficient for 10 or more people

    Maintain a toll-free number for at least 90 days and preserve page screenshots and call logs.

    Official reference (opens in a new tab)
  • As soon as possible under the BAA, and no later than 60 days absent a shorter contractual term

    Business associate notifies the covered entity

    Check the signed agreement for a shorter notice deadline and required data fields. The federal outside limit is not an operational target.

    Official reference (opens in a new tab)
The whole journeyabout 23 days across 6 steps
  1. 01Open the incident command and preserve the discovery clock, Incident commander + Security operations + Privacy officer + Business associate lead, about 1 days
  2. 02Determine whether the event is a reportable breach, Privacy officer + Breach counsel + Security forensics + Data owners, about 3 days
  3. 03Reconcile people, data, locations and thresholds, Privacy analytics lead + Security forensics + Health information management + Business associate data team, about 5 days
  4. 04Set the covered entity and business associate work split, Covered entity privacy officer + Business associate privacy lead + Procurement/contract owner + Counsel, about 2 days
  5. 05Draft and deliver notices that let affected people act, Covered entity communications + Privacy counsel + Patient/member operations + Mailing vendor + Call center, about 7 days
  6. 06File OCR and required media reports, then close the case, Privacy officer + Regulatory reporting owner + Counsel + Internal audit + Executive sponsor, about 5 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 6 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Open the incident command and preserve the discovery clockIncident commander + Security operations + Privacy officer + Business associate leadImmediately on discovery; use one synchronized incident time and maintain the actual discovery definition for each entitySet a start dateIncident command log and evidence preservation indexOpen
Determine whether the event is a reportable breachPrivacy officer + Breach counsel + Security forensics + Data ownersStart as soon as the event is contained; document the analysis before notification decisions and keep a dated supplemental review open as facts changeSet a start dateBreach determination and four-factor risk assessmentOpen
Reconcile people, data, locations and thresholdsPrivacy analytics lead + Security forensics + Health information management + Business associate data teamRun continuously while investigation proceeds; freeze each version used for a filing or noticeSet a start dateAffected-person reconciliation and threshold matrixOpen
Set the covered entity and business associate work splitCovered entity privacy officer + Business associate privacy lead + Procurement/contract owner + CounselThe same day the breach is confirmed; apply the shorter BAA deadline and set internal dates well before the federal outer limitSet a start dateSigned notice allocation and covered-entity/BA responsibility matrixOpen
Draft and deliver notices that let affected people actCovered entity communications + Privacy counsel + Patient/member operations + Mailing vendor + Call centerWithout unreasonable delay and no later than 60 calendar days after discovery; accelerate based on state law, contracts, clinical safety or regulator directionSet a start dateApproved notice set, delivery evidence and patient support runbookOpen
File OCR and required media reports, then close the casePrivacy officer + Regulatory reporting owner + Counsel + Internal audit + Executive sponsor500 or more individuals: OCR without unreasonable delay and within 60 days. Fewer than 500: report to OCR by 60 days after calendar year-end. Media notice: more than 500 residents in one State or jurisdiction, within 60 days.Set a start dateOCR submission receipts, small-breach log and corrective-action closeoutOpen
0 of 6 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Open the incident command and preserve the discovery clock

    Who Incident commander + Security operations + Privacy officer + Business associate lead When Immediately on discovery; use one synchronized incident time and maintain the actual discovery definition for each entity

    Create a severity-rated incident ID and name the decision maker, privacy lead, evidence custodian and covered-entity contacts. Preserve alerts, access logs, cloud audit trails, endpoint images, data-loss alerts, forensic copies, vendor messages, call recordings and system snapshots. Record when the event happened, when it was detected, when each organization discovered facts sufficient to identify the breach and who received each notice. Isolate compromised systems without destroying evidence or interrupting patient care. Suspend affected credentials and tokens, preserve encryption key state, stop data exports, coordinate with law enforcement where appropriate, and keep a parallel clinical-continuity workstream. Do not delay containment while the legal analysis is pending.

    What to produce

    Incident command log and evidence preservation indexRestricted incident log

    Gather first

    • Security alerts
    • Covered-entity and business-associate contacts
    • System and cloud audit logs
    • Data-flow map
    • Incident response plan

    How to prepare it

    1. Record the incident ID, source, incident time, detection time, discovery time for each organization, initial scope and accountable incident commander. Preserve original timestamps and identify the system used to establish each time.
    2. Index forensic copies, access logs, affected systems, data exports, endpoint images, vendor messages and legal holds. Track chain of custody, access restrictions, evidence owner and retention location.
    3. Maintain separate containment, patient-care continuity, privacy determination and notification workstreams. Record every decision, approver, assumption, next fact needed and scheduled reassessment.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional discovery row
    The service desk receives a vendor message at 09:12; the hospital’s privacy officer sees it at 09:28. The log preserves both receipt times and links each to a source message.
    Fictional containment record
    Security isolates one file server at 10:05, preserves a memory image, rotates exposed credentials and records the clinical downtime owner who approved the sequence.

    Check before handing it over

    The incident record preserves evidence and shows how response decisions proceeded without collapsing discovery time into a single meeting date.

    Give the verified discovery timeline and evidence index to the breach assessment team.

  2. 02

    Determine whether the event is a reportable breach

    Who Privacy officer + Breach counsel + Security forensics + Data owners When Start as soon as the event is contained; document the analysis before notification decisions and keep a dated supplemental review open as facts change

    Confirm the data meets the HIPAA definition of PHI and is unsecured under HHS guidance. Identify each access, use or disclosure that was not permitted. Apply the breach presumption, then test the applicable exceptions and, where relying on low probability of compromise, document all four factors: nature and extent of PHI and re-identification risk; the unauthorized person; whether PHI was actually acquired or viewed; and mitigation. For ransomware, do not treat encryption performed by the attacker as protective encryption. Investigate exfiltration, malware behavior, lateral movement, data integrity and availability. Reach a good-faith, reasonable decision; do not equate “no proof of download” with no breach. Record the rationale and approver.

    What to produce

    Breach determination and four-factor risk assessmentCounsel-reviewed decision memo

    Gather first

    • PHI inventory
    • Privacy Rule authorization analysis
    • Encryption and key evidence
    • Forensic findings
    • HHS guidance
    • Incident chronology

    How to prepare it

    1. Identify the information, people, systems and recipients. Decide whether the data was PHI, whether it was unsecured under HHS guidance, and whether an impermissible acquisition, access, use or disclosure occurred.
    2. Apply the breach presumption, then document each applicable exception or all four low-probability factors: nature and extent of PHI and re-identification risk; unauthorized recipient; actual acquisition or viewing; and mitigation.
    3. For ransomware, evaluate what the malware did, what it could access, exfiltration evidence, propagation, integrity and availability. Record an evidence-based conclusion, dissenting views, approver and date for reopening if new facts emerge.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional factor 1
    A claims export contains member names, dates of service and procedure codes. Privacy identifies the sensitivity and explains the practical re-identification risk.
    Fictional factor 2
    Forensics determines whether the recipient was an authorized cloud subcontractor, an unknown attacker or a person who returned the material without reading it.
    Fictional factor 3
    The team distinguishes a confirmed file open from an unverified access log and states what the logs can and cannot prove.
    Fictional factor 4
    The file is recovered and access revoked, but the memo separately evaluates whether copies or credentials remain with the recipient.

    Check before handing it over

    A reviewer can trace each legal conclusion to incident evidence and see why notice is required or why the firm can demonstrate a low probability of compromise.

    Obtain Privacy and counsel sign-off before setting notice recipients or filing thresholds.

  3. 03

    Reconcile people, data, locations and thresholds

    Who Privacy analytics lead + Security forensics + Health information management + Business associate data team When Run continuously while investigation proceeds; freeze each version used for a filing or notice

    Join source-system records to patient, member or employee identity using minimum necessary fields. Normalize and deduplicate individuals across files, periods, products and business associates. Capture PHI types, record count, affected states and jurisdictions, known contact details, minor or deceased status where relevant, and whether one person appears in multiple datasets. Separate confirmed people from estimated upper and lower bounds. The HHS large-breach portal accepts an estimate when the final count is not yet known; save the query, assumptions and transaction number and plan an addendum. Compute two thresholds separately: 500 or more individuals overall for contemporaneous OCR reporting, and more than 500 residents in a single State or jurisdiction for media notice.

    What to produce

    Affected-person reconciliation and threshold matrixVersioned population workbook

    Gather first

    • Patient, member or employee ID
    • Source-system exports
    • Business associate files
    • Address and residence state
    • Data-type and event mapping

    How to prepare it

    1. Create a restricted person-level staging table. Normalize identifiers, retain source record IDs, deduplicate across systems and flag unresolved identities rather than silently dropping them.
    2. Calculate the total unique individuals and separate counts by state or jurisdiction of residence. Classify confirmed, estimated and maximum potential counts and document the query, exclusions, assumptions and cutoff timestamp.
    3. Check the 500-person overall threshold for contemporaneous OCR notice and the separate more-than-500-residents-in-one-state threshold for media notice. If the large-breach count is uncertain, prepare an estimate and a dated addendum plan.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional population row
    An identity appears in the hospital and vendor export with different account numbers. The analyst links both to one person but keeps both source IDs for reconciliation.
    Fictional threshold summary
    The current estimate is 612 people across five states. California has 492 confirmed residents and 38 unresolved addresses. The media decision remains open until the address review sets a defensible count.

    Check before handing it over

    The covered entity can defend who was included, which counts remain estimated and whether each legal threshold was crossed.

    Freeze the approved extract and give it to the notice production and OCR filing owners.

  4. 04

    Set the covered entity and business associate work split

    Who Covered entity privacy officer + Business associate privacy lead + Procurement/contract owner + Counsel When The same day the breach is confirmed; apply the shorter BAA deadline and set internal dates well before the federal outer limit

    Read the exact BAA notice clause, escalation route, required fields, updates and subcontractor flow-down. The business associate should identify affected people and send available details promptly, not hold notice until the 60-day outside limit. The covered entity remains responsible for required individual notices, even if it delegates drafting or mailing. Record who will validate the breach, who owns the HHS filing, who approves public statements, who controls state notices, and who pays for credit monitoring or other mitigation if offered. Where a business associate files on behalf of the covered entity, obtain the OCR transaction ID and confirm the entity’s own duty is met. Keep separate records for incidents involving Part 2 records because their authority and patient threshold differ.

    What to produce

    Signed notice allocation and covered-entity/BA responsibility matrixDecision and responsibility register

    Gather first

    • Executed BAA and subcontractor terms
    • Entity role map
    • Incident facts
    • State-by-state recipient list
    • Federal and state deadline calendar

    How to prepare it

    1. Read the executed BAA for initial notice clock, required fields, updates, cooperation, expenses and subcontractor escalation. Record the shortest applicable deadline and its triggering event.
    2. Assign the covered entity and business associate owners for individual notices, OCR report, media notice, state regulator filings, public statements, patient support and addenda. Confirm the covered entity has approved any delegated filing or mailing.
    3. Set internal due dates earlier than statutory and contractual outer limits. Obtain named approvals and a backup owner for weekends, holidays, staff absence and material changes to the affected population.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional responsibility row
    The business associate sends an initial incident report within its 24-hour contract target, with patient-level facts to follow. The covered entity owns individual notices and OCR submission unless a written delegation is confirmed.
    Fictional media trigger
    More than 500 residents in one state remains plausible. Legal owns the threshold check and Communications keeps a media package ready before the final count is available.

    Check before handing it over

    Every required notice has one accountable filer, an approved recipient list, a deadline and a backup owner.

    Approve the responsibility matrix and route it to the notice and reporting workstream leads.

  5. 05

    Draft and deliver notices that let affected people act

    Who Covered entity communications + Privacy counsel + Patient/member operations + Mailing vendor + Call center When Without unreasonable delay and no later than 60 calendar days after discovery; accelerate based on state law, contracts, clinical safety or regulator direction

    Prepare individualized written notice by first-class mail, or email where the person agreed to electronic notice. Include, to the extent possible, what happened and when; types of PHI involved; steps people can take to protect themselves; what the entity is doing to investigate, mitigate and prevent recurrence; and a contact route. For 10 or more people with insufficient or outdated addresses, provide substitute notice by homepage posting for at least 90 days or major print/broadcast media, with a toll-free number active for at least 90 days. For fewer than 10, use an alternative written notice, telephone or other means. Keep interpreters, accessible formats, returned-mail handling, spokesperson scripts and a staffed escalation path ready. Reconcile print vendor totals, digital delivery, returned mail and call volume to the final affected list.

    What to produce

    Approved notice set, delivery evidence and patient support runbookNotice release packet

    Gather first

    • Approved breach facts
    • Unique affected-person list
    • PHI categories
    • Remediation advice
    • Contact center capacity
    • Accessible and translated formats

    How to prepare it

    1. Draft the individual notice with the breach description, information types, steps people can take, investigation and mitigation, prevention work and a clear contact route. Explain what is known and what remains under investigation without speculation.
    2. Select first-class mail or email where the person agreed to electronic notice. For 10 or more individuals with insufficient contact information, use homepage posting for at least 90 days or major print/broadcast media, and keep a toll-free number active at least 90 days. For fewer than 10, use a permitted alternative method.
    3. Test the notice and help line with a person unfamiliar with the event. Capture final version approval, print files, mailing manifest, email delivery results, return-mail queue, call scripts, interpreter path, accessibility variants and service escalation instructions.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional plain-language paragraph
    A criminal actor accessed a claims file containing names, dates of birth and health-plan information between two stated dates. The letter lists the included data, explains what the plan has done, and provides a direct number for questions.
    Fictional delivery record
    The approved list has 4,920 unique records. The mail vendor reports 4,913 accepted pieces, seven validation rejects and 31 later returns. Each exception has an owner and resolution date.

    Check before handing it over

    An affected person can understand what happened, take a practical protective step and reach a staffed support channel.

    Release notices on the approved schedule and reconcile proof of delivery to the affected-person file.

  6. 06

    File OCR and required media reports, then close the case

    Who Privacy officer + Regulatory reporting owner + Counsel + Internal audit + Executive sponsor When 500 or more individuals: OCR without unreasonable delay and within 60 days. Fewer than 500: report to OCR by 60 days after calendar year-end. Media notice: more than 500 residents in one State or jurisdiction, within 60 days.

    For a breach involving 500 or more people, submit the OCR form electronically on the current portal schedule. If the population is uncertain, submit a reasonable estimate rather than missing the clock; keep the transaction ID and use an addendum when final facts change or clarify the report. For under-500 events, enter each incident separately in a controlled register and file each report by the annual deadline. Provide the same information to prominent media serving a state or jurisdiction when its more-than-500 resident threshold is met. Verify OCR receipt, notice completion, state filings and business associate confirmations. Maintain the decision, notices, delivery evidence, risk assessment and supporting materials under the applicable documentation retention policy. Assign every root cause to an executive owner, control, due date and retest; close only when the remediation works and open regulatory requests are resolved.

    What to produce

    OCR submission receipts, small-breach log and corrective-action closeoutRegulatory filing and remediation record

    Gather first

    • Final threshold workbook
    • Approved notice package
    • OCR portal fields
    • Business associate updates
    • Security root cause
    • Corrective action evidence

    How to prepare it

    1. For 500 or more affected people, file electronically with OCR without unreasonable delay and within 60 days of discovery. Use the best available estimate if needed; retain the transaction number and submit an addendum when facts are clarified.
    2. For fewer than 500 people, record each breach as a separate event and calendar OCR submission within 60 days after the year in which it was discovered. Verify the annual submission includes every incident and keep the filing receipt.
    3. Reconcile individual, OCR, media and state notices to the same approved version and population. Record root cause, control failure, corrective owner, target date, validation method, retest result and executive acceptance of residual risk.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional OCR receipt
    The covered entity saves the portal transaction ID, filing PDF, submitted timestamp, approved count estimate and owner of the next population update.
    Fictional corrective action
    The vendor-access control adds time-bound credentials and an alert on bulk export. Internal Audit retests 30 days of activity and attaches the evidence before closing the action.

    Check before handing it over

    The organization can prove which notices went out, that each incident was reported on time and that the root cause was corrected and retested.

    Give the final record to Privacy, Security, Internal Audit and the executive risk committee.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes