From the working day to an approved record.
Overshow drafts the record on the consultant's computer at the end of each day. The consultant reviews each item and approves the record. Approval freezes the record; publication is a separate action. When it is published, the consultancy receives only the approved record.
Capture what you choose. Nothing else.
Every capture surface is off until you turn it on. Meeting audio, screen context, documents, calendar, and email each have their own switch, and you can pause everything from the app or menu bar.
- Per-surface switches, off by default
- Pause capture instantly from the menu bar
- Exclude apps, sites, and private windows
- Window text is read directly; nothing visual is stored
Attributed to the engagement it belongs to.
Calls, documents, and screen work land on the right engagement. Calendar series, repository and ticket links, and app rules do most of the placing; anything uncertain waits in an unclassified inbox for the consultant. Nothing is guessed into a client record.
- Calendar series map recurring meetings to the engagement
- GitHub, Linear, and Jira links map repository and ticket work
- App and site rules cover the rest of the working day
- Conflicts and unknowns wait in the unclassified inbox
Northwind platform review, from its calendar series.
Northwind platform review, from its repository rule.
Unclassified. Move it to an engagement, or exclude it.
Drafted at the end of each day.
The record can include completed work, commitments and their dates, decisions and their recorded reasons, risks and blockers, scope changes, and next actions. Each item carries its date, time, and source excerpt.
Approved by the consultant. Ready to share.
The consultant reviews each item, and can correct it, exclude it from the record, or delete it. Approval freezes the record with its source excerpts. Publication is a separate action. When it is published, the consultancy receives only the approved record.
- Correct, exclude, or delete any item before approval
- Approval freezes the record with its source excerpts
- Publication is a separate action
- Drafts stay on the consultant's Mac
Client asked for the Germany rollout.
What the approved record feeds.
Once reviewed, an approved daily record can be published to the organisation repository or exported as CSV for customer-managed reporting. That gives the consultancy a dependable source for scope, delivery and handover, without a live feed of the consultant's day.
Consultant's Mac
Drafts and original sources stay local.
- Work sourcesCalls / messages / docs / screens
- Capture
- Attribute
- Draft
- Approve
- Approved daily record
Native publication
Overshow organisation repository
Manual CSV export
Customer-managed import
Reporting destinations
- Reporting / BI
- CRM project record
- PSA project record
- Customer data platform
Longer-term: project names and assignments.Customer-managed project context returns to Attribute.
CSV is a manual plaintext hand-off. Native CRM, PSA and project-system connections remain future capabilities.
Keep the private parts private.
Exclusion categories keep sensitive surfaces out of capture entirely. Password managers are always excluded, and routine server traffic never contains the work you capture.
Exclusion categories
What leaves this Mac
Every answer carries its sources.
Overshow keeps a work record across sources, revisions, summaries, and AI-assisted steps, so you can retrace the evidence behind anything it tells you.
9 Apr
Source
A customer thread captured the original rollout concern.
11 Apr
AI-assisted step
A local summary connected the thread to the weekly review transcript.
14 Apr
Revision
The owner edited the retry cap before the roadmap review.
14 Apr
Decision
Cap confirmed at 120 seconds, with source and reviser still visible.
Request a chat or demonstration.
A 30-minute walkthrough of an engagement record, or a pilot with one engagement.