Team Meeting Minutes: Confirm Owners & Archives | Yihu

Check owner acknowledgment, approved scope and existing storage rules before archiving minutes. Try Yihu’s no-mic notes preview, then review privacy and App Store setup.

Preview privacy before you try

The linked preview uses preset material, needs no login or microphone, and keeps edits only in the open page. Reloading resets edits. Optional read-aloud uses the browser’s voice service; usage analytics require consent.

Keep private originals in approved tools. In the app, on-device recognition and the destination’s storage, sync and access rules are separate steps. Review the installed version before using a source-described workflow. Read the data-flow guide

US listing verified; availability depends on your storefront. No Mac or self-signing for store installation. Bring your workspace address and account; the optional speech model is about 950 MB.

Check acknowledgment and scope before choosing an archive

Check the original, minutes version and the relevant role’s explicit acknowledgment. Separate proposed responsibility from confirmed ownership. Use existing team processes to verify approval scope, access and retention. Without evidence, stay in an authorized draft rather than creating a new share location. A manual checklist does not assign work or sign for anyone.

A different task from fields and to-do extraction

The minutes-fields guide separates facts/proposals/questions; multi-note review handles conflicts across records. Here no new tasks are extracted. Check whether an already proposed handoff was acknowledged by the relevant role and whether archiving conditions are known. Do not fill real names, infer owners or alter departmental permissions just to complete a table.

Manual ownership and archive checklist

Dimension Existing evidence needed Synthetic record Missing-evidence action
Proposed role Role proposed in original text or existing process Role A suggested, not acknowledged Keep it proposed; do not assign automatically
Acknowledgment Explicit response through an authorized workflow No acknowledgment evidence supplied CC, read status or a named person is not ownership
Approved scope Confirmed content, constraints and unapproved parts Review sample only; do not execute No inferred purchasing, email, change or release authority
Open questions Existing process that must confirm next Owner and deadline pending No guessed person/date
Archive location Existing authorized storage and access scope Location unverified; no upload A local/workbench draft is not automatically an official archive
Retention rule Actual team policy/reference, not invented duration Existing rule needs maintainer clarification No permanent-retention, backup-free or deletion guarantee
Copies Actual note, clipboard, document and workbench copies Local sample checked; others unknown One deletion does not recall all material
Handoff stage Separate draft/staged/recorded/uncertain evidence Draft for review; not sent saved/queued are not ownership or completion

A synthetic acknowledgment card that assigns no real work

Item: Three sample editorial fields (not a real task)
proposed_role: Role A suggested, not assigned
acknowledgment_evidence: Not provided; do not mark acknowledged
approved_scope: Review sample wording only; no execution authority
open_question: Which existing process confirms ownership?
archive_location: Unverified; do not upload to a new destination
retention_rule_reference: Pending existing team policy
handoff_state: Local draft, not sent

These are manual checklist labels, not app/Radar imports or a signing API. This page sends no invitation, changes no permission, creates no shared document and collects no names/contact information. Confirm through the team’s existing authorized channel, not by copying the synthetic card to a live ledger as a test.

Ordering before archiving

  1. Check the original and edited version before asking another role to confirm recognition errors.
  2. Separate proposed responsibility from actual acknowledgment evidence. Silence is not consent.
  3. Verify confirmed content/permission scope. Agreeing to review wording does not authorize task execution.
  4. Check existing archive location, access and retention rules. Without evidence, stop in an authorized local draft instead of provisioning accounts, share links or public attachments.
  5. List necessary copies and uncertain handoffs. Previously attempted notes retain original one-handoff state; archiving is not a bypass for repeated delivery.

Radar replies, if needed, retain original eligibility, server authority, phone confirmation and receipt readback. A recorded reply is not completed ownership work, and reply history is not a general document archive.

FAQ

Does writing role A in minutes establish ownership?

No. It is proposed text until the relevant role explicitly confirms through an existing authorized process. CC or silence cannot replace that evidence.

Does Yihu provide departmental assignment or e-signatures?

No such capability is asserted or added. This is manual review guidance; voice drafts and note handoff do not create an organizational approval system.

Is saving a workbench draft formal archiving?

Not necessarily. The existing team process defines location, version, access and retention. Saving a draft alone does not establish those requirements.

No. Scope must be explicit. Review, approval and execution authority are distinct, and unapproved content stays open.

Can this guide prescribe one retention/deletion period?

No. Destinations, accounts, backups and team policies differ. Refer to actual rules without inventing periods or deletion guarantees.

Can Radar reply history be a complete department archive?

Not as an inference. It reads original-item replies/feedback within its permission/implementation limits, not arbitrary documents, versions, signatures or ownership records.

Guides and evidence

Manual minutes fields · Multiple-note/to-do review · Manual noisy-transcript correction · Phone decisions/receipts · Start · Privacy

Implementation boundaries: README replies/history, note one-handoff model. Cards and archive checks are editorial suggestions, not source functionality or compliance certification.