ProofServ

How it works

From signed contract to the morning after.

Six steps, and you do the first one once per property. After that, the nights run, the record builds itself, and everyone who needs an answer can find it.

Running it yourself? Running a crew?

  1. Set upOffice · once per property

    Describe the property the way the contract does.

    Add the property, its buildings and its locations, then say which kinds of location are owed on which nights, inside which service window. Write the notes a worker needs before the first door.

    • Add many locations by range, like 101–112, up to 500 at once.
    • Your exception reasons, and the photo or note each one requires.
    • Service rules: one-step building sweeps, an optional geofence for them, and closing photos.

  2. ScheduleOffice · weekly, mostly automatic

    Nights appear on their own.

    Choose who covers each property and its service nights are created a week ahead. Call a night off, add an extra one, or change who's on it. The week view shows which nights still need someone.

    • This week needs you: every unassigned night, in one list.
    • Called off and missed nights are recorded with their reasons.

  3. ServeWorker app · every night

    Arrive prepared, start on the record.

    The worker clocks in, reads the property's notes and tonight's attention items, and photographs the site on arrival. Location is captured when the phone has a fix, and never blocks the start.

    • Readable offline, before the worker even arrives.
    • Most severe first: a critical item before a warning.

  4. CaptureWorker app · as the work happens

    Evidence as a side effect of the work.

    Tap to collect. Hold for an exception, with the photo or note its reason requires. Callbacks arrive on the phone. Before departure, every location owed needs an outcome, then closing photos on the way out.

    • No signal needed. Saved on the phone, sent when it can be.
    • Observations for things nobody owns: the broken gate, the leaking chute.

  5. ReviewOffice · the morning after

    Start the day with the answer.

    Last night opens sorted by what needs you: follow-ups first, then anything worth a look, then the quiet properties, kept short. Open any property for its full service record, and review the night's hours.

    • Needs follow-up: a callback left without a resolution.
    • Shifts that look off are flagged for review.

  6. ShareProperty and resident portals

    Let the record do the explaining.

    Turn on the property portal and share a property with its manager. They read their own service, night by night. Residents see whether tonight's service is underway or finished, and how to set out.

    • Scoped by design. No worker names, no office notes, no other properties.
    • Observations are shared only when you choose, after you review the words.

Two ways to start

Start where you are. Grow from there.

One property or fifty, every property starts the same way: set it up once in the office, activate it, and the nights run. What changes as you grow is who’s on the route.

Running it yourself

You're the owner, and you're on the route.

Set the property up once in the office, then work it from your phone. Your record holds up the same way a fifty-property company’s does.

  1. Create your company and add the property in ProofServ Office.
  2. Load its locations and its service agreement.
  3. Activate it, and assign its nights to yourself.
  4. Work Tonight in the worker app. Every location owed gets an outcome.

Running a crew

You've got properties, people, and promises to keep.

Load each property's locations once, and every night is counted against what's owed. Nobody departs with a location still pending.

  1. Set up properties, locations and the service agreement in the office, then activate them.
  2. Invite your workers. They sign in to the app on their own phones.
  3. Choose who covers each property. The nights schedule themselves.
  4. Open last night each morning, and share the record with your properties.

One property or fifty. The same record, the whole way.

See how pricing scales →

Walk through a night in ProofServ.

Twenty minutes: what your team sees in the field, and what you see the morning after.

Get started Book a demo