A way for every person who works for you to flag a problem — or good work — about anyone else on the team. Crew members and crew leaders use Report someone on their field link; every office role uses the card on Home. They pick who, why — late, not keeping up, same mistake, unsafe, rough on equipment, won't listen, had to redo, poor attitude or communication, or good work — and what happened, which is required. Reports go to managers only, who see them on the person's record and mark them reviewed or resolved. The person reported never sees a thing. Made only for post-frame and barndominium builders, so the reasons speak the trade: post spacing, girt layout, a harness on the roof, riding the forks.
Also called: employee reporting · report a concern · report someone · conduct report · write-up · incident report · performance log · crew feedback · praise · private report
Anyone on a crew can report anyone on the team
Try itReport someone sits on the Crew tab of the field link for every crew member and leader, not only leaders. The list is the whole team except you: Your crew first, then Office & managers, then Other crews — so Eli can report a teammate, another crew's worker, his own leader or the office. Pick who, why and what happened, and Send to the office.
Problems on a crew travel up as rumours, weeks late, because the only way to raise one was a phone call about a teammate.
A crew member who can raise a problem — or praise a mate — feels heard and safe, and the leader is not the only one carrying it. The owner hears about trouble before it walks off the job. Three taps and a short note is what a man will actually do from a truck, and the list carries names and a role word, nothing else.
Nine reasons, each with an ⓘ that says what counts
Late, Not keeping up, Same mistake, Unsafe, Rough on equipment, Won't listen, Had to redo, Poor attitude / communication and Good work. Each chip has its own ⓘ that says what belongs under it in trade terms — Name the thing: post spacing, girt layout, fastener pattern — and which bucket it counts toward: attendance, performance, safety, conduct or other.
Two people file the same problem under different words, and nobody can see the pattern.
Clear words take the guessing out of it, so people file with confidence instead of not at all. Because the field and the office use the same nine reasons, the owner sees a real pattern, not a pile of different words. A tooltip does not exist on a phone, so the explanation is a button.
No note, no send
The Send to the office button stays grey until What happened has something in it. The prompt asks for the facts — how many times, which day, what you saw — because that is the part a manager can act on.
"He's always late" is a feeling; "fourth time this month, missed the post-setting start" is a fact you can act on.
Writing what happened keeps a report fair — it is about what was seen, not who dislikes whom. Managers can act on facts, and the person filing knows it will be taken seriously.
Good work goes on the record too
Good work sits on the same list as the problems — green, with its own prompt (What he did, and when) and its own Send it in button. Dale can put on Nate's record that he stayed till dark Friday to close in the north wall before the rain.
A worker's file that only holds his worst weeks says nothing about whether to keep him.
People who get noticed for good work work harder and stay. With praise on the same list, the button feels like recognition, not snitching — and the record shows how people really are, not only their worst weeks.
The person reported never sees it
When it is sent, the field link says so plainly: Sent to the office. Only the office sees this. It is not shown to them. The field link files reports and never lists one back — not the one just sent, not anyone else's — and in the office only managers can read them.
Nobody reports a teammate if the teammate might read it on a borrowed phone.
People only speak up when it is safe to. Knowing the person will never see it — not even on a borrowed phone — is what gets the unsafe thing reported today, before somebody gets hurt.
Every office role reports from Home
Salespeople, project managers, admins — every role has the card on Home: Something wrong on the team — or someone doing great? It opens the same report with the same reasons the field uses, so a salesperson who hears a crew was rude to a customer has somewhere to put it.
Office staff see things too, and had nowhere to put them except a hallway conversation.
Office staff see things too. A card on the screen they already open makes speaking up feel normal, and the owner gets the whole picture, not only what reaches him from the field.
About anyone on the team — leaders and office included
Who is it about? lists everyone active on the team with their role — crew members with no login included — and leaves out only you. Reporting is not only downward: a worker can report his crew leader, and a crew leader can report the office.
A reporting line that only runs downhill means nobody can raise a problem about a leader.
When anyone can be reported, leaders are held to the same standard as their crews. That feels fair, and fairness keeps good people. Who can read reports is what stays limited.
How serious starts from the reason — and can be moved
Try itIn the office form, picking a reason sets How serious? to where that reason starts: Unsafe is Serious, Good work is Minor, the rest Needs attention. The person filing can move it. From the field, the reason sets it on its own, so a crew member has one less thing to decide.
If everything is filed as "medium", a safety problem looks the same as a late start.
Starting from the reason saves a decision, so people file instead of putting it off. A safety problem shows up as serious and gets handled first — and the person filing can still move it.
Managers read them on the person's record — and close them out
Try itOnly admins, sales managers and project managers can read reports. On a person's record in Team Members, each one shows its reason, how serious it is, who filed it — marked (from the field) when it came off the field link — the date and its status. Mark reviewed, Resolve or Reopen; the number still open sits in the heading.
A report nobody closes out teaches the person who filed it that nothing happens.
A report marked reviewed tells people their voice did something, so they keep speaking up. For the owner, one list per person shows the pattern — the third Late in a month — at a glance.
Managers hear about it when it is filed
Filing a report notifies the account's admins and project managers by default — you choose who in Notifications. A report from the field arrives with the person, the reason and the note — Wes Miller — late — so a safety problem stands out from a late start before anyone opens it.
Reports that wait for someone to go looking get read after the damage is done.
A safety problem dealt with today is a man who goes home safe tonight. Managers hear while it is still fresh, and the crew see the office respond, which is what makes them trust that reporting works.
- 1On the field link, Report someone sits on the Crew tab for every crew member and leader — not only leaders.
- 2Who: everyone on the team except you, grouped Your crew, Office & managers and Other crews, each with a role word.
- 3Why: nine reasons, each with an ⓘ that says what belongs under it — including Good work, for praise.
- 4What happened is required — the facts: how many times, which day, what you saw.
- 5In the office, every role has the card on Home — Something wrong on the team — or someone doing great? — which opens the same report, with How serious? set from the reason and movable.
- 6The account's admins and project managers are notified when one is filed; you choose who in Notifications.
- 7Managers read reports on the person's record in Team Members, see which came from the field, and mark each reviewed or resolved, or reopen it.
- 8The person reported never sees a report, and the field link never shows one back.
Most problems on a crew reach the owner late, secondhand, or not at all. The man who sees a teammate walk the roof edge without a harness does not want to make a phone call about it, and a crew leader quietly carrying a slow hand never says so until somebody quits. By the time the office hears, it is a pattern nobody wrote down. So anybody can say it, from wherever they are: a framer from the field link on his phone, a salesperson or a project manager from Home. It is not only downward — a crew member can report a leader, and a leader can report the office. Three choices and a short note, because anything longer will not get filed from a truck. Two rules make people actually use it. The person reported never sees it — the field link files and never reads anything back, because that link lives on a phone that gets lent and left on tailgates. And there is a button for good work on the same list, so it becomes a record of how people are doing, not a complaints box the office learns to ignore. The note is required for the same reason a manager needs it: "he's always late" is a feeling. "Fourth time this month, missed the post-setting start" is something you can act on.
- Problems on a crew reach the owner late, secondhand, or never
- There is no written record of a pattern — late starts, repeat mistakes, unsafe work
- People will not report a teammate if the teammate might see it
- Good work goes unrecorded, so a worker's file holds only his worst days
- Reports from the field and from the office land in different places, in different words
