Compare written policies with a named framework's control list and show gaps with evidence.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this to see how written policies line up with a framework before an audit.
Name the framework and version, and the control list the user supplied. Agree the scope: which systems, teams, and period. Record the policies in the review with their versions, owners, and approval dates.
For each control show:
A policy that says a thing happens is not evidence that it does. Keep "written" and "shown working" apart.
List each gap with the control, what is missing (policy text, evidence, or both), the owner, and a suggested order based on audit dates. Give counts for each label.
Never say the company meets a framework or is ready for an audit, and do not claim a control without evidence. This is not an audit opinion or legal advice. Draft for the owners to review.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.