Short answer

Add the contractor as a user on your account (a Field Operative is the usual role, or a shared company login where a firm sends different people), then assign the jobs to them. They complete each job on the mobile app with a photo, so instead of waiting for an email to say "done", you get a dated, photo-backed record against the asset. Even if a contractor will never open the app, adding them as a user and assigning jobs to them by name still gives you a record of who was given the work. The most reliable way to make it stick is to write "log completed work in Civic.ly" into the contract or tender so it is an expectation from day one.

Detail

Contractors (grounds and grass cutters, bin-emptying firms, play-inspection contractors) are outside your own team, so the goal is oversight and evidence, not micromanagement.

1. Add them as a user. A Field Operative role lets them see and complete the tasks assigned to them without changing your wider setup. For a firm that sends whoever is available, a single shared company login works (the same pattern councils use for a shared depot device). The account represents the company, not one named person.

2. Assign the work to them. Assign the jobs (or a routine's sub-tasks) to the contractor's account so the work lands on their task list. If you don't own the asset (for example verges or car parks owned by the principal authority that you maintain anyway), you can still model it and assign jobs to it. That builds a defensible record of the work you or your contractor did.

3. Require proof at completion. When the contractor completes a job on the app they can attach a photo and, where a checklist is attached, record a condition (for example a grass-height or bin-fullness reading). That timestamp-plus-photo is the evidence trail. It replaces chasing an email and answers "did they actually do it, and when?"

4. Make it contractual. The single biggest predictor of a contractor sticking with it is putting it in the tender or contract: "assigned work is logged and signed off in Civic.ly." Set that expectation before the contract starts rather than asking a firm to change habits mid-term.

If the contractor will not use the app

You can still add them as a user and assign jobs to them by name. The job then shows who was given the work, which is a better record than assigning it to yourself. Your own team can open the job and update its status when the work is confirmed, for example after a site check or when the contractor reports back by phone or email. If you would rather keep the contractor out of Civic.ly altogether, assign the job to yourself as the record and reminder, and sign it off after a physical check or a photo.

Getting quotes from several contractors

Create one quote job per contractor, each assigned to that contractor, for example "Get quote: bench repair (Contractor A)", "Get quote: bench repair (Contractor B)" and so on. Do not assign several contractors to the same job. Separate jobs give you a clean record of who was asked, what each quoted, and who then did the work. Put the supplier and figure in the description, and the cost in the Cost (£) field on the job that does the work. See Can I record what a job cost, how long it took, and attach a quote?.

What the contractor receives

When a one-off job is created and assigned to a contractor, they get an email from Civic.ly telling them the task has been assigned, even if they never log in. Routine and recurring work does not send these emails. The email may look unexpected to someone who has not used Civic.ly before, so tell the contractor it is coming and what it is. Each user can switch their own assignment emails off in Edit profile, under Notifications. See account-settings/task-assignment-emails.

Watch-outs

  • A shared login attributes every completion to that one account. That is fine for "the company did it", but you won't see which individual did which job. Use per-person accounts if that matters.
  • Give them only what they need. A Field Operative should see their assigned work, not your whole account. Check the role scope before handing over a login.
  • You still own the schedule. The contractor completes tasks. You (or a supervisor) set up the routine or jobs and assign them. A contractor account is not an admin.
  • A contractor who is a user and never logs in will not complete anything. Jobs assigned to them stay open until someone on your team updates them, so decide up front who does that.
  • Some third-party assets aren't yours to fix. Log those as jobs or defects with the responsible company in the title so the record is clear when you report it back to them.