Financial Templates Hub

Financial Templates Hub

Browse, search and start from a template.

Free templates For individual investors and traders Japanese / English support Paid plans include 412 templates

Template plaza

Pick a business-support template to draft, fill in and share. Templates are drafting aids only — not investment, legal or tax advice, and nothing here rates or recommends any provider.

412 templates

Trade planning Free

Today's Trading Plan

Checklist

A personal note to set out y…

  • Variable merge fields
  • QA check
  • Version control
IB operations Pro

IB Partner Introduction Email

Email draft

A polite, neutral draft emai…

  • Variable merge fields
  • QA check
  • Version control
  • Custom request
View plans
Trade planning Free

Pre-Entry Checklist

Checklist

A personal checklist to conf…

  • Variable merge fields
  • QA check
  • Version control
IB operations Pro

IB Partner Verification Request

Internal memo

A draft internal request to …

  • Variable merge fields
  • QA check
  • Version control
  • Custom request
View plans
Trade planning Free

Entry Rationale Note

Internal memo

A personal note recording wh…

  • Variable merge fields
  • QA check
  • Version control
IB operations Pro

IB Commission Disclosure

Disclaimer text

A neutral draft for disclosi…

  • Variable merge fields
  • Client-share version
  • QA check
  • Version control
  • Custom request
View plans
Trade planning Free

Stop / Take-Profit Rules

Checklist

A personal note to state you…

  • Variable merge fields
  • QA check
  • Version control
IB operations Pro

IB Client Onboarding Checklist

Checklist

A checklist draft to track o…

  • Variable merge fields
  • QA check
  • Version control
  • Custom request
View plans
Trade planning Free

Position Hold Reason

Internal memo

A personal note to check why…

  • Variable merge fields
  • QA check
  • Version control
IB operations Pro

Referral Agreement Summary

Internal memo

A summary draft for aligning…

  • Variable merge fields
  • QA check
  • Version control
  • Custom request
View plans
Trade planning Free

Pre-Trade Risk Check

Checklist

A personal checklist for a f…

  • Variable merge fields
  • QA check
  • Version control
IB operations Pro

IB Monthly Activity Report

Monthly report

A report outline for sharing…

  • Variable merge fields
  • QA check
  • Version control
  • Custom request
View plans

The optional QA check reviews document expression and quality (e.g. unfilled variables, missing disclaimers) — it is not a safety, risk or trust score of any business, and does not confirm legal, tax or regulatory conformity.

About paid plans

Pro / Premium unlock all 412 templates and 12-language output (including Japanese and English).

View plans

📖 How to use the free version

Manual version: v2.4.41 · This manual is operating documentation only — not investment, legal or tax advice.

45 feature guides 98 field entries 17 scenarios 9 quick starts 48 FAQ 26 troubleshooting 72 diagrams

🚀 Quick starts — small wins in minutes

⏱ 5 min Log one of today's trades in five minutes Individual trader
  1. Open the free template hub and type a keyword like "trade log" in the search box
  2. Click "Use" on the trade log template card
  3. Enter the symbol, buy/sell side, quantity, fill price, and your reason for the trade (optional fields can stay collapsed)
  4. Choose the "copy" output format, generate, and review the result
  5. Copy the text and paste it into your own trading notebook or notes app

✓ One ready-to-paste trade log entry in plain text with headings

⏱ 10 min Print a weekly trading review on A4 to keep on your desk Individual investor doing a weekend review
  1. In the free template hub, pick a weekly review template from the review category
  2. Click "Use" and fill in this week's key trades, what went well, and what to improve
  3. Select the "print" output format and generate
  4. Press the print button; the print-ready document is fetched and the print dialog opens
  5. Print on A4 and keep it somewhere you will see before next week's trading

✓ A printed A4 weekly review you can revisit before trading

⏱ 5 min Create a bilingual JA-EN investment note to file alongside English sources Individual investor who also reads English filings
  1. Pick an investment note template in the free template hub and click "Use"
  2. Enter the ticker, why it caught your attention, and the sources you checked
  3. In the language selector, choose the bilingual JA-EN option
  4. Generate in "markdown" format and confirm Japanese and English appear together
  5. Download the file or paste it into your usual note-taking tool

✓ A bilingual investment note that is easy to search later

⏱ 3 min Find a template that fits you in three minutes and check its contents First-time individual trader
  1. Open the template marketplace and choose a category aimed at individual traders
  2. Use sorting and search to narrow the list to two or three candidates
  3. Open a card and review the description and the list of input fields on the detail screen
  4. If the fields match how you keep records, proceed straight to "Use"

✓ One template whose fields you have already verified fit your workflow

⏱ 10 min Write a ten-minute post-mortem note for a losing trade Individual trader reviewing a losing trade
  1. Pick a trade post-mortem template in the free template hub
  2. Click "Use" and enter your entry rationale, expected scenario, actual price action, and the moment you decided to cut the loss
  3. In the improvement field, write exactly one concrete thing you will change next time
  4. Generate in "txt" format and download the file with the date in its name

✓ A dated post-mortem file you can reread before your next trade

⏱ 5 min Turn a watchlist check note into a snippet you can embed in a blog or wiki Individual investor with a personal blog or notes site
  1. Pick a watchlist check template in the free template hub and click "Use"
  2. Enter the symbols you are watching and the points you checked, such as price and volume
  3. Choose the "html" output format and generate
  4. Copy the generated HTML fragment and paste it into your blog post or wiki page

✓ An HTML fragment of your watchlist note, ready to embed

⏱ 10 min Turn a month-end portfolio note into a PDF for your own archive folder Individual investor keeping monthly records
  1. Pick a portfolio or month-end note template in the free template hub
  2. Click "Use" and enter your month-end holdings and observations
  3. Choose the "pdfa_html" format, generate, and download the file
  4. Convert the self-contained HTML to PDF with your usual converter or the browser's save-as-PDF
  5. Rename the file with the year and month and move it to your archive folder

✓ A dated PDF of your month-end note, filed in your archive

⏱ 5 min Create an English-only trade note to import into an overseas tool Individual trader using an overseas journaling tool
  1. Pick a trade note template in the free template hub and click "Use"
  2. Choose English in the language selector (it is preselected when you browse the English page)
  3. Enter the trade details and generate in the "json" format
  4. Download the structured data and import it into your journaling tool

✓ An English trade note as structured data, ready to import elsewhere

⏱ 10 min Turn your own trading rules into a checklist you can run before each trade Individual trader who wants to stick to their rules
  1. Pick a trading-rules checklist template in the free template hub
  2. Review the fields on the detail screen, then click "Use"
  3. Enter your own rules, such as entry conditions, stop-loss line, and maximum loss per trade
  4. Generate in "copy" format and paste it at the top of the notes app you open before trading
  5. Before your next trade, walk through the pasted checklist from top to bottom

✓ A personal trading-rules checklist you can walk through before every trade

Basics

Template Marketplace — A catalog page where you find templates by category, keyword search, and sorting. Free Pro Premium Beginner

What it is: The entry point for quickly finding the right template in the catalog. It combines three tools - category filters to narrow the field, keyword search to zero in, and sorting to compare candidates side by side.

When to use: Use it when you are not sure which document to create, or when you want an overview of what is available. Browsing it occasionally also helps you anticipate which documents you may need next.

What to input: Enter a keyword, pick a category, or change the sort order. All are optional - with nothing set, you simply browse the full list.

Steps:

  1. Open the marketplace page.
  2. Narrow down roughly by category - choosing between business and personal use is an easy first cut.
  3. Refine with a keyword search; short terms such as trade log or client note work best.
  4. Switch the sort order to compare candidates.
  5. Open the details of any interesting card and check its description and input fields.
  6. If it fits your purpose, proceed straight to Use.

Practical scene: A personal trader looking for a trade-log format can narrow candidates by category and compare them. For business use, simply following the category your team works in lists the candidates at a glance, so even first-time users rarely get lost.

Common mistakes:

  • Searching with an overly long phrase and getting zero results - try shorter keywords instead.
  • Mistaking the lock badge on paid templates for a bug.
  • Searching while a category filter is still active and assuming the template does not exist - clear the filter and search again.
  • Picking a template from its card title alone, then having to switch templates midway through input.

Cautions: On the free page only free templates are usable; paid templates appear locked with a plan notice. A lock is not an error - it simply means the template is outside your current plan. From the plan notice on a locked card you can review what the higher plans include.

💡 Tips

  • Short one- or two-word nouns give the best search hits - for example, monthly or checklist.
  • When similar templates sit side by side, comparing the number of fields and the intended use in the detail view speeds up the choice.
  • Remembering the categories you use most lets you reach the right card in a few clicks without searching at all.

◯ Do

  • Narrow by category first, then refine with a keyword.
  • Check the intended use and input fields in the detail view before using a template.

✕ Don't

  • Do not type a whole sentence as a search keyword.
  • Do not treat a locked template as something broken - the lock only reflects your plan.

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Viewing Template Details, Using a Template (From Input to Output), Free Templates Hub

Using a Template (From Input to Output) — The basic flow: press Use on a card, fill in the fields, and generate the document. Free Pro Premium Beginner

What it is: The core feature: fill in the template fields and get a well-structured document. The template takes care of structure and phrasing, so you can concentrate on entering the facts.

When to use: Use it whenever you want to create a document in a fixed format, such as a trade log or a business document. It is faster than writing from scratch and keeps the format consistent every time.

What to input: The template's own fields (date, content, and so on), plus your language and output format. Extra details live inside the collapsible optional-fields section.

Steps:

  1. Press Use on a template card.
  2. Fill in the fields from top to bottom.
  3. Open the optional-fields section for any extra details - templates with many optional fields keep them collapsed.
  4. Choose the language.
  5. Choose the output format that matches how you will use the document.
  6. Press the output button to generate the document.
  7. Review the result, then copy or download it if you need to keep it.
Personal templatesNo audience / tone / sharing controls — personal records.
Business templatesAudience, tone, detail level and sharing mode are selectable.

Practical scene: When reviewing the day's trades, a few minutes of input in a trade-log template gives you a record that is easy to revisit later. Business documents follow the same flow - filling in the fields is all it takes to get a well-organized result.

Common mistakes:

  • Getting confused when optional fields seem missing - open the collapsible section to see them.
  • Assuming every field must be filled before output - you can generate with fields left blank.
  • Generating without checking the output format, then redoing it because the result does not fit where you paste it.
  • Hunting for audience or tone options on a personal-use template - they are hidden by design for self-use records.

Cautions: Personal-use templates do not show audience, tone, or sharing options. This is by design - they are meant as records for yourself, not a missing setting. Your inputs and generated text are never sent to external servers.

💡 Tips

  • Decide how the document will be used - pasted, saved, or printed - before picking the format, and you will rarely need to regenerate.
  • Verify facts such as dates and amounts while entering them; the finished document will then need almost no touch-up.
  • If you use the same template repeatedly, gather the information first - you can then go from opening it to output in a few minutes.

◯ Do

  • Fill in the main fields first and leave finer details to the optional section.
  • Always reread names and numbers in the generated document before using it.

✕ Don't

  • Do not force yourself to fill a field you are unsure about - generate with it blank and add the detail after checking.
  • Do not send the output to anyone without reviewing it first.

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Template Marketplace, Viewing Template Details, Tips for Filling In Fields, Choosing an Output Format (Overview of the 7 Formats)

Viewing Template Details — Check a template's description, fields, and related information before using it. Free Pro Premium Beginner

What it is: A view that helps you decide whether a template fits your purpose before you start typing. Its description, input fields, and related information are visible at a glance, saving you from switching templates later.

When to use: Use it when you are deciding between similar templates, or want to see the required fields in advance. It also works as a preview for gathering the information you will need before you start.

What to input: No input needed - just open the details from a template card to browse the description and field list.

Steps:

  1. Open the details from a template card.
  2. Read the description to confirm the intended use and typical situation.
  3. Review the list of input fields and check that you have the information at hand.
  4. Look over the related information to see how it differs from similar templates.
  5. If undecided, open the details of each candidate and compare them.
  6. If it fits, proceed to Use.

Practical scene: When several monthly-report templates look similar, you can compare their fields and intended use in the detail view before choosing. Knowing what information you will need up front also means fewer stalls halfway through input.

Common mistakes:

  • Trying to generate output from the detail view - output is done through Use.
  • Starting to fill in a template without reading the description, then switching templates halfway.
  • Beginning input without checking the field list, then stopping because the needed information is not at hand.

Cautions: The detail view is read-only and does not generate documents. Generation happens through Use. Treat the detail view as your place to check descriptions and fields, and Use as your place to generate.

💡 Tips

  • With two or three similar candidates, opening each detail view and comparing the field counts makes the choice quick.
  • The field list doubles as a checklist of the information to gather before generating.
  • Even if the described use differs slightly from yours, a template can often be repurposed when its fields match your needs.

◯ Do

  • Read both the description and the field list before using a template.
  • When torn between candidates, compare their detail views first, then commit to one.

✕ Don't

  • Do not start filling in a template based on its card title alone.
  • Do not wait for a document to appear in the detail view - it is read-only.

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Template Marketplace, Using a Template (From Input to Output)

Saving Your Output (Copy, Download, Print) — The three ways to keep a generated document, how output history differs by plan, and habits that make saving reliable. Free Pro Premium Beginner

What it is: The basic steps for making sure a generated document is not lost. Once you understand the three ways to keep output - copy, download, and print - and how history differs by plan, you can reliably preserve important records.

When to use: Do this right after generating, every time you want to keep the result. On the Free plan especially, there is no history, so saving on the spot is the rule.

What to input: No extra input needed - after generating, just choose copy, download, or print to match how you will use the document.

Steps:

  1. Generate the document and read it through for errors.
  2. To use it by pasting, copy it.
  3. To keep a file, download it - it is saved with the correct extension for the format.
  4. To keep a paper copy, use the print format - the print button re-fetches the print document before printing.
  5. Name the file with the date and template name, and put it in your chosen folder.
  6. On the Free plan, double-check that you have saved before closing the screen.

Practical scene: For trade records you want to review at month end, download the txt on the spot and save it with a dated file name. You can also split usage: keep submission documents on paper via the print format, and save data for analysis separately as json.

Common mistakes:

  • Closing the screen without saving on the Free plan and losing the output.
  • Using the html fragment for printing - the print format is made for that.
  • Saving files without meaningful names and being unable to find them later.
  • Treating Pro/Premium history as an all-purpose backup and never keeping local copies of important submitted documents.

Cautions: The Free plan has no output history - copy or download anything you need on the spot and keep it yourself. Pro keeps history for 12 months; Premium keeps it indefinitely. Downloads are saved with the correct extension for each format, and the print button re-fetches the print document rather than printing the on-screen view.

💡 Tips

  • Adopting a naming rule like date_template_recipient makes month-end reviews much faster.
  • If you need the same content both pasted and saved, paste it via copy and then download the txt as well - no rework later.
  • Decide formats by purpose in advance - document formats (print, pdfa_html) for submissions, json for your own analysis - and you will never hesitate.

◯ Do

  • Copy or download anything you need on the spot and keep it locally.
  • Decide your storage rules (folders and file names) before you start routine use.

✕ Don't

  • Relying on the history feature as a backup and skipping local copies of important documents.
  • Manually renaming file extensions after download - the correct extension is applied automatically for each format.

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Choosing an Output Format (Overview of the 7 Formats), Copy Format (Paste-Ready Text), TXT Format (Text File), Output History (12-Month Retention on Pro)

Tips for Filling In Fields — A practical guide of steps and habits for writing inputs that produce better documents. Free Pro Premium Beginner

What it is: Even with the same template, how you write your inputs greatly changes how readable and useful the document is. This entry collects the key writing habits that improve output quality with little extra effort.

When to use: Read this before your first template, or whenever an output feels thin. It also helps when filling in fields is taking longer than it should.

What to input: This applies to the input fields of every template, not one particular screen - the same principles work everywhere.

Steps:

  1. Start with the required fields, writing dates, quantities, and amounts as concrete values.
  2. Keep judgments and reasons to one or two short sentences - the point carries better than a long paragraph.
  3. Include personal or client names only when truly needed.
  4. Replace abbreviations and private shorthand with wording the reader will understand.
  5. Leave unknown fields blank and generate anyway - unfilled items are listed in the output.
  6. Reread the output, fill in only what was missing, and generate again.

Practical scene: In a trade log, writing one sentence of reasoning instead of a vague note turns it into a record you can actually learn from later. In client-facing documents too, concrete dates and amounts alone cut down back-and-forth confirmation.

Common mistakes:

  • Stalling because you feel every field must be filled - you can generate with blanks.
  • Writing only a vague one-liner, ending up with a record you cannot learn from.
  • Leaving unnecessary personal information in a document you then share.
  • Trying to finish in a single pass and skipping the reread-and-refine step.

Cautions: Your inputs are never sent to external servers. Still, when you share a generated document with others, handle personal and client information with care. This service is not investment, legal, or tax advice; actual trading and investment decisions are your own responsibility.

💡 Tips

  • When unsure, write something short, generate, and refine - it finishes faster than aiming for perfection on the first pass.
  • Write numbers with their units (shares, currency, percent) to prevent misreading later.
  • If you use the same template repeatedly, keep your own note of stock phrases you write often - input gets much quicker.

◯ Do

  • Leave at least one sentence of reasoning - it turns the output into a record you can learn from.
  • After generating, check the list of unfilled items and fill in only the ones that matter.

✕ Don't

  • Making completing every field the goal itself and grinding to a halt.
  • Writing unnecessary personal or account details into a document that might be shared.

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Using a Template (From Input to Output), QA Check, Saving Your Output (Copy, Download, Print)

Free Templates Hub — A collection of free templates you can use without creating an account, centered on templates for individual investors and traders, ready to use right away. Free Beginner

What it is: Lets you start using document templates for trade records, reviews, and similar purposes right away, with no sign-up. It is also the entry point for finding out, through real work and at no cost, whether the service fits how you operate.

When to use: Use it when trying the service for the first time, when you want to organize personal trading and study records, or when you want to judge the template quality without registering.

What to input: Fill in each template's input fields with your own information. You can choose Japanese, English, or bilingual output - the page language is preselected - and all seven output formats are available.

Steps:

  1. Open the Free Templates Hub page (no registration or login needed)
  2. Find the template you need via categories or search
  3. Click Use on a card and fill in the fields (optional fields sit inside the collapsible section)
  4. Choose the language: Japanese, English, or bilingual (the page language is preselected)
  5. Pick the output format that fits your purpose from the 7 formats and generate
  6. Copy or download any output you want to keep, right away
Pick a template
Fill in the fields
Choose a format
Copy / print
Review it yourself

Practical scene: An individual trader reviewing the week's trades on the weekend can fill in a record template and save the output as personal notes. Using per-trade records on weekdays and a summary review on weekends builds a recording habit - all without an account.

Common mistakes:

  • Closing the page without saving the output, assuming it is kept in history (Free has no history)
  • Mistaking the lock on paid templates for a malfunction
  • Trying to use 12-language output on Free (Free offers Japanese, English, and bilingual only; 12 languages requires Pro or above)
  • Generating with the default language still selected and ending up with a document in an unintended language

Cautions: Free does not store output history, so download or copy anything you want to keep on the spot. Paid templates appear locked with a plan notice. This service is not investment, legal, or tax advice; actual trading and investment decisions are your own responsibility. Your inputs and generated document bodies are never sent to external servers.

💡 Tips

  • Personal templates do not show audience or tone options - they are designed as records for yourself, so nothing is missing
  • For record templates you use daily, generating txt and saving with a dated file name makes later review in folders much easier
  • Try sticking with one template, such as a trade log, for a full week - it is the quickest way to judge whether the service suits you

◯ Do

  • Save every output you want to keep - download or copy it each time you generate
  • Before showing a document to anyone, reread it for unnecessary personal or account information

✕ Don't

  • Do not treat a generated document as the basis for an investment decision - actual trading and investment decisions are your own responsibility
  • Do not keep trying to open locked paid templates - the plan notice explains what they contain and how to access them

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Using a Template (From Input to Output), Language Selection, Checking Plans and Upgrading

Common Mistakes and How to Avoid Them — A summary of the points beginners most often stumble on, plus a checklist to run before generating and before sharing. Free Pro Premium Beginner

What it is: Helps you avoid typical failures - sharing a document with unfilled fields, or picking the wrong output format - by knowing them in advance. Most failures come from skipped checks rather than wrong operations, so learning them as a fixed-order checklist works best.

When to use: Use it before your first output, before sharing a document with others, and whenever a rushed task tempts you to skip the checks.

What to input: No input is required. Use it as a checklist before generating and before sharing.

Steps:

  1. Fill in all required fields and also open the collapsed optional section to check it
  2. Review any blank-field notices (you can generate with blanks, but decide before sharing whether to fill them)
  3. Check the language field (the page language is preselected)
  4. Choose the format that fits the purpose (copy for pasting, print for printing, pdfa_html for PDF conversion)
  5. On Pro/Premium, review the QA check notices (flagged wording, unfilled fields)
  6. Read the whole document once more before sharing
  7. Save any output you want to keep (Free does not store history)

Practical scene: When you prepare a client document in a hurry, running this checklist before sharing prevents sending it with unfilled fields. Checking in the same order every time also reduces the oversights that creep in once you get comfortable.

Common mistakes:

  • Sharing a document while some fields are still unfilled
  • Mixing up the embeddable html fragment with the full documents print and pdfa_html
  • Closing without saving because you assumed Free keeps history
  • Using the output without reviewing the notices (the QA check is available on Pro/Premium)
  • Not checking the preselected language and generating in an unintended language

Cautions: This service is not investment, legal, or tax advice. Final review of the output, and any actual trading or investment decisions, are your own responsibility. Note that passing the checklist is not a guarantee that the document's content is accurate.

💡 Tips

  • Fix the pre-share check order as: inputs, format, full reread, save - a fixed order is hard to skip even in a rush
  • For documents going to clients or outside parties, set the audience or sharing mode (Pro/Premium), but still do the final review with your own eyes
  • When something goes wrong, check the common-mistakes section of that feature's manual page - the same case is often already listed there

◯ Do

  • Decide on the spot, every time you generate, whether the output needs saving
  • Never skip the full reread before sharing, no matter how rushed you are

✕ Don't

  • Do not send a document to clients or outside parties while notices are still showing
  • Do not treat a clean-looking layout as proof that the content is correct

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: QA Check, Using a Template (From Input to Output), Output History (12-Month Retention on Pro)

Search and Filtering — Combine keyword search, categories, and sorting to reach the template you need quickly. Free Pro Premium Beginner

What it is: Helps you efficiently find the one template you need from the library. Search by keyword for names and purposes, narrow by category, and switch the display order with sorting. The list shows how many items are displayed out of the total, and a show-more control loads the rest, so no candidate is left unseen.

When to use: Use it as your starting point in both cases: when you know what you want and can search by name or purpose, and when your goal is vague and you would rather browse by field.

What to input: A search keyword, a category selection, and a sort order. All are optional and can be combined.

Steps:

  1. Open the template list on the free page or the dashboard
  2. If you know what you need, type a keyword and search (for example, trade journal or client briefing)
  3. Select a category to narrow by field or purpose
  4. Switch the sort order and compare the candidates
  5. Check the displayed-versus-total counter and use the show-more control to load the rest
  6. Open the detail page of a promising template, review its description and fields, then proceed to use it
Open marketplace
Filter by category
Keyword search
Sort results
Pick a card

Practical scene: Say you need a briefing memo for a client. Select the category closest to client communication, then search for briefing within it. Once a few candidates remain, compare their fields on the detail pages and pick the closest match. This is usually the fastest route.

Common mistakes:

  • Searching with a long phrase, getting no hits, and concluding the template does not exist (split it into short words and retry)
  • Searching while a category filter is active and deciding the template is missing when it lives in another category
  • Never pressing show more and assuming the first batch is the whole list
  • Mistaking locked cards on the free page for a defect

Cautions: On the free page, paid templates appear locked, with a link to plan information instead of the use action. This is intended behavior, not a defect. If results are sparse, loosen the conditions: shorten the keyword or remove the category filter and search again.

💡 Tips

  • Narrow broadly by category first, then search by keyword within it for better precision.
  • Even if you do not know a template's name, searching by purpose words such as report, checklist, or journal usually finds it.
  • The item counter tells you at a glance whether your filters have become too strict.

◯ Do

  • Combine search and categories to narrow step by step
  • Review the description and fields on the detail page before using a template

✕ Don't

  • Do not give up after one search; change the conditions and try again
  • Before reporting locked cards as a bug, check your plan and which page you are viewing

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Template Marketplace, Viewing Template Details, Using a Template (From Input to Output), Finding Your Way Around Categories, Free Templates Hub

Finding Your Way Around Categories — Templates are organized into purpose-based categories. This guide explains the top-level structure and how to choose. Free Pro Premium Beginner

What it is: A guide to grasping the overall structure of the library so you can head straight to the right category. Categories broadly split into personal-trader templates for your own records and business-document templates read by colleagues or clients. Categories are more than shelves: they also affect the input form of the template you pick. For example, templates in personal categories do not show audience or tone options.

When to use: Read this when you are exploring the library for the first time, when you want a mental map before searching, or when you are unsure which category to look in.

What to input: No special input is required. Simply browse the list while switching categories.

Steps:

  1. Scan the category display and grasp the top-level split: personal records versus business documents
  2. Pick the category closest to your goal and narrow the list
  3. Read the template descriptions in that category and confirm the purpose matches
  4. If several categories look close, switch between them and compare the candidates' input fields
  5. Once you settle on the categories you use most, combine them with search for everyday access
Search & sortNarrow down with keywords and sorting
Browse categoriesList templates by purpose category
Personal templatesTrade logs and reviews, usable on Free
Business templatesClient and internal docs, Pro and above

Practical scene: A personal trader will naturally start from record-keeping categories such as trade journals and money management. For business use, choose by reader: client-facing briefing materials versus internal reports and checks. Picking by reader gets you to a template with the right field structure sooner.

Common mistakes:

  • Choosing by the category name's impression alone and starting with a template whose fields do not fit
  • Mixing up business and personal categories and picking a business template with an approval block for a private record
  • Looking at only one category and missing a better-suited template in a neighboring one

Cautions: The input form changes by category. Templates in personal categories are designed for your own records, so audience, tone, and sharing options are not shown. The category structure organizes document purposes; it does not represent any legal classification or advice.

💡 Tips

  • When in doubt, choose by who will read the document: personal categories if only you will, business categories if colleagues or clients will.
  • On Premium, setting an industry in the Workspace Profile adjusts the recommended categories, giving you a tighter starting point.
  • Watching the item counter as you switch categories gives you a feel for each category's size.

◯ Do

  • Check a template's description and fields before you start using it
  • Decide the document's reader first (yourself, colleagues, or clients), then pick the category

✕ Don't

  • Do not judge by the category name's impression alone
  • Do not keep searching a single category when you cannot find what you need

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Search and Filtering, Template Marketplace, Using the Personal Trader Categories, Viewing Template Details, Workspace Profile (12 Industry Profiles)

Using the Personal Trader Categories — How to choose and keep using the templates made for your own records, such as trade journals and money management. Free Pro Premium Beginner

What it is: The personal trader categories are template sets for keeping your own records of daily trades and money status. Their purpose is to support the habit of writing down the reasoning behind decisions and reviewing it later. Because they assume private records, no audience or tone options appear during input, and the output contains no business elements such as approval blocks or internal handling labels. The free library centers on templates for individual investors and traders, and you can start without creating an account.

When to use: Use them when you want to log every trade, run weekly or monthly reviews, or put your money-management rules into written form.

What to input: The trade or money details you want to record: date, instrument (stock, currency pair, and so on), size, reasoning, outcome, and observations. Filling in the fields is all it takes.

