Ready-to-Use Templates

Folderit’s Document Template Library gives you ready-to-use examples for common business documents. Each template pack includes an ODT file for Document Generator, a completed PDF example and an editable DOCX example.

You can use a template exactly as provided or adapt its wording, branding, fields and layout. The guides below show the recommended eForm settings and every field required by the supplied ODT template, so no technical knowledge is needed.

Important: These are practical starting points. The Mutual NDA and Employment Offer Letter require review by a qualified professional for your jurisdiction and circumstances. Operational templates should be checked against your internal policies and applicable requirements.

What each download is for

Download	How to use it
ODT template	Upload this file when you create the document-generation template in Folderit. Edit this file when you want to change the layout, wording or branding.
Completed PDF example	Use this to see what a finished, fixed-layout document can look like.
Editable DOCX example	Use this to see the editable output produced from the same template and sample data.
Complete template pack	Download all three files for that template together.

What is a slug? A slug is the form field’s internal name, such as candidate_full_name. It connects the eForm field to the matching placeholder in the ODT template. Enter it exactly as shown in the field table.

Choose a template

Select a template below. Each section contains direct downloads, form settings, exact fields and Document Generator settings.

Template	Best for	Category	Downloads
Mutual Non-Disclosure Agreement	Generate a balanced two-way confidentiality agreement when both parties may share sensitive business information.	01 Agreements and Contracts	Open Folderit pack
Employment Offer Letter	Generate a clear written offer summarizing the proposed role, start date, compensation and key conditions before the full employment agreement is signed.	02 Human Resources	Open Folderit pack
Training Completion Certificate	Generate a polished certificate confirming that a named participant completed a course, program or compliance activity.	03 Training and Certificates	Open Folderit pack
Equipment Handover Form	Record which equipment was handed to a worker or contractor, its condition, responsibilities and expected return arrangements.	02 Human Resources	Open Folderit pack
Incident Report	Capture the facts, impact, immediate response and follow-up actions for a workplace, service, security or operational incident.	04 Operations and Compliance	Open Folderit pack

How to use any template

1. Choose and download the ODT template. The ODT file is the file you upload into Folderit Document Generator.
2. Create the eForm. Open the relevant template section below and add the recommended fields using the exact underscore-based slugs.
3. Add the document-generation template. Connect it to the eForm, enter the recommended generated file name, choose PDF and/or DOCX, and upload the ODT file.
4. Create a test record. Fill in the form using the example values and save it.
5. Generate and check the document. You can store it in Folderit, download it or email it. A stored document can also be used in workflows.

For screenshots and the complete feature walkthrough, see How to Create Documents from eForm Data.

How to customize a template

Open the downloaded ODT file in LibreOffice Writer or another editor that saves ODT files. You may change the logo, colors, fonts, headings, static wording, signature blocks, tables, spacing and footer.

• To keep an existing field: leave its complete placeholder unchanged, for example {{ candidate_full_name }}.
• To add a field: add it to the eForm with an underscore-based slug, save the form, copy the exact placeholder shown in Folderit’s Available form fields table, and paste it into the ODT template.
• To remove a field: remove its placeholder and any surrounding wording from the ODT. You may then remove the field from the eForm if it is no longer needed.
• To change a generated file name: use ordinary text together with placeholders from the same eForm.
• After any change: upload the revised ODT and generate test PDF and DOCX files before production use.

Placeholder rule: copy placeholders from Folderit. Do not guess their spelling and do not split a placeholder across lines or apply different formatting to only part of it.

Mutual Non-Disclosure Agreement

Generate a balanced two-way confidentiality agreement when both parties may share sensitive business information.

Download the complete template pack or browse this template folder in Folderit.

Local legal review required: This jurisdiction-neutral template is a general business example, not legal advice. Confidentiality, remedies, governing-law, competition, employment, privacy and trade-secret rules vary. Have qualified local counsel review the wording and completed agreement before relying on it.

Recommended eForm settings

Setting	Recommended value
Form name	Mutual NDA
Form title	Create a Mutual Non-Disclosure Agreement
Description	Enter the legal party details, purpose, dates, confidentiality periods and governing-law information required for the agreement.
Record identifier pattern	NDA - {agreement_reference}
Submit button text	Create NDA record

Show all 19 eForm fields

Create the fields in the order shown. Enter each slug exactly, including underscores. You may change labels and suggested values, but the ODT placeholders must continue to match the form-field slugs.

