Best way to implement a “Contract Calendar” matrix (Client × Activity × Frequency) in Jira Software

Kirti Rajput_pytnsq

Hi Community,

I’m trying to design a Contract Calendar in Jira Software Cloud (Standard plan).
We currently maintain an Excel matrix like this:

• Rows = Clients (Bajaj, Cohizon, SEIL, etc.)

• Columns = Activities/Controls (Delivery Manager Visit, Monthly SLA/MIS report, Site Audit, CSAT, VIP user connect, etc.)

• Each cell = Frequency (Daily/Weekly/Monthly/Quarterly/Half-yearly/Yearly/NA)

Goals in Jira:

1. Create recurring tasks based on frequency (Monthly/Quarterly/Half-yearly/Yearly).

2. For some activities (e.g., Site Audit), enforce mandatory proof before closure.

   • Evidence is uploaded via Zoho form / SharePoint, so in Jira we prefer storing only a Proof Link / Submission ID (no double upload).

3. Add an approval step before final closure (Pending Approval → Done).

4. We have mixed projects (some team-managed, some company-managed), and we want one approach that works across both.

5. Avoid chaos for PMs and avoid creating thousands of issues for daily checks.

Questions:

• What is the best Jira design pattern for this?

  • Should we use a Catalog + Occurrence model (master list of controls + auto-created occurrences)?

  • How do you typically handle Daily/Weekly checks (logbook vs individual issues)?

• What is the best way to enforce proof mandatory (preferably via Proof Link field) and approval before Done on Standard plan?

• Is there a recommended way to manage “Applicable in this project/client but not in that one” without maintaining different workflows per project?

Any recommended workflow, field structure, and automation approach would really help. Thanks!

Tomislav Tobijas

Hey @Kirti Rajput ,

There are a lot of different points and views in this question but we could break it down to:

• For recurrence, you could use Jira automation - you might need to tweak it a bit, but that's the easiest way to set something like that up
• For catalog - you can maintain it as work items (or a custom issue type). Use automation to generate “occurrence” items based on the frequency field in the catalog.
  • For high-frequency checks (daily/weekly), consider using a single “logbook” item per period (e.g., per week/month)
• Related to mandatory values - you can use workflow validators combined with some custom fields 
• As for approvals, you could check this article. I haven't worked with this in company-managed spaces yet, but I believe you could build something like that. Potentially check this feature suggestion.

And for the workflows itself, you could keep it simple—statuses like To Do → In Progress → Pending Approval → Done 🤔

Hope this helps.
Happy New Year!

Tobi