Daily Operations
The routine operating manual for staff who use Recruitment after setup is complete.
Main Workspaces
Recruitment
Use this sidebar area for the module workflow associated with Recruitment.
Job Postings
Use this sidebar area for the module workflow associated with Job Postings.
Job Positions
Use this sidebar area for the module workflow associated with Job Positions.
Job Portal
Use this sidebar area for the module workflow associated with Job Portal.
Standard Operating Procedure
- Open the module workspace from the sidebar or the route your team normally uses.
- Search or filter before creating a new record so duplicate records are not introduced.
- Open the create form, fill required fields, attach supporting information when the workflow expects evidence, then save.
- Review the saved record from the detail or list view and confirm ownership, dates, status, and linked records.
- Move the record through the next workflow step only when the supporting data is complete.
- Use reports, dashboards, or export screens for review rather than manually editing calculated totals.
- Check scheduled job results for records that rely on SLA, expiry, notification, or synchronization processing.
Record Handling Rules
Create carefully
Use one source document or one real-world event per record. Avoid bundling unrelated items into a single record just to save time.
Review before action
Check status, ownership, dates, amounts, attachments, and related records before approving, publishing, posting, or closing.
Use update actions intentionally
If the module has separate approve, issue, post, sync, export, or close actions, use those instead of editing database-style fields directly.
Keep auditability
Prefer correcting records with comments, revisions, status changes, or replacement files so the business history remains understandable.
Daily Quality Review
- New records have clear owners, dates, statuses, and related records.
- Required documents, comments, attachments, or references are added before approval or closing.
- List filters and report date ranges match the period being reviewed.
- Users can only see and act on records appropriate to their role.
- Public or portal pages show only approved information and do not expose private records.
- Scheduled jobs have run recently when the workflow depends on automation.
- API data matches the intended tenant, permissions, filters, and response schema.
Publishing a Posting for Google for Jobs
Job postings published on the public portal can now appear in Google's job search results. Follow these steps when opening a posting so it qualifies.
- On the job posting form, fill the new fields: Employment Type (Full-time, Part-time, Contractor, Temporary, Internship, Volunteer, Per diem, or Other), Work Arrangement (On-site, Hybrid, or Remote — choosing Remote tells Google the job is fully remote), and Location (City, Region/Province, and the two-letter Country code, default PH).
- Set the Application Deadline. Applications close at the end of that day. Leave it blank and the system fills it in automatically from the default validity window (30 days unless your administrator changed it).
- Enter the salary and tick "Show salary" if you want pay published. Salary appears in Google's job markup only when it is visible on the page, and postings with a published salary attract significantly more applications.
- Set the Status to Open and save. The status choices are now Draft, Open, and Closed.
- From the Job Postings list, open the row menu and choose "SEO & Google for Jobs". Read the eligibility score on the right: 90 or above is Good, 70 or above Needs review, and anything lower is Poor.
- Work through the checklist under the score and fix critical items first — for example a missing deadline, no location on a non-remote job, a description that is too short, or no employment type.
- Optionally polish the search title (60-character counter), meta description (160-character counter), and social share details, watching the live previews of the Google search result, the social share card, and the Google-for-Jobs card update as you edit.
- Use the "Rich Results Test" toolbar button to verify the posting in Google's official tester, and "Go to public page" to see exactly what applicants see.
No SEO input required
Everything works with zero SEO input — the search title, description, and share image auto-generate from the posting itself. The editor is optional polish, not a prerequisite for appearing in search.
Job facts live on the job form
The "From the Job Posting" panel in the editor (status, deadline, location, employment type, salary) is read-only. Edit those facts on the job posting form itself so the public page and Google's markup can never disagree. The score refreshes automatically whenever the job is saved, the SEO settings are saved, or the posting closes or expires — the score chip on the list is never stale.
Fair-wording check applies
The anti-discrimination job-ad checker also reviews SEO titles, descriptions, and keywords. Restricted phrasings are blocked with no override — reword the text instead.
Access
The SEO editor requires the "Manage SEO" permission (administrators always have access). If the row-menu option is missing, ask your administrator.
Reading Posting Analytics
Open the row menu on Job Postings and choose "Posting Analytics" to see how a posting performs. The screen requires the "View Analytics" permission.
KPI tiles
Total Views counts every page view; Unique Views counts distinct visitors (a visitor's first-ever view of that job). Apply Starts counts people who began the application form; Applications counts completed submissions. View→Apply % shows how many viewers start applying, and Apply Completion % shows how many starters finish.
Funnel and Fill Progress
The funnel tracks Views → Apply Starts → Applications → Hired, where Hired is the all-time pipeline count. Fill Progress compares hires against the posting's number of openings.
Views by source
Shows where viewers came from: Direct link, Internal job listing, Recommended jobs, Company page, Saved jobs, Campaign (UTM-tagged links), Search engines, Social media, and Other websites.
Devices, referrers, and trend
Device and top-referrer panels show what visitors browse with and which sites send them. The daily trend chart plots Views and Applications over time; use the Last 7 / 30 / 90 days presets to change the window. All-time counters sit alongside for the posting's full history.
Timing notes
Daily figures use the company time zone, and today is always a partial day. View and apply events record instantly, but the per-day charts refresh hourly, so the newest hour can lag slightly.
How counting works (honest numbers)
No cookies are set and no user identity is ever attached to public views. Repeat views by the same visitor within 30 minutes count once, and browsers sending "Do Not Track" are not counted at all. Google, Bing, and AI crawlers are logged separately and never counted as views. Raw view events are deleted after 90 days — only anonymous daily totals are kept.
The Job Postings table also gained a "Views" column (all-time views, with the unique count in the tooltip) and an "SEO" column showing the color-coded eligibility score, which clicks through to the SEO editor.
Closing, Expiry, and Reopening
What closing does
When a posting is Closed, the public page stays reachable for anyone holding the link but shows "This position is no longer accepting applications" with the Apply button disabled. Search engines are told the page is gone, and the posting drops out of the public job listing and the jobs sitemap.
Automatic expiry
A nightly sweep closes open postings whose application deadline has passed, recording the reason as "expired". Individual postings can opt out of auto-close when a role should stay open past its deadline. Publish, close, and auto-expiry events are all recorded in the system activity log.
Reopening
Reopening a posting restores everything: the Apply button returns, search engines are told the page is live again, and the posting reappears in the public listing and sitemap.
Deadline hygiene
Check deadlines during the daily review — a deadline in the past appears on the eligibility checklist as a critical item because the posting will close on the next nightly sweep.