Steps:

  1. Open a personal category on the free page (no account needed) or the dashboard
  2. Pick the template that fits your goal, such as a trade journal, money management sheet, or review
  3. Press the use action and fill in the fields with your trade or money details
  4. If there are many optional fields, expand the optional section and fill in only what you need
  5. Choose an output format and generate the document
  6. Save the record somewhere you control and revisit it during your reviews
Open the free hub
Choose a journal
Press Use
Enter trade details
Output and keep

Practical scene: A routine that sticks: after each weekday trade, write the entry reasoning and outcome into the trade journal template, then on the weekend review the week and note improvements for the next one. Because every record has the same shape, comparing across periods becomes easy.

Common mistakes:

  • Closing the screen without saving, leaving no copy of the record (Free keeps no history)
  • Picking a business template by mistake and getting an approval block your private record does not need
  • Logging only outcomes without the reasoning, which makes the record useless for review
  • Trying to fill every optional field, turning the habit into a burden that does not last

Cautions: Output from personal templates always includes a line stating that actual trading and investment decisions are your own responsibility. The templates are tools for recording and organizing; they are not investment advice and promise no profits or outcomes. The Free plan keeps no output history, so always save your output yourself. On Free, the language can be Japanese, English, or bilingual output.

💡 Tips

  • Records are most accurate written right after the trade. Keep them short if needed, but always pair reasoning with outcome.
  • Generating bilingual output helps when you review your records against English-language sources.
  • Sticking with the same template keeps the fields consistent, making comparisons across periods easier.

◯ Do

  • Record in the same shape every time: reasoning, outcome, observations
  • Save each output with a name that includes the date

✕ Don't

  • Do not treat the template content as a recommendation for investment decisions
  • Do not log only the trades that went well; a biased journal defeats the review

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Free Templates Hub, Using a Template (From Input to Output), Finding Your Way Around Categories, Saving Your Output (Copy, Download, Print), Language Selection

How to Read a Generated Document — What each part of a generated document means (summary, body, unfilled items, warnings) and how to check it before sharing. Free Pro Premium Beginner

What it is: A generated document generally flows from title and date, to a summary, a list of key details, the body, checklists and next actions, notices, and a footer. Knowing what lives where lets you find the parts to verify immediately, so the pre-sharing check takes little time. Fields you left blank are collected in an unfilled-items list rather than hiding in the body, and on Pro and Premium, issues found by the QA check (questionable wording or missing input) are attached as warnings.

When to use: Useful the first time you generate a document, before sharing or printing, and whenever you need to decide what to fix.

What to input: No special input. You simply read through the generated document on screen.

Steps:

  1. Look at the title and date to confirm this is the document you intended
  2. Check the opening summary and the key-details list to verify your input was reflected correctly
  3. Read the body and confirm the sentences flow naturally around the inserted values
  4. Review the unfilled-items list; if something essential is missing, return to the input and regenerate
  5. Go through the checklist and notices to see what needs attention before sharing
  6. (Pro/Premium) If QA warnings appear, resolve the flagged wording or missing input before using the document
Header & summaryTitle and key points, check this first
Body (your inputs)Your entered values fill the body
Unfilled & checklistUnfilled items and review checklist
Notices & footerDisclaimers always remain at the end

Practical scene: After generating a client briefing memo, the author first checks the unfilled-items list and QA warnings, finds a missing amount, and regenerates. Then a full read-through confirms the text flows correctly, and only then does the memo move on to sharing.

Common mistakes:

  • Reading only the summary and missing blanks or inconsistencies in the body
  • Sharing without checking the unfilled-items list
  • Skipping QA warnings as if they were decoration
  • Deleting the disclaimer or footer as unnecessary boilerplate

Cautions: Do not delete the disclaimers and notices included in the document. Output from this service is not investment, legal, or tax advice, and verifying the content is your responsibility. Business elements such as approval blocks and handling labels do not appear in output from personal templates. On Pro and Premium, changing the detail level or sharing mode changes the structure itself, so a different layout from what you are used to is not an error.

💡 Tips

  • Check in this order: unfilled items, then QA warnings, then the body. You fix the most important issues first.
  • Cross-check numbers and dates against the input screen; digit and unit errors show up quickly that way.
  • For documents with a known recipient, reread just the summary from their point of view to catch communication problems.

◯ Do

  • Always check unfilled items and QA warnings before sharing or printing
  • Verify numbers, dates, and names against the source material

✕ Don't

  • Do not send a generated document externally without checking it
  • Do not delete or rewrite the disclaimers and notices

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Using a Template (From Input to Output), QA Check, Choosing an Output Format (Overview of the 7 Formats), Editing After Output vs. Regenerating

Editing After Output vs. Regenerating — When to touch up a generated document by hand, and when to go back to the input and regenerate. Free Pro Premium Beginner

What it is: Treat a generated document as a high-quality draft, not a finished product. There are two ways to finish it: export in an editable format such as txt or markdown and adjust the wording in your own editor, or return to the input screen, correct values or settings, and regenerate. Splitting the roles this way, regeneration for errors, hand-editing for wording preferences, reduces missed fixes and speeds up the work.

When to use: Decide between the two whenever you want to match your organization's phrasing, fix just one spot before sharing, or notice an input error or omission after generating.

What to input: The generated document (in an editable format such as txt or markdown if you plan to edit) and a note of what needs fixing.

Steps:

  1. Sort each fix into one of two kinds: an input error or omission, or a wording preference
  2. For input errors or omissions, return to the input screen, correct it, and regenerate (more reliable than hand-fixing every occurrence)
  3. For wording adjustments, export in an editable format such as txt or markdown
  4. Paste into your own editor or word processor and make the changes
  5. After editing, confirm the disclaimers and notices are still present
  6. On Pro and Premium you can regenerate from output history, so rebuild with changed settings from there

Practical scene: To change one phrase in a client briefing memo, export as markdown and edit locally. If you spot a wrong amount, go back to the input and regenerate. Keeping these two paths separate is the basic pattern; mixing them invites missed fixes.

Common mistakes:

  • Hand-fixing a wrong input value in every spot and missing one (returning to the input and regenerating is safer)
  • Deleting the disclaimer while editing
  • Treating the edited document as identical to the recorded, generated one
  • On Free, not keeping a note of your inputs and losing time when rebuilding

Cautions: A hand-edited document is no longer what the system generated. Premium record features (Release Register and Evidence Mode) record the output as generated; your edited copy is outside their scope. Likewise, QA results apply to the document at generation time, not to your edits. Always keep the disclaimers and notices when editing.

💡 Tips

  • For large rewrites, changing tone or detail level (Pro and Premium) and regenerating is often faster and cleaner than manual editing.
  • Match the format to the job: markdown when you plan to edit, copy when you will paste as-is. It cuts rework.
  • On Free, keep a note of your inputs so regenerating takes seconds.

◯ Do

  • Fix errors by returning to the input and regenerating
  • After editing, confirm the disclaimers and notices are intact

✕ Don't

  • Do not distribute a version with the disclaimer removed
  • Do not treat an edited copy as identical to the generated record

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: How to Read a Generated Document, Using a Template (From Input to Output), Output History (12-Month Retention on Pro), Markdown Format, QA Check

Naming and organizing downloaded files — How download file names and extensions work, plus naming and folder habits that make files easy to find later. Free Pro Premium Beginner

What it is: Downloaded files are saved with the correct MIME type and extension for the output format you chose. Because the files live on your own device, having a naming and folder convention directly speeds up daily record-keeping and client work.

When to use: Relevant every time you download an output to keep it, and whenever you look back at or share past files.

What to input: A downloaded file and your own naming convention (date, topic, recipient, and so on).

Steps:

  1. Generate an output, choose a format, and download it.
  2. Confirm the saved file's extension matches the format (for example .txt for text, .json for JSON).
  3. Pick a destination folder using your own rule, such as per client or per month.
  4. Rename the file if needed, for example 20260706_trade-log_USDJPY.txt with a date plus topic.
  5. When renaming, keep the extension and edit only the name part.
  6. Before sending a file to anyone, check that the file name itself does not expose client names, account details, or anything you would not want seen.

Practical scene: If you save daily trade logs into monthly folders with date-based names, a month-end review starts in seconds. For files sent to clients, a name that explains the content before opening reduces follow-up questions.

Common mistakes:

  • Accidentally editing the extension while renaming, making the file unopenable.
  • Piling up files under their automatic names until you can no longer tell which is which.
  • Overwriting an earlier version by saving under the same name.
  • Sending a file outside the company with a client name or deal details still in the file name.

Cautions: Files are saved on your own device, and document bodies are never sent to SG Group's external servers. This also means backup and retention are your responsibility; keep a second copy of important documents.

💡 Tips

  • Use YYYYMMDD dates so that sorting by name automatically sorts by time.
  • For documents with revisions, append v1, v2 to the name to avoid mixing up the latest version.
  • If you store files in a cloud or shared folder, also review who can access that folder.

◯ Do

  • Name files with date plus topic (and recipient when relevant)
  • Rename and file each download right after saving it

✕ Don't

  • Do not change file extensions
  • Do not leave every file piled in a single folder

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: How to create PDF files (PDF conversion), Output History (12-Month Retention on Pro), Using a Template (From Input to Output)

Using the service on smartphones and tablets — Works straight from a mobile browser with no app to install. Covers what works well on the go, and which tasks are better left to a desktop. Free Pro Premium Beginner

What it is: Because the service runs entirely in a browser, you can search templates, fill in fields, generate, and copy outputs from a smartphone or tablet. The goal is to let you capture records right after a trade or while on the move, when a desktop is out of reach.

When to use: Use it when you want to write something down on the spot: a log right after a trade, a draft while out of the office, or first notes from a meeting.

What to input: A smartphone or tablet browser. No special setup is required.

Steps:

  1. Open your usual page (the free template hub or the dashboard) in your phone's browser.
  2. Find a template and tap Use.
  3. Fill in the required fields first. Keep the collapsed optional-fields section closed until you need it, so the screen stays readable.
  4. Choose an output format and generate. The copy format is the easiest to handle while on the move.
  5. Copy the result and paste it into a notes app or an email draft to keep it.
  6. Do finishing work such as printing or PDF conversion later from a desktop, using the same template.
Open on phone
Pick a template
Fill the fields
Generate output
Copy or save

Practical scene: The most reliable way to log a trade is to enter it from your phone while the details are fresh. A natural split is to capture on mobile, then reopen on a desktop at home to finish the print-ready version.

Common mistakes:

  • Closing the tab without saving the result (the Free plan keeps no history).
  • Trying to complete long-form input entirely on mobile, which multiplies typos and omissions.
  • Attempting to print on mobile, hitting the popup blocker, and assuming the feature is broken.
  • Reviewing a document with tables without zooming or rotating the screen, and missing details.

Cautions: There is no app to install; everything runs in the browser. Mobile popup blockers can interfere with the print window, so printing and PDF conversion are best done on a desktop. Also note that the Free plan keeps no output history, so copy or download your result on the spot.

💡 Tips

  • Draft longer text in a notes app first, then paste it into the field, so nothing is lost mid-entry.
  • Bookmark the templates you use often so they open in one tap.
  • The copy format comes pre-structured with symbols, which also pastes well into chat apps.

◯ Do

  • Enter short log-style templates on mobile, on the spot
  • Copy or download the result immediately after generating

✕ Don't

  • Do not finalize client-facing documents on mobile alone
  • Do not stay signed in on a shared device

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Using a Template (From Input to Output), Free Templates Hub, How to create PDF files (PDF conversion), Using optional fields (the collapsed section)

Page language vs. output language — The language of the page you are viewing and the language of the document you generate are separate settings. The language field defaults to the page language, but you can change it freely. Free Pro Premium Beginner

What it is: Clears up the common assumption that an English page can only produce English output. The language field simply starts on the page's language as a default; change it before generating and you can produce a document in the language you want from either page.

When to use: Worth keeping in mind whenever you create a document in a language other than your usual one, or when working alongside colleagues who browse the site in the other language.

What to input: Checking and choosing the language field on a template's Use screen.

Steps:

  1. Check whether you are on the Japanese page or the English page.
  2. Open a template's Use screen; the language field starts on the page's language as its default.
  3. If you want a different output language, change it in the language field. There is no need to switch the page itself.
  4. On the Free plan you can choose Japanese, English, or Japanese-English side by side.
  5. On Pro and Premium you can pick from 12 languages, including generating several languages at once (switch to custom selection).
  6. After generating, first confirm the body text is in the language you intended.
Page languageOutput language
Language of the UILanguage of the document
Sets the default language choiceChosen for each output
Switch via JA / EN pagesFree: JA / EN / bilingual
Pro+: up to 12 at once

Practical scene: It is routine for a colleague browsing the English page to produce an internal document in Japanese, or for someone on the Japanese page to generate an English client document. Remembering that page and output are independent removes the confusion.

Common mistakes:

  • Switching the whole page to English just to get an English document (changing the language field is enough).
  • Generating with the default untouched and ending up with a document in the wrong language.
  • Confusing the bilingual option with English-only and sending a document twice the expected length.
  • Assuming that because the page displays in English, the output can only be English.

Cautions: Switching the page language does not change the language of documents you already generated; language is a setting applied at generation time. Also note that the bilingual option puts both languages into one document, which is different from an English-only output.

💡 Tips

  • For routine work where the recipient's language is fixed, make checking the language field a pre-generation habit.
  • The bilingual format is handy when one document must serve both internal review and client delivery.
  • If you need multiple languages daily, that is a good signal to consider the 12-language simultaneous output on Pro/Premium.

◯ Do

  • Check the language field before generating
  • Choose based on the language your reader will read

✕ Don't

  • Do not switch the page language just to change the output language
  • Do not distribute multilingual documents without checking each language first

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Language Selection, Simultaneous 12-Language Output, Using a Template (From Input to Output)

Understanding disclaimers and handling them correctly — Explains what the disclaimers in template outputs are for and why they should not be removed. They are the foundation of a document's credibility. Free Pro Premium Beginner

What it is: This service does not provide investment, legal, or tax advice; template outputs are drafts for your work and records. Disclaimers exist to convey that positioning to readers and to protect both the writer and the reader from misunderstanding. The goal here is to understand that role and keep disclaimers working for you rather than deleting them.

When to use: Keep this in mind before showing a generated document to anyone else, and whenever you add your own sentences to the body.

What to input: A generated output. No special action is needed; what you bring is a reviewing mindset.

Steps:

  1. After generating, locate the disclaimer section at the end of the document or in its designated position.
  2. Consider whether the document's nature (a personal record versus material shown to others) matches the disclaimer's content.
  3. For personal templates, confirm the note that actual trading and investment decisions are your own responsibility is present.
  4. For documents you share with others, leave the disclaimer in place; do not delete it.
  5. Re-read anything you wrote yourself for wording that promises returns or asserts safety, using the QA check warnings as a guide.
  6. If your business requires additional disclaimer language, confirm it with the responsible team or a professional before adding it.

Practical scene: When handing a client an explanation memo, the disclaimer makes it clear the document is information, not advice. Even in a personal trade log, it serves as a level-headed reminder each time you re-read it.

Common mistakes:

  • Deleting the entire disclaimer section just to make the document look cleaner.
  • Treating the disclaimer as a safety net and skipping the content review altogether.
  • Adding self-written passages that promise returns or assert certainty.
  • Reusing the exact same text for a personal record and a client-facing document.

Cautions: Template outputs are drafts; they do not guarantee returns, results, or regulatory compliance. The service is not investment, legal, tax, accounting or regulatory advice, and using the templates intended for financial-institution work does not guarantee the legality of your operations, the outcome of any examination or inspection, or the fulfillment of any duty of explanation. Managing your inputs, outputs, storage, sharing and submissions is your responsibility; to the maximum extent permitted by applicable law, SG Group is not liable for damages, lost profits, refunds, compensation or third-party claims. Any document that must meet regulations or internal policies should be reviewed by the responsible person or a professional before use.

💡 Tips

  • Locked sections on Premium can pin the disclaimer so it always appears in the output, even if set to hidden.
  • The Rulebook on Premium can auto-insert required disclaimers and warn about wording to avoid.
  • When unsure, the fastest test is to ask whether a reader could misunderstand the text.

◯ Do

  • Confirm the disclaimer is intact before sharing
  • Write body text in wording that avoids absolute claims

✕ Don't

  • Do not casually delete or rewrite disclaimers
  • Do not use outputs as-is as legal documents or advice

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: QA Check, Locked Sections, Rulebook (Compliance Rules)

Working with unfilled items — Generating with blank fields is fine. Blanks stay in the body as fill-in slots and are collected into an unfilled-items list, so the document is built to be completed later. Free Pro Premium Beginner

What it is: A mechanism for shaping a document before every value is known. Blank fields remain in the body as fill-in slots, and the unfilled-items list inside the output shows every gap at a glance. It supports both catching omissions and finishing later by hand or by regenerating.

When to use: Use it when you want the document's frame before all the information arrives, and again as a final check before sharing.

What to input: Whatever values you know so far. Blanks can stay blank.

Steps:

  1. Open a template's Use screen and enter only the fields you know right now.
  2. Generate as-is; blank fields remain in the body as fill-in slots.
  3. Review the unfilled-items list inside the output to see every gap in one place.
  4. Choose how to finish: print and fill in by hand, or enter the values once available and regenerate.
  5. On Pro and Premium, the QA check warnings act as a second net for overlooked blanks.
  6. For documents handed to others, do a final pass before sending to confirm no unfilled items remain.
Output with gaps
Check unfilled list
Add missing info
Generate again

Practical scene: Before a client meeting you can print just the frame and fill it in by hand as you listen. For outbound documents, the same list works in reverse: a checklist you drive down to zero before sending.

Common mistakes:

  • Giving up mid-entry in the belief that every field must be filled before generating.
  • Sending a document to a client without checking the unfilled-items list.
  • Filling in a printed copy by hand but never updating the data, so regeneration brings the blanks back.
  • Mistaking the fill-in slots in the body for decoration and deleting them manually.

Cautions: The unfilled-items list exists to surface omissions; blanks never cause an error. On personal templates, the opening text adjusts so the document still reads naturally as a personal record even with gaps.

💡 Tips

  • One trick is to generate with blanks on purpose and use the unfilled list as your questions-to-ask list.
  • If you plan to regenerate, keep a note of your previous inputs (the Free plan stores no history).
  • For figures not yet confirmed, leaving the field blank and tracking it in the list is safer than a placeholder number.

◯ Do

  • Treat generating and checking the unfilled list as one step
  • Finish shared documents to zero unfilled items

✕ Don't

  • Do not share documents with placeholder numbers still in place
  • Do not delete the unfilled-items section just to tidy the layout

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Using a Template (From Input to Output), QA Check, Using optional fields (the collapsed section)

Using optional fields (the collapsed section) — Templates with many optional fields group them into a collapsible section on the input form. Open it, fill only what matters, and you control how rich the document becomes. Free Pro Premium Beginner

What it is: A two-tier design: required fields alone produce a usable document quickly, while each optional field you add deepens the content. The collapsed grouping keeps the form short, so even on an unfamiliar template you can start confidently with the required part.

When to use: Relevant both when you want a richer, more explanatory document and when you want the leanest possible one in minimal time.

What to input: Values for the required fields, plus values for whichever optional fields serve your purpose.

Steps:

  1. Open the template's Use screen and fill in the required fields first.
  2. Expand the optional-fields section to reveal the collapsed items.
  3. Fill in only the fields that relate to the document's purpose.
  4. Leave unused optional fields blank; that is perfectly fine.
  5. Generate and see how each optional field you filled shows up in the body.
  6. If the result feels thin, fill more optional fields and regenerate to tune the density.
Open Use form
Fill required
Expand optional
Fill as needed
Generate

Practical scene: In a trade log you can vary the depth: instrument and result on normal days, but on a bad day also fill in the optional fields for emotions and market conditions. In client documents, carefully filled optional fields translate directly into more convincing explanations.

Common mistakes:

  • Missing the collapsed section and concluding the template has very few fields.
  • Treating every optional field as mandatory and spending far too long on one document.
  • Filling optional fields unrelated to the purpose and bloating the document.
  • Generating without re-reading what you wrote in optional fields and missing overlaps with other parts of the body.

Cautions: Blank optional fields never block generation, but they are either omitted from the output or treated as unfilled items. The more you fill, the longer the document becomes, so keep the reader's attention span in mind.

💡 Tips

  • An efficient order: generate with required fields only, view the whole, then top up just the gaps with optional fields.
  • For routine work, decide in advance which optional fields you always fill; document quality becomes consistent.
  • On personal templates, consistently writing the reflective optional fields becomes a record of your own progress.

◯ Do

  • Fill the fields that serve the purpose first
  • Look at the generated result before deciding to add more

✕ Don't

  • Do not make filling every optional field the goal itself
  • Do not let internal notes slip into client-facing output through optional fields

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Using a Template (From Input to Output), Working with unfilled items, Viewing Template Details

Troubleshooting Basics — Basic steps for diagnosing and solving common problems yourself, such as printing not working, downloads not opening, or paid features being unavailable. Free Pro Premium Beginner

What it is: Many apparent malfunctions can be explained by environmental factors such as browser settings or plan status. The goal is to learn a diagnostic order so you can solve most problems yourself in a few minutes.

When to use: Use this when something does not behave as expected, or when you want to check things yourself before contacting anyone.

What to input: Note the screen where the issue occurred, the steps you took, and any message shown; this speeds up both diagnosis and any later inquiry.

Steps:

  1. First reload the page and try the same operation again.
  2. Classify the symptom: is it about output, input, display, plan, or account?
  3. If printing fails, note that the print button re-fetches a print-ready document, so disable your browser's popup blocker and try again.
  4. If a downloaded document will not open, check that you are opening it with an app that supports that format's file extension.
  5. If a paid feature is unavailable, check your plan and expiry date on the account page.
  6. Search the manual's troubleshooting section and FAQ for the same symptom.
  7. If it is still unresolved, write down the symptom, your steps, and any message before making an inquiry; it shortens the path to a fix.
Identify the issue
Reload the page
Check inputs/format
Check plan limits
Run self-check
Contact support

Practical scene: If nothing seems to happen when you press the print button, the first suspect is the popup blocker. With a diagnostic order decided in advance, most issues can be resolved calmly within minutes.

Common mistakes:

  • Changing settings at random without classifying the symptom, losing track of the cause
  • Repeating the print operation many times without noticing the popup blocker
  • Mistaking an expired plan for a malfunction
  • Making an inquiry without recording the error message, requiring many back-and-forth exchanges

Cautions: Input and output bodies are never sent to external servers. Browser extensions such as ad blockers can affect display and printing behavior. An expired plan is a subscription status, not an error.

💡 Tips

  • Trying another browser or a private window quickly tells you whether the issue is environmental
  • For output issues, trying a different output format first tells you whether the problem is format-specific
  • The account page is the primary source for plan, expiry, and account type; check it first for any paid-feature question

◯ Do

  • Proceed calmly in order: reload, classify, then check the manual
  • Note the symptom and your steps before making an inquiry

✕ Don't

  • Repeating the same failing operation without changing anything
  • Changing multiple settings at once while the cause is still unknown

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Account Page, QA Check, How to Navigate the Manual Center

How to Navigate the Manual Center — An orientation to the Manual Center, which combines feature guides, a field dictionary, practical scenarios, recipes, FAQ, and diagrams, and how to look things up by goal. Free Pro Premium Beginner

What it is: The goal is to know where everything lives in the Manual Center so you can reach the right information by the shortest route, whether you want to learn an operation, understand a field, or solve a problem.

When to use: Read this when you start using the service, before trying a new feature, or when onboarding a new team member.

What to input: No preparation is needed. Just remember that what you see is tailored to your current plan.

Steps:

  1. Open the Manual Center; feature guides are arranged by category.
  2. If you already know the feature you need, open its card from the matching category.
  3. If you are new, start with a quick-start recipe and you can produce your first document in minutes.
  4. When a field's meaning is unclear, check the field dictionary for per-field explanations and sample entries.
  5. For usage that follows a business workflow, consult the practical scenarios.
  6. For problems, search the FAQ and troubleshooting section by symptom.
  7. Features from higher plans appear as overview-only teasers; full details unlock after upgrading.
Quick startRecipes and scenarios you can try fast
Feature guidesSteps, tips, and cautions per feature
Field dictionaryHow to fill each field, with examples
FAQ & troubleshootCommon questions and fix-it steps

Practical scene: For a new team member, you can use it for training: hands-on document creation via recipes on day one, then scenarios close to their actual work from the next day. Telling them to search the FAQ by symptom also reduces the load of answering questions.

Common mistakes:

  • Mistaking teaser cards for higher-plan features as a malfunction
  • Filling in fields by guesswork without the field dictionary and getting unexpected output
  • Researching the same question repeatedly instead of checking the FAQ

Cautions: Manual content is displayed according to your current plan. Cards for higher-plan features appearing in abbreviated form is not a malfunction. This manual explains operations and is not investment, legal, or tax advice.

💡 Tips

  • Diagrams are handy for grasping how features relate; when text is unclear, look at the diagram first
  • If you are unsure which output format to use, the format example pages let you compare finished results
  • Guiding new members through recipes, then scenarios, then feature guides makes onboarding stick faster

◯ Do

  • Skim the relevant feature card before performing an operation
  • When searching by symptom, start from the troubleshooting section

✕ Don't

  • Trying to reproduce steps for features outside your plan
  • Treating manual content as a basis for business or legal decisions

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Troubleshooting Basics, Free Templates Hub, Viewing Template Details

Using the Compact Manual — How to quickly find and read the manual using search, a table of contents, and accordions. Free Pro Premium Beginner

What it is: This feature displays the manual in a compact, readable way without cutting any content. It solves the problem of the manual running too long vertically on the dashboard or the free page, making it hard to find what you need. An overview panel at the top gives you the big picture, and a search box lets you jump to the right entry by keyword. Tabs and a table of contents switch between major sections, and each entry is collapsed into an accordion so you can open only what you need. Long entries scroll within a fixed-height area, and pressing 'Open full text' shows the whole thing at once in a drawer or modal. Open and closed states are remembered in localStorage, so your previous state is preserved next time. The content itself is not abbreviated, and printing or exporting always outputs the full text. The Free, Pro, and Premium display scopes are preserved, so the set of features explained does not change unexpectedly per plan.

When to use: Use it when you want to quickly find how to use a feature or a caution in the manual, when a long page makes it easy to lose the entry you want, or when you want to read the full text all at once. It suits anyone who opens the dashboard or the free page regularly.

What to input: There is no special input field. You use it by opening the manual and typing a keyword in the search box, choosing a section with the tabs or table of contents, and pressing an entry heading to open or close it. To read everything at once, press 'Open full text'.

Steps:

  1. Open the manual on the dashboard or the free page and check the overview panel at the top
  2. Type a feature name or keyword in the search box to narrow down to the relevant entry
  3. Switch between major sections such as 'Basics' or 'Output' using the tabs or table of contents
  4. Press the heading of the entry you want to read to open the accordion and view its content
  5. Scroll within the area to read through longer entries
  6. To read everything at once, press 'Open full text' to show it in a drawer or modal
  7. Since opened entries stay in the same state next time, keep frequently used entries open
  8. To keep a paper or file copy, use print or export, which always outputs the full text
Overview panel
Search to filter
Tabs / index
Expand section
Open full text

Practical scene: Someone opening the dashboard for the first time wants to check the differences between output formats. Typing 'print' in the search box shows only the relevant entry, and pressing its heading reveals the steps. On another day, they use 'Open full text' to show the whole manual in a drawer and review several parts together. Entries they left open before appear the same way the next time they open it.

