Skip to content

What a night looks like

Premisa runs on the order the work already happens in. Nobody types anything up at the end.

  1. 1

    Clock in at the site.

    The crew opens the app on their own phone and clocks in. The punch carries the location and the time with it, so arrival is a fact rather than a claim. A punch outside the site is flagged rather than silently accepted.

  2. 2

    Work the checklist.

    Each item that needs a photo says so, and the photo attaches to the item it proves. The crew can see what is still missing without calling anyone.

  3. 3

    The gate.

    Try to close a shift with a required photo missing and the app refuses. So does the office. There is no override button, because a system with an override button is a system whose records can be argued with.

  4. 4

    The shift closes itself.

    When the last piece of evidence lands, the shift completes and the client report is built from what actually came in.

  5. 5

    The client sees it.

    Your client logs into their own portal, in your branding, and sees the same night. Not a PDF you emailed. Not a summary you wrote.

When there is no signal.

The crew keeps working and everything is saved on the phone. When the phone comes back, it sends. Until it sends, the app says so in plain words: this work has not reached the office and the client will not see it. It offers to retry and it backs off instead of hammering a dead connection.

What it does not do.

No invoicing. No bidding. No payroll. Those are solved, they are crowded, and chasing them would cost the thing Premisa is actually for. It is the proof layer and it stays that.

See it on your own building

Twelve minutes, screen share. Bring the account that gives you the most grief.