LocalForces documentation

LocalForces follows the way an agency actually works. A client sends you a request (a role to fill). You position candidates from your talent pool on that request and move them through the client’s pipeline until one is placed. The placement records the engagement and the fee you earn.

• Clients: the companies you recruit for, each with its own pipeline and terms.
• Requests: the roles a client asked you to fill.
• Talent pool: your agency’s private candidates. Other agencies never see them.
• Positionings: a candidate on a request, moving through the pipeline.
• Placements: the hire, with rates, salary and your fee.

1. 1Sign up at /signup with your agency name. Your workspace gets its own address (your-agency.localforces.com) and a 14-day trial.
2. 2Open Team and invite your recruiters and account managers; they get an email to set their password.
3. 3Add your first client in the admin panel under Clients, with its contacts and fee terms.
4. 4Create a request for that client, or paste the client’s brief and let the AI fill it in.
5. 5Add candidates to your pool (upload a CV, the AI reads it) and position them on the request.

Account managers can only edit requests while they are drafts. A recruiter completes and validates them.

A client holds its contacts (hiring managers), country, currency and terms: fee percentage for permanent hires, guarantee period and payment terms. These terms prefill the placement form later.

By default every client uses the standard pipeline, grouped in three phases: qualification, preparation and closing. Open Pipeline, pick the client and choose Customise columns to rename, reorder, add or remove columns, mark the ones where a candidate can be rejected, or copy the pipeline of another client.

A request has a client and job title, the number of profiles, a target start date, the profile sought (mission type, seniority, minimum years, key skills) and the terms (work mode, location, days, currency, daily rate range, contract type).

1. 1Save it as a draft while details are missing.
2. 2Validate it once it has a client, title, start date and key skills.
3. 3Position candidates and follow progress in the pipeline.
4. 4It becomes Filled automatically when enough candidates are placed.

Saved views help you work through the list: Active, No positioning, Past due, Drafts, Filled / cancelled and Archived.

On the candidate form, “Read the CV with AI” extracts the text of a PDF or Word CV and asks the model for structured data: name, contact details, years of experience, seniority, skills and domains. Only valid values are kept, and you check them before saving.

On a draft request, “Read the brief with AI” does the same for a pasted text or an uploaded brief: job title, client, skills, seniority, dates, rates and a suggested mission type.

Candidates are grouped by category (employees, freelancers, suppliers, referrals). Each profile has the CV, skills, seniority, domains, availability, currency and buy-rate range. Duplicates are detected by email or by name.

Candidates who register on your website land in the pool with source “Website” and their consent date.

Pick a client to see its own columns, or All clients to see every positioning grouped by phase. Drag a card to move it. Open a card to see the stepper, add client feedback and a follow-up date, log activity or reject the candidate with a reason.

The placement form is prefilled from the request and the client: start date, engagement, selling and buying rates, annual salary, fee model, guarantee days. It shows the fee before you confirm.

Confirming places the candidate, optionally closes their other positionings and marks the request filled when enough people are placed. Follow each placement from pending to confirmed, invoiced and paid. Cancelling a placement puts the candidate back in the pool.

On a validated request, use the globe button to publish it: choose the country, write the public description, and decide whether to show the client name and the daily rate. Closed or archived requests disappear from the board automatically.

Candidates register at /join or apply to a job. Every submission is checked (hidden honeypot field, rate limit, reCAPTCHA) and stored in Applications. A new candidate is created in your pool and, when applying, positioned in the first column of that job’s pipeline. Existing profiles are never overwritten.

1. 1A company fills in the “Hire talent” form: who they are, the role, the start date, budget and a description or a brief file.
2. 2LocalForces matches the company to an existing client (same website or name) or creates the client with that contact.
3. 3A draft request is created for that client, with the contact and budget in the account manager note and the brief file attached.
4. 4If AI is enabled, it fills the key skills, seniority, work mode and rates from the description.
5. 5Your agency contact email gets a notification, and the company a confirmation.

When publishing a job you can tick channels: your Facebook page, your LinkedIn company page, or a signed webhook for Zapier, Make or Buffer. The post is written in your agency’s language. Each attempt is logged.

The Stats page shows visitors, page views, time on site, countries, referrers, devices and bot traffic. Tracking is first-party and cookie-less: no IP addresses and no cookies are stored.

• Candidate profiles are kept for a retention period (24 months by default).
• Before it ends, the candidate gets an email to renew their consent with one click.
• Without an answer, the profile is deleted or anonymised, as you configure.
• Deleting a candidate deletes their positionings too.
• The audit log keeps only technical references, never candidate personal data.

Every agency gets your-agency.localforces.com. On Pro, add a custom domain (for example jobs.your-agency.com) with a CNAME record pointing to LocalForces, then upload your logo and pick your colours in the agency settings.

Billing is handled with Stripe: change plan, update your card or download invoices from the billing page.

Use the contact form on the Hire talent page or write to the address in the privacy notice. Enterprise customers can run LocalForces on their own servers, for example in Germany, with nightly backups.