01 / FROM SETUP TO A WORKING ROUTINE
Begin with a representative project
The getting-started guide follows a useful sequence: establish the workspace, add the right people, create a project and configure its billing context. A representative project is more informative than an empty demo because it reveals the fields, roles and review steps your team really needs. Avoid importing years of records before the basic workflow is understood. A small, complete trial is easier to inspect and correct.
02 / FROM SETUP TO A WORKING ROUTINE
Set the commercial model before interpreting reports
Tracked time only becomes meaningful financial information when the project’s billing approach and cost assumptions are understood. Review the time-and-billing guide before using margin figures to make decisions. Hourly, fixed-fee and retainer projects do not recognize revenue in the same way. Role visibility also matters: contributors, owners and clients should each see the information appropriate to their responsibilities.
03 / FROM SETUP TO A WORKING ROUTINE
Verify access from the recipient’s view
The client-portal guide explains a deliberate sharing workflow. Invite a test client, inspect what is visible and check that internal material remains internal. Preview the shared project before sending the invitation. The same principle applies to team roles and project membership: inspect the actual workflow with the relevant account rather than relying only on an administrator’s view.
04 / FROM SETUP TO A WORKING ROUTINE
Use the automation reference for exact field paths
Automation rules depend on the trigger and the fields available in its payload. The field-path reference documents the current declared inputs, while the automation guide explains how to choose a trigger, condition and action. Not every business event is wired to emit automatically, and a declared trigger should not be treated as proof of live behavior. Test a rule with a safe example and inspect the actual outcome.
05 / FROM SETUP TO A WORKING ROUTINE
Import carefully and preserve an archive
The importing guide explains a staged move from supported sources and CSV. Check field mapping, identities and unsupported history before treating an import as complete. Keep the original export or source archive, validate one project and only then expand the migration. Documentation can describe the path, but the imported records themselves are the evidence that your particular move succeeded.
THE PRACTICAL DETAILS
Questions, answered.
Which guide should I read first?
Start with Getting started, then Project setup and Time and billing. Add client access and automation guidance as those workflows become relevant.
Are the docs a promise that every event is automated?
No. The automation pages distinguish declared fields and supported behavior from events that are not automatically emitted.
Where can I ask a product question?
Use the contact page for the product and support email routes. Include the relevant workflow and a clear description without sharing credentials.