WorkMonitor for outsourced delivery
End the monthly argument about hours
The people doing the work and the people paying for it sit in different companies, so every close ends in two reports and a phone call. Give both sides one record neither takes on trust.
Free for two seats, no card.
Outsourcing
What changes across the contract boundary
Pick a line and the page it happens on opens on the right.
- AKProof LedgerClient-grade proof.Search or ask…
- Proof Ledger
- Outcomes
- Certificates
- Audit log
- Data access
- Disputes
- Data egress
- Export
- What We See
- Controls
Northlight StudioProof LedgerDeliverables, and the hours behind themATTRIBUTED HOURS · SEPTEMBER1,284linked to shipped workDELIVERABLES38merged or donePROPOSED LINKS5awaiting a personDELIVERABLEPERSONHOURSTIME LINK- PR #482Checkout redesign — final buildCarried into cert_2f7b0cAKAria K.12h 40mConfirmed
- DES-77Brand system v3 handoffSDSara D.15h 30mConfirmed
- NLS-214Invoice export endpointJMJon M.8h 05mConfirmed
- PR #476Reporting dashboard — data layerLMLena M.9h 50mConfirmed
- NLS-231Onboarding flow copy passwhy:ticket_key:NLS-231assignee_matchRPRavi P.4h 15mProposed
- WEB-119Mobile nav accessibility fixesTVTomas V.6h 30mProposed
Every link arrives proposed, with its receipts. A person confirms it before it counts as proof.6 of 38 shown
- Proof Ledger
- Outcomes
- Certificates
- Audit log
- Data access
- Disputes
- Data egress
- Export
- What We See
- Controls
- PR #482Checkout redesign — final buildCarried into cert_2f7b0cAKAria K.12h 40mConfirmed
- DES-77Brand system v3 handoffSDSara D.15h 30mConfirmed
- NLS-214Invoice export endpointJMJon M.8h 05mConfirmed
- PR #476Reporting dashboard — data layerLMLena M.9h 50mConfirmed
- NLS-231Onboarding flow copy passwhy:ticket_key:NLS-231assignee_matchRPRavi P.4h 15mProposed
- WEB-119Mobile nav accessibility fixesTVTomas V.6h 30mProposed
Rollout
Running one record across a contract boundary
- 1
Separate the clients at the database
Composite foreign keys make a cross-tenant row an error rather than a code-review question, and per-client scoping sits on top of that.
- 2
Run approval across the boundary
Multi-stage approval with separation of duties, so provider-side and client-side sign-off are distinct steps rather than one person’s judgement.
- 3
Hand over proof, not a report
A finalized invoice seeds a certificate the client verifies on a public page, with selective disclosure over a zero-screenshot record.
- 4
Put your brand on the client view
White-label branding, custom domains and embeddable widgets, so the client sees your service rather than a third-party portal.
Two versions of the truth vs. one neither side has to trust
workmonitor.vsClient–provider reporting today
The monthly reconciliation
With WorkMonitor
One record, verified independently by both, so there is nothing to reconcile.
Client–provider reporting today
Your report against theirs, and a call to decide whose is right.
Client separation
With WorkMonitor
Composite foreign keys in the schema: a cross-client row cannot be written, let alone read.
Client–provider reporting today
A policy document, and a promise that the schema keeps clients apart.
Proving delivery
With WorkMonitor
Selective disclosure over work edges: the fields you choose, and no pixels.
Client–provider reporting today
Screenshots, which expose the client’s own data to prove you worked on it.
Approval
With WorkMonitor
A multi-stage chain that spans both sides, with separation of duties enforced.
Client–provider reporting today
Ends at the boundary; the client signs a PDF weeks later.
Multi-country delivery
With WorkMonitor
Capture policy per region, consent by version, and guidance for 32 jurisdictions.
Client–provider reporting today
A single policy written in one country and applied in six.
Whose brand
With WorkMonitor
Yours: white-label, custom domain, embeddable badge.
Client–provider reporting today
The vendor’s portal, which you have to explain.
- Proof Ledger
- Outcomes
- Certificates
- Audit log
- Data access
- Disputes
- Data egress
- Export
- What We See
- Controls
- PR #482Checkout redesign — final buildCarried into cert_2f7b0cAKAria K.12h 40mConfirmed
- DES-77Brand system v3 handoffSDSara D.15h 30mConfirmed
- NLS-214Invoice export endpointJMJon M.8h 05mConfirmed
- PR #476Reporting dashboard — data layerLMLena M.9h 50mConfirmed
- NLS-231Onboarding flow copy passwhy:ticket_key:NLS-231assignee_matchRPRavi P.4h 15mProposed
- WEB-119Mobile nav accessibility fixesTVTomas V.6h 30mProposed
What an outsourcing provider gets to work with
- WORM-anchored certificates (from a finalized invoice)
- Public no-login verifier
- Selective disclosure
Ask AI
Ask AI about delivered hours
Answers built from tracked activity, the approval chain and per-client mapping.
Pick a question above and WorkMonitor AI will answer from your team's real numbers.
- Today
- Insights
- Activity board
- Live screens
- Team
- Agents
- Integrity
- App categories
- Reports & digests
- Capacity
- AKAria K.Figma92Active
- JMJon M.Terminal78Active
- SDSara D.Slack61Active
- RPRavi P.Notion34Idle 11m
- LMLena M.Teams55In a call
- TVTomas V.Off shift0Off
The status meeting, already written
Status is normally assembled by asking. Here it is already: hours, activity, attendance and risk on one board, for one person or the whole company. Set the thresholds once and it tells you who needs you.
Jobs to be done
The jobs an outsourcing provider runs here
- Prove work with certificatesA finalized invoice mints a signed certificate the client checks for themselves. Selective disclosure proves the work without handing over the work.
- Bill defendable client hoursBudgets that burn down while you can still move somebody, rate-card billing off captured hours, and an invoice the client verifies without asking you for anything.
- Capture screenshots on your termsA randomised cadence, exclusions applied on the device, retention that expires, and the consent record and appeal route that keep the programme standing.
- Monitor legally & stay compliantVersioned consent, a capture scope that cannot quietly widen, retention and DSAR handling, and written guidance for 32 jurisdictions before you roll out in one.
Where you operate
Delivery-centre monitoring law, by country
- PhilippinesTransparency, legitimate purpose and proportionality: the three-part NPC test.
- IndiaDPDP gives employment a legitimate use, but automated monitoring is argued to sit outside it.
- PolandThe Labour Code lists the permitted purposes, and productivity is not one of them.
- MexicoThe privacy notice is the central legal instrument, and it must be specific.
- BrazilThe ANPD is sceptical of legitimate interest in employment. Transparency carries the weight.
- South AfricaPOPIA plus RICA, and RICA makes unlawful interception a criminal offence.
Straight answers
The questions we would ask in your position
Every answer here is the one you would get on a call. Open as many as you like; they stay open, so two can be held side by side.
Whoever holds the organisation the records belong to. Isolation is enforced by the schema rather than by policy, so an arrangement where you run the tenancy and issue certificates outward is genuinely different from one where the client runs it, worth settling in the contract before rollout, not after.
Only what you expose. A certificate attests to a period of work without exposing screens or individuals, and roles scope to a node in the org tree. What a client-facing report contains is a decision rather than a default.
It is the normal case. Activity is read per local day rather than in one time zone, and consent, notice and retention apply per jurisdiction with a record of which version each person accepted, which matters when one centre sits under a very different regime from another.
Integrity signals flag periodic input, jiggler patterns and impossible location jumps with the underlying evidence rather than as a score, randomised screenshot cadence removes the fixed interval people learn to work around, and separation of duties keeps the person who worked the hours out of the approval. None of these is a lie detector; together they make inflation visible.
Nearby
Teams with the same problem, from another angle
Take these with you
The software is the easy part of a rollout
Here is what we would send a manager doing one for the first time: how to read a productivity number, what to say to a remote team before anything is installed, and a policy you can adopt as written.
Point it at one team for a week.
Create the account, put the agent on a handful of desks, and leave it alone. On Friday you read the week instead of reconstructing it: hours against their projects, focus and idle per person, and the timesheets already filled in.
Free for two seats. No card, and no sales call to sit through.