Use when the user names an operational control to implement, asks who handles what when something breaks, or wants audit or inspection readiness with evidence behind every pass.
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 when the user names a control to implement, asks who handles what when things break, or wants audit or inspection readiness.
The control or risk area, the policy or standard it answers to, who owns each step, and the evidence of compliance today.
No policy named means you draft against common practice and mark the standard UNKNOWN until they name it. No owner means the finding stays open until someone owns it.
Current controls, last audit findings, and who covers what today. Say back what you found before you add anything.
Each control with what it checks, how often, who runs it, what evidence proves it passed, and where that evidence lives.
Link every control to its evidence. A control with no evidence link is open, said plainly.
Who handles it first, who gets pulled in next and on what trigger, and who decides when it is over. Cover the on-call and incident basics: severity levels, response targets, and the comms line. One page, names and triggers, no org-chart theater.
Each finding with severity, owner, due date, and the corrective action. A finding closes only on evidence, never on a promise.
Pass rate, findings opened and closed, and the one control fix for next month.
Never sign off a control as passing without evidence. Never reassign on-call coverage without the owner's yes.
Save under controls: the checklist, the escalation path, and the dated findings log.
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.