One approval, fully supported.
Here’s one record from Cedar Cloud Software’s fictional Toolkit: the use is disclosed, the evidence is attached, the decision states its reason, and the follow-up has an owner and a date. The leadership report is built from the same record.
See the full sample reportFictional example. Review your own report before sharing.
01 Disclosure
Product lead disclosed DocsDraft
- Date
- Oct 8, 2026
- Purpose
- Draft documentation from public product information
- Information
- Published release notes and synthetic examples
02 Evidence
Vendor assessment attached
- Vendor assessment
- Attached
- Information boundary
- Published release notes and synthetic examples
03 Decision with a reason
Approved with conditions by the engineering manager
- Reason
- Vendor assessment attached and inputs limited to published release notes and synthetic examples.
- Condition
- Product owner checks actual behavior and avoids unsupported security or AI claims.
04 Follow-up
Two contractors have not confirmed personal assistants or repository connections
- Owner
- Engineering manager
- Due
- Oct 22, 2026
Example of a gap the kit flags
CodeDraft · Approved with conditions
! No vendor assessment or reason recorded
Next action: attach the vendor assessment, or record why the use is approved without one, before relying on this approval. Owner: Engineering manager.
Also open: A suggested dependency still needs provenance and license review. Owner: Engineering manager, due Oct 22, 2026.