We Realized Today That We Don’t Need Timesheets Anymore
How connecting our meetings, projects, documents, agents, and engineering tools made manual timekeeping redundant.
Today we realized that we have accidentally made clocking in unnecessary.
Over the past year, we have been pulling more and more of PermitZIP into Polygnotos, our internal platform. Transcription, documents, CRM, engineering tools, project files, agent threads, client self-service portals, proposals, closeout, and everything in between now runs through the same system.
The system already knows what project we’re working on
We transcribe most of the day. Internal and external meetings.
Polygnotos knows who is talking, which meeting they are in, how long the meeting lasts, and which projects come up during the conversation.
One conversation does not always belong to one project. We might spend eighteen minutes on one building, twenty-nine minutes on another, and the rest on internal work. The transcript already contains those transitions, so the system can see them.
It even knows which Revit project is open. The only part of our production work that is not yet fully delegated to agents is the actual mouse-clicking inside Revit, and that gap is already closing.
Work activity is automatically logged as we do our work. We don’t need to stop and describe the work. We can just do it.
Our agents clock in.
Each person at PermitZIP might drive ten or fifteen agents during a day. Several can be running at the same time. And with agent loops coming onlin, we have agents working and auditing while we sleep.
One might be reviewing an electrical gear submittal while another works on an RFI. Another might be assembling a commissioning package or searching the project record for an earlier decision.
Those agents are already clocking in on behalf of the person driving them.
We know who started the work. We know which project it belongs to. We know how long it ran. We know which tools and files it used. We know the token spend.
If Carter spends ten minutes directing five agents, and those agents perform work across three projects for the next hour, what should the timesheet say?
The old timesheet does not have a good way to express this agentic workflows. That’s been a challenging problem to solve.
We’ve had to build a way to keep track of the person’s time and the agents’ work separately, then connect both to the correct projects.
Owning your data
We do not own the underlying AI models (yet), but we do own the system and data around them.
We own the project history and every moment connecting it all together.
Every project produces a large trail of proposals, meetings, emails, drawings, redlines, submittals, RFIs, change orders, and final documents. Normally, the reasoning that connects those items gets lost.
That dataset belongs to PermitZIP. It gets better every time we complete another project.
Timesheets are dead
We no longer need to ask our employees to manually report information that the system already has.
Polygnotos knows who is in the meeting, which project is being discussed, which project is open, which agent is working, who is driving it, and what it is producing.
We still have many challenges to work through around privacy, access, and how this information should be used. An automatic record of work should remove administrative effort and let the engineers focus purely on their work.
We’ll see where we go from here, but one thing is becoming abundantly clear:
Nobody needs to clock in anymore.