Months after a request was closed, someone asks a simple question. Was this person’s access really removed? Was this change approved before it went live? The request says Done. The answer is spread across comments, attachments, approvals and other systems, and the agent who handled it may have moved on.
An evidence handoff is a short page, written when the request closes, that answers those questions in one place. This article gives you a blank template, a filled example and the wording for the parts that are hardest to write: the gaps.
A closed request is not an evidence handoff
A status is a workflow fact. It says the work moved to its last step. It doesn’t say how anyone knows the work was right, or what nobody looked at.
| Question someone asks later | What a closed request shows | What the handoff adds |
|---|---|---|
| Did the work finish? | Yes: the status and its date | The same, in one sentence |
| What exactly was checked? | Spread across comments and linked work items | A list, with where each record is |
| What could not be checked? | Usually nothing, or one comment | Its own section, with the reason |
| Who accepted a gap, and why? | Not recorded | A named role, a date and the reason |
| Can someone read it without the agent? | Rarely | That is its purpose |

Each section of the handoff answers one question a later reader will ask.
A handoff doesn’t make the work better than it was. It makes the record match the work, including its weak spots. A handoff that says “two things could not be checked, and here is why” is more useful than a clean one that hides them.
When you need one
Most requests don’t need a handoff. The request itself is enough when one team did the work, the proof is on the request and nobody outside the team is likely to ask.
Write one when:
- the request crossed teams, such as an offboarding with HR, IT and app owners;
- someone outside the team will read it later, such as a security reviewer, an auditor or HR;
- part of the proof lives outside Jira, in an identity provider, an HR system or a device record;
- something could not be checked, or a step was skipped on purpose.
If you already know someone will ask what was checked, write the handoff before they ask, while the people and records are still easy to reach.
What Jira already records
Start from what Jira Service Management keeps for you, and use the handoff to point at the rest.
- The request’s activity. The activity section has views for comments, history (field changes and workflow moves), work log and approvals. Atlassian describes the approvals view as showing “who was involved in approvals, when they approved (or declined) requests”.
- Exports. From a work item search, the more actions menu (•••), then Export, offers CSV, Word, XML and print. Atlassian says the Word export includes the description, comments and all other work item data. Its list of exported data doesn’t include the change history, so write the key dates into the handoff rather than relying on an export to keep them.
- The Jira audit log. It records configuration changes that affect users and spaces, for people with the Administer Jira permission. It isn’t available if all your Jira apps are on the Free plan.
- The organization audit log. In Atlassian Administration it needs Atlassian Guard (Standard or Premium) or an Enterprise plan, and keeps up to 180 days of events.
- Everything outside Jira. Jira only knows what someone wrote or attached about the identity provider, the HR system or a laptop. The handoff should name those records and their references, not pretend the request holds them.
Sources: Atlassian, View the different types of activity on a work item, Export search results, Audit activities in Jira and View audit log activities, checked 13 October 2026.
The template
Copy it as it is. Keep the headings even when a section is empty: “None” is an answer.
EVIDENCE HANDOFF
1. REQUEST
Key and summary:
Request type and space:
What it covers: (person, system or change; only the
personal data the reader needs)
Opened: Closed:
2. OUTCOME
What was done, in one or two sentences:
3. WHAT WAS CHECKED
Item | Record, and where it is | Checked by (role) | When
- | | |
- | | |
4. WHAT COULD NOT BE CHECKED
Item | Status | Reason | Effect on the outcome
- | | |
Status words: Not checked / Not available / Outside this request /
Still open
5. DECISION
Gaps accepted: Yes / No / There were none
Accepted by (role), date:
Why that was acceptable:
6. WHERE EVERYTHING IS
Linked work items:
Attachments or pages:
Records outside Jira: (system and reference, not copies)
7. WRITTEN BY
Role, date:
How to fill it in
- Name the record, not the feeling. “The user’s page in Atlassian Administration showed no app access on 2 Oct at 17:05” can be checked again. “Access verified” can’t.
- Use the same four words for gaps. Not checked: a record exists, but nobody looked. Not available: the record doesn’t exist or can’t be retrieved. Outside this request: another team or process owns it, and you say which. Still open: it isn’t finished yet, and you say where it is tracked.
- Keep facts and decisions apart. Sections 3 and 4 are facts. Section 5 is a decision someone made about those facts. A reader should be able to disagree with the decision without having to doubt the facts.
- Point, don’t copy. Give the reference of an HR record or a device record. Don’t paste personal details into Jira.
- Say the effect of each gap. Does it change the outcome, or only what you can show? “We can show she has no access now, not which groups she was in” is a precise limit.
- Write it before you close the request, while the people involved can still answer a question.
Worked example: an employee offboarding
This is the closing record for the fictional offboarding in the offboarding checklist for IT and HR. Sample data: fictional company, people and keys.
EVIDENCE HANDOFF
1. REQUEST
Key and summary: HR-214, Maya Chen
Request type and space: Offboarding, People Services
What it covers: Departure of one finance analyst; access,
devices, badge, final pay
Opened: Mon 21 Sep 2026 Closed: Wed 7 Oct 2026
2. OUTCOME
Atlassian access removed and the identity provider account turned
off on her last day (Fri 2 Oct). Laptop returned, badge turned off,
final pay run. Two limits below.
3. WHAT WAS CHECKED
Item | Record, and where it is | By | When
Atlassian access | User page, Atlassian Administration | Jira admin | 2 Oct 17:05
Open work items | Jira search, 0 assigned to her | Jira admin | 2 Oct 16:10
Laptop | Asset record LT-0457 | IT lead | 5 Oct
Badge | Security system, FAC-310 | Facilities | 6 Oct
4. WHAT COULD NOT BE CHECKED
Item | Status | Reason | Effect
Groups before removal | Not available | Not written down before | We can show no
| | removal; the organization | access now, not
| | audit log is not on our | which groups she
| | plan | was in
Finance app access | Not checked | Removal confirmed by the | Relies on the
| | app owner on FIN-77; not | owner's word
| | checked in the app |
Identity provider record | Not checked | Only a screenshot on | Relies on a
| | ITS-881; no record from | screenshot
| | the system itself |
5. DECISION
Gaps accepted: Yes
Accepted by, date: IT service owner, Wed 7 Oct 2026
Why that was acceptable: Access is gone everywhere we checked, and
the finance app owner confirmed removal in
writing. The gaps limit what we can show
later.
6. WHERE EVERYTHING IS
Linked work items: ITS-881, ITS-882, FIN-77, FAC-310
Attachments or pages: Identity provider screenshot on ITS-881
Records outside Jira: HR system, leaver reference HRS-5521;
payroll reference PAY-1093
7. WRITTEN BY
Jira admin, Wed 7 Oct 2026
Notice what the example doesn’t do. It doesn’t say “fully verified”, and it doesn’t bury the group history gap in a comment. It also doesn’t overstate the gap: the person’s access is gone, and the handoff says so.
Wording for common gaps
Reusable sentences for section 4. Replace the parts in brackets.
[Item] was not written down before [change]. We can show [what is
visible now], not [what was true before].
Removal in [app] was confirmed by its owner on [task key]. It was not
checked in [app] itself.
[Record] is kept in [system], outside Jira, under reference [ref].
It is not attached to the request.
[Task key] was still open when the request closed. It is due
[date] and owned by [team].
The approval on [request key] was given after the change was marked
done. [Who] gave it as an emergency approval on [date].
[Item] is owned by [team or process] and is outside this request.
See [key or page].
The readback test
Before you call the handoff finished, give it to someone who wasn’t involved and ask them to say back, in their own words:
- which request and which person or system it covers;
- what was checked, and where they would find each record;
- what wasn’t checked, and why;
- who accepted that, and why it was acceptable.
If they have to ask you anything, the answer belongs in the handoff. The test also works the other way: if the handoff is so cautious that the reader can’t tell what was actually checked, it is just as hard to use as one that hides the gaps.
Common mistakes
- Treating Done as proof. Done is a workflow state. The handoff says what supports it.
- Leaving gaps in a comment. Comments are easy to skim past. A gap belongs in section 4, where every reader looks.
- Handing over fragments. A PDF of the request, a screenshot and a spreadsheet can each be accurate and still not tell the story. The handoff is the page that connects them.
- Copying personal data. Point to the HR record; don’t paste it.
- Promising more than the record shows. Avoid “audit-ready” or “fully verified”. Describe what was checked and let the reader judge.
How RequestOps helps
RequestOps can produce part of section 3 for you, from what Jira already knows.
- Evidence summary. On a request’s History tab, Evidence summary opens a short page with the request’s details, each checklist item as done or open, the approvals with who decided and when, service levels, and the key timeline of status changes, assignments, approvals and closing. It ends with a verification code that shows the summary was not changed, and you can copy it as text to attach or paste. It covers only requests you can see in Jira, and comment text is not part of the downloads.
- Record proof for a change. The Change evidence checklist template checks the parts of a change that are easy to get wrong. Approved before the change was marked done is done only if an approval came before the request reached Done. Approver is not the person doing the work checks that no approver is the assignee or the person who raised the request. Two more items watch the test plan and rollback plan fields. If the approvals can’t be read, the item isn’t marked done.

The Evidence summary for one sample request, with the timeline shortened here. It covers what Jira records; sections 4 and 5 of the handoff are still yours to write. Sample data.
The Evidence summary is built from what Jira records. RequestOps doesn’t collect records from your identity provider, HR system or other apps, and it doesn’t decide whether a gap is acceptable. The setup guides are Record proof for a change and Request history and export.