Team Space

Better records.
Clearer reviews.
Stronger teamwork.

A connected workspace for selected accomplishments, evaluation drafts, and award packages. See reporting relationships and help the next draft move forward.

Team requires sign-in and applicable workspace permissions.

Real reporting relationships in Team Space
Real reporting relationships in Team Space

A clear boundary

Your team gets the work
you choose to share.

Joining a Team does not expose your entire Personal Log. Rank, title, payment, or a product-admin role does not grant access to another member’s private records.

01 / Connect your people

See how the team
fits together.

Create or join a Direct Team, manage invitations and assignments within your role, and view the reporting structure for the people you are authorized to work with.

  • View the connected reporting tree.
  • Open profiles and navigate supported team views.
  • Keep direct-report responsibilities distinct from wider authorized visibility.

This release does not include expanded organization administration/verification, sponsored seats, or Team billing.

The Team tree with actual example members
The Team tree with actual example members

02 / Route, review, revise

Feedback that goes
with the draft.

Route a selected draft to an authorized reviewer. Review the submitted text and bounded sources, return specific requested changes, and keep revisions moving through the review steps.

Send for reviewRequest changesResubmit
  • Review the exact submitted revision.
  • Add feedback and request focused changes.
  • Approve or send onward when the workflow and your permissions allow.

In-app review is a collaboration workflow. It is not an official military approval, submission, or award decision.

Actual reviewer feedback and next actions
Actual reviewer feedback and next actions

03 / Prepare award packages

Bring the right inputs
into one package.

Set the package brief and required sections, include authorized sources, and complete source-owner consent and review requirements before generating and using the result.

  • Use a brief that reflects the actual solicitation or local guidance.
  • Keep selected sources, access, and consent explicit.
  • Generate with the required authority and active Pro.
  • Review the result before authorized export.
Reviewers do not need Pro merely to receive, read, or review an existing generated package. Payment never bypasses permissions or source consent.
Package brief · Android capture
Package brief · Android capture
Review the selected package
Review the selected package

Built for deliberate collaboration

Clear permissions.
Clear responsibilities.

Selected copies, not your Log.

Contribution, sharing, and routing are explicit actions. A submitted draft is a bounded Team copy, not a live view of everything on your device.

Review and report concerns.

Use the available reporting, blocking, and appeal paths. Keep report summaries truthful and free of restricted information.

Understand copies and retention.

Revocation can limit future access or use; it cannot pull back a file that someone has already exported. Read the retention and deletion details.

Read the Team privacy details →

Start with your record

Don’t start your next eval
from memory.

Capture the work now. Give yourself—and your reviewer—a better starting point later.

Free to download. Optional Pro subscription.
Store availability and pricing may vary.

App screen