Field label	Slug	Type	Required	Example	What to enter
Agreement reference	agreement_reference	Text	Yes	NDA-2026-014	Use a unique internal reference.
Party A legal name	party_a_legal_name	Text	Yes	Northstar Analytics OÜ	Enter the complete registered legal name.
Party A registration number	party_a_registration_number	Text	No	14987654	Use the official company or organization number.
Party A registered address	party_a_address	Textarea	Yes	Narva mnt 7, 10117 Tallinn, Estonia	Enter the full registered address.
Party A signatory name	party_a_signatory_name	Text	Yes	Elena Saar	Person authorized to sign for Party A.
Party A signatory title	party_a_signatory_title	Text	Yes	Managing Director	Signatory's role or title.
Party A notice email	party_a_notice_email	Email	Yes	legal@northstar.example	Email for formal agreement notices.
Party B legal name	party_b_legal_name	Text	Yes	Blue Harbor Systems Ltd	Enter the complete registered legal name.
Party B registration number	party_b_registration_number	Text	No	09876543	Use the official company or organization number.
Party B registered address	party_b_address	Textarea	Yes	25 Harbour Street, Dublin 2, Ireland	Enter the full registered address.
Party B signatory name	party_b_signatory_name	Text	Yes	Aoife Murphy	Person authorized to sign for Party B.
Party B signatory title	party_b_signatory_title	Text	Yes	Chief Operating Officer	Signatory's role or title.
Party B notice email	party_b_notice_email	Email	Yes	legal@blueharbor.example	Email for formal agreement notices.
Permitted purpose	permitted_purpose	Textarea	Yes	Evaluate a possible integration and commercial partnership between the parties.	Describe the limited reason for sharing information.
Effective date	effective_date	Date	Yes	15 August 2026	Date the agreement starts.
Disclosure period in years	disclosure_period_years	Number	Yes	3	How long disclosures may be made under the agreement.
Confidentiality period in years	confidentiality_period_years	Number	Yes	5	How long confidentiality obligations continue after each disclosure.
Governing law	governing_law	Text	Yes	Laws of Estonia	Have local counsel confirm the appropriate law.
Courts or dispute forum	dispute_forum	Text	Yes	Courts of Tallinn, Estonia	Have local counsel confirm the appropriate forum.

Document Generator settings

Setting	Recommended value
Template name	Mutual NDA
Generated file name	Mutual NDA - {{ party_a_legal_name }} - {{ party_b_legal_name }} - {{ agreement_reference }}
Available output formats	PDF and DOCX
ODT template file	Mutual NDA – Template.odt

After saving the document-generation template, create a test record using the example values above. Generate both PDF and DOCX once, then check the wording, page breaks, long values and empty optional fields before real use.

Return to the template list ↑

Employment Offer Letter

Generate a clear written offer summarizing the proposed role, start date, compensation and key conditions before the full employment agreement is signed.

Download the complete template pack or browse this template folder in Folderit.

Local legal review required: This template is a non-binding, jurisdiction-neutral example and is not legal, tax, immigration or employment advice. Local laws may require specific disclosures, terms, languages, collective-agreement references or a separate employment contract. Obtain local professional review before use.

Recommended eForm settings

Setting	Recommended value
Form name	Employment offer
Form title	Create an Employment Offer Letter
Description	Enter the employer, candidate, role, compensation and offer-condition details used in the letter.
Record identifier pattern	Offer - {offer_reference} - {candidate_full_name}
Submit button text	Create offer record

Show all 23 eForm fields

Create the fields in the order shown. Enter each slug exactly, including underscores. You may change labels and suggested values, but the ODT placeholders must continue to match the form-field slugs.