Common mistakes:

  • Mistaking a collapsed entry for missing information and giving up without opening it from search or the table of contents
  • Assuming compact display removes content
  • Being confused that a different device or browser does not carry over the previous open/closed state
  • Opening accordions one by one when you want the full text, instead of using 'Open full text'
  • Wanting to print only part but not selecting a range, then being surprised the full text is output

Cautions: Compact display only tidies the appearance; it does not remove content. Entries that are collapsed and not visible still exist and can be opened from search or the table of contents. Open and closed states are saved in your browser's localStorage, so a different device or browser may not carry over your previous state. Print and export always output the full text, so select the range you need if you want to keep only part of it. This service is not investment, legal, or tax advice.

💡 Tips

  • Even if you only half-remember a feature name, typing a partial keyword in the search box narrows the candidates.
  • Keep frequently referenced entries open so they appear the same next time and you spend less time searching.
  • When you want to review everything or read along together, use 'Open full text' for a drawer view that is easier to follow.
  • To share on paper or as a file, use print or export, which keeps the full text regardless of the compact display.

◯ Do

  • Open the content you want from the search box or the table of contents
  • Use 'Open full text' when reading everything at once
  • Select the range you want to keep before printing or exporting

✕ Don't

  • Do not conclude a collapsed entry means the information is missing
  • Do not assume compact display removes content
  • Do not expect open/closed state to always carry across devices or browsers

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Choosing an Output Format (Overview of the 7 Formats), Printing and PDF/A-ready Output

Output formats

Choosing an Output Format (Overview of the 7 Formats) — Pick from 7 formats to match your purpose: copy, txt, markdown, html, print, PDF/A-ready HTML, and json. Free Pro Premium Beginner

What it is: A guide to picking the right output format for how you will use the document: pasting, saving, printing, converting to PDF, or handing data to another system. You can regenerate the same input in a different format at any time, so knowing the mapping is all it takes.

When to use: Refer to it before generating, when deciding where the document will be used. Once you settle on a default format per purpose, choosing becomes automatic.

What to input: Select one format on the output screen. You can also keep your input as is and regenerate with a different format.

Steps:

  1. First decide how the document will be used: pasting, saving, printing, PDF conversion, or data handoff.
  2. For pasting into chat or email, choose copy.
  3. For keeping a file, choose txt; for continued editing in a note app or wiki, choose markdown.
  4. For embedding in a web page, choose html - a body-only fragment.
  5. For a paper submission, choose print - a complete document laid out for A4.
  6. For PDF conversion, choose PDF/A-ready HTML; for handing data to another system, choose json.
  7. Press the output button, then download the file if you need to keep it.
FormatUse forContent
Copy / TextPasting into chat or emailPlain text
MarkdownImporting into document toolsMarkdown
HTMLEmbedding / on-screen reviewHTML fragment
PrintPrinting as-isComplete HTML document (A4)
PDF/A-ready HTMLPDF conversion / archivingSelf-contained HTML document
JSONSystem integration / storageStructured data

Practical scene: Use copy for a quick paste into chat, txt to keep a record, and print when you need a paper copy to submit. Once you fix a default format for each purpose, every generation goes smoothly without hesitation.

Common mistakes:

  • Mistaking the html fragment for a complete document - use print or PDF/A-ready HTML for full documents.
  • Choosing copy when you actually want to print, and ending up with plain-text layout.
  • Picking a text format for a data handoff, which forces extra processing on the receiving side - json is the right choice there.
  • Rethinking the format from scratch every time - fixing a default per purpose is much faster.

Cautions: All 7 formats are available on the Free plan. Downloads are saved with the correct file extension for each format. PDF/A conformance depends on your conversion tool and is not guaranteed by this service.

💡 Tips

  • When unsure, start from a simple split: copy or print if a person will read it, markdown or json if a tool will consume it.
  • An efficient flow is to check the content on screen first, then regenerate in the format you want to keep.
  • Downloads already carry the correct extension, so adding a date or project name to the filename is all the organizing you need.

◯ Do

  • Before generating, decide the one place where the document will finally be used.
  • Download any output you need to keep as soon as it is generated.

✕ Don't

  • Do not pick a format at random before the purpose is clear - you can always regenerate in another format later.
  • Do not submit a converted PDF without checking it when PDF/A conformance is required - conformance depends on the conversion tool.

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Copy Format (Paste-Ready Text), TXT Format (Text File), Markdown Format, HTML Format (Embeddable Fragment), Saving Your Output (Copy, Download, Print)

Copy Format (Paste-Ready Text) — Plain text formatted with simple symbols, ready to paste anywhere. Free Pro Premium Beginner

What it is: Gives you readable text you can paste straight into email or chat. Headings and separators are shaped with symbols, so the document's structure still comes through wherever you paste it.

When to use: Use it when you want to paste the output directly into another app instead of saving a file. It is the fewest-steps route to sharing, which also makes it handy for urgent messages.

What to input: Just select copy as the output format - your template inputs stay exactly the same.

Steps:

  1. Select copy as the output format.
  2. Press the output button.
  3. Read the generated text on screen and confirm the content.
  4. Copy the text.
  5. Paste it into email or chat, then check how it looks on the receiving side.

Practical scene: When sharing a trade memo in team chat, generate it as copy and paste it in as is. No file is involved, so it takes the fewest steps from output to shared message.

Common mistakes:

  • Expecting rich formatting like a word processor - consider html or print if you need styling.
  • Closing the screen before actually copying the text.
  • Mistaking symbol alignment shifts caused by the destination's font for broken output.

Cautions: It is plain text, so there are no colors or table borders; headings and separators are expressed with symbols. If you need styled documents, choose html or print instead.

💡 Tips

  • Because headings and separators come as symbols, even longer text stays readable when pasted as is.
  • Templates that condense the key points into a short body are the best match for copy-and-chat sharing.
  • If you need both a paste and a saved file, simply regenerate the same input once more as txt.

◯ Do

  • After pasting, check once how the text appears on the receiving side.
  • Make copy your first choice whenever the goal is a straight paste.

✕ Don't

  • Do not use copy for printing or formal submissions - print is the right format there.
  • Do not choose copy for documents that need colors or table borders.

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Choosing an Output Format (Overview of the 7 Formats), TXT Format (Text File), Saving Your Output (Copy, Download, Print)

TXT Format (Text File) — Download the document as a simple .txt text file. Free Pro Premium Beginner

What it is: Keeps the output as a file on your device so you can reopen it later. It needs no special app, which makes it a safe choice for long-term storage and moving between environments.

When to use: Use it when you want to save records as files or manage documents in folders. It suits a routine of building up daily records especially well.

What to input: Just select txt as the output format. The download is saved with the correct .txt extension.

Steps:

  1. Select txt as the output format.
  2. Press the output button.
  3. Check the content on screen.
  4. Download the file - it is saved with the correct .txt extension.
  5. Add a date or project name to the filename and file it in your chosen folder.

Practical scene: Saving each day's trade log as a txt file lets you organize and review them in folders later. Since the format opens anywhere, it suits records you want to keep for the long run.

Common mistakes:

  • Closing without saving on the Free plan and losing the output.
  • Expecting tables or styling in txt - consider markdown or html if you need structure.
  • Piling up files with default names, then being unable to tell which record is which.

Cautions: It is plain text with no styling. On the Free plan there is no output history, so download and keep any output you need right away.

💡 Tips

  • Set a filename rule with a date from the start, and your records will line up chronologically on their own.
  • Because txt opens in virtually any environment, it works well for handing files to others and for long-term storage.
  • For content you plan to keep editing and extending, generating as markdown and growing it in a note app is a good alternative.

◯ Do

  • Download and save any output you need as soon as it is generated.
  • Decide on a folder location and a filename rule, and stick to them.

✕ Don't

  • Do not close the screen on the Free plan assuming you can retrieve the output from history later - Free keeps no output history.
  • Do not choose txt as the final format for documents that need tables.

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Choosing an Output Format (Overview of the 7 Formats), Copy Format (Paste-Ready Text), Saving Your Output (Copy, Download, Print)

Markdown Format — Outputs headings and lists in Markdown syntax, easy to reuse in note apps and wikis. Free Pro Premium Beginner

What it is: Lets you import the document into Markdown-aware note apps or internal wikis while keeping its structure. Headings and lists survive as syntax, which makes later re-editing and searching much easier.

When to use: Use it when you plan to manage or edit the output in a note app or wiki. It suits documents you keep adding to over time rather than one-off outputs.

What to input: Just select markdown as the output format. Check beforehand that your destination tool understands Markdown.

Steps:

  1. Select markdown as the output format.
  2. Press the output button.
  3. Check the content, then download the file or copy the text.
  4. Import it into a Markdown-aware note app or wiki.
  5. Confirm that headings and lists render as intended in the destination.
  6. Keep adding to and editing the document there as needed.

Practical scene: Generate your weekly review memo as markdown, paste it into your usual note app, and keep adding to it. Since headings and lists remain as syntax, organizing and searching the accumulated notes stays easy.

Common mistakes:

  • Pasting into a place that does not support Markdown, so the raw symbols show up.
  • Always choosing markdown even when copy would be more readable for a plain paste.
  • Mistaking rendering differences between tools for broken output - appearance depends on the destination's Markdown engine.

Cautions: The final appearance depends on how your tool renders Markdown. Downloads are saved with the correct file extension. If the rendering looks off, check the destination tool's Markdown support first.

💡 Tips

  • The longer the document, the more you gain from importing it as markdown, since the heading structure carries over intact.
  • Standardizing on markdown for documents stored in an internal wiki keeps them easy to search and re-edit later.
  • If you are unsure whether the destination supports Markdown, test with a short output before moving the real document.

◯ Do

  • Generate as markdown for documents you will grow in a note app or wiki.
  • After importing, verify that the heading levels display correctly.

✕ Don't

  • Do not paste raw markdown into chat or email tools that do not render it - copy is the better fit there.
  • Do not choose markdown as the final format for a document you will print and submit.

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Choosing an Output Format (Overview of the 7 Formats), Copy Format (Paste-Ready Text), TXT Format (Text File)

HTML Format (Embeddable Fragment) — Outputs an HTML fragment for embedding in a web page - not a complete document. Free Pro Premium Intermediate

What it is: Lets you drop the document's content into an existing web page or blog post. Because it is a body-only fragment, it inherits the styling of the host page and blends naturally into your site's design.

When to use: Use it when you want to embed the output inside the body of a site or blog. It is not the right choice when you need a file that opens on its own.

What to input: Just select html as the output format. It helps to confirm in advance that the destination lets you edit HTML.

Steps:

  1. Select html as the output format.
  2. Press the output button.
  3. Copy or download the generated fragment.
  4. Open the editing screen of the target page.
  5. Paste the fragment where the body HTML can be edited.
  6. View the page and confirm the content blends with the surrounding design.

Practical scene: You can embed a notice created from a template directly into an announcements page on your own site. Since it inherits the page's styling, the result matches the look of the rest of your site.

Common mistakes:

  • Opening the fragment by itself in a browser and thinking the layout is broken.
  • Choosing html for printing - the print format is the right choice for that.
  • Pasting into a field that does not accept HTML, so the tags show up as literal text.

Cautions: The html format is a body-only fragment and is not meant to be opened or printed on its own. If you need a complete HTML document, use print or PDF/A-ready HTML instead.

💡 Tips

  • The fragment inherits the host page's styling, so design adjustments belong on the page side, not in the fragment.
  • When you need a complete HTML document that opens on its own, switch to print or PDF/A-ready HTML instead.
  • Confirming that the destination offers an HTML editing mode before pasting saves you from redoing the work.

◯ Do

  • Paste the fragment in the destination's body HTML editing mode.
  • Check the finished look on the live page view before publishing.

✕ Don't

  • Do not distribute the html fragment as a standalone file - use print or PDF/A-ready HTML for complete documents.
  • Do not paste the fragment into fields or chats that do not interpret HTML tags.

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Choosing an Output Format (Overview of the 7 Formats), Saving Your Output (Copy, Download, Print)

Print (Full HTML Document) — Generates a complete HTML document laid out for A4 paper, printable straight from the print button. Free Pro Premium Beginner

What it is: Use this format when you need a cleanly laid-out paper copy for submission or filing. Unlike the on-screen fragment, it is a complete document designed for A4 and printable on its own.

When to use: When you need a paper copy, an in-person review, or handwritten signature fields - and also when you want filed records to look properly formatted.

What to input: No extra input beyond the template fields; simply choose "print" as the output format.

