Governance documents · Gixo Lex
Company Policy Template Builder
Create a governed internal policy with ownership, approval, review dates, exceptions, and revision history.
What a company policy template has to contain
A policy that states only the rules is unenforceable six months later: nobody can say which version applied on a given day, who approved it, or when it was last looked at. The fields below are the governance record a real company policy carries, and the next review date is calculated from the effective date and the review cycle rather than left blank.
- Title and policy type — information security, privacy, acceptable use, records, operations or custom. The type is recorded on the face of the policy; it does not restrict what the statements can say.
- Owner and approver — two different people. The owner maintains the policy; the approver is who signed it off.
- Version and effective date — the first thing an auditor asks for: which text was in force, and from when.
- Review cycle — the next review date is computed from the effective date, so the policy carries its own expiry.
- Scope and purpose — who the policy binds, and the outcome it exists to produce.
- Policy statements — one requirement per row, each with the rationale that outlives the person who wrote it.
- Roles and responsibilities — the named jobs that have to do something for the policy to hold.
- Exception route — how someone obtains a recorded exception instead of quietly ignoring the rule.
- Consequences — what happens when the policy is breached.
- Related documents and revision history — the surrounding set, and the change record from version 1.0 onward.
Policy and procedure template
A policy says what must be true; a procedure says how it is done. The policy-statement rows take one requirement each, and the roles and responsibilities field takes the ordered steps with the job title that performs them, so a single governed document can carry both without blurring which is which.
Document inputs
Required gaps remain visible as [ ], so the downloaded handoff never silently hides unfinished work.
Need a different artifact?
Browse all 12 governed builders on the public template hub, or use the smaller checkers on the free tools hub.
Details
Company Policy Template Builder details
See the accepted inputs, generated sections, output formats, and important limits.| Topic | Details | What to know |
|---|---|---|
| Inputs | 15 fields across 6 groups | Every field required by this template is shown before generation. |
| Required inputs | 12 required fields | Unfilled required values remain visible instead of being silently invented. |
| Repeatable sections | 2 repeatable sections | Templates without a row field render each field once. |
| Outputs | HTML, Markdown, embed snippet, and print-ready HTML | Every output is generated from the same validated field values. |
Do I need an account to use Company Policy Template Builder?
No. The builder runs without an account.
Does the builder invent missing information?
No. Required gaps remain visibly marked for review.
Is my document stored?
No. The public builder does not save the submitted field values.
Which formats can I download?
The public result supports HTML and Markdown downloads, an embed snippet, and print-to-PDF through the browser.
What should a company policy include?
Scope, purpose, the policy statements themselves, a named owner and a named approver, a version and effective date, a review cycle, an exception route, the consequences of breach, and a revision history. The governance fields are required here: leave one out and the built policy carries it as [ ] with a warning, rather than quietly issuing a policy nobody approved.
What is the difference between a policy and a procedure?
A policy sets the rule and who is accountable for it; a procedure sets the steps that satisfy the rule. Policies change rarely and are approved at a senior level. Procedures change whenever the tooling does, which is why they are kept separate from the policy that authorises them.