Field label	Slug	Type	Required	Example	What to enter
Offer reference	offer_reference	Text	Yes	OFF-2026-027	Use a unique internal reference.
Employer legal name	employer_legal_name	Text	Yes	Northstar Analytics OÜ	Registered employer name.
Employer address	employer_address	Textarea	Yes	Narva mnt 7, 10117 Tallinn, Estonia	Registered or principal business address.
Candidate full name	candidate_full_name	Text	Yes	Sofia Lindberg	Use the candidate's full legal name.
Candidate address	candidate_address	Textarea	Yes	Kalevankatu 18 B 12, 00100 Helsinki, Finland	Address used for the offer.
Candidate email	candidate_email	Email	Yes	sofia.lindberg@example.com	Email used for offer communication.
Position title	position_title	Text	Yes	Senior Customer Success Manager	Official proposed role title.
Department	department	Text	Yes	Customer Success	Team or department.
Reports to	reports_to	Text	Yes	Director of Customer Success	Manager name or role.
Work location	work_location	Text	Yes	Helsinki, Finland (hybrid)	Primary work location or arrangement.
Employment type	employment_type	Select	Yes	Full-time, indefinite-term	Choose the proposed arrangement. Options: Full-time, indefinite-term, Full-time, fixed-term, Part-time, Other
Proposed start date	start_date	Date	Yes	1 October 2026	Expected first day, subject to conditions.
Salary amount	salary_amount	Number	Yes	68000	Gross salary amount without currency symbols.
Salary currency	salary_currency	Select	Yes	EUR	Currency used for the salary. Options: EUR, USD, GBP, CAD, AUD, Other
Pay period	pay_period	Select	Yes	year	Frequency represented by the salary amount. Options: year, month, hour, other
Working hours	working_hours	Text	Yes	37.5 hours per week	Normal proposed working hours.
Probation period	probation_period	Text	Yes	Six months, subject to applicable law	Use wording approved for the jurisdiction.
Benefits summary	benefits_summary	Textarea	Yes	Private health coverage, annual learning allowance and company pension contributions, subject to plan terms.	Summarize benefits without replacing official plan documents.
Offer conditions	offer_conditions	Textarea	Yes	Proof of right to work, satisfactory reference checks and signature of the definitive employment agreement.	State conditions that must be satisfied.
Offer expiry date	offer_expiry_date	Date	Yes	22 August 2026	Deadline for accepting the offer.
Employer signatory name	employer_signatory_name	Text	Yes	Elena Saar	Authorized employer representative.
Employer signatory title	employer_signatory_title	Text	Yes	Managing Director	Representative's role.
Governing jurisdiction	governing_jurisdiction	Text	Yes	Finland	Jurisdiction for local review and definitive contract.

Document Generator settings

Setting	Recommended value
Template name	Employment Offer Letter
Generated file name	Employment Offer - {{ candidate_full_name }} - {{ offer_reference }}
Available output formats	PDF and DOCX
ODT template file	Employment Offer Letter – Template.odt

After saving the document-generation template, create a test record using the example values above. Generate both PDF and DOCX once, then check the wording, page breaks, long values and empty optional fields before real use.

Return to the template list ↑

Training Completion Certificate

Generate a polished certificate confirming that a named participant completed a course, program or compliance activity.

Download the complete template pack or browse this template folder in Folderit.

Review before production use: This is a general certificate example. Confirm the wording, issuer authority, course requirements, validity period and any regulatory statements against your training policy and applicable accreditation or compliance rules before issuing certificates.

Recommended eForm settings

Setting	Recommended value
Form name	Training completion
Form title	Create a Training Completion Record
Description	Enter the participant, course, issuer, result and validity information used on the certificate.
Record identifier pattern	Certificate - {certificate_id} - {participant_full_name}
Submit button text	Create completion record

Show all 12 eForm fields

Create the fields in the order shown. Enter each slug exactly, including underscores. You may change labels and suggested values, but the ODT placeholders must continue to match the form-field slugs.

Field label	Slug	Type	Required	Example	What to enter
Certificate ID	certificate_id	Text	Yes	CERT-2026-014	Use a unique certificate reference.
Participant full name	participant_full_name	Text	Yes	Maria Tamm	Name exactly as it should appear on the certificate.
Course or program title	course_title	Text	Yes	Workplace Information Security Essentials	Official course or program name.
Completion date	completion_date	Date	Yes	28 July 2026	Date the participant completed the requirements.
Training duration	training_duration	Text	Yes	6 hours	Duration shown on the certificate.
Result or achievement	result_or_achievement	Text	Yes	Successfully completed	For example: Successfully completed or Passed with distinction.
Instructor name	instructor_name	Text	Yes	Dr. Laura Niemi	Instructor, assessor or responsible trainer.
Issuer organization	issuer_organization	Text	Yes	Northstar Learning Institute	Organization issuing the certificate.
Issue date	issue_date	Date	Yes	30 July 2026	Date the certificate is issued.
Validity statement	validity_statement	Text	Yes	Valid until 28 July 2028	Use 'Does not expire' when appropriate.
Authorized signatory	authorized_signatory	Text	Yes	Dr. Laura Niemi	Name shown under the signature line.
Signatory title	signatory_title	Text	Yes	Director of Training	Title shown under the signatory name.

Document Generator settings

