Certificate Review Dates Are Workflow Triggers, Not Capacity Decisions

A passed review date tells you that the certificate record needs human attention. It does not prove that capacity, entitlement or work arrangements changed. A three-state AI queue can expose the gap without converting a document date into a claim outcome.

A certificate review date has one safe automatic consequence: it can place the record in a human review queue. It cannot restore full capacity, extend certified restrictions, end incapacity, alter payments or rewrite a recovery-at-work arrangement.

That boundary sounds obvious. It becomes fragile at scale, where payroll cut-offs, case-load pressure and dashboard traffic-lighting reward a clean status. If your system turns REVIEW DATE PASSED into NO CURRENT INCAPACITY, it has changed an evidence gap into a finding.

The better design separates three things: the document state you can observe, the evidence question that remains unresolved, and the action owned by a named person. AI can maintain that separation. A human claims professional must verify the source, decide what further information is needed and make any decision under the scheme.

What does a passed review date actually prove?

The current in-force Safety, Rehabilitation and Compensation Act 1988 is Compilation No. 82, with a compilation date of 1 July 2026. Section 19 applies to an employee who is incapacitated for work as a result of an injury, other than an employee to whom section 20, 21, 21A or 22 applies. It does not make a certificate review date a self-executing capacity finding.

Section 54 deals with making a claim. Subsection 54(2) requires a written claim in the approved form and, except where the claim is for compensation under section 16 or 17, an approved-form certificate from a legally qualified medical practitioner. Subsection 54(5) provides that strict compliance with an approved form referred to in subsection 54(2) is not required and that substantial compliance is sufficient. It does not turn a date on an ongoing certificate into present capacity or entitlement.

Comcare's current medical evidence guidance says a certificate must contain a review date and not be open-ended, and must include capacity for work and any modifications or restrictions. That makes the review date a control for evidence currency. It does not make the date a medical opinion about what happened next.

Comcare's certificate page says the form was updated in February 2026. The Certificate of Capacity form separately records the examination date, date of issue, capacity category, applicable from and to dates, estimated return-to-work date and review date. It also records functional observations and modifications. Collapsing those fields into one certificate expiry date destroys information.

Use a date vector instead:

The last field is a local control, not law or Comcare guidance. It does not change the certificate, evidence or SRC Act. That distinction matters more here than it does for the scheme's genuine statutory timeframes, where the clock is fixed by the Act. A review date sets no clock at all; your service standard is the only deadline in play, and it binds you rather than the claimant.

Comcare's Gathering claims information manual reinforces the distinction. It says a medical certificate should normally include a review date and that decision-making should focus on the practitioner's information, not format or technicalities. Where delay is reasonable, it says Comcare may, on the merits, temporarily extend a treatment plan using other current medical information, support the employee to obtain a certificate and maintain communication. That treatment-plan guidance is not a general rule continuing incapacity liability or payments. Nor is it an automatic capacity transition. The manual is Comcare operational guidance, not the Act. Licensees must map it to their own obligations, licence conditions, delegations and procedures.

This prompt extracts the date vector and document state. A human must compare every field with the original certificate and correct extraction errors before the output enters the claim record.

Extract a document-state record from the de-identified certificate for [CLAIM_NUMBER].

Source document ID: [CERTIFICATE_ID]
Source page range: [PAGE_RANGE]
System date: [SYSTEM_DATE]

Record separately:
- examination date
- issue date
- certified capacity category, copied exactly
- certified from and to dates
- review date
- hours, duties, modifications and restrictions, copied exactly
- whether each field is PRESENT, BLANK, ILLEGIBLE or NOT LOCATED
- a page and field anchor for every value

Calculate date comparisons only. Do not infer current capacity, extend a restriction, decide entitlement, change a payment, recommend duties or describe the claimant as recovered. If a relevant date has passed, write DOCUMENT DATE PASSED, CURRENT POSITION NOT ESTABLISHED. Send all output to human source verification.

How should the three-state queue work?

Do not ask the model for a single claim status. Require three columns that cannot be merged.

Observed document state contains only source-anchored facts. Examples include review date is [REVIEW_DATE], certified period ends [CAPACITY_TO_DATE], capacity category recorded as [VERBATIM_CATEGORY], and no later certificate located in [SEARCH_SCOPE] as at [SEARCH_TIME]. The last statement is a search result, not proof that no document exists anywhere.

Unresolved evidence question states what the file does not establish. Examples include current practitioner opinion after [REVIEW_DATE] is not located, two certificates overlap, the restriction field is blank, or the uploaded document has not been matched to its source. Use UNKNOWN for an unresolved fact. Do not substitute zero, no restriction, full capacity or non-compliance.

Human-owned action records an authorised next step, owner and internal due date. It may say case manager to verify controlled records, case manager to contact [CLAIMANT_NAME] under the approved communication process, or human reviewer to clarify the conflicting periods. It must not say cease payment, close entitlement, increase hours or return to pre-injury duties.

Useful queue labels include REVIEW DATE APPROACHING, REVIEW DATE PASSED, CURRENT POSITION UNKNOWN, NEW DOCUMENT UNVERIFIED, CONFLICTING DOCUMENTS and HUMAN ACTION OVERDUE. These are proposed internal workflow labels. They are not capacity categories, Comcare classifications or statutory findings.

Add two further controls. First, make the source file immutable within the AI workflow. A later certificate creates a new document-state record; it does not silently overwrite the earlier certificate. Secondly, record the search scope. A result based on the claim-management system alone should not claim that payroll, correspondence and an approved provider channel were also checked.

