—
Loading…Overview
Your work and timesheet status for the selected day.
MY PERFORMANCE
Efficiency & record completeness
Efficiency = estimate ÷ actual time for your Done tasks, weighted by hours. Record completeness = hours recorded ÷ scheduled capacity. These are numbers only, not a performance grade.
—
Loading…—
Loading…CURRENTLY WORKING ON
Your WIP
YOUR WORK
Assigned tasks
PRIVACY
How to interpret these records
Timesheet completeness describes the coverage of your records. Utilization is shown as a formula, not a score. Presence, calendar acceptance, and commit activity are not proof of time worked.
MY RECORDS · DRAFT
Timesheet
Review your time, make reasoned draft corrections, then submit for approval.
PRIVATE MEMBER REVIEW
Work evidence check
This optional check is for your review only and does not change your entries, block submission, or send email. No matching commit or PR does not prove no work; compare the information with your own recollection and confirm or correct it.
Calendar shows busy intervals only. Presence is current-only context and is never correlated to past work. This screen does not claim that any source or AI verified what work happened.
Run a check to review information for this date.
Observed events
Possible gaps
Limitations
TIME ENTRIES
Recorded segments
TIME ENTRIES
Recorded segments
Swipe or scroll horizontally to see all columns. Efficiency = task estimate ÷ actual time logged for that task on this date.
| Time | Task / category | Duration | Source | Correction state | Efficiency | Action |
|---|
MANUAL ENTRY
Add time segment
SUBMISSION
Submit for approval
Submitted and approved records are locked. After approval, request an adjustment; the original record remains in the audit history.
Status DraftTotal 0m
INTERNAL ISSUE TRACKER
Work board
Backlog → WIP → Ready for Testing → Done. Rework requires a reason.
Jira-style workflow: work items, estimates, assignees, target dates, branch references, comments, labels, transitions, and audit history are managed here.
ACCOUNT SETTINGS
My profile
Keep your work department up to date.
LEAD & ADMIN
Projects
Create and maintain projects for your delivery teams. Customer records remain administrator-managed.
CUSTOMERS
Create customer
PROJECTS
Create project
CUSTOMERS
Customer directory
| Code | Customer | Status | Actions |
|---|
PROJECT DIRECTORY
Projects
| Project key | Project | Customer | Billability | Status | Actions |
|---|
MANAGER REVIEW · SCOPED TO YOUR REPORTS
Team review
Capacity and records support planning; they are not employee performance grades. Finish estimates use the task's WIP start and Jira estimate and are planning hints only.
TEAM CAPACITY
Members and current status
Swipe or scroll horizontally to see all columns.
| Member | Department | Efficiency | Hours spent | Record completeness | Timesheet | Current WIP task | Estimated finish | Next backlog task |
|---|
APPROVAL QUEUE
Submitted timesheets
CORRECTIONS
Pending adjustment requests
TIME OFF
Pending leave requests
ADMINISTRATOR
Admin & schedules
Accounts, schedules, and organization settings grouped by task.
INVITE-ONLY ACCESS
Accounts
Create a member or lead through a one-time invitation. Account information, leave policy, and schedule are grouped in the setup dialog.
WORK SCHEDULE
Member schedule
MICROSOFT 365 · MICROSOFT GRAPH
Email Settings
Email is sent by the server through Microsoft Graph. This browser never calls Graph and never stores credentials.
Subdomain and Microsoft Entra setup
DNS / subdomain: Configure the new sending subdomain and its SPF, DKIM, and DMARC records with your DNS provider. DNS is shown as verified only when the server reports verification; this page does not verify DNS automatically.
DNS verification has not been reported by the server.
Entra consent: An administrator must grant consent to the Entra app’s required Microsoft Graph application permissions before sending can work.
ACCOUNTS
Team members
| Name | Role | Manager | Department | Timezone | Status | Actions |
|---|
ADMINISTRATOR
AI Settings
One Generic provider and model is shared by issue suggestions, report summaries, and completion reviews. The API key is encrypted server-side and never returned to this page. Users cannot switch provider or model.
Only administrators can configure the shared Generic endpoint and model.
LEAVE POLICY
Carry-forward & handover controls
CONNECTORS
Integrations
Connector status loads from the server configuration.
BITBUCKET CLOUD SETUP
Configure the read-only connector on the VPS
There is no browser OAuth/connect button or webhook sync. This connector reads allowlisted commit and pull-request metadata only when a member manually requests an evidence preview for their own timesheet.
- Create a Bitbucket API token with repository read access only (for example,
read:repository:bitbucket). Keep it in the protected VPS.env; never enter it in PulseOps or send it in chat. - In the VPS
.env, setBITBUCKET_READ_TOKEN,EVIDENCE_BITBUCKET_REPOSITORIES, andEVIDENCE_BITBUCKET_USERS. The repository mapping can contain multiple repos per project. User mapping format:{"PULSEOPS_USER_UUID":"bitbucket_username"}. - Enable
EVIDENCE_CHECK_ENABLED=trueonly after privacy approval, member notice, and an approved positiveEVIDENCE_RETENTION_DAYS; setEVIDENCE_PRIVACY_NOTICE_ACKNOWLEDGED=trueonly when that notice is in place. - Rebuild the API and UI with
docker compose up -d --build api pulseops-ui. Then a mapped member can request the preview from their own timesheet.
Configured status does not prove the token works; the first successful preview verifies live access. Empty results do not prove that no work occurred.
ADMIN TOOL
Discover and map repositories
The server uses its stored read-only token to list repositories in one workspace. Select only the repos you approve and assign each to a PulseOps project; no repo is linked automatically.
Repository names are fetched only after you click Load repositories.
The generated line contains repo/workspace identifiers only. Add it to the protected VPS .env; user-to-Bitbucket mappings and privacy/retention approval are configured separately.
Data handling
- Calendar and commit activity may create suggestions only; neither proves work duration.
- Graph presence is disabled by default and is never used as a performance grade.
- Credentials remain server-side. Admin status responses never return secrets.
- Country-specific notice, purpose, access, and retention must be approved before collection is enabled.
ADMINISTRATOR
Audit log
Task, timesheet, adjustment, and schedule changes.
LEAD & ADMIN
Team reports
Review team timesheets, capacity, assigned leads, and issue counts for a date range.
Choose a date range and generate a report. The current week is selected by default.
Manual reminders are available only on a one-day report and only for eligible direct reports whose status is missing or draft. Each reminder is an explicit, neutral server-side send after confirmation; there is no automatic email scheduling or AI-generated outbound content.
Timesheet counts show how many days fall in each status for the selected range. Recorded time and scheduled capacity are range totals. Issue counts are each member’s current assigned issues.
HUMAN-REVIEWED PREVIEW
AI report summary
Loading the administrator-configured workspace AI model…
Preview only. Review cited evidence and data gaps; no people are ranked or scored, and no causes are inferred.
TEAM STATUS
Members and work summary
Swipe or scroll horizontally to see all columns.
| Member | Role | Assigned lead | Department | Active task | Draft | Submitted | Approved | Returned | Missing | Recorded | Capacity | Backlog | WIP | Ready for Testing | Done | Billable minutes | Non-billable minutes | Unclassified minutes | Manual reminder |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Choose dates and generate a report. | |||||||||||||||||||
TEAM AVAILABILITY · PLANNING VIEW
Leave Planner
Approved and pending leave at a glance. Dates and leave types are shown as authorized by the server.
MONTH VIEW
Team leave calendar
Balances are shown only when the server authorizes access. Members see their own balance; leads see their own and direct reports’ balances.
MY REQUESTS
Your leave requests
MY REQUESTS
Your leave requests
COVER REQUESTS
Cover acceptance & handover
Offers assigned to you appear here and in Notifications. Accept or reject an offer. Accepted cover can complete handover within the configured policy window.
PULSEOPS GUIDE
Help
A practical guide to planning work, recording time, and reviewing your records.
Getting Started
Use the navigation to open your overview, timesheet, and work board. Work in PulseOps is recorded by you; review suggestions and entries before submitting them.
Work Board and Issues
Issues move from Backlog to WIP, then to Ready for Testing. WIP may return to Backlog or move to Ready for Testing; Ready for Testing can return to WIP for rework or move to Done. Returning work to Backlog or WIP requires a reason, retained in issue Details under Activity and change history. Leads and administrators can edit issue details. Members do not get full issue editing.
Delegation
On a task assigned to you, choose Delegate to transfer it to another active member in your team. Select a teammate and enter a reason of at least 8 characters. Assignment history and its reason remain visible in issue Details. Leads and administrators manage assignments through their issue-edit permissions.
Comments
Open Comments to read or add a note. Comments show their author, posting time, and PulseOps internal source. They are visible to the workspace team. Use Close comments to collapse the panel.
Timer and Time Entries
When the assigned task owner moves a task into WIP, the workflow automatically starts their timer. Leaving WIP for Ready for Testing or Backlog stops that timer and saves a draft entry. Do not also start or stop it manually. Only the assigned task owner triggers this automation; a lead or administrator changing another person's status must not change that person's timer. If you already have an active timer, the transition may be rejected; resolve the current timer and refresh the task. A stopped timer creates a draft entry that you can review. Manual entries are also available.
Project Billability
Each new project is explicitly marked Billable or Non-Billable. Older projects with no classification are shown as Unclassified; an administrator can choose a classification later. Unclassified time is reported separately and is not assumed to be billable.
Department
Set your Department in My profile. The available departments are Project Manager, UI/UX Designer, Business Analyst, Developer, Analytics, QA, and Content Engineer. Administrators can set a department when inviting or editing an account.
Timesheets, Submissions, and Corrections
Review the entries for each work date, then submit the day for approval. Leads review timesheet approvals with the capacity, recorded time, unallocated time, category breakdown, and each entry's time, task, category, duration, note, and source. Approve or return the sheet with a note; a return reason is required. Submitted or approved entries are locked; use an available correction or adjustment action and provide a reason. The original approved record remains in the review history.
Team Reports
Leads and administrators can filter reports by date range. Report rows are grouped by lead, with the lead's own row followed by direct members. Reports include Department, current active timer task, and Billable, Non-billable, and Unclassified minute totals. CSV export flattens the groups and safely quotes spreadsheet values.
Leave Requests
Choose Full Day, AM Leave, or PM Leave, select Annual Leave, Sick Leave, or Other Leave, and enter your dates and reason. For planned leave, assign a teammate and leave handover notes when required by policy. The assigned cover receives a separate coverage request in Notifications and Leave Planner, with Accept cover and Reject cover actions. After coverage is accepted, the team lead separately approves or rejects the leave request from Overview notifications or Team review → Leave requests. Accepted cover can complete handover within the configured window before leave (14 days by default). If handover is still incomplete at the configured cutoff (one day by default), policy may cancel the request and notify the requester, cover, and lead. Check Leave Planner for dates, statuses, and only the balances the server permits you to see.
Integrations and Privacy
Integrations are Not connected. Calendar events, presence, and commit references are not proof of time worked and must not be treated as performance scores. You control the time entries you submit, and changes are retained for review.