Setting	Recommended value
Template name	Training Completion Certificate
Generated file name	Certificate - {{ participant_full_name }} - {{ course_title }} - {{ certificate_id }}
Available output formats	PDF and DOCX
ODT template file	Training Completion Certificate – Template.odt

After saving the document-generation template, create a test record using the example values above. Generate both PDF and DOCX once, then check the wording, page breaks, long values and empty optional fields before real use.

Return to the template list ↑

Equipment Handover Form

Record which equipment was handed to a worker or contractor, its condition, responsibilities and expected return arrangements.

Download the complete template pack or browse this template folder in Folderit.

Review before production use: Review this form against your asset-management, information-security, health-and-safety, employment and return-of-property policies. It is an operational example and does not replace local legal or HR advice.

Recommended eForm settings

Setting	Recommended value
Form name	Equipment handover
Form title	Record an Equipment Handover
Description	Enter recipient, equipment, condition, security and return details. This starter uses one multiline equipment field so it works without custom repeating-row syntax.
Record identifier pattern	Equipment handover - {handover_reference} - {recipient_full_name}
Submit button text	Create handover record

Show all 16 eForm fields

Create the fields in the order shown. Enter each slug exactly, including underscores. You may change labels and suggested values, but the ODT placeholders must continue to match the form-field slugs.

Field label	Slug	Type	Required	Example	What to enter
Handover reference	handover_reference	Text	Yes	EH-2026-0031	Use a unique internal reference.
Organization name	organization_name	Text	Yes	Northstar Analytics OÜ	Organization providing the equipment.
Recipient full name	recipient_full_name	Text	Yes	Markus Tamm	Employee or contractor receiving the equipment.
Recipient ID	recipient_id	Text	Yes	EMP-0142	Employee, contractor or personnel number.
Department or project	department_or_project	Text	Yes	Field Operations	Owning team, department or project.
Manager	manager_name	Text	Yes	Liisa Kask	Responsible manager.
Handover date	handover_date	Date	Yes	3 August 2026	Date the equipment is transferred.
Expected return	expected_return	Text	Yes	On request or on the final day of engagement	Date or return trigger.
Equipment items	equipment_items	Textarea	Yes	Laptop: Dell Latitude 7450, asset LT-0842, serial DL7450-88421, good condition Dock: Dell WD22TB4, asset DK-0311, serial WD22-31984, good condition Phone: iPhone 15, asset PH-0218, serial F2LX91Q7, new condition	Enter one item per line, including description, asset tag, serial number and condition.
Accessories included	accessories_included	Textarea	Yes	Laptop charger, USB-C cable, headset, protective phone case	List chargers, cases, adapters and other accessories.
Condition summary	condition_summary	Textarea	Yes	All items tested and operational. Laptop lid has one small cosmetic mark.	Record existing damage and test status.
Security requirements	security_requirements	Textarea	Yes	Use the equipment only for authorized work, protect credentials, install no unapproved software and report loss or damage immediately.	Summarize applicable security duties.
Return requirements	return_requirements	Textarea	Yes	Return all items and accessories in reasonable condition, allowing for normal wear, and cooperate with secure data return or removal.	State how and when items must be returned.
Additional notes	additional_notes	Textarea	No	Device enrollment and multi-factor authentication completed during handover.	Optional operational notes.
Handed over by	handed_over_by	Text	Yes	Karl Vaher	Person who issued the equipment.
Recipient acknowledgement	recipient_acknowledgement	Checkbox	Yes	Checked	Require the recipient to confirm the record before submission.

Document Generator settings

Setting	Recommended value
Template name	Equipment Handover Form
Generated file name	Equipment Handover - {{ recipient_full_name }} - {{ handover_reference }}
Available output formats	PDF and DOCX
ODT template file	Equipment Handover Form – Template.odt

After saving the document-generation template, create a test record using the example values above. Generate both PDF and DOCX once, then check the wording, page breaks, long values and empty optional fields before real use.

Return to the template list ↑

Incident Report

Capture the facts, impact, immediate response and follow-up actions for a workplace, service, security or operational incident.

Download the complete template pack or browse this template folder in Folderit.

Review before production use: Adapt this template to your incident-response, safety, privacy, cybersecurity, insurance, regulatory and reporting duties. Serious incidents may require immediate escalation or reporting to authorities; this general form is not a substitute for those procedures or professional advice.

Recommended eForm settings

Setting	Recommended value
Form name	Incident report
Form title	Report an Incident
Description	Record factual incident details, people involved, immediate actions, impact and required follow-up. Do not include unnecessary sensitive information.
Record identifier pattern	Incident - {incident_id} - {incident_title}
Submit button text	Create incident record

