Team-Week
Log in Request a demo

Weekly check-ins for teams

Weekly check-ins a manager actually reads.

Five minutes to write, one minute to read. A flag when someone needs help; trends instead of surprises.

Built and used by a tech leader, for any team that wants an honest weekly pulse.

Request a demo See how it works

Team-Week is in a pilot with its first team. Invite-only, no trackers, no AI.

The weekly check-in page with demo data: a 1 to 5 pulse with 3 picked (the pulse is never private), wins and challenges each with a Make private button, last week's priority ticked off, and the person's recent weeks with their pulse.
The weekly check-in: pulse, wins, challenges and priorities, with your recent weeks alongside. Demo data.

How it works

One short loop, every week

Each team has a due day. Everyone checks in, managers read and reply, and the pulse builds up into a trend.

  1. You check in

    Pick a pulse from 1 to 5, write your wins and challenges, tick off last week's priorities and set next week's, answer the team's question of the week, and flag anything you need help with. Drafts save themselves.

  2. Your manager replies

    Managers read each check-in from the Team page and leave feedback on it, or simply mark it reviewed. You see their feedback next to your check-in.

  3. The team's pulse becomes a trend

    Every check-in feeds the Team page: who has checked in, the average pulse, who asked for help, and pulse trend charts per manager and per team. A dip shows up as a line, not as a surprise.

Features

What's in it

Everything here is in the app today, except the last card, which is what's coming next.

The weekly check-in

  • A 1–5 pulse: how the week went, in one tap.
  • Wins and challenges.
  • Priorities for next week, carried into the next check-in with a tick for each one done.
  • After you submit, see your own last 8 weeks: your pulse, your streak and the priorities you finished. This view is yours alone.
  • Unfinished priorities carry to next week in one tap, and private ones stay private.
  • A rotating question of the week, set per team.
  • Belong to several teams, with one check-in they all see.
  • “Need help?”: an optional ask your manager sees flagged, and can acknowledge, reply to and mark helped. You get an email when they do, unless you switched it off.
  • Need to tell only your manager something? Mark a note private and only they can read it — not admins, not owners.
  • Drafts save automatically while you write.
  • Step between weeks and look back through your history.
  • Going away? Mark the week, and no reminder goes out and your team sees Away instead of Missing.

For managers

  • Feedback on each check-in, shown to the person next to it.
  • The Team page: an org roll-up of everyone below you, by reporting line, with who has checked in, the average pulse, who asked for help and who has been reviewed.
  • Open asks for help are listed first on the Team page, oldest first, with how long each has been open: acknowledge one, reply to the person and mark it helped.
  • A panel per person with their last 8 weeks.
  • Pulse trend charts per manager and per team.

High fives

  • Thank up to ten people at once, with a short message.
  • Visible to the whole team, on its own page and at the top of the Team page.

Email

  • A reminder on your team's due day.
  • A note when your manager leaves feedback or someone gives you a high five.
  • Each person chooses which of these emails they get.
  • Managers get one short email the morning after check-ins are due: who checked in and which asks for help are still open.
  • Every reminder and notice has a stop link.

People and access

  • Invite-only: an admin adds each person and sends them a one-time setup link.
  • Check-ins and feedback follow the reporting line: you see yourself and the people below you. Admins see everyone except the people above them. Everyone signed in can read the directory: name, email, title, team, manager, admin flag and joined date.
  • Owners set the rules; admins look after people and teams.
  • Users page: everyone's sign-in status, and invite or reset links.
  • Owners can see who changed what: sign-in links, people, teams and settings.
  • Teams page: a tab for each team, with its due day and weekly questions.

Settings

  • Minimum password length and session length.
  • The email sender name and org-wide switches for each kind of notice.
  • The instance name shown in the app.
  • Owners can mark a holiday week: no reminders, and nobody shows as late.

