For providers: proving you came and did the work
Make the proof part of the job, not an afterthought. At arrival, photograph the space as you find it, with something that identifies the place in frame: a house number, a doorway, a recognisable feature. Do the work, then photograph the result at departure from the same angles. For a cleaner that is the before and after of each room; for a pet sitter, the animal and the home at each visit; for a gardener, the hedge or lawn done. The arrival photo matters as much as the after, because it is the only thing that shows the state you walked into if the client later claims you caused damage.
The weak point is always the date. A photo on your camera roll can be called old, staged, or from another client's place, and a screenshot sent by message has lost the metadata that would have timed it. That is why a timestamp on its own is not enough: it proves presence, not the work, and it can be changed. Attach the photos to the job record the same day rather than leaving them in a chat thread, so the visit carries its own proof instead of your word against the client's.
For clients: checking the provider really came
If you are paying for visits you do not witness, you are right to want a check, and a good provider will welcome it. Ask for an arrival and departure record of each visit: a photo of the work with a trustworthy date, not a tick on an app. A standalone photo can be questioned as old or from the wrong place, but a photo tied to a verifiable time and position is much harder to dispute, in either direction. It protects you from paying for a visit that did not happen, and it protects an honest provider from your doubt.
Be fair about what the proof shows. A sealed photo tells you the work was captured at a given time and place; it does not read the quality of the clean or whether the dog enjoyed the walk. Agree up front on what each visit should produce, so a missed visit is obvious and a real one is undeniable. The goal is not to catch anyone, it is to make the visit speak for itself so neither side argues about it at invoice time.
Why a phone timestamp is not enough
The instinct is to screenshot the clock or rely on the photo's metadata, but both are fragile. A phone's date and time can be set by hand, so a timestamp burned on by the device proves little to a sceptical client. And metadata rarely survives the trip: every pass through a messaging app recompresses the image and strips the embedded date, time and location, so by the time the photo reaches the client it carries nothing verifiable.
A timestamp also answers the wrong question. At best it shows someone was present, not that the work was done, which is exactly the gap a disputed invoice turns on. What closes it is a record that binds the photo of the work to a date and place that neither side set and that cannot be edited afterwards, so the visit proves itself.
Which photos, at which moment
The same record serves a clean, a pet-sitting visit and a small repair. What changes is only the subject; what makes the proof weak never changes.
| Moment | What to capture | What makes the proof contestable |
|---|---|---|
| At arrival | The space as you find it, with the place identifiable in frame: house number, doorway, a recognisable feature | A plain photo can be called old or from another site; nothing ties it to this visit |
| During the visit | The work being done: the room, the pet, the repair, enough to show it actually happened | A single mid-visit photo proves a moment, not the full job |
| At departure | The result from the same angles as arrival, so before and after compare one to one | Taken later or edited, an after photo loses its value if the date cannot be shown |
| Sending to the client | The sealed record attached to the job the same day, not dropped in a chat thread | A photo passed through a messaging app is recompressed and stripped of its metadata |
Sealing the visit instead of defending it
Every weakness above is the same one: an ordinary photo does not prove its date, its place, or that it has not been touched, and a timestamp only shows presence. That is the gap Danaya closes at the moment of capture. The provider opens a capture link, the photo is taken live in the browser camera, nothing can come from the gallery, and the file is sealed with a cryptographic fingerprint, the GPS position and a server timestamp. Anyone can check it on a public page, including the client reading the invoice.
In practice it is one sealed record per visit, arrival and departure, that lands in a report you can send with the bill. Because field work runs at volume, this is also an API use case: create a capture link per visit from your own scheduling system and collect the sealed report back. The honest limits: a sealed photo makes the visit verifiable, it does not grade the work or decide a dispute, which stays between the parties. The GPS position comes from the capturing device, so read it as a strong indication of place rather than a proof of the exact address, and Danaya is not an attendance tracker, a warranty or an insurance.