Steps:

  1. Open the template with "Use" and fill in the fields.
  2. Choose "print" as the output format and generate.
  3. Check the content on screen for errors.
  4. Click the print button (it re-fetches the full print document, then opens your browser's print dialog).
  5. Check the A4 layout and page count in the print preview.
  6. Adjust browser-side settings such as copies or duplex if needed, then print.
Generate output
Press Print
The complete print document is fetched
Browser print dialog

Practical scene: When filing monthly trade records on paper, the print format gives you an A4-ready document you can print as is. It also suits in-person meetings where someone signs a confirmation field by hand.

Common mistakes:

  • Printing the list screen with the browser's own print command (use the print button in the print format instead).
  • Choosing print when your real goal is PDF conversion (pdfa_html is the better fit).
  • Printing without checking the preview and getting page breaks in unintended places.
  • Assuming a print dialog that fails to open is a bug - the browser's popup blocker settings are often the cause.

Cautions: The print button does not print the on-screen view; it re-fetches the complete print document first, so the layout is always correct. Your content is never sent to external servers. If your real goal is a PDF, the pdfa_html format is the better fit.

💡 Tips

  • For templates with handwritten signature fields, check where the fields land in the preview before printing to avoid redoing it.
  • If the print dialog does not open, check your browser's popup blocker settings first.
  • If paper filing is the plan, include the date or a reference number in the document fields so you can find it after binding.

◯ Do

  • Always print via the print button in the print format - it re-fetches the print document, so the layout is always right.
  • Check page count and margins in the preview before printing.

✕ Don't

  • Printing the on-screen list view as-is and submitting it.
  • Submitting or filing printed pages without checking how they came out.

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: PDF/A-Ready HTML (pdfa_html Format), JSON Format (Structured Data), Using a Template (From Input to Output)

PDF/A-Ready HTML (pdfa_html Format) — A self-contained complete HTML document with no scripts or external assets, suited as source material for PDF conversion. Free Pro Premium Intermediate

What it is: Use this format to produce a fully self-contained HTML document - no scripts, no external assets - intended for conversion to PDF for archiving or submission. With zero external references, conversion results are far less environment-dependent.

When to use: When you plan to save or submit the document as a PDF, or need a file with zero external references. It also suits audit situations where you want to keep the pre-conversion source alongside the PDF.

What to input: Only the template fields. Choose "pdfa_html" as the output format; downloads are saved with the correct file extension and MIME type.

Steps:

  1. Fill in the template fields.
  2. Choose "pdfa_html" as the output format and generate.
  3. Download and save the file - it uses the correct extension and MIME type.
  4. Open it in a browser to check the content and layout.
  5. Convert it to PDF with your own conversion tool.
  6. Open the resulting PDF and confirm the layout and text are intact.
  7. For long-term storage, keep the pre-conversion pdfa_html file alongside the PDF.

Practical scene: When you want records converted to PDF for audits or long-term storage, the dependency-free pdfa_html file makes a stable conversion source. If a recipient asks for a PDF submission, converting from this format gives you a well-formatted result.

Common mistakes:

  • Assuming the downloaded pdfa_html is already a PDF/A-compliant PDF (a separate conversion step is required).
  • Confusing it with the html format for embedding (html is a fragment; pdfa_html is a complete document).
  • Submitting the converted PDF without opening and checking it.
  • Believing the service guarantees PDF/A conformance - that depends on your conversion tool.

Cautions: PDF/A conformance depends on the conversion tool you use; the service does not guarantee conformance. The file is designed to reference no external URLs. Like all formats it is available on Free, and Pro and Premium include unlimited PDF/A-ready output.

💡 Tips

  • For audits and archiving, note down which conversion tool you used and when - it makes the trail easy to explain later.
  • Because the file is self-contained with no scripts or external references, it is easy to handle even in tightly restricted environments.
  • When converting documents in bulk, convert one first and check the result before processing the rest - it saves rework.

◯ Do

  • Open the pdfa_html in a browser and check the content before converting to PDF.
  • Ask the recipient whether PDF/A compliance is required before choosing your conversion method.

✕ Don't

  • Submitting the pdfa_html file itself as if it were a PDF.
  • Using the embeddable html fragment as source material for PDF conversion.

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Print (Full HTML Document), JSON Format (Structured Data), Output History (12-Month Retention on Pro)

JSON Format (Structured Data) — Outputs the document as structured data, suited for analysis and reuse in your own spreadsheets or systems. Free Pro Premium Intermediate

What it is: Use this format to receive the output as machine-readable structured data rather than a human-facing document. Because values can be pulled out field by field, it suits analysis and import into your own systems.

When to use: When you want to import records into your own tracking sheet or internal tools, or work with the data field by field. It also suits recurring records you plan to batch-process later.

What to input: Only the template fields. Choose "json" as the output format; downloads use the correct MIME type and file extension.

Steps:

  1. Fill in the template fields.
  2. Choose "json" as the output format and generate.
  3. Download and save the file - it uses the correct MIME type and extension.
  4. Import it into your spreadsheet software or internal tools.
  5. Check how field names map to values, then set up your summary columns and filters.
  6. If you will do this regularly, write down your import steps for next time.

Practical scene: If you save each trade record as JSON, you can later batch-import them into your own analysis sheet for review. When you want monthly trends tallied field by field, that is faster and more accurate than rereading documents.

Common mistakes:

  • Sending the raw JSON file to clients or outside parties as if it were a document.
  • Choosing json when you actually want a readable document (html or print works better for reading).
  • Bulk-importing without checking how fields map in the target tool, and tallying with misaligned columns.
  • Editing the file directly and breaking its structure - fixing the original inputs and regenerating is safer.

Cautions: JSON is a data format, not a submission-ready document. For submission or sharing, use document formats such as print or pdfa_html. Output data is never sent to external servers.

💡 Tips

  • For recurring outputs like trade records, saving them consistently as json lets you aggregate them all later.
  • If a target tool cannot read the file, open it first and look at the section and field structure - it makes the cause easy to isolate.
  • When you need both a readable deliverable and analysis data, generate twice from the same inputs - a document format such as print, plus json - so the contents match.

◯ Do

  • Choose json when your goal is data handoff or aggregation.
  • Keep an unmodified original of the file before importing or processing it.

✕ Don't

  • Sending the json file as a submission or sharing document.
  • Hand-editing the file contents for analysis - fix the original inputs and regenerate instead.

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Print (Full HTML Document), PDF/A-Ready HTML (pdfa_html Format), Using a Template (From Input to Output)

Printing at Home or the Office — How the print button fetches an A4-formatted print document and prints it cleanly through your browser. Free Pro Premium Beginner

What it is: Lets you take a generated document straight to paper. Pressing the print button re-fetches a complete print document laid out for A4, separate from the on-screen view, and then opens the print dialog. Because the result does not depend on how the screen looks, printing is consistent. Switching the destination in the print dialog also lets you save a PDF instead of printing on paper.

When to use: Use it when you want trade records or reviews on paper, need printed copies for a meeting or internal check, or want to save a PDF that looks exactly like the printout.

What to input: Just press the print button on an existing output. No additional input is needed.

Steps:

  1. Fill in the template and generate the document
  2. Press the print button on the output screen (it re-fetches the A4 print document, then opens the print dialog)
  3. Confirm the paper size in the print dialog is set to A4
  4. Check page breaks and layout in the print preview
  5. If everything looks right, print
  6. To keep a PDF, choose the save-as-PDF destination in the print dialog
  7. If the print dialog does not open, check your browser's pop-up blocker settings
Generate output
Press Print
Refetch print doc
Print dialog opens
Print on A4

Practical scene: It suits a personal trader who prints the week's trade records to keep with a notebook, or a staff member who prints a single client briefing memo to bring to a meeting. In both cases, one test print to confirm the layout before the real run avoids waste.

Common mistakes:

  • Printing the on-screen preview through the browser menu and getting a broken layout (always print via the print button on the output screen)
  • Printing with a paper size other than A4 and ending up with a mismatched layout
  • Mistaking a pop-up-blocked print dialog for a defect
  • Skipping the print preview and noticing layout problems only after a large print run

Cautions: Fine details of the result, such as margins and page breaks, depend on your browser and printer settings. If the print dialog does not open, a pop-up blocker is the usual cause and allowing the site fixes it. For distribution that will be converted to PDF, the self-contained pdfa_html format with no external references is also available (PDF/A conformance depends on the conversion tool and is not guaranteed).

💡 Tips

  • Print one test page first, confirm margins and page breaks, then print the copies you need.
  • Documents headed for paper deserve a final check of unfilled items and QA warnings first; it saves reprinting.
  • Saving a PDF lets you reprint later with exactly the same appearance.

◯ Do

  • Print via the print button on the output screen
  • Check the print preview before committing to paper

✕ Don't

  • Do not run a large print job without a test page
  • Do not hand out printed documents you have not checked

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Print (Full HTML Document), PDF/A-Ready HTML (pdfa_html Format), Choosing an Output Format (Overview of the 7 Formats), How to Read a Generated Document, Saving Your Output (Copy, Download, Print)

How to create PDF files (PDF conversion) — How to save an output as a PDF. Use the pdfa_html format (built for PDF conversion) or the print format, then convert with your browser's Save as PDF or a conversion tool. Free Pro Premium Beginner

What it is: Lets you save and share a generated document as a PDF file. Instead of generating PDFs directly, the service provides a self-contained HTML document with no scripts or external assets (pdfa_html) and a complete A4 print document (print); you convert it to PDF in your own environment. The document body is never sent to an external server.

When to use: Use it when you need a fixed-layout file, such as sending a document to a client, archiving it long term, or submitting it on paper.

What to input: A generated output and a format choice (pdfa_html or print).

Steps:

  1. Open a template, fill in the fields you need, and generate the output.
  2. Choose the pdfa_html format (a self-contained HTML document built for PDF conversion).
  3. Save the file with the download button. The file extension is set automatically to match the format.
  4. Open the saved HTML file in your browser.
  5. From the browser's print menu, choose Save as PDF, set the paper size to A4, and save.
  6. Alternatively, use the print button of the print format and choose Save as PDF in the print dialog. The print button re-fetches the latest print document before opening.
  7. Open the finished PDF and check the body text, page breaks, and layout.
Select pdfa_html
Generate
Save the file
Convert to PDF
Review result

Practical scene: Useful when emailing a client a PDF of the explanation memo used in a meeting, or archiving monthly trade logs as PDFs. Even for paper submissions, converting to PDF first makes reprints and replacements easy.

Common mistakes:

  • Choosing the html format (an embed fragment) by mistake; it loses its styling when opened on its own. Use pdfa_html or print for PDF conversion.
  • Changing the paper size away from A4 or adjusting the scale in the print dialog, which shifts the layout.
  • Mistaking a browser popup blocker for a bug when the print window does not open.
  • Sending the converted PDF without checking it and missing awkward page breaks or cut-off content.

Cautions: pdfa_html is a self-contained document suited to PDF conversion, but full conformance to the PDF/A standard depends on the conversion tool you use and is not guaranteed by the service. If a recipient requires strict conformance, validate the file with a dedicated tool before submitting.

💡 Tips

  • The print format is designed for A4. Keeping paper size A4 and scale 100% avoids layout issues.
  • You can turn off the browser's automatic print headers and footers (URL and date).
  • For long documents, preview the page breaks before sending.

◯ Do

  • Do a final check of the body text and unfilled items before converting to PDF
  • Keep the downloaded file's extension unchanged

✕ Don't

  • Do not convert the html embed fragment directly to PDF
  • Do not send unvalidated files to recipients that require strict PDF/A conformance

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Using a Template (From Input to Output), QA Check, Naming and organizing downloaded files

Printing and PDF/A-ready Output — A gentle guide to clean printing and to obtaining self-contained HTML that converts easily to PDF. Free Pro Premium Beginner

What it is: This feature is for printing a generated document on paper or obtaining it in a form that converts easily to PDF. FTH provides a print format for printing and a pdfa_html format for conversion. The print format is a complete HTML document assuming A4 paper; when you press the print button, it re-fetches a dedicated print document before printing. Bodies used to sometimes print as garbled text, but because the print button now re-fetches the print document, the current version prints correctly. The pdfa_html format is a self-contained, complete HTML document with no scripts or external assets, suited for loading into an external PDF conversion tool. Whether it conforms to PDF/A, however, depends on the conversion tool you use, and FTH does not guarantee conformance. Both formats are available on all plans. The preview is shown inside a sandboxed frame, and printing is based on the re-fetched print document rather than the on-screen appearance, so you get a result with fewer layout problems.

When to use: Use it when you want to hand out a document on paper, print a copy for your records, or turn it into a PDF to send or submit. It is especially useful when you want to deliver a clean layout to the recipient or keep the printed appearance stable.

What to input: There is no special input field. Simply generate the document from the target template, then choose print (for printing) or pdfa_html (for PDF conversion) as the output format. If you plan to convert to PDF, have your browser or PDF conversion tool ready.

Steps:

  1. Open the target template, fill in the required fields, and generate the document
  2. To print on paper, choose print as the output format
  3. Press the print button on screen; a dedicated print document is re-fetched and a print preview opens
  4. Check the paper size and margins, then print from the browser print dialog
  5. To make a PDF, choose pdfa_html as the output format and download it
  6. Open the downloaded self-contained HTML with your browser's 'Save as PDF' or an external PDF conversion tool
  7. Confirm the generated PDF has correct layout and no garbled text, then save or send it

Practical scene: A personal trader wants to keep a printed copy of a monthly summary made from their trading-record template. They choose print as the format, press the print button, and a dedicated print document is fetched and prints in a clean A4 layout. Another staff member exports a client explanation note as pdfa_html and prepares a PDF for delivery using the browser's Save as PDF. Both come out without garbled text.

Common mistakes:

  • Trying to print the on-screen preview directly instead of choosing the print format, resulting in a broken layout
  • Assuming pdfa_html always conforms to PDF/A and overlooking that it depends on the conversion tool
  • Pressing print with the pop-up blocker on and mistaking the blocked window for a failure
  • Not checking paper size and margins before printing and noticing layout problems only after distribution
  • Sending a converted PDF without checking for garbled text or layout issues

Cautions: The pdfa_html format is self-contained HTML that converts easily to PDF, but whether the final result conforms to PDF/A depends on the conversion tool you use, and FTH does not guarantee conformance. Printed results can vary in margins and so on depending on the browser and settings, so check an actual copy before distributing. If your browser's pop-up blocker is enabled, the print window may not open. This service is not investment, legal, or tax advice.

💡 Tips

  • If printing fails, first check the browser's pop-up blocker and remember that the print button re-fetches the latest document.
  • For delivery PDFs, set margins to 'none' or 'default' in the browser's Save as PDF to better preserve the template's A4 layout.
  • When using the same document on paper and as a PDF, print-check with print first, then export as pdfa_html for a stable result.
  • For destinations that require strict PDF/A conformance, validate with a tool that claims that support before submitting.

◯ Do

  • Choose the print format when printing on paper
  • Check an actual print or PDF once before distributing
  • Validate PDF conversion conformance with the tool you use

✕ Don't

  • Do not distribute a broken layout by printing the preview directly
  • Do not assume pdfa_html always conforms to PDF/A
  • Do not conclude printing is broken without checking the pop-up blocker

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Choosing an Output Format (Overview of the 7 Formats), Brand Kit, Evidence / Document Seal

Output Contract — A per-template data declaration of purpose, audience, layout, and output formats that doubles as the audit yardstick for output quality. Free Pro Premium Intermediate

What it is: An output contract declares, per standard template and as data rather than code, what the document is for, who reads it, which layout family shapes it, which input fields matter, which sections, checklists, and cautions it carries, and which languages and formats it may be produced in. The contract plays two roles: it guides how the document is composed, and it serves as the yardstick for an independent 12-axis quality audit of real renders (purpose alignment, field relevance, checklist relevance, actionability, structure, visual hierarchy, audience fit, tone fit, language integrity, format integrity, compliance honesty, download integrity). A template without an explicit contract is never auto-passed - it is honestly reported for manual review. The contract is a record-format and quality-check framework; it never judges or guarantees the legal adequacy of any document.

When to use: It works in the background whenever you check a template's purpose and audience on the detail view, or confirm that the output structure and formats match expectations. Day-to-day use never requires editing a contract yourself.

What to input: Nothing to enter on your side. Contracts ship as data bundled with the templates and take effect simply by choosing a template and generating output as usual.

Steps:

  1. Choose a template and review the purpose, audience, and format notes on the detail view.
  2. Enter values and generate output as usual; the document structure (summary, checklist, cautions, and so on) follows the contract declaration.
  3. If the format choices look narrower on some templates, only the formats the contract declares are being offered.
  4. If the composition does not fit your purpose, consider another template or reach out via the contact page.
Header & summaryTitle and key points, check this first
Body (your inputs)Your entered values fill the body
Unfilled & checklistUnfilled items and review checklist
Notices & footerDisclaimers always remain at the end

Practical scene: When producing a client-facing explanation, the contract declares the outward audience, the pre-share check, and the allowed formats, which helps keep internal-memo composition from leaking in. When an auditor reviews quality, the 12-axis comparison of contract versus real output provides the working evidence.

Common mistakes:

  • Reading a manual-review flag as a bug - it is the honest report that no explicit contract exists.
  • Skipping the content check on the assumption that a contract makes the substance correct.
  • Treating a template with fewer format choices as broken - only contract-declared formats are offered.

Cautions: An output contract does not review the substance of your document. Verifying the accuracy and legality of what you write remains your own responsibility. Templates without an explicit contract run on the default generic composition and are reported for manual review in audits - that is honest reporting, not a defect.

💡 Tips

  • The purpose and audience notes on the detail view come from the contract - use them to compare candidate templates.
  • When torn between templates in one category, comparing the declared checklists and cautions makes the choice easier.

Data handling: Output contracts are declaration data bundled with the plugin; resolving and auditing them happens entirely inside the customer-controlled environment. Inputs and output text are never transmitted externally.

Related: Layout Families, Translation Status and Untranslated Items, QA Check

Layout Families — Twenty-two layout groupings that align the skeleton or styling of outputs by document character; each template's output contract declares exactly one. Free Pro Premium Intermediate

What it is: Layout families align the appearance and composition of template outputs with the character of each document. Structural families - letter and email, checklist and worksheet, ledger and register, minutes and committee papers, periodic reports, personal records, consent and disclaimer, procedure and FAQ - shape the section composition itself to match the document type. Styling families - client leaflet, internal approval form, partner request, media brief, seminar note, bilingual parallel, performance journal, risk worksheet, and others - keep the shared skeleton and refine headings and presentation. Twenty-two families are defined, and each template declares exactly one through its output contract; without a declaration the generic memo shape applies. Whatever the family, the offering remains a record format - it never judges the substance of a document.

When to use: When you produce documents of different characters back to back - say a client leaflet and an internal ledger - the fitting skeleton and styling are chosen automatically. There is no manual family switch to operate.

What to input: Nothing to enter. Choosing a template applies the family its output contract declares.

Steps:

  1. Choose a template - the family follows from its output contract declaration.
  2. Enter values as usual and pick an output format such as HTML, print, or PDF/A-ready.
  3. For print and PDF-save output you get a document whose headings and separations match the family.
  4. If the composition does not suit the task, compare other templates in the same category and switch.
Host pagePaste into your own site or page
HTML fragmentBody content only, not a full document
Section markupHeadings, tables and checklists as tags
DisclaimersFixed notices are kept in the fragment

Practical scene: Ledger-type templates center on row order and record fields, while client-explanation types lead with readable headings and confirmation areas. The same input flow yields a finish matched to the document's character, cutting the manual layout fixes needed after output.

Common mistakes:

  • Mistaking visual differences for plan-gated features - families work the same on every plan.
  • Letting a tidy layout stand in for a content review.
  • Treating generic-memo output as a defect - it is the honest default when no explicit declaration exists.

Cautions: Layout families arrange appearance and composition; they do not verify the accuracy or legality of what you write. Review content yourself before sharing. PDF/A-ready output is HTML prepared for PDF saving, not a certified PDF/A file.

💡 Tips

  • When similar templates compete, comparing the skeleton (ledger versus report, say) via the detail notes and sample output speeds the choice.
  • Checking separations and headings in print preview before printing shortens the final presentation check.

Data handling: Resolving and applying layout families happens entirely inside the customer-controlled environment. Inputs and output text are never transmitted externally.

Related: Output Contract, Choosing an Output Format (Overview of the 7 Formats), Print (Full HTML Document)

Languages

Language Selection — Choose the output language. On Free you can pick Japanese, English, or a bilingual JA+EN layout; the page language is preselected. Free Pro Premium Beginner

What it is: The basic control for switching the output language to match your reader. The language of the page you are viewing is preselected, so a Japanese page starts in Japanese and an English page starts in English.

When to use: When you want records in English, or both languages side by side in one document - the standard adjustment whenever your reader's language differs from your own.

What to input: Open a template with "Use" and the language field appears. Pick Japanese, English, or the bilingual layout.

Steps:

  1. Open the template with "Use".
  2. Check the language field - the language of the page you are on is preselected.
  3. Pick Japanese, English, or the bilingual layout.
  4. Fill in the remaining fields and generate.
  5. Confirm the output is in the language you intended.

Practical scene: If your trading tools are in English and you want matching records, switching the language field to English is all it takes. When you have readers of both languages, the bilingual layout covers everyone in a single document.

Common mistakes:

  • Generating with the default language still selected and getting an unintended language.
  • Trying to select 12 languages on Free (Free has three options; 12 languages requires Pro or Premium).
  • Generating twice for a mixed-language audience instead of using the bilingual layout once.

Cautions: Free offers only Japanese, English, and bilingual output. Simultaneous 12-language output is a Pro/Premium feature. The default follows the page language, so double-check before generating to avoid an unintended language.

💡 Tips

  • For documents read by both Japanese and English speakers, the bilingual layout handles it in one output.
  • Opening from an English page preselects English, so making a habit of glancing at the language field before generating prevents surprises.
  • Settle the content first in the language you read best, then switch languages and regenerate - reviewing becomes much easier.

◯ Do

  • Always check the language field before generating.
  • Match the choice - Japanese, English, or bilingual - to your reader.

✕ Don't

  • Generating repeatedly without checking the language field.
  • Making the bilingual layout stand in for true multilingual distribution - the 12-language output on Pro/Premium is built for that.

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Simultaneous 12-Language Output, Using a Template (From Input to Output), Free Templates Hub

Using Japanese-English Side-by-Side Output — How to generate one document with Japanese and English side by side. Available on the Free plan as well. Free Pro Premium Beginner

What it is: Generate one document containing the same content in both Japanese and English, so you can share a single document with readers of either language. On every plan, it works with any of the 7 output formats.

When to use: Use it when sharing the same document with overseas counterparties or English-speaking team members, or when you want to keep records while checking the English phrasing.

What to input: The input fields are the same as for any template. Just choose the Japanese-English side-by-side option in the language selector; no extra input is required.

Steps:

  1. Click Use on the template card.
  2. Fill in the required fields.
  3. Choose the Japanese-English side-by-side option in the language selector (the page language is the default).
  4. Pick the output format that fits your purpose from the 7 formats.
  5. Click the output button and review the document with both languages side by side.
  6. Save it via copy or download and share it with the recipient.
Single languageJA + EN bilingual
Japanese or English onlySame content in both languages
Shorter, compact documentEasy to share internationally
Best for one-language readersRoughly doubles the length
Available on Free too

Practical scene: For example, you can keep your records in Japanese and quote the English half directly when contacting an overseas support desk. In a team with English speakers, a single output serves both audiences with the same document.

Common mistakes:

  • Exporting with the default setting and sharing a document that contains only one language.
  • Editing only the Japanese half afterward, so it no longer matches the English half.
  • Printing a long side-by-side document without checking the print layout first.

Cautions: A side-by-side document is longer than a single-language one, so check the page count and page breaks before printing. The default language follows the page language, so select the side-by-side option explicitly each time you want it.

💡 Tips

  • If the recipient reads only English, a single-language English output is easier to read than side-by-side.
  • When edits are needed, update both languages at the same time to keep the content consistent.

◯ Do

  • After exporting, confirm that both Japanese and English appear in the document.
  • Choose between side-by-side and single-language output based on the audience.

✕ Don't

  • Rewriting only one language and sharing a document whose halves no longer match.
  • Including a language the recipient will not read and making the document needlessly long.

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Language Selection, Using a Template (From Input to Output), Choosing an Output Format (Overview of the 7 Formats)

Per-language Input and Manual Translation Values — Lets you optionally register your own translation of each free-text field per output language. Nothing is translated automatically; languages without a manual value show the original text with an untranslated note. Free Pro Premium Intermediate

What it is: Per-language input lets you optionally register your own translation of each free-text field for every output language. Under each text field on the Use form, open the per-language values (manual translation) block and an input appears for each selected output language. The value is sent internally as the pair of the field key and the language code (the key__lang form) and takes precedence in that language's output. No automatic translation is ever performed. For a language without a manual value, the original text is shown as entered, an untranslated note is attached, and the QA check at output time shows an untranslated warning. Choice fields render as bilingual options and dates render in each language's locale format, so only free-written sentences ever need a manual value.

When to use: Use it when a document generated in several languages contains free-text values such as a company name, a case name, or a description. Entering a manual value for at least the language you hand to the client avoids output with original-language text mixed in.

What to input: First select additional output languages, then open the per-language block under each text field and enter a value per language. Everything is optional; a language left blank gets the original text plus the untranslated note.

Steps:

  1. On the Use form, select additional output languages - with only the default language selected, the per-language block does not appear.
  2. Open the per-language values (manual translation) block under the text field.
  3. Enter your own translation into the input shown for each selected language; right-to-left languages accept right-to-left input.
  4. Generate and confirm each language version uses your manual value.
  5. For languages you left blank, confirm the original text, the untranslated note, and the untranslated QA warning.
  6. If an untranslated value remains in a language you will hand over, add the value and regenerate.
Select languages
Generate per lang
Detect gaps
Fill with English
RTL rendered

Practical scene: For a report handed to an English-speaking client, the staff member registers English values for the subject and the description in the per-language inputs. The English output now uses those values, and the untranslated note that marked the earlier version is gone. For material aimed at an Arabic-speaking client the inputs switch to right-to-left, and dates render in each language's own format, so only the free-written sentences ever needed manual work.

Common mistakes:

  • Selecting only one output language and mistaking the absent per-language block for a bug.
  • Believing that entering one value translates it into the other languages - each language is entered individually.
  • Distributing output with original-language text mixed in because the untranslated note went unnoticed.
  • Assuming choice fields also need manual values - options and dates render per language automatically.

Cautions: No automatic translation is performed. Languages without a manual value show the original text with the untranslated note. The per-language block appears when output languages beyond the default are selected (the number of selectable languages follows your plan). Verifying the accuracy of your translations is your own responsibility.

💡 Tips

  • You do not need to fill every language - prioritize the ones you actually hand to clients.
  • Use the untranslated QA warning as the final check that no warning remains in the language you deliver.
  • For boilerplate sentences, keep the translation you wrote once at hand and the next entry is fast.

◯ Do

  • Enter manual values for the languages you deliver and confirm no untranslated note remains before distributing.
  • Use translations after checking them yourself or with someone who knows the language.

✕ Don't

  • Do not describe this feature as automatic translation - every value is your own manual input.
  • Do not hand a language version with a remaining untranslated warning to a client without review.

Data handling: Per-language values are used only to generate the output; nothing is sent externally to translation services or anywhere else.

Related: Simultaneous 12-Language Output, English Fallback for Untranslated Content, Using Japanese-English Side-by-Side Output, Language Selection

Translation Status and Untranslated Items — Free-text inputs are never translated automatically. Untranslated items appear honestly with a note, and outward-facing outputs ask for confirmation first. Free Pro Premium Beginner

What it is: In multilingual output, template headings and fixed sections are assembled from per-language dictionaries, but text you write freely is never machine-translated. Translation status is the mechanism that reflects the real state - translated, untranslated, or fallback display - honestly in the output. Items with a manual per-language value appear in that language; items without one appear in the original wording together with an untranslated note. JSON output records the list of untranslated fields and any fallback usage as metadata. And when an outward-facing output still carries untranslated or unfilled items, a confirmation dialog appears before generation so you can proceed knowingly. The system never fabricates a translation to make the document look finished - knowing the true state before sharing comes first.

When to use: It matters when content entered in Japanese is output in English or another language, and when using 12-language simultaneous output. To check untranslated spots before sharing, look at the notes in the output and the JSON metadata.

What to input: Optionally enter your own translation per output language. Without one, the original text is output as provided, with an untranslated note.

Steps:

  1. Fill in the template as usual.
  2. For output in other languages, optionally add per-item translations via the per-language inputs.
  3. Generate the output. If untranslated items remain in an outward-facing output, a confirmation dialog lists them.
  4. Review, generate, and if needed add translations and regenerate.
Select languages
Generate per lang
Detect gaps
Fill with English
RTL rendered

Practical scene: Before sending an English request document to an overseas counterparty, the confirmation dialog reveals that a payment proviso is still untranslated; you add the translation and regenerate. Fewer translation gaps get discovered only after sending.

Common mistakes:

  • Reading the untranslated note as a bug - it is the honest display of a no-auto-translation design.
  • Confirming the dialog without reading it and sharing with items still untranslated.
  • Expecting every language to come out translated without using the per-language inputs.

Cautions: Because nothing is translated automatically, writing translations and verifying their accuracy is your own work. Whether to share an output that carries untranslated notes is also your decision. The confirmation dialog reports the state - it does not guarantee translation quality.

💡 Tips

  • Keep a note of your per-language wording for frequent phrases - next time it is a simple paste.
  • Before sharing, the JSON metadata (the untranslated-field list) gives you a mechanical sweep for anything missed.

Data handling: Translation-status detection, notes, and the confirmation dialog all run inside the customer-controlled environment. Your inputs are never sent to any external translation service.

Related: Per-language Input and Manual Translation Values, Output Contract, Simultaneous 12-Language Output

Account & billing

Account Page — A page where you can check your current plan, subscription status, expiry date, days remaining, and account type (master account or subaccount) at a glance. Free Pro Premium Beginner

What it is: Gives you a single place to review your subscription details and account status. It is also the starting point for billing tasks, and the first screen to check whenever a question about your plan or expiry date comes up, before contacting support.

When to use: Use it when you want to check your plan or expiry date, before moving on to billing tasks such as renewal or cancellation, or when you need to confirm whether you are the master account or a subaccount in a team setup.

What to input: No input is required. Your subscription details appear automatically once you are logged in.

Steps:

  1. Log in to the dashboard
  2. Open the account page
  3. Check your current plan and subscription status
  4. Check the expiry date and days remaining (days remaining is shown only when subscription period data is available)
  5. Check your account type (master account or subaccount)
  6. If you are the master account and need to handle billing, proceed via the button to the Stripe portal

Practical scene: When renewal is approaching, you can confirm the expiry date and days remaining on the account page before handling payment. It is also the first screen a new team member should visit to find out whether they are the master account or a subaccount.

Common mistakes:

  • Looking for billing settings from a subaccount (payment screens exist only on the master account side)
  • Never checking the expiry date, then mistaking a lapsed subscription for a malfunction
  • Treating a missing days-remaining value as an error (it is simply not shown when no period data exists)
  • Not returning to this page after a payment procedure to confirm the subscription status was updated

Cautions: Subaccounts do not see billing buttons; instead a notice explains that contracts and billing are managed by the master account. Days remaining is displayed only when actual subscription period data exists, so a blank value is not a malfunction. When a subscription lapses, paid features stop working - this is normal behavior reflecting the plan status.

💡 Tips

  • Make it a habit to open the account page before your renewal month to verify the expiry date - it prevents overlooked lapses
  • In team use, have every member check the account type field first; it makes it easier to route all billing questions to the master account
  • After any payment or cancellation procedure, come back to this page to confirm the subscription status has been updated

◯ Do

  • Start every billing task from the account page and proceed to the Stripe portal from there
  • When unsure about your plan or expiry date, check this page before contacting support

✕ Don't

  • Do not wait until after the expiry date to start renewal procedures
  • Do not ask subaccount users to handle billing tasks - subaccounts have no payment screens

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Managing Payments (Stripe), Checking Plans and Upgrading, Subaccount Management (Premium)

Checking Plans and Upgrading — Compare the Free, Pro, and Premium plans and upgrade once you know exactly which features you need. Free Pro Beginner

What it is: Helps you compare what each plan offers and move to the plan that matches how you work. Free is the no-registration entry point with the free templates, Pro adds the full catalog with 12-language output and output history, and Premium adds team operation and document governance features on top.

When to use: Consider it when you want more than the free templates, when you need 12-language output, the QA check, or output history, or when team features such as subaccounts and approval flows become necessary.

What to input: Upgrading requires an account (login) and payment via Stripe. Comparing the plans themselves requires no registration.

Steps:

  1. Compare Free, Pro, and Premium on the plan list page
  2. Confirm which plan includes the features you need (12-language output, output history, team features, and so on)
  3. Register an account or log in
  4. Choose the plan to upgrade to
  5. Complete payment via Stripe
  6. Confirm the new plan is reflected on your account page

Practical scene: A common path is to get comfortable with the input-to-output flow on the free templates, then move to Pro once you need the business templates or 12-language output. When your team later wants approval flows or brand settings, that is the moment to consider Premium.

Common mistakes:

  • Assuming only the price difference is charged when changing plans (the new plan's full price is charged as a new payment)
  • Subscribing without checking which plan includes the features you need
  • Trying to change plans from a subaccount (the master account manages the contract)
  • Not checking the account page after payment and concluding the new features never arrived

Cautions: When changing plans, the new plan's price is charged as a new payment, and there are no prorated refunds. Check in advance which plan includes the features you need. Pro allows up to 3 accounts, but there is no self-management UI - the operator configures them. If you want to manage subaccounts yourselves, Premium is the plan for that.

💡 Tips

  • If unsure, get used to the basic input-to-output flow on Free first, and upgrade once the missing features become concrete - nothing is wasted that way
  • As a rule of thumb: Pro if you need 12-language output, the QA check, or 12-month output history; Premium if you need team operation features such as Brand Kit and approval flows
  • Before upgrading, jot down the moments where something was not possible in your daily work - it tells you exactly which rows of the plan comparison to look at

◯ Do

  • List the specific features missing from your current workflow before choosing a plan
  • Understand before you proceed that the new plan's price is charged as a new payment and there are no prorated refunds

✕ Don't

  • Do not rush into a higher plan for features you have no plans to use
  • Do not switch plans without checking how much of the current period remains - there is no prorated refund at switch time

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Account Page, Managing Payments (Stripe), Free Templates Hub

Choosing the right plan — A guide to deciding which of Free, Pro, or Premium fits you, working backward from what you actually need. Starting with Free is the default move. Free Pro Beginner

What it is: Helps you judge plans by how you actually work rather than by scanning a feature list. Three questions simplify the choice: is your focus personal records, do you need client-facing or multilingual documents, and do you need team-level approvals and controls?

When to use: Revisit this when you first start, when your usage grows and Free starts to feel tight, or when you begin considering team use.

What to input: A quick inventory of your main use: who reads your documents, in which languages, and how often you produce them.

Steps:

  1. Start with Free. No account is needed, and the free library templates are fully usable as-is.
  2. Write down your use cases: personal records, internal documents, or client-facing materials.
  3. If personal trade logs and reviews are your focus, Free already covers Japanese, English, and bilingual output across all 7 formats.
  4. Consider Pro when you need access to all templates, 12-language simultaneous output, or the 12-month output history.
  5. Premium becomes relevant once you need organizational operations: team approval flows, brand application, and audit readiness.
  6. Payment methods and receipts are handled in the Stripe portal. When changing plans, the new plan's price is billed fresh; there are no prorated refunds.
  7. If undecided, identify which of four things you are missing: template range, languages, history, or team operations.
Free: first try
Pro: full use
Premium: team ops
Manage via Stripe

Practical scene: A common path is building a logging habit on Free as an individual trader, then moving to Pro when client-facing documents enter the picture. Once a team needs approvals and audit trails, that is the moment to look at Premium.

Common mistakes:

  • Assuming nothing works without a paid plan (Free does not even require registration).
  • Using Free as if history were saved, then losing results that were never downloaded.
  • Expecting prorated refunds on plan changes and mistiming the switch.
  • Needing genuinely multilingual documents but stretching the bilingual option far past its purpose.

Cautions: Pro includes up to 3 accounts, but there is no self-service screen to add or assign them; the operator configures this for you. If you want to invite and manage subaccounts yourselves, that requires Premium. On every plan, document bodies stay off external servers by design.

💡 Tips

  • The core question is who reads your documents: yourself means Free, clients and languages mean Pro, team controls mean Premium.
  • Even a few client documents per month can justify Pro for the 12-month output history alone.
  • Verify template quality and output formats on Free before subscribing, so the decision is grounded in real use.

◯ Do

  • Try Free hands-on before deciding
  • Handle billing and receipts through the Stripe portal

✕ Don't

  • Do not jump to a higher plan before you actually need it
  • Do not switch plans without checking the billing terms first

Data handling: Your inputs and output text are never transmitted to external SG Group servers.

Related: Free Templates Hub, Account Page, Managing Payments (Stripe), Simultaneous 12-Language Output, Output History (12-Month Retention on Pro)

Plan Comparison Export — Exports the Free, Pro, and Premium comparison table in six formats - HTML, print HTML, PDF-save HTML, CSV, JSON, and Markdown - plus a combined ZIP bundle. Free Pro Premium Advanced

What it is: The Plan Comparison Export writes out the Free, Pro, and Premium feature comparison in six formats convenient for distribution, storage, and further editing: embeddable HTML, print HTML, PDF-save HTML, CSV for spreadsheets, JSON for processing, and Markdown for pasting into documents - plus a ZIP bundle containing all of them. The table is generated from the plan registry (the single source of plan information) at every export, so each export reflects the comparison as of that moment. One important honesty note: the print and PDF-save HTML are HTML documents intended for saving as PDF through the browser's print function - they are not certified PDF/A (the certified archival PDF standard). The headings and file names state this plainly.

When to use: Use it when distributing plan explanation materials, attaching the comparison to internal deliberation documents, or re-distributing the latest comparison when plans change.

What to input: Just choose the format to export. If you need every format, choose the ZIP bundle.

Steps:

  1. Open the plan-comparison export screen.
  2. Choose from the six formats - html, print, PDF-save, CSV, JSON, Markdown - or the ZIP bundle.
  3. Check the downloaded file.
  4. For the print or PDF-save HTML, open it in the browser and choose save as PDF from the print function.
  5. Confirm the content matches the comparison as of the export before distributing.
  6. After a plan change, re-export instead of continuing to hand out the old file.
FreeProPremium
TemplatesFree libraryFull catalogueFull catalogue
LanguagesJapanese & English12 simultaneous12 simultaneous
Accounts1 (no sign-up)Up to 310 standard + paid add-ons
OperationsHistory & QABrand Kit / Rulebook / approvals / Evidence…

Practical scene: For a plan-change announcement, the administrator exports the latest comparison as PDF-save HTML, saves it as a PDF via the browser's print function, and attaches it to the announcement. A CSV is exported as well and trimmed down in a spreadsheet for internal deliberation. Both come from the same plan registry, so no figure or feature name disagrees between them.

Common mistakes:

  • Presenting the PDF-save HTML as certified PDF/A - it is the save-as-PDF-via-browser-print method.
  • Continuing to distribute an old export as the current comparison.
  • Distributing a garbled CSV because the character-encoding setting in the spreadsheet app was never checked.
  • Mixing up the embeddable HTML and the print HTML.

Cautions: The print and PDF-save HTML use the save-as-PDF-via-browser-print method and are not certified PDF/A. An export is a snapshot of the comparison at that moment, so a plan change requires re-exporting. The export operation is performed from an administrator-facing screen.

💡 Tips

  • Keep the export date in the file name or inside the document, so anyone can tell which point in time the comparison reflects.
  • If you will use every format, pick the ZIP bundle so no format lags behind another.
  • JSON preserves the item order and values as data, which suits processing such as re-posting to an internal portal.

◯ Do

  • Confirm the content is current as of the export before distributing, and always re-export after a plan change.
  • When a PDF is needed, save the print or PDF-save HTML as a PDF via the browser's print function.

✕ Don't

  • Do not describe the print or PDF-save HTML as certified PDF/A.
  • Do not distribute a hand-edited comparison as the official one - regenerate it from the plan registry.

Data handling: Generating and exporting the comparison stay inside the customer-controlled environment; nothing is transmitted externally.

Related: Choosing the right plan, Checking Plans and Upgrading, Print (Full HTML Document), PDF/A-Ready HTML (pdfa_html Format)

🔒 Available on paid plans

These features are not available on your current plan — shown for reference only (no operating steps).

🔒 Simultaneous 12-Language Output — Generates the document in 12 languages in a single run. Untranslated parts fall back to English with a note, and Arabic and Urdu render right-to-left. View plans
🔒 Tone Selection — Pick from six tones; the choice changes both the writing style and the section structure of the document. View plans
🔒 Audience Selection — Pick the reader (internal, client, external, partner, approver, legal, and more) and the document structure automatically adapts to that reader. View plans
🔒 Detail Level Selection — Switch the document between three levels of depth - brief, standard, and detailed - changing the length and section structure without retyping your input. View plans
🔒 Sharing Mode (Presets) — Four presets (internal draft, client sharing, approval review, partner request) set the audience and tone together in one step. View plans
🔒 QA Check — Inspects the output for problematic expressions and unfilled fields and shows warnings on the relevant spots, helping your pre-share review. View plans
🔒 Output History (12-Month Retention on Pro) — Keeps a record of documents you generated so you can review and regenerate them later. Pro retains history for 12 months, Premium indefinitely; Free has no history. View plans
🔒 Unlimited History Retention (Premium) — On Premium, output history is retained with no time limit. There is no deletion path, so past records never quietly disappear. View plans
🔒 Template Packs — Groups related templates into a set, making it easier to line up the documents you need along a workflow. View plans
🔒 Subaccount Management (Premium) — Lets the master account invite team members and assign them different roles. Up to 10 subaccounts are included as standard; more are available for a fee. View plans
🔒 Brand Kit — Apply your brand name, logo, colors, footer, and cover page to generated documents for a consistent client-facing appearance. View plans
🔒 Clause Library (Approved Standard Text) — Manage standard clauses so that only approved text is inserted into outputs, keeping wording such as disclaimers unified across the team. View plans
🔒 Locked Sections — Pin critical text such as disclaimers and compensation disclosures into every output. View plans
🔒 Rulebook (Compliance Rules) — Warn or block banned wording, auto-insert required disclaimers, and add pre-share checks at output time. View plans
🔒 Evidence Mode — Choose from four modes to control how much evidence of each output is retained. View plans
🔒 Legal Hold — Block regeneration of a specific output ID so the output is preserved as-is. View plans
🔒 Workspace Profile (12 Industry Profiles) — Pick one of 12 industry presets to switch Rulebook defaults and recommended template categories for your field. View plans
🔒 Client and Case Workspaces — Keep a ledger of clients and cases with notes and next-action dates. View plans
🔒 Customization Request (Paid Quote) — Request additional languages, new templates, or adjustments as a paid quotation. View plans
🔒 Delivery Pack — Add a cover letter and a receipt-and-confirmation section to client-facing outputs, ready to hand over. View plans
🔒 Release Register — Register an output as the shared version in a ledger, so you can identify later exactly which version went out. View plans
🔒 Review Board — A board that shows at a glance how many items are pending approval, waiting on you, returned, or approved, so you can spot bottlenecks in the flow. View plans
🔒 Five-Step Approvals — An approval flow where up to five approvers act in strict order, with no skipping and every action written to the audit record. View plans
🔒 Local Audit Export — Download your output history, approvals, and hashes as a JSON file. Nothing is sent to any external server. View plans
🔒 Self-Check Center — Generates a self-diagnostic JSON summarizing your setup and operating state. It contains zero document bodies and zero input values. View plans
🔒 Client-Safe Summary — Generates a summary with internal information removed, in a form suitable for sharing with clients. View plans
🔒 Template Builder — Create your own custom templates for your organization, and operate them together with versioning and diff. View plans
🔒 Template Versioning — Manage template changes as versions so you can trace how a template evolved. View plans
🔒 Version Diff — Compare two versions of a template and see exactly what changed. View plans
🔒 English Fallback for Untranslated Content — How 12-language output fills untranslated sections with English and marks them with a note. View plans
🔒 Right-to-Left (RTL) Document Output — Selecting Arabic or Urdu produces the entire document in a right-to-left layout. View plans
🔒 Tone Examples and How to Choose — A guide to comparing how the six tones change a document's structure and style, so you can choose the right one. View plans
🔒 Audience-Based Structure and How to Choose — How choosing an audience such as internal, customer, or approver changes the document's structure and what it includes. View plans
🔒 Business Templates Guide — A cross-cutting guide to getting the most out of the paid business template library using categories, audience, tone, and detail level. View plans
🔒 Output History and Regeneration — How to find past outputs in your history and regenerate them under the same conditions, with notes on retention periods and Legal Hold. View plans
🔒 A Document Workflow Built Around QA Checks — A basic workflow that reviews QA warnings on every output and fixes wording and unfilled fields before sharing, preventing avoidable mistakes. View plans
🔒 Premium Onboarding Guide — A setup guide covering what to configure, and in what order, after subscribing to Premium, from choosing an industry preset to going live. View plans
🔒 Compliance Features at a Glance — A bird's-eye view of how Premium's governance and evidence features, from the Rulebook to Legal Hold, layer together to protect your document operations. View plans
🔒 Team Operations Guide — A practical guide to running the service as a team: inviting subaccounts, designing roles, managing workspaces, and operating 5-step approvals with the Review Board. View plans
🔒 Trusted Timestamp Center — A Premium capability that attaches a timestamp to hashes of outputs, releases, Evidence Packages, Binders and similar items, recording that the hash existed at that moment (proof of existence) and giving a basis to detect later changes. Two modes are available: a local signed timestamp that sends nothing externally, and an RFC3161 mode that sends only the hash to a TSA you configure. View plans
🔒 Evidence Chain Dashboard — A Premium capability that shows, on one screen, the document hash, manifest hash, timestamp state, release state, Legal Hold, locked sections, Rulebook/clause/Brand versions, Evidence Mode, and chain health. You can run verify all to inspect the state and export a verification report. View plans
🔒 Proof Verification — A Premium capability that re-hashes a received original file, matches it against the manifest, and verifies the timestamp token. Hashing is done in the browser where possible and the body is not sent externally. Because the TSA certificate chain is bundled, verification works offline even years later, and recipients can check it for free. View plans
🔒 Evidence / Document Seal — A Premium capability that inserts an Evidence Seal (a shortened document hash, generation time, timestamp state, and Verification ID) on the cover of print and PDF/A-ready HTML, a short hash in the footer, and verification steps on the last page. It uses no external URLs or QR codes, showing the entry point to verification from the document alone. View plans
🔒 Content Playbook / Conditional Smart Sections — A Premium capability that automatically controls document structure with a bounded, deterministic rule engine centered on industry presets. Depending on conditions such as category, audience, language, output format, sharing mode, and Workspace Profile, it decides actions like making a section required, locking it, warning, inserting an approved clause, requiring approval, or hiding internal memos. View plans
🔒 Local DLP (Internal-only Scanner) — Before you share a document with a client, check for internal-only wording, guarantee- or advice-looking phrasing, personal data, and missing disclaimers entirely inside this environment. View plans
🔒 Obligation / Follow-up Register — Track next-check dates, deadlines, and renewal dates tied to your outputs as a register entirely inside this environment, and export them as an ICS file. View plans
🔒 Export / Submission Binder — Assemble multiple documents into one locked, self-contained file with Evidence Seals, a manifest, timestamps, a hash chain, a requirement index, and a searchable metadata index. View plans
🔒 TSA (RFC3161) Timestamp Settings — Register your own RFC3161-compatible timestamp authority (TSA), and only a hash is sent to obtain a third-party time attestation. If none is configured, nothing is sent externally. View plans
🔒 Timestamp Failure and Fallback — If a TSA connection fails, output is not blocked; it automatically switches to a local signed timestamp and records the sequence in the audit log. View plans
🔒 What Timestamps Mean, and Their Limits — A guide to what an FTH timestamp does and does not tell you, so you can use it correctly. View plans
🔒 Evidence Features Overview — An introductory map of how hashes, the manifest, timestamps, and verification fit together. View plans
🔒 Meeting Prep and Follow-up Pack — A work pack that chains pre-meeting preparation documents, same-day records, and a follow-up letter sent within 24 hours into one connected template sequence. View plans
🔒 Intent Capture and Comparative Recommendation Record Set — A work pack of three record templates - intent capture, comparative recommendation, and intent confirmation - each with a dedicated field for the basis of the recommendation. View plans
🔒 Purpose-based QA Presets — Switchable sets of QA check viewpoints and banned phrases for four purposes: ad review, client sharing, internal, and counterparty. View plans
🔒 Pre-share Handoff Check — Turns the final review just before handing a document to a client or an external party into a recorded checklist. View plans
🔒 Governance Setup Document Pack — A Premium work pack for governance-setup duties, bundling base internal-rule documents, a self-inspection check sheet, and an inspection record ledger. View plans
🔒 Ad Review Flow Preset — A Premium preset that adds a finance-advertising review path, review application form, and review ledger on top of the existing 5-step approvals. View plans
🔒 Audit Binder Scheduler — A Premium feature that plans the preparation of audit-ready evidence binders on a quarterly or annual cadence. It never sends anything automatically. View plans
🔒 Premium Control Center — A single view showing the configuration state of the Premium operations features - Brand Kit, Rulebook, evidence mode, timestamps, and the release register. View plans
🔒 B2B Meeting Agenda Builder — A work pack that produces meeting agendas and minutes in one consistent format for internal meetings, committees, and counterparty sessions. View plans
🔒 Client Intent Record Pack — A work pack for keeping suitability hearings, document delivery, explanation records, and the client's stated intent in one uniform record format. View plans
🔒 Product Explanation Checklist — A work pack of checklists and explanation-record templates so product explanations are confirmed and recorded from the same viewpoints every time. View plans
🔒 Compliance Wording Assistant — Preset phrase lists for seven common problem types that merge into the rulebook so the output QA flags them mechanically. View plans
🔒 Follow-up Task Board — A work pack that runs dated action items, submissions, and periodic checks with follow-up templates plus a single task list. View plans
🔒 Investment Committee Memo Pack — A Premium work pack keeping investment-committee submission memos, deliberation notes, minutes, and decision follow-ups in one consistent format. View plans
🔒 Financial Institution Review Pack — A Premium work pack organising product-review records and inspection-response registers - document requests, findings, and remediation status - in one uniform format. View plans
🔒 Conflict of Interest Register — A Premium work pack keeping identification records, chosen control measures, and periodic verification for potential conflicts of interest in register form. View plans
🔒 Delegation & Vendor Oversight Pack — A Premium work pack assembling the outsourcing lifecycle documents: vendor register, selection evaluation, at-contract check, annual monitoring, and termination checklist. View plans

Practical scenarios

Create a trading plan before you trade — Individual trader who wants to prepare before entering a trade
  1. Open the free template hub and find a trading-plan template by category or search
  2. Click Use on the card and enter the pair, planned entry price, and your stop-loss and take-profit levels
  3. If there are many fields, expand the optional-fields section and fill in only what you need
  4. Choose an output format, generate the document, and reread it before trading to check for gaps
  5. The document is your own record, not advice; make the final trading decision yourself
Review your trades on the weekend — Individual trader reviewing the week's trades on the weekend
  1. Pick a trade-review (trading journal) template in the free template hub
  2. Enter this week's trades: instrument, direction, profit or loss, and your reason for entering
  3. Fill in the what-went-well and what-to-improve fields in your own words
  4. Export as markdown or txt, keep the file, and reread it when you write next week's plan
Organize your MetaTrader results — Individual trader who trades on MetaTrader
  1. Choose a template from the MetaTrader category in the free template hub
  2. Copy figures from your MetaTrader trade history: period, number of trades, wins and losses, total profit or loss
  3. Add any patterns or lessons you noticed in the notes field
  4. Generate the document and save it as your monthly record (the free plan keeps no history, so keep the file yourself)
Check your risk-reward ratio before entering — Individual trader who wants to check numeric entry criteria
  1. Open a risk-reward ratio (RRR) template and check its fields on the detail page
  2. Enter your planned entry price, stop-loss distance, take-profit distance, and position size, then generate
  3. Review the organized output and check whether it meets the RRR threshold you set for yourself
  4. If it does not meet your threshold, skip the trade and keep that decision on record too
Use an emotion log to spot your decision habits — Individual trader who wants to understand their own decision habits
  1. Pick an emotion or trading-psychology log template
  2. Write down what you felt before and after the trade (rushed, unsure, confident) and the decision you made
  3. Save each output with the date and collect a few weeks of entries
  4. Reread them together and look for patterns that keep repeating
Write your stop-loss and take-profit rules in advance — Individual trader who wants rules in place before trading
  1. Open a trading-rules template
  2. Write concrete conditions for cutting losses, taking profit, and how you handle exceptions if you allow any
  3. Generate the document and keep it at hand so you can refer to your rules while trading
  4. After each trade, record in the review field whether you actually followed the rules
Print from the free plan and review on paper — Individual trader who prefers marking up a printed page
  1. Create a document with a free template and choose the print output format
  2. Press the print button; the print-ready document is fetched again and then printing starts
  3. The page is laid out for A4, so you can mark it up and review it on paper
Organize your yearly trading notes before tax season — Individual trader who wants to get a head start on tax-season preparation
  1. Pick a yearly-summary or record-organizing template in the free template hub
  2. Enter the period, profit and loss per account, costs such as fees and swaps, and where your supporting documents are stored
  3. Write down anything you are unsure about, or questions for your tax accountant or tax office, in a notes field
  4. Export as txt or markdown and keep it as prep notes for your tax filing (the free plan keeps no history, so save the file yourself)
  5. This service is not tax advice, so always confirm the actual filing details with a tax professional or your tax office
Prepare your track record and rules before a prop-firm application — Individual trader preparing to apply to a proprietary trading firm
  1. In the free template hub, pick a track-record summary template and a trading-rules template
  2. Check the fields on the detail page, then enter the figures reviewers tend to look at: period, win rate, average profit and loss, maximum drawdown
  3. Write your stop-loss and money-management rules in your own words and cross-check them against your actual trade records for contradictions
  4. Export as markdown, use it as the draft for your application, and adapt the details to the firm's required format
  5. Requirements differ between firms, so read the application guidelines yourself before submitting
Prepare an inquiry to an overseas broker in Japanese and English — Individual trader who needs to contact an overseas broker in English
  1. Open an inquiry or correspondence template in the free template hub
  2. Choose the bilingual Japanese-English option for the language; even the free plan lets you pick Japanese, English, or both side by side
  3. Describe exactly what you want to ask, and keep details such as account numbers to the minimum necessary
  4. Export in copy format and paste the English part into the broker's contact form or an email
  5. Before sending, compare the English text against the Japanese side to confirm it says what you intend
Set this month's risk budget at the start of the month — Individual trader who decides money-management limits before trading
  1. Pick a money-management or risk-management template in the free template hub
  2. Enter your account balance, the loss you will accept this month, and the maximum risk per trade
  3. Decide in advance what you will do when the limit is hit, such as stopping trading or waiting until next month, and write it down
  4. Generate the document and keep it visible so you can check your numbers against it during the month
  5. At month end, compare the plan with your actual results and adjust next month's budget and limit rules
Build a checklist for weeks with major economic releases — Individual trader who plans ahead for major economic announcements
  1. Use categories or search in the free template hub to find a preparation-notes or checklist template
  2. Enter this week's key events, their release times, and how you expect them to affect your open positions
  3. Write your response policy in advance, such as reducing positions before the release or staying on the sidelines
  4. Keep the output next to your trading screen and follow the written policy for decisions around the release
  5. Afterwards, record in the review field whether things went as expected, and use it to prepare for the next event week
Organize a year of trading notes before tax season — Individual trader getting a year of trades in order ahead of tax season
  1. In the free template hub, browse categories or search for a template that helps organize a year of trades and profit-and-loss notes
  2. With your broker statements at hand, copy in the period, profit or loss, fees, and other figures
  3. Generate the document and save the file as your yearly notes (the free plan keeps no history, so store the file yourself)
  4. Always verify the underlying figures against the official statements issued by your broker; never file based on your notes alone
  5. This service does not provide tax advice, so confirm whether and how to file with a tax professional or your tax office
Summarize your track record in Japanese and English for a prop-firm application — Individual trader considering an application to an overseas prop firm
  1. In the free template hub, pick a template for organizing your trading results or trading journal
  2. Lay out what you would explain to the firm: trading period, style, profit-and-loss progression, and your own risk-management rules
  3. Choose the Japanese-English side-by-side language option and generate a document with both languages together
  4. Reread the English portion and adjust the wording yourself to fit the firm's application form and requirements
  5. The firm sets its own screening criteria and decisions; use this document as material for organizing your own record
Export trade records as JSON and tally them yourself — Individual trader who wants to tally trade records later in bulk
  1. Create your record as usual with a trade-record template in the free template hub
  2. Choose the json output format (structured data) and download it; the file is saved with the correct extension
  3. Load the JSON into a spreadsheet or a script and tally monthly trade counts and profit or loss yourself
  4. Also export a txt or markdown copy for rereading, keeping the same record in one format for tallying and one for reading
  5. The free plan keeps no output history, so put the date in the file name and manage the files in your own folders
Keep a pre-market morning checklist on your phone — Individual trader who wants a fixed pre-market routine every morning
  1. In the free template hub, pick a checklist-style template for pre-trade checks and routines
  2. Enter the items you check every morning in your own words: economic calendar, yesterday's review, order conditions, and so on
  3. Choose the copy output format (plain text with symbols) and paste it into the notes app on your phone
  4. Run through the list in the same order each morning, and rewrite any items that have become empty ritual
Check your position-sizing limits with a worksheet — Individual trader who wants to manage per-trade risk with concrete numbers
  1. Open the detail page of a money-management template and check its input fields first
  2. Enter your account balance, the loss you accept per trade, and the distance to your stop, then generate
  3. Review the organized result and check whether the size you have in mind stays within the limit you set for yourself
  4. When market conditions or your account balance change, re-enter the numbers to keep the worksheet current
  5. The final sizing decision is your own responsibility; keep that decision on record as well

🗂 Output format samples — what each format looks like

Copy — 10 examples

Pasting a trade journal entry into chat

Choose this when you want to paste the day's trade journal directly into a notes app or team chat.

== Trade Journal (2026-07-06) ==
- Instrument: USD/JPY
- Side: Buy / Size: 0.5 lot
- Rationale: Entered after confirming breakout above recent high
- Result note: Took profit early; consider scaling out next time

⚠ Check that line breaks and symbols survive intact in the destination before sending.

Using a client explanation note as an email body

Handy when you want to send an explanation to a client as a plain email body without formatting.

== Explanation Note: Fee Structure ==
[Key points]
- Trading fees are charged per executed order
- Monthly reports are sent by the 3rd business day of the following month
* This note does not constitute investment advice

⚠ Some email clients render symbols differently, so preview the message before sending.

Sharing a risk disclosure draft internally

Use this at the drafting stage when handing a disclosure document to a reviewer for edits.

== Risk Disclosure (Draft) ==
1. Price risk: losses may occur depending on market conditions
2. Liquidity risk: orders may not execute at desired prices
--- Disclaimer ---
This document does not guarantee future results

⚠ Keep the word "Draft" in place when sharing so the text is not mistaken for the final version.

Transferring meeting minutes to an internal tool

Choose this to quickly transfer minutes into a wiki or a project tool's comment field.

== Operations Meeting Minutes (No. 12) ==
[Decisions]
- Roll out the new template set starting next month
[Action items]
- Tanaka: organize the approval flow (due Jul 15)
- Sato: revise client-facing wording

⚠ Verify who can view the destination before pasting names, deadlines, or other specifics.

Using a weekly trading checklist without printing

Good for pasting weekly review items into a notes app and ticking them off as you go.

== Weekly Checklist (Trading Prep) ==
[ ] Reviewed last week's trade journal
[ ] Checked this week's economic calendar
[ ] Reconfirmed max loss allowed per trade
[ ] Audited for any deviation from order rules

⚠ The checkbox marks are plain text, not interactive; tick items by editing the characters manually.

Sending a monthly report summary to a manager

Use this to extract the highlights of a monthly report and share them with a manager ahead of the full document.

== Monthly Summary (June 2026) ==
- Case volume: up from the previous month
- Main topic: prepared explanation materials for new clients
- Next month's focus: start operating the approval flow
(See the full report for details)

⚠ Add one line pointing to the full report so the summary is not read out of context.

Using pre-account-opening items as a phone-call memo

Choose this to line up confirmation items before a client call and jot answers as you talk.

== Pre-Account-Opening Memo ==
- ID documents: ____ (verified on: ____)
- Investment experience: ____
- Inquiry details: ____
- Next step: ____

⚠ Blank underscores remain as-is, so review for unfilled fields after the call before saving.

Saving a daily investing diary as a draft

Handy for keeping a short daily note of your market view and lessons as private drafts.

== Investing Diary (Jul 6) ==
- Market view: mostly waiting ahead of data releases
- Actions: no new entries, watch list only
- Insight: recording "no trade" days also helps later review
* Actual trading and investment decisions are your own responsibility

⚠ If posting publicly, take care not to include personal figures such as account balances.

Sending approval-request highlights to an approver

Use this to give an approver a heads-up with the document's key points before the formal request.

== Approval Request (Advance Notice) ==
- Document: Client product explanation v3
- Changes: fee section updated to the latest rate table
- Please review: wording of the disclaimer
- Requested by: Fri, Jul 10

⚠ This memo is not a formal approval record; always submit the request through the approval flow as well.

Keeping money-management rules beside your trading screen

Choose this to paste your own money-management rules into a sticky-note app and keep them visible while trading.

== Money-Management Rules (Personal) ==
- Max loss per trade: within a fixed share of account funds
- Concurrent positions: up to 3
- After losses: stop for the day after 2 consecutive losses
- Review compliance with these rules weekly

⚠ When you update the rules, replace older pasted copies too so multiple versions do not coexist.

Text — 10 examples

Saving a trade journal entry as txt

Choose this when you want to keep daily trade records as unformatted plain text that you can later open and search in any text editor.

Trade Journal 2026-07-06
Instrument: USD/JPY
Entry rationale: Confirmed break above the moving average
Stop-loss level: 158.20
Review: Exited earlier than planned; hold per the rules next time.

⚠ The txt format carries no styling, so headings are not emphasized; it is best suited for long-term storage and full-text search.

Sharing a client explanation note as a txt draft

Choose this when you want to review a client explanation note as a plain-text draft before pasting it into an email body or internal chat.

Client Explanation Note
Date of explanation: 2026-07-06
Topic: Changes to the fee structure
Remarks: Please contact your representative with any questions.
Note: This document is provided for informational purposes only.

⚠ Before sending to a client, always confirm that QA-check warnings have been addressed and the disclaimer text is still present.

Keeping a risk disclosure document as txt for records

Choose this when you want to store the body of a disclosure document as raw text that does not depend on any formatting, keeping a simple copy for your records.

Risk Disclosure Document
Product: Foreign exchange margin trading
Key risks: Price fluctuation, liquidity, amplified losses from leverage
Disclosure date: 2026-07-06
This product involves the risk of loss.

⚠ Regulatory suitability of disclosures varies by firm and jurisdiction; have your legal or compliance team review before use.

Importing meeting minutes as txt into internal systems

Choose this when your document management or search system requires tag-free plain text for importing meeting minutes.

Operations Meeting Minutes
Date: 2026-07-06 10:00
Attendees: Sato, Tanaka, Suzuki
Decision: Monthly report deadline moved to the 3rd business day
Next action: Share the new format (owner: Tanaka)

⚠ The txt output contains no table borders; items are separated line by line, so verify against the import specification of the target system.

Using a pre-trade checklist as txt without printing

Choose this when you want to keep a pre-trade checklist open in a plain text editor next to your trading screen.

Pre-Trade Checklist
[ ] Checked the economic calendar for scheduled releases
[ ] Set the stop-loss together with the order
[ ] Position size is within the rules
[ ] Not right after a losing streak (calm check)

⚠ Checkboxes are rendered as literal [ ] characters and are not clickable; mark items done by editing the text yourself.

Backing up a monthly money-management report as txt

Choose this when you want a long-term backup of monthly money-management records in a form that does not depend on any application or version.

Monthly Money Management Report - June 2026
Opening balance: 1,000,000 JPY
Closing balance: 1,024,000 JPY
Max drawdown: -3.2%
Notes: One rule deviation this month; recheck the lot cap next month.

⚠ Figures are output exactly as entered; no calculations are performed, so review the amounts before saving.

Pasting a client interaction log as txt into a CRM

Choose this when you want to paste a record of a client meeting or call directly into a free-text CRM field without formatting issues.

Client Interaction Log
Date: 2026-07-06
Channel: Phone
Summary: Inquiry about revising the monthly contribution amount
Outcome: Mailed materials; next meeting set for July 20

⚠ Include personal details such as client names or account information only in line with the data-handling rules of the destination system.

Handing over a work transition memo in universally readable txt

Choose this when you do not know the successor's software environment and need a file format that opens reliably on any computer.

Work Handover Memo
Duty: Preparing and submitting the monthly report
Deadline: 3rd business day of each month
Contact: Ms. Yamamoto, Accounting (recipient)
Note: Reflect month-over-month figures only after accounting close

⚠ The file is saved in UTF-8; if opening in older internal tools, check once that characters display correctly.

Viewing a personal investment policy memo as txt on mobile

Choose this when you want your personal trading rules in a phone notes app so the same content is available on the go.

Personal Investment Policy Memo
Max loss per trade: up to 1% of account balance
Trading hours: 21:00-24:00 only
Prohibited behavior: Immediate re-entry after a stop-loss
Review date: End of each month
Actual trading and investment decisions are your own responsibility.

⚠ Personal-template output includes no approval block or internal classification labels; it can be used as-is for your own records.

Recording an incident report memo instantly as txt

Choose this when you need a fast, timestamped memo of an event such as an order error or system issue right after it occurs.

Incident Report Memo
Occurred: 2026-07-06 14:32
Event: Order quantity entry error (10 entered as 100)
Initial response: Offset with a reverse trade; reported verbally to supervisor
Follow-up: Consider introducing a double-check on order entry

⚠ If a formal report is required later, use this memo as a draft and produce a clean version in the print format.

Markdown — 10 examples

Keeping a trade journal in Markdown

Choose this when you want to paste daily trade records into note apps like Obsidian or Notion. Headings and bullet lists are recognized as structure as-is.

# Trade Journal 2026-07-06
## Entry Rationale
- Pair: USD/JPY
- Direction: Long
- Basis: Break above moving average

⚠ If the destination app does not support Markdown, the symbols will show as plain characters; use the copy format in that case.

Editing a client explanation note in Markdown

Useful when you output a client explanation note and want to refine the wording in a Markdown editor before converting it to PDF or an internal tool.

# Client Explanation Note
## Product Overview
- Product: Investment Trust A
- Main risk: Price fluctuation risk

## Key Points Explained

⚠ Keep the disclaimer section intact in the final version you hand to the client; do not delete it while editing.

Sharing meeting minutes with your team in Markdown

Choose this when sharing minutes via Slack, GitHub, or an internal wiki—tools that render Markdown formatting automatically.

# Operations Meeting Minutes
## Decisions
- Standardize the monthly report format
## Action Items
- [ ] Draft the new format (Owner: Tanaka)

⚠ Checkbox syntax (- [ ]) renders differently across tools, so verify the appearance after pasting.

Version-controlling a risk disclosure draft

Choose this when you want to put a disclosure draft under text-based diff management such as Git. Being plain text, changes can be tracked line by line.

# Risk Disclosure (Draft)
## Covered Service
- Service name: [service name]
## Main Risks
- Possible losses due to market price fluctuations

⚠ For the final disclosure, complete your internal review first, then re-output in a distribution format such as print or pdfa_html.

Weekly trading review checklist

Choose this when you want to append a weekend review checklist to your regular Markdown notes as a habit. Bullet points become checklist items directly.

# Weekly Review (Week 1, July)
- Did I enter according to my rules?
- Did I set stop-loss levels in advance?
- Did I avoid emotional add-on trades?

⚠ This is output from a personal-use template. Actual trading and investment decisions remain your own responsibility.

Internal procedure doc for account opening

Choose this when publishing internal procedures, such as an account-opening flow, to a wiki where numbered lists make each step clear.

# Account Opening: Internal Procedure
## Steps
1. Confirm receipt of identity documents
2. Cross-check details against the application
3. Record the reason if returning for correction

⚠ Numbered lists are auto-numbered by the rendering tool, so you do not need to renumber when inserting steps.

Drafting a monthly performance report

Choose this when you want to shape a monthly report's outline in Markdown first, adjusting chapters at the heading level before finalizing.

# Monthly Report - June 2026
## Overview
- Summary of market conditions
## Holdings
- Major changes and reasons

⚠ When adding figures or results, take care not to phrase them in a way that implies guaranteed returns.

Preparing a pre-meeting question list

Choose this when preparing a question list before a client meeting and running through it in a tablet note app during the conversation.

# Meeting Interview Items
## Current Situation
- Current investment approach
- Any recent changes in circumstances
## Requests

⚠ Store any notes containing client information taken during the meeting in line with your internal data-handling rules.

Organizing your money-management rules

Choose this when consolidating your personal money-management rules into a single Markdown document, grouped by headings for regular review.

# Money Management Rules
## Position Sizing
- Up to 2% of account balance per trade
## Stop-Loss
- Always set the stop level before entering

⚠ Adjust the numeric values to your own situation; the template's example figures are illustrative only.

Logging a complaint-handling record chronologically

Choose this when recording the timeline of a complaint or inquiry response as searchable text for internal record-keeping.

# Complaint Handling Record
## Timeline
- 07/01 Received complaint by phone
- 07/02 Escalated to responsible team
- 07/03 Sent initial response

⚠ Record dates, names, and other facts as they happen rather than from memory, so the log stays accurate.

HTML — 10 examples

Embedding a trade journal into a blog post

Choose this when you want to paste your trade review directly into a post on your own site. It is an HTML fragment, so it does not break your article's design.

<h2>Trade Journal (July 2026)</h2>
Pair: USD/JPY
Entry reason: Break above the moving average
Review: Took profit too early. Next time, hold according to the rule.

⚠ This is a fragment, not a complete HTML document, so paste it into a page rather than opening it as a standalone file.

Publishing a client explanation note on an intranet portal

Choose this when you want to publish the key points of a product explanation on an intranet page. Headings and paragraphs keep their structure, making it easy to read.

<h2>Client Explanation Note</h2>
Product: Investment Trust A
Key points: Fee structure and expected price fluctuations
Disclaimer: This document does not indicate future results.

⚠ The portal's own CSS applies, so fine display details depend on the destination page's settings.

Integrating a risk disclosure document into a web page

Choose this when you want to integrate risk disclosure content into an information page on your own site. The disclaimer section is preserved with its structure.

<h2>Risk Disclosure</h2>
Covered transactions: Foreign exchange margin trading
Main risks: Price movements, interest rates, liquidity
Disclaimer: Losses may occur.

⚠ Before publishing, review the content according to your internal approval procedures.

Sharing meeting minutes in groupware

Choose this when you want to paste regular meeting minutes into groupware that accepts HTML input. The list of decisions displays without losing its layout.

<h2>Operations Meeting Minutes</h2>
Date: July 3, 2026 / Attendees: 4
Decision: Standardize the monthly report format
Next action: Share a draft of the new format

⚠ If the destination does not accept HTML, switch to the markdown or copy format instead.

Displaying a pre-trade checklist on a dashboard

Choose this when you want to keep a pre-trade checklist visible on your personal dashboard page every morning. Checklist items remain in list structure.

<h2>Pre-Trade Checklist</h2>
- Checked today's economic calendar
- Set the maximum acceptable loss
- Verified entry conditions against my rules

⚠ Actual trading and investment decisions are your own responsibility; the checklist is only an aid.

Formatting a monthly performance report for an email body

Choose this when you want to paste a monthly report, headings intact, into an email client that supports HTML. Tabular figures stay aligned.

<h2>Monthly Report (June)</h2>
Trades: 18 / Win-rate memo: see record section
Notes: Followed my rules during volatile sessions
Next month's focus: Reviewing position sizing

⚠ Some email clients alter formatting when pasting HTML, so check the preview before sending.

Adding a fee explanation page to your site

Choose this when you want to publish a fee structure explanation as a static page on your site. The mapping between item names and amounts is preserved structurally.

<h2>Fee Guide</h2>
Account fee: shows the entered value
Trading commission: stated per executed amount
Note: See the pre-contract disclosure document for details.

⚠ Check the unfilled-item notices after output so you do not publish the page with empty amount fields.

Posting an investment study note on a learning site

Choose this when you want to post a study note summarizing terms you learned and your own understanding on a note-sharing service or website.

<h2>Study Note: Stop-Loss Rules</h2>
What I learned: Decide the stop-loss width before placing an order
My understanding: Build a system that decides by numbers, not emotion
Next topic: Approaches to money management

⚠ Use this as a personal study record and avoid wording that reads like advice to others.

Pasting a meeting preparation memo into a CRM record

Choose this when you want to paste a client meeting preparation memo into a CRM record that accepts HTML. Items to confirm are organized paragraph by paragraph.

<h2>Meeting Preparation Memo</h2>
Meeting date: July 10, 2026
Items to confirm: Understanding of the previously explained product, further questions
Materials: Product explanation sheet, fee list

⚠ If the memo contains personal information such as client names, verify the destination's access permissions first.

Registering a complaint-handling record in a knowledge base

Choose this when you want to register a completed complaint-handling record as an article in your internal knowledge base. Background, response, and prevention are separated under headings.

<h2>Complaint-Handling Record</h2>
Received: June 20, 2026 / Category: Insufficient explanation
Response: Provided additional explanation and resent materials
Prevention: Added an item to the explanation checklist

⚠ When registering in the knowledge base, remove any details that could identify an individual client.

Print — 10 examples

Keeping a paper copy of a trade journal

Choose this when you want to print the day's trade journal on A4 paper and keep it in a notebook or binder.

(Formatted as a complete document for A4 printing)
Top of page 1: title "Trade Journal - 6 July 2026"
Below: a table of symbol, buy/sell, quantity, and fill price
Lower section: a review notes area
Footer: a reminder that trading decisions are your own responsibility

⚠ The print button re-fetches the print document when pressed, so regenerate the output first if you edited anything on screen.

Bringing a client explanation note to a meeting

Choose this when you need an explanation note to hand to a client in a meeting; it is laid out for paper, not for the screen.

(Printed as an A4 document with margins)
Title: "Explanation Note for Your Transaction"
Heading 1: Summary of the proposal
Heading 2: Fees and costs you will bear
Heading 3: Important notices (including the disclaimer)
Bottom: footer with the creation date and the preparer's name

⚠ For client-facing documents, review QA warnings and unfilled fields before printing.

Printing a disclosure document for signature

Choose this when preparing a disclosure document, such as fee or conflict-of-interest disclosure, that will be signed on paper.

(Printed straight through from page 1 to the signature block)
Title: "Disclosure Statement on Fees and Charges"
Body: an explanatory paragraph for each disclosure item
Middle: a table breaking down the costs
End: confirmation date, signature block, and disclaimer

⚠ If used as a signed original, keep a copy of the exact file you printed in your own storage so the printed copy is not silently replaced later.

Distributing meeting minutes

Choose this when you want to hand out committee or regular meeting minutes to attendees on paper.

(Produced as an A4 document with page numbers)
Title: "Investment Meeting Minutes - Session 12"
Opening: date, location, and attendee list
Body: decisions and assignees per agenda item
End: next meeting date and a confirmation area

⚠ For large distributions, check page-break positions in the browser's print preview before printing.

Keeping a monthly risk checklist on your desk

Choose this when you want a paper checklist of monthly risk review items that you can tick off by hand.

(Produced as a printable document with checkbox rows)
Title: "Monthly Risk Checklist - July 2026"
[ ] Confirmed no position limits were exceeded
[ ] Confirmed no deviations from stop-loss rules
[ ] Reviewed the response plan for unexpected moves
End: fields for the reviewer's name and review date

⚠ Handwritten ticks on paper are not fed back into the system, so keep a separate file copy if you need a record.

Sharing a money management plan with family

Choose this when an individual trader wants to put their investment budget and policy on paper to share with family.

(Printed with an easy-to-read page layout)
Title: "Our Household Money Management Plan"
Item: monthly cap on funds allocated to investing
Item: how living expenses and trading funds are kept in separate accounts
Item: the threshold for pausing after consecutive losses
Footer: a note that trading decisions remain your own responsibility

⚠ As a personal template, it carries no approval block or internal classification, so it is ready for household use as is.

Circulating an approval document for review

Choose this when preparing an internal document to circulate on paper for approver sign-off, which some approvers prefer over on-screen review.

(Printed as an A4 document with an approval block)
Title: "Approval Request: New Product Announcement"
Body: background of the request and a summary of changes
Middle: the full text of the document under review
End: an approval block with rows for the drafter and approvers

⚠ If you also use the in-system approval flow, remember it leaves an audit trail; choose paper or system routing deliberately.

Printing a seminar handout

Choose this when you need clean printed copies of an explanatory handout for an investor education seminar or study group.

(Produced as a tidy A4 handout)
Title: "A Beginner's Guide to Order Types"
Heading: The difference between market and limit orders
Heading: Three things to check before placing an order
Heading: Frequently asked questions
Footer: source line and disclaimer

⚠ Avoid wording that promises results in seminar material, and always review QA warnings before distributing.

Preparing paper copies for an audit

Choose this when assembling paper copies of client interaction records or disclosure documents ahead of an internal review or external audit.

(Each document prints as a self-contained A4 document)
First line, acting as a cover: "Client Interaction Log - June 2026"
Body: a chronological list of date, staff member, and summary
Bottom of each page: footer including the creation date
End: a field for the record reviewer's name

⚠ Downloading the source file and storing it alongside the paper copies makes reconciliation easy.

Filing a weekly market review note

Choose this when you print your weekend market review in a consistent layout every week and file the pages in one binder.

(An A4 document you can print in the same layout every week)
Title: "Weekly Review - Week 27, 2026"
Item: What went well this week
Item: What to improve on
Item: Next week's watchpoints and plan
End: a line for the entry date

⚠ Generating from the same template each week keeps the layout consistent, making week-to-week comparison easier later.

PDF/A-ready HTML — 8 examples

Preserving a trade journal for long-term storage

Choose this when you want to convert your monthly trade journal to PDF for archiving in a form that resists later modification.

= Self-contained HTML document (excerpt of opening lines) =
Trade Journal — July 2026
Date created: 2026-07-06
----------------------------
1. Monthly trading overview
2. Individual trade entries (instrument, size, rationale)

⚠ Whether the result is PDF/A compliant depends on your conversion tool, so verify the converted file after saving.

Sending a client explanation note as a PDF

Choose this when you need to turn a client explanation note into a PDF for email attachment. It references no external assets, so it looks the same in any environment.

= How the document opens =
Client Explanation Note
Subject: Changes to the fee structure
Audience: For client sharing
----------------------------
- Summary of explanation

⚠ Before sending to a client, confirm the disclaimer is present and no internal information is included.

Producing a disclosure document in submission-ready form

Use this when a disclosure document, such as a compensation disclosure, must be output as a single complete document suitable for submission and retention.

= Document structure (excerpt) =
Compensation Disclosure
Period covered: H1 2026
----------------------------
Section 1: Purpose of disclosure
Section 2: Breakdown of compensation
(Fixed disclaimer section at the end)

⚠ By design the document contains no scripts, so the converted PDF retains no dynamic elements.

Finalizing meeting minutes as a fixed record

Choose this when approved meeting minutes should be converted to PDF as a final version that will not be edited further.

= Opening of the minutes (excerpt) =
Minutes — Investment Policy Review Meeting
Date and time: 2026-07-03 10:00
Attendees: (fill-in field)
----------------------------
- Decisions made
- Items carried over

⚠ While the minutes are still a draft, the txt or markdown formats are easier to edit and are recommended instead.

Using an inspection checklist both on paper and as a PDF

Handy when a checklist, such as a pre-account-opening review, will be both stored as a PDF and filled in by hand on paper.

= How the checklist section appears =
Pre-Account-Opening Checklist
----------------------------
[ ] Verified the expiry date of identity documents
[ ] Received an explanation of the fee structure
[ ] Read the risk explanation materials

⚠ Checkboxes are meant to be ticked by hand after printing; clicking them on screen does not save any state.

Archiving a monthly performance report

Choose this to convert monthly reports to PDF in a consistent layout and accumulate them in yearly folders.

= Report opening (excerpt) =
Monthly Performance Report — June 2026
Prepared by: (fill-in field)
----------------------------
- Summary of the month
- Key drivers of change
- Points to watch next month

⚠ Including the year and month in the file name makes later searching and sorting much easier.

Fixing a risk explanation document for distribution

Use this to finalize a product risk explanation as a distributable file that does not depend on the recipient's environment.

= Document opening (excerpt) =
Explanation of Risks
Product: (fill-in field)
----------------------------
1. Points to note on price fluctuation
2. Points to note on liquidity
* This document is not investment advice

⚠ Check the QA warnings as well to make sure the text contains no wording that implies guaranteed returns.

Bundling a cover letter and documents into one PDF

Choose this when documents for a client should include a cover letter and an acknowledgment section, delivered as one complete PDF.

= Cover letter page (excerpt) =
Cover Letter
To: (fill-in field)   Date sent: 2026-07-06
Enclosed: Contract summary, 1 copy
----------------------------
Receipt and confirmation section (please sign and return)

⚠ Automatic addition of the cover letter and acknowledgment section is configured with the Premium Delivery Pack.

JSON Manifest — 10 examples

Exporting a trade journal as JSON

When you want to feed your daily trade journal into a spreadsheet or your own analysis script, JSON gives you structured data you can import directly.

{
  "title": "Trade Journal",
  "sections": [
    { "heading": "Trade Summary", "items": ["Date", "Symbol", "Quantity"] }
  ]
}

⚠ JSON is meant for data integration rather than reading; regenerate in another format when you need a document to share with people.

Feeding a client explanation note into an internal system

When you need to register a client explanation note into a CRM or document management system field by field, JSON with separate headings and bodies is the easiest shape to handle.

{
  "title": "Client Explanation Note",
  "sections": [
    { "heading": "Purpose", "body": "..." },
    { "heading": "Items to Confirm", "body": "..." }
  ]
}

⚠ Your entered values, such as client names, are included as-is, so check the access permissions of the destination system before importing.

Sharing a disclosure document structure for review

When you want to mechanically compare the section layout and disclaimer placement of a disclosure document with a reviewer, JSON makes structural differences easy to spot.

{
  "title": "Disclosure Document",
  "sections": [
    { "heading": "Fee Disclosure" },
    { "heading": "Disclaimer", "locked": true }
  ]
}

⚠ Editing the JSON does not change the original output; to revise the content, regenerate from the template input form.

Storing meeting minutes in a searchable database

When you want to store recurring meeting minutes so you can later search by agenda item or decision, JSON with separated fields suits building a search index.

{
  "title": "Meeting Minutes",
  "sections": [
    { "heading": "Agenda", "items": ["Topic 1", "Topic 2"] },
    { "heading": "Decisions", "body": "..." }
  ]
}

⚠ Downloads are saved with a .json extension, so you can open them directly in a text editor or import tool.

Importing a checklist into a task tracker

When you want to bulk-register items from a pre-account-opening checklist as tasks in a tracker, JSON with the items as an array makes conversion simple.

{
  "title": "Verification Checklist",
  "sections": [
    { "heading": "Before You Start", "checklist": ["ID documents", "Fee confirmation"] }
  ]
}

⚠ Check states themselves are not stored, so track completion in the destination tool.

Using money management rules for automated checks

When you want a script to load your own money management rules and check conditions before each trade, JSON with each rule as a separate field is useful.

{
  "title": "Money Management Rules",
  "sections": [
    { "heading": "Per-Trade Limit", "body": "..." },
    { "heading": "Stop-Loss Criteria", "body": "..." }
  ]
}

⚠ The output is for your own records and organization; actual trading and investment decisions remain your own responsibility.

Sorting multilingual output by language for storage

When you generate the same document in several languages and want to sort the results into files or folders per language, JSON lets you route them mechanically using the language and title fields.

{
  "title": "Service Overview",
  "language": "en",
  "sections": [
    { "heading": "Summary", "body": "..." }
  ]
}

⚠ Simultaneous 12-language output requires Pro or above; on Free, sort within Japanese, English, and bilingual output.

Accumulating weekly reviews for later reflection

If you want to store weekly trading reviews in the same structure and aggregate them at month end, JSON with a consistent key layout works well with aggregation scripts.

{
  "title": "Weekly Review",
  "sections": [
    { "heading": "This Week's Findings", "body": "..." },
    { "heading": "Improvements for Next Week", "body": "..." }
  ]
}

⚠ The Free plan does not keep output history, so store the downloaded JSON files yourself.

Passing a request document to a forms system

When you pour a request document for a business partner into your internal forms layout, JSON with separate headings, bodies, and confirmation fields makes it easy to map each part to its slot.

{
  "title": "Request to Business Partner",
  "sections": [
    { "heading": "Details of Request", "body": "..." },
    { "heading": "Response Deadline", "body": "..." }
  ]
}

⚠ This format assumes the forms system handles the layout; if you plan to print and hand over the document, regenerating in the print format is more reliable.

Preserving document structure information for audits

When you want to be able to verify later which section layout a client-facing document used, saving the JSON alongside the document gives you a reference for cross-checking.

{
  "title": "Client-Facing Explanation",
  "generated_at": "2026-07-06",
  "sections": [
    { "heading": "Service Overview" },
    { "heading": "Important Notes" }
  ]
}

⚠ For full audit workflows, consider the Premium local audit export and Evidence Mode features.

Field dictionary — what to write in each input

Notes

A free-form field for observations or supplementary comments you want to keep with the record. Write enough detail that you can reconstruct the situation later.

Example: Volatility spiked right after the US jobs report, so I took profit earlier than planned. Next time, review position size before major releases.

◯ Separate facts from your reasoning and keep sentences short and specific so the note is easy to review later.

✕ Vague impressions such as "it just felt right" give you nothing to learn from when reviewing the record.

⚠ Do not include other people's names, account numbers, or other sensitive details in documents you might share.

Date

The date on which the trade or event took place. It serves as the reference point when you sort and review your records.

Example: 2026-07-06

◯ Use a consistent year-first format such as 2026-07-06 so your records stay in order.

✕ Relative expressions like "yesterday" or "last Friday" cannot be pinned down when you read the record later.

Instrument / Currency pair

The name of the instrument or currency pair you traded. It becomes the key you use when searching or aggregating your records later.

Example: USD/JPY

◯ Write a widely used code together with the name, such as "USD/JPY" or "AAPL (Apple Inc.)", so there is no ambiguity.

✕ Nicknames like "the usual one" become meaningless once time has passed.

Date of preparation

The date the document was prepared. It is the reference for telling newer versions from older ones.

Example: July 6, 2026

◯ Enter the date you finalized the document, and update it whenever you revise the content.

✕ Updating the content while leaving an old date makes it impossible to tell which version is current.

Additional notes

Supplementary details or background that do not fit in the main body. This field is optional and can be left blank.

Example: This request follows up on our meeting on June 20.

◯ Add one or two sentences of background that explain why this request is being made.

✕ Repeating the body text or adding unrelated topics only makes the document harder to read.

⚠ Do not put sensitive personal information in this field if the document might be shared.

Check date

The date the check or inspection was actually performed. It serves as the reference date for the record.

Example: July 6, 2026

◯ Write the full date including year, month, and day, using the day the check was actually done.

✕ Avoid relative wording like "today" or "last week," and avoid month-day-only entries such as "7/6" that lose the year later.

Checklist items

List the items to verify, one item per line. The output formats them as a checklist.

Example: Confirm account balance matches the records Save screenshots of the order history Copy total fees into the summary sheet

◯ Keep each line to a single action and end with a verb phrase like "confirm" or "save" so nothing gets skipped.

✕ Avoid packing several tasks into one line or writing vague items like "check various things."

⚠ Do not embed customer names or account numbers in the items. Generalize instead, for example "the customer's records."

Review date

The date the content was reviewed. It becomes the starting point for deciding when the next review is due.

Example: July 6, 2026

◯ Write the exact date the review was completed, including the year, and update it after every review.

✕ Avoid reusing the creation date, or updating the date without actually performing a review.

Author

The person who created this document. This is also the first point of contact for questions about the content.

Example: Ichiro Suzuki, Sales Planning Department

◯ Write the department together with the name, and list the lead author first when several people contributed.

✕ Avoid initials or nicknames alone; over time no one can tell who they refer to.

⚠ The author's name is personal information. Before sharing client-facing or external output, confirm whether the name needs to appear at all.

Date prepared

The date the document was prepared. It tells the reader what point in time the content reflects.

Example: July 6, 2026

◯ Write the full date including the year, and update it whenever the content is substantially revised.

✕ Avoid leaving an old date behind when reusing a template; it misleads readers about how current the information is.

Key points

Bullet points covering the main issues or takeaways of this document. Readers use them to grasp the whole picture quickly.

Example: Three changes to the fee structure Effective date is October 1, 2026 Notify existing clients by the end of September

◯ Keep to roughly three to five points, one per line, leading with the conclusion or the number.

✕ Avoid pasting in the body text and ending up with ten or more points; that defeats the purpose of a summary.

⚠ If a point includes customer-specific information, confirm who will see the output before adding it.

Subject

A concise subject line for the document, or the matter it explains. It is what you scan for when searching lists and history.

Example: Delivery of account opening documents (July 2026)

◯ Include at least two of subject, purpose, and time period so the line is meaningful even in a list view.

✕ Avoid one-word subjects like "Request" or "Notice," which are impossible to find again later.

⚠ Subjects appear in history lists. Do not put customer names or account numbers in the subject line.

Steps

Enter the steps of a task or procedure in execution order, one step per line. The output formats them as a numbered sequence.

Example: Download the transaction history Paste it into the summary sheet and calculate profit and loss Copy the result into the monthly record

◯ Keep one action per step, and add conditions ("if X, then...") wherever the path can branch.

✕ Avoid inserting long background explanations between steps; keep explanations outside the sequence so the order stays easy to follow.

⚠ Do not write account numbers, passwords, or other secrets into the steps.

Risk-reward ratio (RRR)

The ratio of expected profit (reward) to expected loss (risk). Used to sanity-check a trade plan with numbers.

Example: 1:2.5 (stop distance 40 pips, target distance 100 pips)

◯ Record not just the ratio but also its basis: the stop distance and the target distance.

✕ Writing an aspirational number without any basis makes the plan impossible to review later.

Risk amount / risk rate

The loss you accept per trade, written as an amount or as a percentage of your account balance.

Example: Up to 1% of the account balance (e.g., 100 USD on a 10,000 USD account)

◯ Write both the amount and the percentage so the rule stays consistent as the account balance changes.

✕ Avoid wording like "I'll decide if I lose" that leaves the limit undefined before the trade.

Stop-loss plan

The price or condition at which you will cut the loss, decided and written down before entering the trade.

Example: Exit at market if the close breaks below 1.0850 (about 40 pips from entry)

◯ Specify the price, the trigger condition, and how it will be executed (stop order or manual) so it can be acted on without hesitation.

✕ Avoid vague wording like "I'll watch and decide" that leaves the condition undefined in advance.

Take-profit plan

The target price or condition for taking profit, decided and written down before entering the trade.

Example: Close half at the recent high of 1.0950 and trail the remainder

◯ Including partial exits and an abort condition (what to do if the setup breaks) reduces hesitation.

✕ Avoid wording like "hold as long as it rises" that gives no basis for deciding when to exit.

Emotional state

A record of how you felt before and after the trade. Used to spot patterns of trading while not calm.

Example: Felt a strong urge to win back losses after a losing streak. Waited five minutes before deciding to enter.

◯ Briefly record what you felt and what you did as facts; patterns become easier to find later.

✕ Writing only self-criticism, without the situation and actions, makes the note useless for review.

Trading rules

Your own trading rules, such as entry conditions, money management, and limits on trade frequency.

Example: Enter only on pullbacks in the direction of the moving average. Maximum three trades per day. Stop for the day after two consecutive losses.

◯ Write rules in verifiable terms with numbers and conditions so you can later judge whether you followed them.

✕ Avoid unverifiable wording like "be careful" or "don't overdo it."

Review note

A look back at the trade or period, recording what went well and what did not.

Example: Cut the loss exactly as planned, which was good. However, took profit too early, at half the target distance.

◯ Write at least one positive and one issue, focused on actions, so it leads to the next improvement.

✕ Recording only the profit or loss, without evaluating your own actions, does not lead to improvement.

Next improvement

The action to improve in the next trade or period. Limiting it to one or two items makes it easier to actually do.

Example: Do not close manually before the target is reached. After placing the limit order, close the chart.

◯ Write it as a concrete action you can later verify you did or did not do.

✕ Avoid wording like "try harder" or "be mentally stronger" that does not translate into an action.

Language

A control that selects the output language. On the Free plan you can choose Japanese, English, or a bilingual layout, with the page language preselected. Pro and Premium support simultaneous output in 12 languages.

Example: Choose English for a document shared with overseas offices, Japanese for a domestic team, or the bilingual layout when both will read it.

◯ Choose based on the language your readers can actually read. On Pro and Premium, use custom mode when you want to pick individual languages.

✕ Avoid generating with the default value and handing readers a document in a language they cannot read.

Output format

A control that selects one of seven output formats: copy, txt, markdown, html, print, pdfa_html, and json. Downloads use the correct MIME type and file extension for each format.

Example: Choose copy for pasting into chat or email, print for printing, or pdfa_html when you plan to convert the output to PDF.

◯ Work backward from the final use (pasting, printing, PDF conversion, or system integration) when choosing the format.

✕ Avoid opening the embeddable HTML fragment (html) as a standalone file and assuming the layout is broken; that format serves a different purpose.

Fee and cost summary

A field for summarizing the fees and costs stated in the document, covering amounts, tax treatment, conditions under which they arise, and payment terms.

Example: Monthly advisory fee: JPY 50,000 (excluding tax); initial setup fee: JPY 30,000; no performance fee; payment due at the end of the following month.

◯ State amounts, tax treatment, and triggering conditions concretely, at a granularity that lets the reader calculate the total themselves.

✕ Avoid writing only that fees are negotiable without any basis, or attaching wording that promises returns.

⚠ Before including client-specific terms such as discounts, confirm who the document will be shared with.

Compensation and commission summary

A field for summarizing the compensation and commission structure associated with a transaction or service, organized by rate, calculation method, caps, and when charges apply.

Example: Trading commission: 0.5% of the executed amount (capped at JPY 10,000); account maintenance fee: JPY 3,300 per year (including tax); no other charges.

◯ State not just the rate but also the calculation method and any caps or floors, and describe the conditions for any exceptions.

✕ Avoid stating only a rate while omitting the calculation method and caps, leaving the reader unable to estimate the actual cost.

⚠ For client-specific terms such as individually negotiated rates, confirm the sharing scope before including them.

Expression cautions

A field for listing expressions to avoid when writing or sharing the document, along with notes that must always accompany certain statements.

Example: Do not use wording that promises returns or asserts absolute safety. When citing past performance, always add that it does not indicate future results.

◯ Describe risky wording by category, and include acceptable alternatives and the required accompanying notes.

✕ Avoid notes so abstract that they cannot guide real decisions, or leaving unsupported categorical claims in place.

Contact email address

A field for the email address where replies and communications should be received. It is required when submitting a customization request (Premium).

Example: Enter the address that serves as the point of contact for the matter, for example compliance@example.co.jp.

◯ Use a team address that keeps working even if the person in charge changes, and check for typos before sending.

✕ Avoid sending with a mistyped address and missing the reply, or using a personal address that does not match the document's sharing scope.

⚠ An email address is personal information. Depending on who the document is shared with, consider using a team address instead of a personal one.

Subject / Title

A field for the title of a document or request. Use a short subject line that makes the content clear at a glance.

Example: July 2026 Portfolio Status Report (for Client A)

◯ Include the date, recipient, and purpose as needed so the item is easy to find later in lists and history.

✕ Avoid overly generic titles such as a plain word for document or report, which make items impossible to distinguish later.

⚠ Titles appear in list views. If you include a client name, confirm who can see those lists.

Template ID

An identifier that uniquely identifies a template. Use it to pinpoint the exact template in requests and inquiries.

Example: When submitting a customization request, copy the ID shown on the template detail view into the request as-is.

◯ Specify the target by ID rather than by name to avoid mixing up templates with similar names.

✕ Avoid identifying a template only by its name when similar names exist, which can target the wrong template.

Disclaimer

The disclaimer wording placed at the end of the document. It tells the reader how to treat the content, for example that it is informational and that decisions rest with the reader.

Example: This material is prepared for informational purposes only and does not constitute a solicitation or advice regarding any financial product. Actual trading and investment decisions are your own responsibility.

◯ State the document's purpose, scope, and where responsibility lies in short sentences, and reuse your organization's approved standard wording when one exists.

✕ Avoid improvised wording that softens the disclaimer, or pairing it with promotional claims that undercut what the disclaimer says.

Target date

The date this document is about, such as the day being reviewed, the day the figures refer to, or the planned implementation date, depending on the template.

Example: July 3, 2026

◯ Write the full date including the year, and keep this field distinct from the preparation date when the two differ.

✕ Relative phrases like "last week" or "as of month-end" cannot be pinned to a specific day when read later.

Summary of changes

A concise summary of what is changing and how. It gives the reader the whole picture before they read the details.

Example: The transaction fee will change from a value-based to a per-trade calculation. Two new line items will also be added to the statement.

◯ Write it as a before-and-after comparison so the affected people and scope are clear at a glance.

✕ Empty summaries like "there are some changes" only force the reader to dig through the details themselves.

Effective date

The date on which the change or new arrangement takes effect. In notices, this is one of the first things the reader looks for.

Example: Effective for trades executed on or after Thursday, October 1, 2026

◯ State not just the date but the trigger it applies to, such as trades executed, applications received, or renewals, to prevent differing interpretations.

✕ Month-only wording like "from October" leaves the exact day and the affected transactions ambiguous.

Background

The background and circumstances that led to this document. It helps the reader understand why this is being communicated now.

Example: Following the regulatory revision in April 2026, the reporting format changed, prompting a review of our internal record-keeping method.

◯ Give the facts in two or three sentences in chronological order, and leave conclusions or requests to their own fields.

✕ An overly long history buries the main point; limit this field to the facts needed to understand the decision.

⚠ Do not include other clients' cases or identifiable personal details when describing the background; generalize where needed.

Decisions

Items that were formally decided in the meeting or review. One decision per line makes follow-up easy to track.

Example: - The new report format will be used starting with the August report - Both formats may be used during the transition period (until the end of September)

◯ State who does what by when, and keep items still under discussion out of this field.

✕ Recording undecided items like "to be considered positively" as decisions creates misunderstandings later.

Explanation body

The main body of the explanation. This is the core of the document, so choose wording that matches the reader's level of familiarity.

Example: Distributions from an investment trust may be paid out of gains or partly out of the principal. This document explains the difference and how to check which applies.

◯ Lead with the conclusion, add short glosses for technical terms, and keep each paragraph to a single point.

✕ Avoid definitive predictions about the future, and avoid wording that promises returns or asserts safety.

⚠ If the body includes a client's name, account details, or specific holdings, confirm who will see the document before writing them in.

Question 1

The first anticipated or actually received question. In Q&A-style documents it pairs with Answer 1.

Example: Does the fee change also apply to holdings I already have?

◯ Write a single question in the reader's own words, phrased as an actual question.

✕ Bundling several doubts into one question makes the answer long and hard to follow.

⚠ When copying a real inquiry, remove the asker's name and account details before entering it.

Answer 1

The answer to Question 1. State the conclusion first, then any conditions or exceptions.

Example: Yes, it applies. The new fee rate covers trades executed on or after October 1, 2026; earlier trades keep the previous rate.

◯ Answer with a clear yes/no or a specific date and condition, and cite the source when one exists.

✕ "It depends" on its own resolves nothing; spell out which case leads to which outcome.

⚠ If the answer refers to a specific client's case, generalize it so the person cannot be identified.

Question 2

The second anticipated or received question. Cover a different point from Question 1, without overlap.

Example: Where can I check the fee schedule after the change?

◯ Pick the doubt a reader is most likely to have next, so the sequence reads naturally after Question 1.

✕ A rephrased duplicate of Question 1 only dilutes the document.

⚠ When copying a real inquiry, strip out anything that could identify the asker.

Answer 2

The answer to Question 2. Keeping the same tone and level of politeness as Answer 1 makes the whole document easier to read.

Example: The revised fee schedule is shown at the end of your transaction statement and on the fees page of our website.

◯ When the answer points to a procedure or a place, name the exact location, method, and anything the reader needs.

✕ Answering only "please contact us" forces the reader to ask twice; answer what you can within the document.

⚠ If the answer includes a contact, list a shared team contact rather than an individual's direct line.

Languages

Selects the output language. The free tier offers Japanese, English, or a bilingual Japanese-English layout; Pro and Premium support simultaneous output in 12 languages.

Example: Bilingual Japanese-English (English shown below the Japanese text)

◯ Choose based on the language the reader will actually read; for international recipients, English or the bilingual layout works well.

✕ Selecting many languages "just in case" makes the output long and harder to read; limit it to what is needed.

Next step

The action planned after this document. It turns a review into a concrete improvement, or shows the reader what happens after a request.

Example: Review the last 10 trade records by the weekend and reset the numeric stop-loss rule.

◯ Name one action with a deadline; a single concrete step is far more likely to get done.

✕ Entries like "keep trying" or "wait and see" are not actions and lead nowhere.

From

The person or unit issuing this document or notice. Knowing who it is from helps the reader judge how to treat the content.

Example: Customer Support Department, Sample Trading Co., Ltd.

◯ Decide whether the sender should be an individual or a department based on the document's nature, and keep the style consistent internally.

✕ Leaving the sender blank, or switching between individuals and departments from one document to the next, leaves readers unsure whether the notice is official.

⚠ If an individual's name is used, it circulates with the document as personal information; for widely distributed notices, consider using a department name instead.

Addressee

The name of the person or department this document is addressed to. It appears as the salutation at the top of the document.

Example: Mr. Ito, Accounting Department

◯ Include the department, full name, and the proper courtesy title so the output is ready to send as generated.

✕ Addressing it only "to whom it may concern" leaves recipients with multiple desks unsure who should act, and responses slow down.

⚠ The addressee's name is personal information. If the document may be forwarded to someone else, think carefully about how much of the name to include.

Recorded by

The person who created or entered this record. When questions come up later, this is the first person to ask.

Example: Saburo Nakamura, Sales Department

◯ Write the department and full name, and as a rule the person who made the record should enter their own name.

✕ Role-only entries like "duty staff," or entering the record under someone else's name, undermine the reliability of the record.

⚠ The recorder's name is personal information; before sharing the record externally, decide whether the name should remain.

Original language

The language in which the source material or communication took place. It later helps determine whether the original or a translated version is authoritative.

Example: English (original: contract draft, June 2026 edition)

◯ Alongside the language name, note which document it refers to so the original can be matched with certainty.

✕ Entries like "a foreign language" or "the client's language" make the original impossible to identify in multilingual matters.

Billing cycle

How often the fee or charge is billed, such as monthly, quarterly, or annually. It only carries meaning together with the amount.

Example: Monthly (closing at month-end, invoiced on the 10th of the following month)

◯ State not just the cycle but also the closing date and invoice date to prevent misunderstandings about when payment is due.

✕ Wording like "periodically" or "as needed" tells the reader nothing about when or how much will be billed.

Fee items

An itemized list of fees and charges, one per line, each with its name, rate or amount, and the condition under which it applies.

Example: Account maintenance fee: JPY 3,300 per year (tax included) Trading commission: 0.5% of the transaction amount (tax included, minimum JPY 550) Withdrawal fee: none (borne by the company)

◯ Spell out whether amounts include tax and any conditions such as minimum charges, so there is no room for later disagreement.

✕ Writing only "various fees apply" without the breakdown makes the document inadequate as a client explanation.

Observations

Facts and patterns you noticed during a trade review or inspection. Keep judgments and countermeasures in their own fields; record what you observed here.

Example: Stop-losses were delayed three times this month, all on trades entered within about 30 minutes of an economic release.

◯ Write observations in countable terms, such as frequency or time of day, so you can compare them at the next review.

✕ Impressions like "it was an off week" lead neither to identifying causes nor to improvement.

⚠ When used for client records, avoid comparisons with other clients and keep third parties' personal information out of this field.

Requested changes

The changes you want made as a result of a review: for each item, state where it is, what it currently says, and how it should read.

Example: p. 3, fee description: change "lowest in the industry" to "among the lower tier" or cite the comparison basis p. 5, chart: add the source and as-of date

◯ State where, why, and how to fix each item separately, so the person making the change never has to guess.

✕ Vague requests like "soften the tone throughout" almost guarantee the revision misses your intent.

Update date

The date the content was last updated. Readers use it to judge how current the information is.

Example: July 6, 2026

◯ Enter the full date on which the content actually changed, and refresh it with every revision.

✕ Avoid leaving an old date after editing the content, or bumping the date when nothing actually changed.

Preparation items

Things to prepare or complete before a meeting, listed one per line.

Example: Print and bring the latest transaction statements Re-read the notes from the previous meeting Narrow the questions down to three

◯ Separate items to bring from tasks to finish beforehand, and end each line with a verb so nothing is missed on the day.

✕ Bundled entries like "all the materials" leave you unable to tell what is missing until the meeting itself.

⚠ If an item name includes a client's name, limit who can see the list to the people involved.

Recorder name

The name of the person responsible for taking the minutes or writing the record. Questions and correction requests about the record go to this person.

Example: Yuki Kimura, Corporate Planning Department

◯ Write the department and full name, entering exactly the person assigned to take the record at the start of the meeting.

✕ Avoid filling in a different name from memory afterward, or circulating the record with this field blank.

⚠ The recorder's name is personal information; check whether it should appear in versions distributed outside the company.

Contact person

The name of the person who receives inquiries about this document, used together with the field for how to reach them.

Example: Naoko Watanabe, Sales Department (weekdays 9:00 a.m. to 5:00 p.m.)

◯ Add the department and available hours to the name so the reader knows exactly when to reach out.

✕ Leaving the name of someone who has transferred or left produces a document nobody can actually respond to.

⚠ The contact's name is personal information; for widely distributed documents, consider naming a shared team desk instead of an individual.

Action items

The tasks to be carried out as a result of this document, one per line, each with an owner and a due date.

Example: Prepare the revised fee list (owner: Tanaka, by July 15) Send the client notice to Legal for review (owner: Takahashi, by July 10)

◯ Writing what, who, and by when for each item lets you track completion mechanically at the next check-in.

✕ Tasks without an owner or deadline tend to sit untouched because nobody sees them as their own.

Points of caution

Matters the reader should pay particular attention to. Prioritize points that are easily misunderstood or costly if judged wrongly.

Example: - The fee rates shown are as of July 2026 - Yen-converted amounts rise and fall with exchange-rate movements

◯ Keep one point per item, stated briefly, and order them from most to least important.

✕ Piling up too many items buries the ones that matter, and copying boilerplate disclaimers here defeats the field's purpose.

Share date

The date this document was, or is scheduled to be, shared with the recipient. It records what point in time the information was handed over.

Example: July 8, 2026 (sent by email)

◯ Adding how it was shared, such as email, in person, or post, makes the trail easy to verify later.

✕ Reusing the creation date as the share date leaves no record of when the recipient actually received it.

Requested response

State exactly what answer or action you want from the recipient. This is effectively the conclusion of a request document.

Example: Please reply in writing by July 20 on whether you accept the revised fee rate.

◯ Cover what you need, in what form, and by when, so the recipient can act without guessing.

✕ Closing with only "please consider this" conveys neither whether a reply is needed nor by when, and often gets no response.

Contact channel

The communication channel used, or to be used, for the exchange. In interaction records it documents how the contact was made.

Example: Phone (called from the main office line, 1:05-1:20 p.m.)

◯ Name the channel type (phone, email, in person) and add the originating line or time so the record can be verified later.

✕ Writing only "contacted" leaves no way to confirm later how or when the contact happened.

⚠ Writing out a personal mobile number or private email exposes it to everyone who sees the document; consider recording only the channel type (mobile, main line) instead of the number itself.

Approver name

The name of the person who approves this document or matter. It makes clear on the document who bears approval responsibility.

Example: Kenichi Nakamura, Head of Sales (approved July 8, 2026)

◯ Write the title with the full name, and add the approval date once approval is given so the record is complete.

✕ Do not fill in the name before approval actually happens; it makes an unapproved document look approved.

⚠ The approver's name is personal information; for external versions, consider listing only the title.

Request details

The concrete content of what you are asking for. Where the purpose field explains why, this field spells out what should be done and how.

Example: For Articles 2 and 5 of the attached draft contract, please check them against your standard clauses and return the file with any proposed changes marked.

◯ Identify the target, the task, and the expected deliverable, and number each item when there is more than one request.

✕ Leaving the details to "we appreciate your cooperation" lets the recipient's interpretation decide the outcome.

⚠ If the details include customer names or transaction data, first confirm the recipient is authorized to see that information.

Client reference

The internal reference number or code your organization uses to identify the client. It pins down the client regardless of duplicate or inconsistently written names.

Example: CL-2026-0148

◯ Copy the number exactly as registered in your client ledger, keeping the digits and separators unchanged.

✕ Do not write the number from memory or mix codes from an old numbering scheme with the current one.

⚠ A reference code is more anonymous than a name, but combined with your internal ledger it still identifies a person; think carefully before putting both the code and the name in the same external document.

Case reference

The number identifying the case, application, or inquiry this document belongs to. It distinguishes documents when several matters run in parallel for the same client.

Example: Case 2026-KY-0072 (inquiry regarding foreign-currency products)

◯ Pair the number with a short subject line so the case is recognizable at a glance in a list.

✕ Assigning a fresh number to every document breaks the chain of records for the same case.

⚠ Keep customer names and account details out of the subject part; if the number identifies the case, a generic subject is enough.

Participants

The people who took part in the meeting, interview, or call. Who was present is basic information that underpins the reliability of the record.

Example: Our side: Tanaka and Hayashi (Asset Management Section) / Client: Mr. Yamada in person

◯ List your side and the other side separately, and note the standing of any proxy or accompanying person such as a family member.

✕ "A few people from their side" makes it impossible to prove later who received the explanation.

⚠ Participant names are personal information; in particular, restrict documents naming clients or their family members to those who genuinely need them.

Summary points

The key outcomes of the meeting or review, listed as bullet points. Readers should grasp the conclusions here without reading the full text.

Example: - The fee revision proposal was taken back for internal review - We will send the renewal documents within July - Next meeting set for July 24

◯ Keep one point per line and separate what was decided from what was deferred to avoid misreading.

✕ Mixing in background narrative or impressions turns the summary into prose and defeats its purpose.

⚠ If a point touches on sensitive matters such as a client's asset position, decide who will see the document before writing it down.

Follow-up actions

Actions planned after this record, or the next steps to take. It turns the record into a trigger for action rather than a dead file.

Example: Prepare the fee comparison table by July 15 and walk the client through it at the July 24 meeting (owner: Tanaka).

◯ Write each item as who does what by when, so missed actions are easy to spot.

✕ "Continue to follow up" commits nobody to any action or date.

Risk note

The risks and uncertainties associated with the transaction, product, or decision. It keeps possible downsides on record, not just the upside.

Example: Because the product is denominated in a foreign currency, exchange-rate movements may reduce the amount received in yen. Early termination may return less than the amount invested, depending on market conditions.

◯ Write each risk as a condition paired with its possible outcome, using "may" rather than absolutes.

✕ Do not downplay risks or assert that something is safe; equally, writing just "risky" with no explanation helps nobody.

Fee note

Explanation of fees and charges, including how they are calculated. In client-facing documents this field demands especially unambiguous wording.

Example: Purchase fee: 1.1% of the transaction amount (tax included). While held, a management fee of 0.55% per year (tax included) is deducted from the fund's assets.

◯ State the rate, whether tax is included, and who pays when, and note the as-of date of the source material.

✕ Avoid unsupported comparisons like "our fees are low," or showing only some charges to make the total look smaller.

⚠ If you record a rate negotiated for a specific client, be careful not to reuse that document for other clients.

Source note

Where the figures and facts in the document come from. It lets the reader judge the freshness and reliability of the information for themselves.

Example: Sources: regulator's published materials (June 2026); execution history from our trading system (as of July 3, 2026)

◯ Give the title, publisher, and as-of date together, and for internal data add the date it was extracted.

✕ Entries like "from various materials" or "found online" convey nothing as a citation.

⚠ If an internal source's title includes a client or case name, replace it with a generalized title in externally shared versions.

Period start date

The first day of the period the report or summary covers. Together with the end date, it defines exactly what range the document deals with.

Example: April 1, 2026

◯ Write the full date including the year, and use the same format as the end date so the two read as a pair.

✕ Entries like "from April" or "start of the fiscal year" leave the exact starting day undefined.

Period end date

The last day of the period the report or summary covers. Trades and events up to and including this day fall within the document's scope.

Example: June 30, 2026

◯ Make clear whether the end date itself is included, for example "through June 30," to avoid disputes over month-end cutoffs.

✕ Wording like "until month-end" or "up to recently" shifts with the calendar and makes the record imprecise.

Purpose of this document

One or two sentences stating why this document is being prepared. It sets the frame for how the reader should treat the content.

Example: To review trading results for the first half of 2026 and organize material for revising rules in the second half.

◯ Limit the field to a single use and make clear who will use the document and for what.

✕ "For the record" alone does not tell the reader whether this is a report or a personal review, leaving them unsure how to handle it.

Distribution scope

Who this document may be distributed or shared with. Writing it into the document itself preserves the handling boundary.

Example: Limited to Sales and Compliance departments; not to be taken outside the company

◯ State the boundary concretely, such as department names plus whether external sharing is allowed, so recipients know instantly whether they may forward it.

✕ "Relevant parties only" means something different to everyone and provides no real control over circulation.

⚠ The more customer information a document contains, the narrower the scope should be; refer back to this field before any forwarding outside it.

Revision number

The version or revision number of the document. When several versions exist side by side, this is how readers identify the latest one.

Example: Rev. 2 (revised July 6, 2026)

◯ Pair a sequential number such as "Rev. 2" with the revision date, and advance the number every time the content changes.

✕ Unnumbered labels like "latest" or "corrected version" become indistinguishable the moment the next revision appears.

List of attachments

List the materials delivered with this document, one per line. The recipient uses it to confirm nothing is missing or extra.

Example: 1. H1 2026 trade list (PDF) 2. Fee summary sheet (Excel) 3. Copy of the account balance certificate (1 page)

◯ Adding the format and page count to each name lets the recipient verify delivery simply by ticking against the list.

✕ "Related materials enclosed" tells nobody what was supposed to be included, so nothing can be verified.

⚠ If an attachment's title itself contains a customer name, consider generalizing or omitting it depending on who will see the list.

Note on the period

Special circumstances the reader should know when interpreting the period's figures, such as market holidays or a change in how totals were calculated.

Example: No trades May 18-22 due to hospitalization. From June onward, fees are aggregated on an execution basis.

◯ State plainly when something differed from normal and what it was, so anomalies in the numbers explain themselves later.

✕ Filling in a rote "nothing in particular" makes it impossible to tell whether there truly were no exceptions or the check was skipped.

⚠ If the reason is personal, such as health or family matters, adjust how much detail you include based on who will read the document.

Items for confirmation and consent

List the points you want the other party to read, confirm, and consent to, one per line. The output formats them so each can be checked off.

Example: I have received an explanation of the fee structure and understand it I understand that price movements can result in losses I confirm this material is not a solicitation document

◯ Keep one point per item, phrased as a statement the reader can affirm, such as "I understand that..." or "I confirm that...".

✕ Bundling several points into one item blurs what was actually agreed to and defeats the purpose of the record.

⚠ If any item concerns handling the other party's personal information, state the purpose of use within the item itself.

Risks and points of caution

The risks and points of caution the reader should know about the trade or product in question. This field carries much of the document's credibility.

Example: - Exchange-rate movements can reduce the value in your home currency - In thin markets you may be unable to sell at your intended price - Fees and taxes change the amount you actually receive

◯ Spell out cause and effect in each item — what can happen and how it affects the reader — so the risks feel concrete rather than boilerplate.

✕ Wording that downplays risks, or conversely asserts safety, defeats the entire purpose of this field.

Section items

The items or subheadings you want in the body, one per line. The output arranges them as sections in this order.

Example: This month's trading overview What the winning trades had in common What the losing trades had in common Focus themes for next month

◯ Imagine the reader going top to bottom and order the items overview first, details next, outlook last for a natural flow.

✕ Item names like "miscellaneous" that reveal nothing about the content make the sections pointless.

⚠ Item names appear as headings throughout the output; keep customer names and other identifying details out of them.

Key events

Market events and notable happenings in your own trading during the period, listed in chronological order. This factual timeline is the foundation of any later review.

Example: June 5: US jobs report beat expectations; USD/JPY jumped June 12: Closed the position per my stop-loss rule June 25: Hit the monthly loss limit and paused new trades

◯ Use a date-plus-fact format and keep interpretations in a separate field such as lessons; a clean factual timeline is far easier to reuse.

✕ Mixing facts with feelings, as in "the market was rough and stressful," produces a record that cannot be verified later.

Rules

Your self-imposed trading rules or operational agreements, one per line. Write them so that compliance can be verified afterward.

Example: Risk no more than 1% of the account balance per trade Place no new orders within 30 minutes before a major data release Always set the stop-loss at the same time as the order

◯ Include numbers and conditions so each rule can be judged kept-or-broken mechanically; that is what makes later reviews precise.

✕ Attitude-only rules like "don't overdo it" or "be careful" can never be judged kept or broken.

Lessons learned

What you learned from the period's trading or work. This is the interpretive counterpart to the factual events field, and the raw material for improvement.

Example: Entries right after a data release make stop-losses unreliable. From next time, wait 15 minutes after the release before acting.

◯ Write the trio of what happened, what you learned, and what you will change next time; that turns the note into an actionable record.

✕ Resolutions like "I'll do better next time" leave no record of what, concretely, will change.

⚠ When sharing with a team, avoid naming colleagues in connection with mistakes; describe the event in generalized terms instead.

Setup steps

The preparation steps for a task or pre-trade routine, one per line in the order performed. The output formats them as a numbered procedure.

Example: Check today's key events on the economic calendar Mark yesterday's high and low on the chart Calculate and note the order size and stop-loss level Confirm the trading platform connection and account balance

◯ One action per line, in the exact order you perform them, turns the field into a checklist you can reuse every session.

✕ Coarse entries like "get ready" or "look at the charts" cannot be reproduced as a procedure.

⚠ Never write account numbers or login credentials into the steps; authentication details do not belong in a document.

Period

The time span that a review or record covers. Express it as a category such as weekly, monthly, or yearly, or as a date range.

Example: June 2026 (2026-06-01 to 2026-06-30)

◯ Pair a label such as "monthly" with the matching date range so the scope stays clear when you aggregate later.

✕ Vague spans such as "recently" leave the start and end undefined.

Record date

The date on which you wrote the record itself. It captures when you made the entry, separately from when the event occurred.

Example: 2026-07-11

◯ Treat it as distinct from the event date and use a consistent year-first format.

✕ Merging it with the event date hides the timeline when you write the record after the fact.

Start date

The start date of a period, backtest, or holding. Pair it with an end date to define the span.

Example: 2026-06-01

◯ Use a year-first format together with the end date so you can compute the span later.

✕ Recording only the start date and leaving the end blank makes the span impossible to total.

Direction

A select for the trade direction: Long (buy) or Short (sell).

Example: Long

◯ Pick from the options and keep the wording consistent so you can tally results by direction.

✕ Mixing free text such as "added more" or "waiting" breaks any grouping by direction.

Profit or loss

The realised profit or loss amount for a trade or period. Record it in whatever currency you use.

Example: -12,500

◯ Always include the plus or minus sign and keep the currency and units consistent across records.

✕ Expressions such as "small loss" or "so-so" cannot feed a total or a win-rate calculation.

Number of trades

How many trades you made in the period. It is the denominator when you compute win rate or average profit and loss.

Example: 24

◯ Count only the trades included in the tally and keep it aligned with the period and conditions.

✕ Writing a count without a clear scope leaves derived figures such as win rate meaningless.

Win rate

The percentage of winning trades, from 0 to 100. Calculate it yourself from the number of trades and the number of wins.

Example: 58

◯ Note the trade count behind the rate so the reliability of the figure is clear.

✕ Avoid treating a win rate from only a handful of trades as if it were a stable measure of skill.

Timeframe

The chart timeframe used for analysis or trading, such as M5, H1, or D1. It can also indicate the intended holding horizon.

Example: H1 (1-hour)

◯ Stick to fixed labels such as daily or 1-hour so you can organize records by timeframe.

✕ Subjective notes such as "shortish" or "longer" fail to pin down the timeframe.

Test period

The date range that a backtest or validation covers. It makes clear which period the results come from.

Example: 2024-01-01 to 2025-12-31

◯ Show the start and end dates in a year-first format and pair the range with the sample size.

✕ A vague span such as "the recent stretch" cannot be reproduced later.

Sample size

The number of trades or observations used in a backtest or statistic. It is a guide to how much weight the result can bear.

Example: 120

◯ Record the exact count you aggregated and tie it to the test period and assumptions.

✕ Avoid treating a result as a firm tendency when the sample size is small.

Parameters

The indicator or strategy parameter values you are recording. Capture them so you can reproduce the same conditions later.

Example: MA: period 20 / RSI: period 14, overbought 70, oversold 30

◯ Write each parameter name with its value and make clear what you changed from the defaults.

✕ Writing only "the usual settings" makes the original conditions unrecoverable over time.

Trigger

The event or moment that set off an emotional reaction or a deviation from your rules.

Example: The unrealised loss grew larger than expected, and I made an unplanned extra entry to win it back.

◯ Describe concretely the situation and the specific trigger so a countermeasure is easier to design.

✕ Writing only "I just lost it" leaves nothing to help you avoid the same situation next time.

⚠ When sharing the record, avoid naming other people as the cause; describe the event in generalized terms.

Countermeasure

The concrete action you decided on to keep the same mistake or deviation from happening again.

Example: When the unrealised loss reaches 2% of the account balance, stop trading for the day instead of trying to win it back.

◯ State when, what, and how far in numbers or conditions so the countermeasure is actually actionable.

✕ Resolutions such as "be careful" or "stay calm next time" leave no concrete action.

Rule ID

An identifier you assign to one of your own trading rules. It links the record to which rule it concerns.

Example: R-012 (trend-following entry condition)

◯ Adopt a scheme such as "R-012" with running numbers so rules and records stay linked.

✕ Writing the same rule differently each time makes it impossible to review by rule later.

Emotion scale

A self-rating of your emotional state on a 1-to-5 scale. A higher number means stronger agitation.

Example: 4 (Somewhat agitated)

◯ Fix what each level means for you (1 = calm to 5 = agitated) and rate on the same basis every time.

✕ Changing the numbers by mood without a fixed basis makes later comparison meaningless.

🛠 Troubleshooting — symptom, cause, fix

❓ Printing produces a garbled page or a document full of broken characters.

Cause: The Print button re-fetches a complete print-ready HTML document at the moment of printing. Printing an outdated page, or using the browser's own print command on the on-screen preview instead, can produce broken output.

Fix:

  1. Print again using the Print button on the output screen, not the browser's print menu.
  2. If the problem persists, reload the page, generate the output again, and then print.
  3. If it still looks broken, re-select the print format and print from the freshly generated document.

✓ Prevention: Always print via the Print button on the output screen rather than printing the on-screen view directly.

❓ Nothing happens when the Print button is pressed; the print dialog never appears.

Cause: A browser popup blocker or an extension may be preventing the print document from opening or the print dialog from launching.

Fix:

  1. Check for a blocked-popup notice near the address bar and allow popups for this site.
  2. Temporarily disable ad-blocking or similar extensions and press the Print button again.
  3. If it still fails, try printing the same output in a different browser to isolate the cause.

✓ Prevention: Allow popups for this site in your everyday browser so printing works reliably.

❓ A downloaded file will not open, or it opens in an unexpected application.

Cause: Downloads are saved with the correct MIME type and file extension for each format. When a file will not open, the issue is usually the application associated with that extension on your device.

Fix:

  1. Check the file extension (.txt, .md, .html, .json, etc.).
  2. Use right-click and Open With to choose a suitable application, such as a text editor or a browser.
  3. If you cannot find the file, open its location from the browser's download history.

✓ Prevention: Set your preferred application as the default for the formats you download most often.

❓ Pressing the Download button does not save any file.

Cause: Browser download settings (ask-before-saving prompts or automatic blocking) or security software may be stopping the file from being saved.

Fix:

  1. Open the browser's downloads list and check for pending or blocked items.
  2. If the browser is set to ask where to save each file, complete the save dialog when it appears.
  3. Check notifications from your security software and allow the file if it was blocked.
  4. If nothing changes, try downloading the same format in a different browser.

✓ Prevention: Allow downloads from this site in both your browser and your security software.

❓ An html-format file looks unstyled or broken when opened on its own.

Cause: The html format is an HTML fragment intended for embedding into another page, not a complete standalone document. Opened by itself, it may render without full styling.

Fix:

  1. For standalone viewing or printing, choose the print format, which is a complete A4 print-ready HTML document.
  2. For a self-contained file suited to PDF conversion, choose the pdfa_html format.
  3. Use the html format only when embedding the content into an existing page or intranet.

✓ Prevention: Match the format to the purpose: html for embedding, print or pdfa_html for standalone viewing and printing.

❓ A PDF created from the pdfa_html format is reported as non-compliant by a PDF/A validator.

Cause: The pdfa_html format is a self-contained HTML document (no scripts, no external assets) prepared for PDF conversion, but final PDF/A compliance depends on your conversion tool and is not guaranteed by this service.

Fix:

  1. Enable the PDF/A output options in your conversion tool, such as font embedding.
  2. Re-validate after conversion and resolve reported items through the tool's settings.
  3. For strict compliance requirements, consider a conversion tool that explicitly supports PDF/A.

✓ Prevention: Confirm the recipient's requirements in advance and keep your conversion tool's PDF/A settings fixed.

❓ The template list or output screen keeps showing old content and does not reflect the latest state.

Cause: When the browser has cached an old version of the page or its scripts, what you see on screen can lag behind the actual current state.

Fix:

  1. Reload the page; a hard reload (Ctrl+F5 on Windows, Cmd+Shift+R on Mac) is most reliable.
  2. If that does not help, clear the browser cache and visit the page again.
  3. If the content is still stale, open the page in a private window to confirm whether caching is the cause.

✓ Prevention: When a page seems out of date, make a hard reload your first step.

❓ A previously generated output cannot be found in the history.

Cause: History retention depends on the plan. Free keeps no history, Pro retains outputs for twelve months, and Premium retains them indefinitely. Outputs created on Free, or Pro outputs older than twelve months, will not appear.

Fix:

  1. Check your current plan and when the output was created.
  2. Outputs made on the Free plan are not stored, so re-enter the values and generate the document again.
  3. For long-term retention, download each output when you create it and store it locally.
  4. If long-term history is essential for your work, consider moving to a higher plan.

✓ Prevention: Do not rely on history alone for important outputs; download and archive them at creation time.

❓ The language selector on the free page only shows Japanese, English, and Japanese-English side by side; other languages cannot be selected.

Cause: The free library is limited to Japanese, English, and the bilingual format. Simultaneous 12-language output is a Pro/Premium feature.

Fix:

  1. On the free page, choose Japanese, English, or the bilingual format for output.
  2. If you need 12-language output, consider upgrading to Pro or higher from the plan page.
  3. If you already have Pro/Premium, open the template from the logged-in dashboard instead of the free page.

✓ Prevention: Do multilingual work from the logged-in dashboard, not from the free page.

❓ The output was generated in an unexpected language (for example English) even though nothing was changed.

Cause: The language field defaults to the language of the page you are viewing. Opening a template on the English page pre-selects English.

Fix:

  1. Check the language field in the Use form and re-select the language you want.
  2. Press Generate again to rebuild the output in the selected language.

✓ Prevention: Glance at the language field before pressing Generate.

❓ The Audience and Tone options do not appear for some templates.

Cause: Personal trader templates are meant for your own records, so audience, tone, and sharing options are intentionally not shown. This is by design, not a defect.

Fix:

  1. Check on the detail screen whether the template belongs to a personal category.
  2. If you need audience or tone controls, choose a template from a business (internal or client-facing) category.

✓ Prevention: Pick the template category based on whether the document is for yourself or for internal/client use.

❓ A field mentioned in the template description cannot be found on the form.

Cause: On templates with many optional fields, non-required fields are collapsed together under an Optional fields section.

Fix:

  1. Click the Optional fields heading in the form to expand it.
  2. Locate the field in the expanded list and fill it in.

✓ Prevention: Scroll through the whole form before starting and check for collapsed sections.

❓ The generated document still contains blank fields and shows an unfilled-items notice.

Cause: Fields left empty on the input form are treated as unfilled in the output, and the QA check displays a warning about them.

Fix:

  1. Review the unfilled-items list or QA warning shown with the output.
  2. Return to the form and fill in the missing fields.
  3. Generate again and confirm the warning is gone.

✓ Prevention: Always check the QA notice before sharing and finalize only when nothing is left unfilled.

❓ Typing a keyword into the search box does not bring up the template you are looking for.

Cause: Search narrows the list by matching your words against template names and descriptions, so spelling variations or word combinations can prevent a match. An active category filter narrows the results even further.

Fix:

  1. Retry the search with a single short keyword.
  2. Try alternative spellings or the English name of the topic.
  3. Reset the category filter to All.
  4. If it still does not appear, clear the search box and browse the list by category.

✓ Prevention: Start with short keywords, and watch the results when combining search with a category filter.

❓ Switching the output format from copy to txt produces output that looks almost the same.

Cause: Both are plain-text formats: copy is shaped with symbol-based headings for pasting, while txt is intended for saving as a file. The body content is the same, so the visual difference can look small. This is not a defect.

Fix:

  1. Choose the format by purpose: copy for pasting into chats or e-mails, txt for saving as a file.
  2. If you need clearer structure, choose markdown or html instead.
  3. Downloads are always saved with the correct extension and file type for the chosen format.

✓ Prevention: Pick output formats by how the file will be used, not by how similar they look.

❓ When downloading the json format, the file is not saved and the raw text opens in a browser tab instead.

Cause: Downloads are served with the correct file type and extension, but some browser or extension settings display json and other text files in a tab instead of saving them.

Fix:

  1. In the opened tab, press Ctrl+S (Cmd+S on Mac) to save the content as a file.
  2. Open the browser download history (Ctrl+J) in case the file was already saved.
  3. Set the browser to save files instead of opening them, or temporarily pause interfering extensions and retry.

✓ Prevention: After downloading json, confirm the saved file has the .json extension.

❓ After narrowing the list by category, the filter cannot be cleared and other templates do not appear.

Cause: The list keeps the selected category, so templates from other categories stay hidden while the selection remains. Occasionally an old page state also remains in the browser cache.

Fix:

  1. Set the category selector back to All.
  2. Check the search box for leftover keywords and clear them.
  3. If the list still does not change, force-reload the page (Ctrl+F5).

✓ Prevention: Before browsing for something else, check the category selector and the search box first.

❓ Clicking the Optional fields heading on the input form does not expand the collapsed section.

Cause: If the page scripts have not finished loading, or an outdated script remains in the browser cache, the expand and collapse control may not respond.

Fix:

  1. Wait a few seconds for the page to finish loading, then click again.
  2. Force-reload the page bypassing the cache (Ctrl+F5 on Windows, Cmd+Shift+R on Mac).
  3. If it still does not open, try the same page in another browser.

✓ Prevention: After an announced update, force-reload the page once before you start filling in forms.

❓ After sharing markdown output, the recipient reports seeing raw symbols such as # and - in the text.

Cause: Markdown is a text format that keeps its notation: # marks headings and - marks list items. It is rendered as formatted text only in markdown-capable tools.

Fix:

  1. If the recipient's tool does not support markdown, share the copy, txt, or html format instead.
  2. To hand over a formatted document, generate the print or pdfa_html format.
  3. For markdown-capable tools such as note-taking apps, pasting as-is works fine.

✓ Prevention: Check whether the destination tool can render markdown before choosing the format.

❓ After a plan change or an update, the form's language options or fields still look like the old version.

Cause: The browser may be showing an old page or script from its cache. Actual availability is enforced server-side at generation time, so only the display is stale.

Fix:

  1. Force-reload the page (Ctrl+F5 on Windows, Cmd+Shift+R on Mac).
  2. If that does not help, clear the browser cache and open the page again.
  3. Right after a plan change, log out and back in, then check the plan shown on the account page.

✓ Prevention: After a plan change or announced update, force-reload the page once before working.

❓ On the free template hub, some templates show a lock icon and the Use button cannot be clicked.

Cause: Only free-library templates are usable on the free page. Paid templates appear locked with a link to the plan information.

Fix:

  1. Use categories or search to find free templates without a lock icon.
  2. If you specifically need a locked template, follow the plan link on the locked card to review paid plans.
  3. After subscribing and logging in, the template becomes available.

✓ Prevention: You can tell in advance which templates are free by checking for the lock icon.

❓ On the free version, a previously generated output cannot be found anywhere afterwards.

Cause: The free version does not save output history. Outputs are not retained unless you save or copy them at generation time.

Fix:

  1. Copy or download outputs immediately after generating them.
  2. Past outputs cannot be recovered, so re-enter your data in the same template to recreate them.
  3. If you need history, consider Pro (12 months) or Premium (unlimited retention).

✓ Prevention: On the free version, make it a habit to download every output when you generate it.

❓ On a smartphone, tables and checklists in the output extend beyond the right edge of the screen.

Cause: Tables need horizontal space for their columns, so on narrow screens the right side can fall outside the view. The content itself is not lost.

Fix:

  1. Scroll the table area sideways, or rotate the device to landscape.
  2. For printing or sharing, generate the print or pdfa_html format and handle it as an A4 document.
  3. Do detailed checking and editing on a PC screen.

✓ Prevention: Review and share table-heavy documents as full documents (print/pdfa_html) rather than as on-screen views.

❓ The template list shows fewer items on screen than the total indicated by the counter.

Cause: The list loads a fixed number of items at a time, and the Show more button loads the rest. The counter shows loaded items versus the total.

Fix:

  1. Press the Show more button at the bottom of the list to load more items.
  2. Repeat until the counter reaches the total.
  3. If you know what you need, narrow the list with search or a category instead.

✓ Prevention: Narrowing by search or category first is usually faster than loading the whole list.

❓ Pressing an export button, such as the plan-comparison export, downloads nothing.

Cause: The browser is blocking the download or pop-up, or the page was left open so long that the login session or the single-use action key (nonce) expired. When expired, the request is rejected and no file is produced.

Fix:

  1. Check the blocking indicator near the browser's address bar and allow downloads from this site.
  2. Reload the page and press the export button again - reloading refreshes the single-use action key.
  3. If it still fails, log out, log back in, and try again.
  4. Try another format (for example JSON instead of CSV) to isolate a format-specific problem.
  5. Try another browser, temporarily disabling extensions such as ad blockers.

✓ Prevention: Run exports from a freshly opened page rather than one that has been sitting open for hours.

❓ The per-language values (manual translation) block does not appear on the Use form, or opens with no inputs inside.

Cause: The most common cause is that only the default output language is selected. The per-language inputs appear only for output languages selected beyond the default, one input per language. Also, the block exists only on free-text fields (single-line and multi-line); choice fields and dates never have it, because they render per language automatically and need no manual value.

Fix:

  1. In the language selection on the Use form, choose the languages you want in addition to the default.
  2. Re-open the per-language values block under the text field - the inputs are built from the language selection at the moment it opens.
  3. If the field without the block is a choice or date field, that is normal - those render per language automatically.
  4. If you cannot add languages on the free page, check how many languages your plan allows.
  5. After changing the language selection, close and re-open the block to rebuild it for the current languages.

✓ Prevention: For multilingual documents, select the output languages first, then open the per-language inputs.

FAQ

Q. What can I do with the free version?

A. Without creating an account, you can use a free library of 120 templates focused on individual investors and traders. You can choose from three language options (Japanese, English, or combined Japanese-English) and use all seven output formats: copy, text, Markdown, HTML, print, PDF-ready HTML, and JSON. Output history is not saved on the free plan, so download or paste your results right away.

Q. Do I need to register an account?

A. The free templates can be used as-is, with no account. To access the full template library, 12-language output, output history, and other features, you need a paid plan (Pro or Premium) with an account. We recommend trying the free version first to see how it fits your workflow.

Q. Which languages are supported?

A. The free version offers Japanese, English, or combined Japanese-English output, with the language of the current page preselected. Pro and Premium support simultaneous output in 12 languages, with Arabic and Urdu rendered right-to-left (RTL). Untranslated portions are filled in with English and marked with a note.

Q. What is the combined Japanese-English output?

A. It is a format that places Japanese and English side by side within a single document. It is useful when you share content with overseas contacts or English speakers, or when you want to keep your own records in both languages. It is available even on the free plan.

Q. What is the difference between personal and business templates?

A. Personal templates are designed for your own records, so options such as audience, tone, and sharing mode are not shown, letting you focus on the inputs. Their outputs include a clear note that actual trading and investment decisions are your own responsibility. Business templates are structured for team and client use, with audience and tone controls, approval fields, and similar elements.

Q. Where is the information I enter stored?

A. Your inputs and generated documents are never sent to SG Group's external servers; they are processed within the customer-controlled environment where the service runs. On the Free plan, no output history is kept, so save your results yourself. On Pro and Premium, outputs are stored in the output history, and Premium's Evidence Mode lets you choose whether the document body is stored (the default keeps a manifest only, without the body).

Q. Is my data sent to outside servers?

A. The body of your inputs and outputs is never transmitted externally. The only external communication is with Stripe, for payments, the billing portal, and subscription-status sync, and it never includes document content. Even Brand Kit logos are fetched by your own environment from the URL you specify, and only when you press the fetch-and-embed button.

Q. Is this service investment advice?

A. No. This service is a tool that helps you create and output document templates; it is not investment, legal, or tax advice. It does not guarantee returns, outcomes, or regulatory conformity. Make actual trading and investment decisions at your own responsibility, and consult a qualified professional when needed.

Q. How do I choose among the seven output formats?

A. Use copy for pasting into chat or email, text for saving a plain file, and Markdown for tools such as Notion or wikis. Choose HTML to embed in an existing page, print for paper output, PDF-ready HTML when you want a PDF, and JSON for reusing the data in other systems. Downloads are saved with the correct file type and extension for each format.

Q. Why does printing produce a clean document instead of the screen?

A. The print format is generated as a complete HTML document with A4 page settings. When you press the print button, the system fetches the print document again and prints that document, rather than the on-screen page. As a result, on-screen elements such as menus are not mixed in, and you get a clean, standalone printed document.

Q. How do I turn an output into a PDF?

A. Choose the PDF-ready HTML format, which produces a self-contained HTML document with no scripts or external assets. Convert it to PDF using your browser's save-as-PDF (print-to-PDF) feature or a conversion tool of your choice. Note that conformance to the PDF/A standard depends on the conversion tool, so the service does not guarantee it.

Q. When should I use the JSON format?

A. JSON outputs the document as structured data, with field names and values in a machine-readable form. It is useful when you want to reuse the document as data, such as importing it into spreadsheets, connecting it with internal systems, or automating record processing. Downloads are saved with the correct file type and extension.

Q. What is the difference between the copy and text formats?

A. Copy is plain text arranged with symbols for headings and separators, meant to be pasted directly into chat or email. Text is plain text intended to be saved and shared as a file. Choose copy when you want to paste from the screen, and text when you want to keep a .txt file.

Q. When is the Markdown format useful?

A. Markdown preserves headings and bullet lists as notation. When pasted into tools that render Markdown, such as Notion, GitHub, or an internal wiki, the document structure is reproduced and easy to read. It also suits documents you plan to keep editing over time.

Q. Can I generate output with some fields left blank?

A. Yes, you can generate output even with blank fields. Unfilled items are clearly marked in the output, so you can see at a glance what still needs to be completed. On Pro and Premium, the QA check detects unfilled fields and shows a caution, which helps you review before sharing.

Q. Can I redo an output later?

A. You can change your inputs and generate output as many times as you like. On Pro and Premium, you can regenerate from the output history, recalling a past output and changing its format or language (outputs under Premium's Legal Hold cannot be regenerated). The Free plan keeps no history, so enter your details again and generate a new output.

Q. Does the Free plan have output history?

A. No, the Free plan does not save output history. Download or copy your results on the spot and keep them yourself. If you need regeneration from history, consider Pro (12-month retention) or Premium (indefinite retention).

Q. Something seems wrong. What should I check first?

A. Start with the account page and confirm your plan, contract status, expiry date, and account type (Master or subaccount). When paid features are unavailable, the cause is most often an expired subscription or a subaccount role without the needed permission. For output issues, the QA check notices and the Rulebook or clause-library warning messages usually point to the cause. On Premium, you can also generate the Self-Check JSON, which contains no bodies or input values, and share it when contacting support.

Q. What are the basic steps to create my first document?

A. Pick a template card from the library and press the use button to open the input screen. Fill in the fields shown, choose your language and output format, and press the generate button to produce the document. You can then copy, download, or print the result depending on how you want to use it.

Q. How do I quickly find the template I need?

A. The template marketplace offers category filters, keyword search, and sorting. Browse by category if you know the type of document you want, or search by keyword if you remember part of the name. The list loads more items as you press the show-more button, so every template is reachable even in a large catalog.

Q. Can I check what a template contains before using it?

A. Yes. Opening the detail view from a card shows the template's description, the fields you will fill in, and related information. This gives you a clear picture before you start typing, and makes it easy to compare similar templates. If it fits your needs, proceed straight to the use screen.

Q. There are many input fields. Do I have to fill them all in?

A. No, you do not need to complete every field. Templates with many optional items group them under a collapsed optional section, so open and fill in only what you need. If you generate with blanks remaining, those spots are clearly marked as unfilled, which also makes the output usable as a draft you complete later.

Q. Why are some templates locked on the free page?

A. On the free page, only templates in the free library can be used; templates for paid plans appear locked, with a link to the plan information. The free library focuses on templates for individual investors and traders, so start there. Access to the full business-oriented catalog requires a Pro or Premium subscription.

Q. Do I need to install any software to use the service?

A. No installation is required; simply open the service pages in your browser. Everything from input to output is handled within the environment where the service runs, and document content is never sent to SG Group's external servers. Downloaded output files are saved on your own device.

Q. HTML, print, and PDF-ready HTML are all HTML. What is the difference?

A. The HTML format is a fragment (partial HTML) meant to be embedded into an existing page or tool. In contrast, print is a complete HTML document with A4 page settings, and PDF-ready HTML is a complete self-contained document with no scripts or external assets. Choose HTML for embedding, and print or PDF-ready when you want a standalone document.

Q. Can I switch to a different format after generating an output?

A. Yes. Select another format and generate again to produce the same content in a different format. On Pro and Premium you can also recall a past output from the history and regenerate it in another format. Since the Free plan keeps no history, it is safest to generate every format you need before leaving the screen.

Q. Where are downloaded files saved?

A. Downloads work like normal browser downloads: files are saved to your device's download location with the correct file type and extension for the chosen format. The service does not keep a separate copy of the file, so manage the saved files yourself; this matters especially on Free, where no output history is kept. Renaming files so the contents are obvious makes them easier to find later.

Q. Does PDF/A-ready mean the output is guaranteed to conform to the PDF/A standard?

A. No, it is not a guarantee. PDF/A-ready means the output is a self-contained HTML document with no scripts or references to external assets, prepared to be well suited for PDF/A conversion. Actual conformance to the PDF/A standard depends on the conversion tool you use, so if conformance is a requirement, verify the converted file with a PDF/A validation tool.

Q. How do paid templates appear on the free page?

A. On the free page, free templates are fully usable, while paid templates are shown in a locked state. Locked cards display a plan notice that links to the pricing information page. You can browse the paid catalog before subscribing, which makes it a useful way to evaluate whether an upgrade suits you.

Q. Does the free version have a time limit or usage cap?

A. No, the free version does not expire; there is no trial period that runs out. The templates in the free library remain available without registration. Keep in mind, however, that no output history is saved, so download or copy each result you need at the time you generate it.

Q. When am I billed after upgrading?

A. When you subscribe to or change a plan, the new plan's price is billed as a new charge. There are no prorated refunds for the remaining period of an existing subscription, so time your switch as it suits you. After subscribing, you can confirm your status in the plan and contract sections of the account page.

Q. Are outputs made on the free version carried over after I subscribe to Pro?

A. No, they are not. The free version keeps no output history, so outputs generated before subscribing cannot be recalled later. Save anything you want to keep by downloading or copying it while on the free version. After subscribing to Pro, outputs are kept in your history for 12 months and can be regenerated.

Q. My printout came out garbled and full of symbols. What should I do?

A. The print button does not print the screen itself; it re-fetches a dedicated print document with A4 page settings and prints that. Reload the page to get the latest state, generate the output again in the print format, and then press the print button. If the layout still breaks, try another browser, or download the PDF-ready HTML, convert it to PDF, and print from there.

Q. Nothing happens when I press the print button. Why?

A. Printing works by fetching the print document, loading it into a hidden frame, and then opening the print dialog, so browser settings, popup blockers, and extensions can interfere. Allow this site in your popup-blocker settings, temporarily disable ad-blocking extensions, and try again. If it still fails, a reliable fallback is to download the PDF-ready HTML and print it with your browser's own print feature.

Q. A PDF/A validator says my converted PDF is non-conformant. Is this a bug?

A. No. The service outputs a self-contained HTML document suited to PDF conversion (no scripts or external assets), and whether the resulting PDF actually conforms to the PDF/A standard depends on the settings and capabilities of the conversion tool you use. The service does not guarantee PDF/A conformity, so if conformance is a requirement, choose a converter that supports PDF/A output and review its settings.

Q. The template I want shows a lock and will not open.

A. On the free page, only templates in the free library are directly usable; templates for paid plans appear locked with a link to the plan information. Using that template requires a Pro or higher subscription. First check whether a free template in the same category can serve your purpose, and consider a paid plan if you need it regularly for your work.

Q. The language selector only shows Japanese, English, and bilingual. Where are the 12 languages?

A. Simultaneous 12-language output is a Pro/Premium feature; on Free, the language choices are limited to Japanese, English, and combined Japanese-English. If you have a paid subscription but still see only three options, check your contract status and expiry date on the account page. When a subscription has expired, language selection also reverts to the Free-equivalent set.

Q. Some templates do not show the audience or tone options.

A. Templates for individual investors and traders intentionally hide the audience, tone, and sharing-mode options. They are designed for personal records, so their output carries no approval fields or internal classifications, letting you focus on the inputs. If you need to adjust the audience or tone, choose a business template instead (available on Pro and Premium).

Q. A field I expected is missing from the input screen.

A. When a template has many optional fields, they are collapsed together under an optional-items section so you can focus on the required ones. Expand that section on the input screen to reveal the hidden fields. If you still cannot find the field, check the field list on the template detail page and make sure you have not mixed the template up with a similarly named one.

Q. Can I print from a smartphone?

A. Yes, the print button also works in smartphone browsers. It fetches a complete document formatted for printing rather than the on-screen view and then opens the browser's print function, and on many phones the print dialog also offers saving as a PDF. Since the print dialog's appearance and options depend on your browser, if it does not work well you can instead download the PDF-ready HTML format and handle it on a computer.

Q. How are the name and extension of a downloaded file decided?

A. The file name and extension are assigned automatically to match the output format you chose. A text output is saved as .txt and a JSON output as .json, for example, so the extension always matches the actual content and the file opens directly in other software. Renaming the extension after saving does not convert the content, so if you need a different format, select it on the output screen and download again.

Q. What changes when I switch the page language between Japanese and English?

A. The on-screen text such as template lists and descriptions follows the page language, and the default output language is also set to match it (English pages preselect English). You can still change the output language before generating. Note that content you have already typed is not translated automatically.

Q. Can I finish a document later if I generated it with some fields left blank?

A. Yes. When you generate with blanks, the unfilled items are noted in the output, so the reliable way to finish is to return to the input screen, fill in what is missing, and generate again. On Pro and Premium the output history lets you check later which document you generated and when, but the Free plan keeps no history, so keep a note of your inputs if you plan to complete the document later.

Q. The manual is long and hard to read. Is there a compact view?

A. Yes. The compact manual view keeps all the content and only reorganizes how it is shown. An overview panel, search, tabs or a table of contents, accordions, a scroll frame, and an open-full-text drawer resolve the problem of pages growing too long on the dashboard and free pages. Open and closed states are remembered in your browser, so only the items you care about stay expanded next time. Print and export always output the full text, and the visible scope stays the same for Free, Pro, and Premium.

Q. In which formats can the plan comparison be exported, and how do they differ?

A. The Plan Comparison Export offers six formats: embeddable HTML (a fragment to paste into a page), print HTML (a complete document for printing as-is), PDF-save HTML (a document meant to be saved as a PDF via the browser's print function), CSV (for spreadsheets), JSON (for processing and integrations), and Markdown (text that pastes easily into documents). A ZIP bundle containing all of them is also available. Every format is generated from the same plan registry at each export, so they never disagree with one another.

Q. Is the PDF-save HTML different from a real PDF or PDF/A?

A. Yes, and we state this honestly: the service has no engine that generates PDFs directly. The print and PDF-save HTML are HTML documents designed to become PDFs by opening them in the browser and choosing save as PDF from the print function. Likewise, the PDF/A-ready HTML template output is a self-contained HTML document laid out for archiving - it is not certified PDF/A (the certified archival PDF standard). The headings and file names say so plainly. If you need certified PDF/A, process the saved PDF with a dedicated conversion tool.

Q. What do the untranslated note and QA warning on an output mean?

A. They mean a free-text field has no manual translation value for that output language. The service never translates automatically, so for a language without a manual value the original text is shown as entered, an untranslated note is attached, and the QA check raises a warning. It is not a bug - it is the honest statement that this part has not been translated. To resolve it, open the per-language values (manual translation) block under the text field on the Use form, enter a value for that language, and regenerate. Choice fields and dates render per language automatically, so only free-written text is affected.

Q. How do the Pro packs differ from the Premium packs?

A. The counts are equal - four each - but the depth differs. The four Pro packs standardize daily practice: meeting preparation and follow-up, intent-capture and comparative-recommendation records, purpose-based QA checks, and the final pre-share check. The four Premium packs deepen organizational approval, evidence, and audit readiness: governance rules with an inspection ledger, an ad-review approval path with a review ledger, cadence-based audit-binder preparation, and a one-view check of Premium settings. Pro suits individual or small-team daily work; Premium suits operations that must keep approval records and prepare for audit submissions.

Showing the manual in a compact panel — full content is inside (scroll) or open it full-width above.

Entries: 45 / Fields: 98 / Scenarios: 17 / Quick starts: 9 / Format samples: 68 / Troubleshooting: 26 / FAQ: 48

Important notes

  • This tool does not provide investment, legal, tax, AML, KYB, or KYC advice.
  • SG Group does not rate, recommend, or rank entities.
  • No guarantee is made of the completeness, accuracy, timeliness, or availability of public records.
  • "No match found" does not prove an entity is unlicensed in every jurisdiction.
  • "No warning found" does not prove a broker is without issue.
  • When a source is temporarily unavailable, manual verification by you is required.
  • Always verify directly with the official regulator in the relevant jurisdiction.

This tool assists with drafting, organizing and record keeping; it is not investment, legal, tax, accounting or regulatory advice. It does not guarantee the legality of your operations, examination outcomes or regulatory conformity. Handling your inputs, outputs, storage, sharing, evidence and submissions — and managing your own environment — is your responsibility. To the maximum extent permitted by applicable law, SG Group is not liable for damages, lost profits, refunds, compensation, third-party claims or regulatory responses.