integration verification log

Read, adapt, then use privately

Download the plain-text file or copy the text below into your own editor. Replace the fictional examples with your own plan. Keep personal, customer and confidential information in systems approved for that information. This page never uploads your completed worksheet or imports it into a workspace.

INTEGRATION VERIFICATION LOG
Companion guide: https://quadrant.works/guides/calendar-slack-integration-status

This is a private manual worksheet, not an import file or a completed test report.
Use a low-stakes example. A Slack test posts a visible message; a calendar change
can notify people. Perform either only when appropriate and authorized.

DO NOT RECORD passwords, tokens, webhook URLs, private calendar feed links,
invitation links, or confidential task descriptions. Redact screenshots.

CHECK CONTEXT
Date and time, including timezone:
Provider:
Workspace label (non-sensitive):
Connection owner:
Intended account / destination label (avoid full identifiers if unnecessary):
Visible connection status:
Last activity time shown:
Issue in one sentence:

EVIDENCE LADDER
[ ] Requested: an access request exists; not proof of connection.
[ ] Connected/configured: intended account or destination confirmed.
[ ] Provider accepted this specific operation.
[ ] Result observed in the intended destination.
[ ] Human acknowledgement obtained, only if the workflow requires it.

SLACK VERIFICATION
Is one visible test appropriate for this destination? Yes / No
Who approved or initiated it?
Send test time:
Safe response text:
Message visible in intended workspace and channel? Yes / No / Not checked
Observed time:
Remaining reminder-specific questions (timing, channel, task status):

CALENDAR VERIFICATION
Use a neutral task label:
Calendar account and scope checked? Yes / No
Task allocation:
Task due date and governing timezone:
App block start / end:
Provider event start / end:
Preceding event end:
Following event start:
Gap before action block (minutes):
Gap after action block (minutes):
Absence/OOO checked? Yes / No
Stale app-owned block observed? Yes / No / Unknown
Do not bulk-delete events by color or sender.

CONCLUSION
Strongest evidence actually observed:
What remains unverified:
Temporary failure or action required?
Next safe action:
Action owner:
Review time:
Private support reference, if any (no secrets):

REMEMBER
Provider acceptance is not a read receipt. Calendar color is not proof of
availability or synchronization. A single test proves one path at one moment,
not every future delivery. Keep this worksheet private and delete it according
to your organization's retention policy when no longer needed.

Permission: you may copy and adapt this Critical Path worksheet for personal or internal team planning. No account, payment or attribution is required. Product links are optional; using the template is not enrollment in a service.