GRC Parameter Entry Form

General Details

GRC Category

Parameter Details

GRC Summary

Category Parameter Name Responsible Party Details

Help

Use the prompt to quickly fill the GRC parameter entry form. Ensure your prompt follows the specified format for accurate parsing.

Tips for Writing Prompts:

Need More Help?

Contact support at support@example.com or refer to the user manual.

Follow this prompt format:

Create a GRC parameter for company in on prepared by category parameter responsible effective [policy ] [frequency ] [description ] [type ] [level ] [mitigation ] [regulation ] [deadline ] [requirements ] [notes ]

Keywords (use exactly as shown): Create, GRC parameter, for company, in, on, prepared by, category, parameter, responsible, effective, policy, frequency, description, type, level, mitigation, regulation, deadline, requirements, notes

Values:

  • company_name: Company name (e.g., ABC Corp)
  • department: Department name (e.g., Risk Management)
  • entry_date: YYYY-MM-DD (e.g., 2025-04-25)
  • prepared_by: Name of preparer (e.g., Jane Doe)
  • grc_category: governance, risk, compliance
  • parameter_name: Parameter name (e.g., Data Privacy Policy)
  • responsible_party: Responsible entity (e.g., IT Department)
  • effective_date: YYYY-MM-DD (e.g., 2025-05-01)
  • policy: Governance policy (e.g., Board Oversight) [for governance]
  • frequency: monthly, quarterly, annually [for governance]
  • description: Description (e.g., Ensure board approval for major decisions) [for governance]
  • risk_type: financial, operational, strategic, cyber [for risk]
  • risk_level: low, medium, high, critical [for risk]
  • mitigation: Mitigation plan (e.g., Implement regular audits) [for risk]
  • regulation: Regulation/standard (e.g., GDPR) [for compliance]
  • deadline: YYYY-MM-DD (e.g., 2025-06-01) [for compliance]
  • requirements: Compliance requirements (e.g., Data encryption for all customer data) [for compliance]
  • notes: Additional notes (e.g., To be reviewed by legal team)

Examples:

  • Create a GRC parameter for company ABC Corp in Risk Management on 2025-04-25 prepared by Jane Doe category governance parameter Data Privacy Policy responsible IT Department effective 2025-05-01 policy Board Oversight frequency quarterly description Ensure board approval for major decisions notes To be reviewed by legal team
  • Create a GRC parameter for company XYZ Inc in Compliance on 2025-04-26 prepared by John Smith category compliance parameter GDPR Compliance responsible Legal Team effective 2025-05-15 regulation GDPR deadline 2025-06-01 requirements Data encryption for all customer data
  • Create a GRC parameter for company DEF Ltd in IT on 2025-04-27 prepared by Alice Brown category risk parameter Cybersecurity Risk responsible Security Team effective 2025-05-10 type cyber level high mitigation Implement multi-factor authentication notes Requires budget approval

GRC Parameter Entry Form

General Details

GRC Category

Parameter Details

GRC Summary

Category Parameter Name Responsible Party Details

Help

Use the prompt to quickly fill the GRC parameter entry form. Ensure your prompt follows the specified format for accurate parsing.

Tips for Writing Prompts:

Need More Help?

Contact support at support@example.com or refer to the user manual.

Follow this prompt format:

Create a GRC parameter for company in on prepared by category parameter responsible effective [policy ] [frequency ] [description ] [type ] [level ] [mitigation ] [regulation ] [deadline ] [requirements ] [notes ]

Keywords (use exactly as shown): Create, GRC parameter, for company, in, on, prepared by, category, parameter, responsible, effective, policy, frequency, description, type, level, mitigation, regulation, deadline, requirements, notes

Values:

  • company_name: Company name (e.g., ABC Corp)
  • department: Department name (e.g., Risk Management)
  • entry_date: YYYY-MM-DD (e.g., 2025-04-25)
  • prepared_by: Name of preparer (e.g., Jane Doe)
  • grc_category: governance, risk, compliance
  • parameter_name: Parameter name (e.g., Data Privacy Policy)
  • responsible_party: Responsible entity (e.g., IT Department)
  • effective_date: YYYY-MM-DD (e.g., 2025-05-01)
  • policy: Governance policy (e.g., Board Oversight) [for governance]
  • frequency: monthly, quarterly, annually [for governance]
  • description: Description (e.g., Ensure board approval for major decisions) [for governance]
  • risk_type: financial, operational, strategic, cyber [for risk]
  • risk_level: low, medium, high, critical [for risk]
  • mitigation: Mitigation plan (e.g., Implement regular audits) [for risk]
  • regulation: Regulation/standard (e.g., GDPR) [for compliance]
  • deadline: YYYY-MM-DD (e.g., 2025-06-01) [for compliance]
  • requirements: Compliance requirements (e.g., Data encryption for all customer data) [for compliance]
  • notes: Additional notes (e.g., To be Reviewed by legal team)

Examples:

  • Create a GRC parameter for company ABC Corp in Risk Management on 2025-04-25 prepared by Jane Doe category governance parameter Data Privacy Policy responsible IT Department effective 2025-05-01 policy Board Oversight frequency quarterly description Ensure board approval for major decisions notes To be reviewed by legal team
  • Create a GRC parameter for company XYZ Inc in Compliance on 2025-04-26 prepared by John Smith category compliance parameter GDPR Compliance responsible Legal Team effective 2025-05-15 regulation GDPR deadline 2025-06-01 requirements Data encryption for all customer data
  • Create a GRC parameter for company DEF Ltd in IT on 2025-04-27 prepared by Alice Brown category risk parameter Cybersecurity Risk responsible Security Team effective 2025-05-10 type cyber level high mitigation Implement multi-factor authentication notes Requires budget approval