Browse, search and start from a template.
Free templates For individual investors and traders Japanese / English support Paid plans include 412 templates
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
Checklist
A personal note to set out your plan, scenarios and "do-nots" for the day.
Email draft
A polite, neutral draft email for introducing your service to a prospective IB partner.
Checklist
A personal checklist to confirm your own rules before placing an order.
Internal memo
A draft internal request to begin reviewing a new prospective IB partner.
Internal memo
A personal note recording why you entered, for later review.
Disclaimer text
A neutral draft for disclosing how IB commission arrangements work.
Checklist
A personal note to state your stop and take-profit rules before trading.
Checklist
A checklist draft to track onboarding steps for a new client.
Internal memo
A personal note to check why you are still holding a position.
Internal memo
A summary draft for aligning on the key terms of a referral arrangement.
Checklist
A personal checklist for a final risk review before trading.
Monthly report
A report outline for sharing monthly IB activity with stakeholders.
This is a structure preview. The real text is generated by the output feature (paid plans).
These are the same confirmation items the generated output includes.
Variable fields appear here once a template is selected.
Japanese / English (12-language output is available on the paid dashboard).
Output generation requires a paid plan.
This output is a drafting aid only and is not investment, legal, tax or regulatory advice. Reviewing and editing it, and managing how it is stored, shared and submitted, are your responsibility.
QA reviews wording and expression quality of the document, not the safety or risk of any business.
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.
Pro / Premium unlock all 412 templates and 12-language output (including Japanese and English).
View plansManual version: v2.4.41 · This manual is operating documentation only — not investment, legal or tax advice.
✓ One ready-to-paste trade log entry in plain text with headings
✓ A printed A4 weekly review you can revisit before trading
✓ A bilingual investment note that is easy to search later
✓ One template whose fields you have already verified fit your workflow
✓ A dated post-mortem file you can reread before your next trade
✓ An HTML fragment of your watchlist note, ready to embed
✓ A dated PDF of your month-end note, filed in your archive
✓ An English trade note as structured data, ready to import elsewhere
✓ A personal trading-rules checklist you can walk through before every trade
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:
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:
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
◯ Do
✕ Don't
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
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:
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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
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
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:
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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
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
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:
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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
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
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:
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:
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
◯ Do
✕ Don't
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
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:
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:
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
◯ Do
✕ Don't
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
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:
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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
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)
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:
| Page language | Output language |
|---|---|
| Language of the UI | Language of the document |
| Sets the default language choice | Chosen for each output |
| Switch via JA / EN pages | Free: 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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
Data handling: Your inputs and output text are never transmitted to external SG Group servers.
Related: QA Check, Locked Sections, Rulebook (Compliance Rules)
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:
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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
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
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:
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:
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
◯ Do
✕ Don't
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
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:
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:
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
◯ Do
✕ Don't
Data handling: Your inputs and output text are never transmitted to external SG Group servers.
Related: Troubleshooting Basics, Free Templates Hub, Viewing Template Details
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:
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:
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
◯ Do
✕ Don't
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
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:
| Format | Use for | Content |
|---|---|---|
| Copy / Text | Pasting into chat or email | Plain text |
| Markdown | Importing into document tools | Markdown |
| HTML | Embedding / on-screen review | HTML fragment |
| Printing as-is | Complete HTML document (A4) | |
| PDF/A-ready HTML | PDF conversion / archiving | Self-contained HTML document |
| JSON | System integration / storage | Structured 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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
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
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:
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:
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
◯ Do
✕ Don't
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
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:
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:
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
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
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:
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:
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
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)
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:
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:
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
◯ Do
✕ Don't
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
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:
| Single language | JA + EN bilingual |
|---|---|
| Japanese or English only | Same content in both languages |
| Shorter, compact document | Easy to share internationally |
| Best for one-language readers | Roughly 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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
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
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:
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:
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
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
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:
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:
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
◯ Do
✕ Don't
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)
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:
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:
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
◯ Do
✕ Don't
Data handling: Your inputs and output text are never transmitted to external SG Group servers.
Related: Account Page, Managing Payments (Stripe), Free Templates Hub
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:
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:
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
◯ Do
✕ Don't
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)
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:
| Free | Pro | Premium | |
|---|---|---|---|
| Templates | Free library | Full catalogue | Full catalogue |
| Languages | Japanese & English | 12 simultaneous | 12 simultaneous |
| Accounts | 1 (no sign-up) | Up to 3 | 10 standard + paid add-ons |
| Operations | — | History & QA | Brand 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:
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
◯ Do
✕ Don't
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)
These features are not available on your current plan — shown for reference only (no operating steps).
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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."
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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."
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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:
✓ Prevention: Always print via the Print button on the output screen rather than printing the on-screen view directly.
Cause: A browser popup blocker or an extension may be preventing the print document from opening or the print dialog from launching.
Fix:
✓ Prevention: Allow popups for this site in your everyday browser so printing works reliably.
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:
✓ Prevention: Set your preferred application as the default for the formats you download most often.
Cause: Browser download settings (ask-before-saving prompts or automatic blocking) or security software may be stopping the file from being saved.
Fix:
✓ Prevention: Allow downloads from this site in both your browser and your security software.
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:
✓ Prevention: Match the format to the purpose: html for embedding, print or pdfa_html for standalone viewing and printing.
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:
✓ Prevention: Confirm the recipient's requirements in advance and keep your conversion tool's PDF/A settings fixed.
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:
✓ Prevention: When a page seems out of date, make a hard reload your first step.
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:
✓ Prevention: Do not rely on history alone for important outputs; download and archive them at creation time.
Cause: The free library is limited to Japanese, English, and the bilingual format. Simultaneous 12-language output is a Pro/Premium feature.
Fix:
✓ Prevention: Do multilingual work from the logged-in dashboard, not from the free page.
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:
✓ Prevention: Glance at the language field before pressing Generate.
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:
✓ Prevention: Pick the template category based on whether the document is for yourself or for internal/client use.
Cause: On templates with many optional fields, non-required fields are collapsed together under an Optional fields section.
Fix:
✓ Prevention: Scroll through the whole form before starting and check for collapsed sections.
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:
✓ Prevention: Always check the QA notice before sharing and finalize only when nothing is left unfilled.
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:
✓ Prevention: Start with short keywords, and watch the results when combining search with a category filter.
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:
✓ Prevention: Pick output formats by how the file will be used, not by how similar they look.
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:
✓ Prevention: After downloading json, confirm the saved file has the .json extension.
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:
✓ Prevention: Before browsing for something else, check the category selector and the search box first.
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:
✓ Prevention: After an announced update, force-reload the page once before you start filling in forms.
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:
✓ Prevention: Check whether the destination tool can render markdown before choosing the format.
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:
✓ Prevention: After a plan change or announced update, force-reload the page once before working.
Cause: Only free-library templates are usable on the free page. Paid templates appear locked with a link to the plan information.
Fix:
✓ Prevention: You can tell in advance which templates are free by checking for the lock icon.
Cause: The free version does not save output history. Outputs are not retained unless you save or copy them at generation time.
Fix:
✓ Prevention: On the free version, make it a habit to download every output when you generate it.
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:
✓ Prevention: Review and share table-heavy documents as full documents (print/pdfa_html) rather than as on-screen views.
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:
✓ Prevention: Narrowing by search or category first is usually faster than loading the whole list.
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:
✓ Prevention: Run exports from a freshly opened page rather than one that has been sitting open for hours.
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:
✓ Prevention: For multilingual documents, select the output languages first, then open the per-language inputs.
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 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.