Team mode

One site report
from the whole crew

Run one job across several phones without a server, account or sign-up. Everyone types the same team code, records their own visit, then sends the visit back as a .saytpack file.

Local-first · Offline · iPhone and Android · No account needed

The problem

Five phones, one group chat, and somebody up late

Everyone on site shoots on their own phone. The photos land in a Viber or WhatsApp group — recompressed, out of order, with the capture date stripped off. The notes arrive separately, if they arrive at all.

Then one person has to turn all of it into a report. Saving photos one at a time, working out which wall each one was, scrolling back through chat to find what somebody said about it, pasting the lot into Word. It takes a night, and the result is only as good as the memory of whoever assembled it.

Sayt keeps the walk together instead. Each person records on their own phone and sends one file. The photos keep their capture date and their pin on the plan, every observation and issue says who recorded it, and the week comes out as one report.

Team codes

The code is the job

The supervisor picks words the crew can remember, for example sayteam 1. Everyone opens Project Settings and types the same words.

The same words resolve to the same job on every device, offline. Nothing is shared except the words themselves. The code is never sent anywhere. It is hashed on the device.

  • No server
  • No account
  • No sign-up
  • Nothing uploaded
  • Minimum 4 characters
  • Works across iPhone and Android

Case and punctuation do not matter. Sayteam 1, sayteam-1 and SAYTEAM 1 are one job.

Sending a visit in

Each person records the visit as normal

The engineer, architect, QA/QC checker or supervisor walks the site on their own phone. Photos, observations, issues, measurements and plan pins are recorded the usual way.

When the visit is ready, they share a .saytpack handoff file. Use AirDrop, email, WhatsApp, Drive or whatever the site already uses. The supervisor opens the file in Sayt and the visit lands in the shared job, tagged with who sent it.

Importing a handoff file is a Sayt Pro feature.

The Team screen

See what came back

Job code

Shows the team code for the job, so the supervisor can check what the crew should type.

Share the job

Send the job details to someone else without making them create an account.

Batch import

Take in several .saytpack files at once, not one visit at a time.

Who sent what

Show which person sent each visit, and what has landed in the shared job.

Group reports

One report for the crew's work

Pick a week or any date range. Sayt builds one report spanning all the visits in that period.

In a group report, every observation and every issue says who recorded it. The reader can see which engineer, architect, checker or supervisor saw each item.

A solo report does not repeat the name on every card, because the name is already on the letterhead.

  • Weekly reports for this week, last week or any week you choose
  • Custom-range reports for any start and end date
  • Every visit in the range, renumbered into one document
  • Every observation and issue labelled with the person who recorded it
  • The same report templates and preview used for solo visits

Free users get ten weekly reports and ten custom-range reports. Sayt Pro removes the limit.

Local-first

Team mode does not add a backend

Sayt stays offline. There is no shared cloud workspace, no login and no dashboard. The team code is hashed on each phone. Visits move only when a person chooses to share a .saytpack file.

That is why it still works in basements, plant rooms, rural sites and any job where signal is bad.