Show all 21 eForm fields

Create the fields in the order shown. Enter each slug exactly, including underscores. You may change labels and suggested values, but the ODT placeholders must continue to match the form-field slugs.

Field label	Slug	Type	Required	Example	What to enter
Incident ID	incident_id	Text	Yes	INC-2026-0087	Use a unique incident reference.
Incident title	incident_title	Text	Yes	Unauthorized access to project folder	Use a short factual title.
Incident date	incident_date	Date	Yes	31 July 2026	Date the incident occurred or was discovered.
Incident time	incident_time	Text	Yes	14:35 EEST	Include time zone where relevant.
Location or system	location_or_system	Text	Yes	Client Projects / Orion folder	Physical location, system or process affected.
Department	department	Text	Yes	Professional Services	Department responsible for the affected area.
Reported by	reported_by	Text	Yes	Helen Pärn	Person completing the report.
Reporter email	reporter_email	Email	Yes	helen.parn@example.com	Contact for follow-up questions.
Incident type	incident_type	Select	Yes	Information security	Choose the closest category. Options: Health and safety, Information security, Privacy, Service disruption, Property damage, Quality, Other
Severity	severity	Select	Yes	Medium	Use your organization's severity model. Options: Low, Medium, High, Critical
People involved	people_involved	Textarea	Yes	One internal project user and the Information Security Officer. No external individuals were confirmed affected.	List only necessary names or roles.
Incident description	incident_description	Textarea	Yes	A project user inherited access to a restricted subfolder after being added to the parent project folder. The access was detected during a permission review.	Describe observable facts in chronological order.
Immediate actions	immediate_actions	Textarea	Yes	Removed the inherited permission, reviewed access logs, notified the folder owner and preserved the relevant audit records.	State what was done to contain or stabilize the incident.
Impact or injury	impact_or_injury	Textarea	Yes	No injury. The user viewed two document titles; no download was recorded.	Describe confirmed impact and clearly distinguish unknowns.
Witnesses or evidence	witnesses_or_evidence	Textarea	Yes	Folder permission history, audit-log export and screenshots retained under the incident record.	List witnesses, logs, photos or other evidence.
Preliminary cause	preliminary_cause	Textarea	No	Permission inheritance was not reviewed after the user's project role changed.	Mark as preliminary until formally confirmed.
Corrective actions	corrective_actions	Textarea	Yes	Review all restricted subfolders in the project; add a role-change access checklist; schedule a quarterly permissions review.	List concrete corrective or preventive actions.
Action owner	action_owner	Text	Yes	Information Security Officer	Person or role responsible for follow-up.
Target completion date	target_completion_date	Date	Yes	14 August 2026	Target date for agreed actions.
Status	status	Select	Yes	Under investigation	Current record status. Options: Open, Under investigation, Actions in progress, Closed
Supporting files	supporting_files	File	No	Audit-log export and screenshots	Attach relevant evidence subject to access and privacy rules.

Document Generator settings

Setting	Recommended value
Template name	Incident Report
Generated file name	Incident Report - {{ incident_id }} - {{ incident_date }}
Available output formats	PDF and DOCX
ODT template file	Incident Report – Template.odt

After saving the document-generation template, create a test record using the example values above. Generate both PDF and DOCX once, then check the wording, page breaks, long values and empty optional fields before real use.

Return to the template list ↑

Troubleshooting

A placeholder appears unchanged

Confirm that the eForm field slug matches this guide exactly. Copy the placeholder again from Folderit’s Available form fields table and replace the placeholder in the ODT file. Keep the whole placeholder together with consistent formatting.

Generation reports a missing key or numeric-type error

Check that the field slug uses underscores rather than hyphens and that the placeholder was copied from the correct eForm. Also confirm that Number fields contain numbers rather than formatted text.

The PDF or DOCX layout looks different

Simplify complex tables, floating text boxes and pasted formatting. Test unusually long names, addresses and descriptions. Keep placeholders in one piece and check both enabled output formats.

An optional value leaves awkward punctuation or empty space

Make the field required when the document cannot be valid without it. Otherwise, place optional information on a separate line or rewrite the surrounding sentence so it still reads naturally when the value is empty.

What happens after generation?

Generated documents can be stored in Folderit, downloaded as PDF or DOCX, or emailed from the system. When stored in Folderit, they can be managed with permissions, audit trail, sharing, version history, retention and approval, review, acknowledgement or signing workflows.

Need another copy of the files? Open the complete public Document Template Library.