For a bank, insurer or other large licensee claims team, this creates a cross-system exception queue without converting absence of a document into absence of incapacity.

This prompt audits the queue for unsafe state transitions. A human control owner must review the exceptions, assign permitted actions and decide whether any procedure or decision needs to follow.

Audit the de-identified certificate exception queue for [QUEUE_DATE].

Inputs:
[QUEUE_ROWS]
[APPROVED_SEARCH_SCOPES]
[ROLE_AND_DELEGATION_MATRIX]
[LOCAL_FOLLOW_UP_STANDARD]

For each row, return three locked columns:
1. OBSERVED DOCUMENT STATE, with source anchor
2. UNRESOLVED EVIDENCE QUESTION
3. HUMAN-OWNED ACTION, owner and internal due date

Flag:
- a passed date translated into a capacity, entitlement, payment or work-arrangement outcome
- BLANK translated into NONE
- UNKNOWN translated into NO
- a newer document overwriting source history
- an action without an authorised human owner
- an internal deadline presented as legislation or Comcare policy
- a search claim wider than the recorded search scope

Do not rank claimants, predict recovery, interpret clinical meaning or select the substantive action. Return CONTROL BREACH REVIEW where a prohibited transition appears. A human control owner decides remediation.

What must never be automated?

Never connect the certificate clock directly to payment, entitlement, capacity or work-design controls. In its direct-payment guidance for people who have separated from an Australian Government agency, Comcare's income support page asks the person to provide a Medical Certificate of Capacity and to have a medical appointment booked before the current certificate expires. It also says a claims manager determines incapacity liability from medical evidence. That is not permission for a date field to make the determination.

The prohibited transitions should be explicit in your system design:

• passed review date to full capacity
• passed certified period to no entitlement
• missing later document to recovered
• blank restrictions to unrestricted duties
• conflicting certificates to whichever record arrived last
• overdue human action to adverse claimant correspondence
• low extraction confidence to a substantive claim outcome

Fictional worked example

This scenario is fictional and de-identified. Certificate [CERTIFICATE_ID_01] for [CLAIMANT_NAME] records capacity for suitable duties from [CAPACITY_START] to [CAPACITY_END], specified restrictions and a review date of [REVIEW_DATE]. [SYSTEM_DATE] is after both [REVIEW_DATE] and [CAPACITY_END]. No later certificate is located in the claim-management-system search recorded by the workflow.

The safe output is narrow. Observed state: the dates passed. Unresolved question: the supplied sources do not establish current capacity or whether later evidence exists elsewhere. Human action: [CASE_MANAGER_ROLE] checks approved channels and contacts the claimant under the controlled process by [INTERNAL_ACTION_DATE].

The unsafe output is capacity expired, followed by a payment stop or instruction to resume ordinary duties. The stated certified period ended. The person's condition has not been proved to have ended.

Later, [CERTIFICATE_ID_02] arrives with a period that overlaps the first certificate. AI may flag the overlap, copy the competing fields and preserve both sources. It cannot choose which medical opinion governs, interpret why the practitioner changed the wording or alter the claim. A human reviews the full record and takes the authorised next step.

Do this Monday

1. Split the dates. Replace the single expiry field in your queue with examination date, issue date, certified period, review date and internal action date.
2. Install the three columns. Require observed state, unresolved question and human-owned action for every exception.
3. Ban automatic outcomes. Test that no certificate date can stop a payment, change capacity, alter duties, close entitlement or send adverse correspondence.
4. Preserve source history. Store each certificate as a separate evidence object with document ID, page anchors, search scope and human verification status.
5. Name local controls. Label follow-up lead times and service standards as internal settings, then keep them separate from the Act and Comcare guidance.
6. Run fictional failure tests. Include late, overlapping, duplicated, incomplete and illegible certificates, plus a state certificate that may meet the SRC Act requirements but is not Comcare's preferred form.

Bottom line

A review date is a prompt to inspect the evidence, not a finding about the person. AI can build a precise exception queue when document state, unresolved questions and human action remain separate. The strongest control is simple: no date changes a substantive claim state without verified evidence and an authorised human decision. If your workflow cannot preserve that boundary, it should not touch certificate monitoring.

This article is general information and education only. It is not legal advice, and it is not advice about any individual claim. Decisions under the Safety, Rehabilitation and Compensation Act 1988 are made by human decision-makers on the individual merits of each claim, and claimants have reconsideration and review rights in respect of determinations. Seek advice specific to your scheme and circumstances.

References

1. Federal Register of Legislation, Safety, Rehabilitation and Compensation Act 1988, Compilation No. 82, compilation date 1 July 2026. https://www.legislation.gov.au/C2004A03668/latest/text
2. Comcare, Certificate of capacity. https://www.comcare.gov.au/claims/assessing-claims/certificate-of-capacity
3. Comcare, Certificate of Capacity for Work form, updated February 2026. https://www.comcare.gov.au/sites/default/files/docs/certificate-of-capacity-form.pdf
4. Comcare, Medical evidence. https://www.comcare.gov.au/claims/assessing-claims/medical-evidence
5. Comcare, Claims Manual - Gathering claims information, Comcare Claims Manual current as at 2 December 2025. https://www.comcare.gov.au/sites/default/files/2026-03/Claims%20Manual%20-%20Gathering%20claims%20information_0.pdf
6. Comcare, Income support. https://www.comcare.gov.au/claims/supports-benefits/income-support