How we build content

Last updated 26 August 2026 · Maintained by Steven Jagurić

This page explains the practical process behind GetToWork guides, articles, templates, and public tools. The work is done by Steven Jagurić (Founder, builder, and editor of GetToWork.online), who builds and maintains the product. For standards and corrections, see the editorial policy.

Written content

1. Start from a specific workday problem (a handoff, a blocker update, a shredded meeting day), not a keyword list.
2. Write steps, examples, and checklists someone could use without creating a GetToWork account.
3. Link to related guides, templates, and tools that actually exist on the site.
4. Keep authorship in About and the author profile; content pages stay informational without an author bio block.
5. Revisit pages when the product or a stated fact changes.

We keep claims supportable. Unsupported research, filler, and invented personal stories stay out.

Templates

Templates include purpose, when to use them, a copyable blank, a filled example, and a short note on why the example works. Copy actions run in the browser. Templates are meant to be useful even if you never register.

How our tools work

Most GetToWork calculators and text utilities run locally in your browser. Your inputs are processed on your device for those tools. We state privacy notes on tool pages when client-side processing applies.

• Local by default: many transforms and calculations do not need to send your text or numbers to our servers to produce a result.
• Assumptions are stated: tool pages should say what the math includes and excludes (for example, business days that skip Saturday and Sunday only, or money amounts that exclude tax unless you add tax yourself).
• Not professional advice: money and freelance tools are general calculators, not tax, legal, or financial advice.
• Tested before publish: calculations and transforms have automated tests in our repository. We do not publish a tool page for a calculator we have not exercised.
• Examples on the page: tools include worked examples so you can sanity-check the output.

Browse the catalog on Tools. If a result looks wrong, tell us via Contact (hello@gettowork.online).

Quality bar

• State calculator assumptions clearly
• Publish tools only after they have been exercised in tests
• Keep privacy notes accurate for client-side processing
• Ship pages that help a workday, not keyword shells

Author profile · Editorial policy · About · Contact · Privacy