What sections does the generated policy include?

The prompt asks for purpose, scope and applicability, definitions, the policy statement and rules, roles and responsibilities, enforcement and consequences, exceptions, and a review schedule — the structure most organizational policies follow.

Does specifying jurisdiction make the policy compliant?

It tells the model to align the policy with the named jurisdiction's expectations and to flag where legal review is required, but it does not produce legally binding or compliant text on its own. A qualified professional must review any policy before adoption.

Why set the organization size?

A two-person startup and a 5,000-person enterprise need very different policies. Size tells the model how formal, detailed, and role-heavy to make the policy so it is proportionate rather than over- or under-engineered.

What enforcement mechanisms can I specify?

Options like progressive discipline, automatic system controls, manager discretion, or audit-and-report. The model then writes an enforcement section consistent with the mechanism you chose.

Is anything sent to a server?

No. The prompt is built entirely in your browser. Nothing is uploaded or stored.

Policy Writing Prompt Builder

Policy writing prompt builder

Organizational policies have a predictable anatomy — purpose, scope, definitions, the rules themselves, who’s responsible, how it’s enforced, and when it’s reviewed. Ask an LLM for “a remote work policy” and you’ll get prose that’s missing half of those sections. The policy writing prompt builder produces a prompt that demands the full structure, calibrated to your organization, so the model returns a usable first draft. It runs entirely in your browser, no API key.

How it works

You select a policy type, set the organization size, name the jurisdiction, choose an enforcement mechanism, and set a review cycle. The builder then composes a prompt instructing the model to draft a policy with:

Purpose and scope/applicability (who and what it covers).
Definitions of key terms used in the policy.
The policy statement and rules — the substantive content.
Roles and responsibilities for the people who administer and follow it.
Enforcement consistent with your chosen mechanism, plus an exceptions process.
A review schedule on your chosen cycle, with an owner.

It also tells the model to respect the named jurisdiction and flag anything that needs legal review.

Tips and examples

Match formality to size: for a small team, ask for a concise one-page policy; for a large organization, the prompt’s full section structure produces the rigor auditors expect. Always set the jurisdiction even approximately (“UK / GDPR”, “California / CCPA”) — it changes definitions, data-handling language, and employee rights sections. Treat the output as a first draft, never a final document: the prompt instructs the model to flag where legal counsel must review, and that flag is there for a reason. For sensitive policies (data protection, harassment, financial controls), human and legal review before adoption is non-negotiable.