Anywhere

  • Works on a phone as well as a laptop, in light and dark mode.
  • Got feedback or an idea for a feature? Choose it in the account menu and it opens an email to us.
  • What's new, inside the app: a short note when something changes, so nobody has to be told.

Coming next

Coming

On the roadmap, not in the app yet.

  • Posts to Microsoft Teams channels: high fives, reminders and a weekly digest.
  • A brag doc: export your own wins, finished priorities and high fives for review season.
  • 1:1 prep.
  • Reminders at the right hour in each person's time zone.

Screenshots

See it

Real screens from the app, filled with demo data: the people, teams and addresses are made up.

The Team page with demo data: tabs for everyone and for each of three teams, this week's numbers (checked in, average pulse, asked for help, reviewed), the average pulse over the last 8 weeks, and a small pulse trend per manager.
The Team page: this week's roll-up, and pulse trends for the team and per manager.
Further down the Team page, with demo data: an open help ask, people in reporting-line order with this week's status (one shows a private note), and one person's panel with their last 8 weeks, their help ask with Acknowledge and Mark helped, and their check-in.
Everyone below you by reporting line, and a panel per person with their last 8 weeks, any ask for help and their check-in.
The High fives page with demo data: a form to thank up to ten people, and the team's recent high fives.
High fives: thank up to ten people at once; the whole team sees them.
The Users page with demo data: people with their teams and sign-in status, and one person's panel to pick every team they are on, who they report to and admin access.
Users (admins): add people, set their team and manager, see who has signed in, send setup links.
The Settings page with demo data: tabs for the instance, sign-in, email and the Activity log, the instance name, and who changes what.
Settings (owners): the instance name, sign-in rules and email, one tab each.
The weekly check-in on a phone, with demo data.
The check-in on a phone.
The Team page on a phone, with demo data.
The Team page on a phone.

Built with

A small, conventional stack

Chosen to run on an ordinary server, with nothing exotic to operate.

Language
Go for the server and the pages, with a little plain JavaScript for the screens' behaviour.
Web app
Server-rendered pages with templ and htmx, Tailwind CSS v4, and the trend charts drawn on the server as SVG.
Server
One static Go binary on the standard library's net/http, in a distroless container.
Data
PostgreSQL 18, with pgx, sqlc-generated queries and reviewed SQL migrations (goose).
Sign-in
Scrypt password hashing, HttpOnly session cookies, invite-only accounts.
Email
go-mail, sending through Resend.
Running it
Docker Compose, with Cloudflare in front: DNS, proxy, Tunnel, rate limiting and Turnstile.
Tests
Go tests on a real PostgreSQL, and Playwright end to end in a real browser, on desktop and phone.

Security and privacy

Check-ins are personal. They're treated that way.

People write honestly only when they trust where it goes. In plain language:

  • Invite-only.There's no public sign-up: an admin adds each person.
  • Check-ins follow the reporting line.You see yourself and the people below you. Admins see everyone except the people above them. Everyone signed in can read the directory: name, email, title, team, manager, admin flag and joined date.
  • Passwords are never stored in clear.Only salted scrypt hashes; common passwords are refused.
  • Sessions in HttpOnly, Secure cookies.Scripts on the page can't read them.
  • A strict Content-Security-Policy.Pages run only their own scripts and fonts, plus Cloudflare's bot check on the sign-in and demo forms.
  • Bot check and rate limits on sign-in.Cloudflare Turnstile and per-account and per-address limits slow down guessing.
  • Plain-text email only.No HTML, no tracking pixels, no link tracking.
  • No trackers, no analytics.Not in the app, and not on this page.
  • No AI reading anyone's check-ins.What people write is read by people.
  • Your data stays yours.It lives in a PostgreSQL database the operator controls. Export and deletion on request.

Request a demo

See it with your own team in mind

Tell us a little about your team. A person reads every request and replies by email; there's no mailing list and no automated sequence.

What you send is stored with your IP address (to limit abuse) and used only to reply to you. Ask, and it's deleted.