Count person-hours, not computers

An editor may use an office Mac and a home Mac. Those devices should belong to the same person, while different editors need separate identities. This keeps reports useful when work moves between locations.

The planned launch offer includes up to five editors and unlimited report-only users. Producers can review hours without occupying a recording-editor place. We’re starting on Mac; Windows support is not available yet.

Automatic capture still needs a clear job structure

The companion detects Premiere projects automatically. In the dashboard, link those detected files to your production job so you can compare the work with its quoted editing allowance. This is especially useful when one job has several project files or filenames change.

Agree on who manages job links and revision stages. Editors should not need to select a timer on every task switch, but a producer still needs to decide which customer job a project belongs to.

Read the report in three passes

First, check the total confirmed editing time for the job and compare it with the allowance. Next, look at the editor and sequence breakdown to understand where the work happened. Finally, review revision stages and any excluded or ambiguous intervals.

  • Job total: are we inside the editing allowance?
  • Editor and sequence context: how was the work shared?
  • Stages and exceptions: what caused the extra work, and are the records complete?

Keep recorded time separate from billable time

An editing tracker records activity according to its rules. It does not decide what the client should be billed. Training, internal review, technical fixes or included revision rounds may have different commercial treatment.

Use the recorded total as evidence, then apply the job agreement. Missing time should prompt a review, not an automatic assumption that an editor was not working. Research, planning and calls outside Premiere are outside the present capture scope.

Export and integrations

The dashboard supports CSV export and a read-only MCP interface for compatible clients. These provide ways to use reporting data elsewhere without giving an integration permission to change time records.

Direct Xero and CRM connections are planned. Automatic timesheet posting, invoicing and payment collection are not part of the current waitlist release. A CSV export should be reviewed and mapped to the destination system before use.

Company access and privacy

Editors have their own accounts. Workspace permissions govern access: managers can review company time, while ordinary editor reporting is limited to the editor’s own time.

The database is hosted in Sydney. Operational services such as website hosting and email delivery may process information elsewhere. Project paths and sequence names can contain customer information, so keep those naming choices in mind when enrolling a company.

Put real numbers behind the next quote.

Join the early-access waitlist and tell us which software your team uses. Public trials and payments are not open yet.

Get early access