Skip to main content
Early pricing is live. Start free for up to 3 AI systems — no card, no time limit.Early pricing is live. Free for up to 3 AI systems.
All docs
How-to guideWhen enabled for your organization

Set up the weekly email and staff check-in

Turn the weekly owner summary on or off, choose who gets the one-question check-in, and cite staff-reported hours.

5 minFor: Workspace owner

When enabled for your organization

Both features are in release 0.3.0 and are switched on by Oabo for a deployment, off by default: the weekly email by OABO_WEEKLY_OWNER_EMAIL_ENABLED, the staff check-in by OABO_STAFF_CHECK_IN_ENABLED. Oabo sets these; the controls below appear on the Scorecard report page when they are on. Until then the job sends nothing.

Weekly owner email

At the bottom of Scorecard, under Weekly email, the switch Email the workspace owner a short summary each week turns the email on or off for the workspace owner. The change and each send are audited.

The email holds the month so far: cost, cash saved, time saved and possible extra revenue on their own lines, what is missing, and the one next step. It is built from the same report as the page and links to /scorecard. It never adds the lines together.

Weekly staff check-in

Under Weekly staff check-in: Ask the people below one question a week about the time AI saved them. Each person answers with one tap from the email, with no sign-in, through a single-use link that expires after 7 days. Opening the page records nothing; only tapping an answer does, once.

Answers show on each use case as staff-reported, apart from the owner's estimate. A question nobody answered counts as no answer, never zero. Unsubscribe needs no sign-in and is audited, as is every send and answer.

Recipients

  • Who is asked: tick workspace members.
  • People without a sign-in: type an Email address to ask and click Add. No user is created; they get the same weekly email and can turn it off. Remove takes them off the list. An unsubscribe sticks even through remove and re-add.
  • Which use cases: tick the use cases the question is about.

Note

The public check-in page (/check-in) shows no email address, and the link's key rides the URL fragment, which no browser sends to a server.

Cite staff-reported hours

On a use case's time benefit, an Administrator can cite a month's staff-reported hours from the check-in as evidence, and stop citing it. The cited range is a snapshot shown beside the benefit as Staff-reported. It is never added to the owner's estimate, the use case's figures or any value, and the benefit's confidence stays Estimated. Each change is audited.

Why it stays Estimated: a staff answer is a statement, not a measurement. See Confidence on the Scorecard.

Previous

Manage team members and roles

Last documented 2026-11-18 against master fb17e1c5. Live release 0.3.1.