Operating.app Allocation Updates — March 25, 2026
Summary
Updated allocations to align with end-of-month (March 31, 2026) cutoff for billing cycle.
Changes Made
Allocations Updated (32)
Allocations changed to end March 31, 2026 via API:
| Status | Count |
|---|---|
| ✅ Successfully updated | 32 |
| ⚠️ Could not update (future start date) | 8 |
Allocations Not Updated (8) — ✅ PTO Confirmed
These allocations are PTO/Time Off entries with future start dates. They correctly remain as planned vacation time and should NOT be changed.
| Person | Allocation Dates | Duration | Type |
|---|---|---|---|
| Zoran Selinger | May 11-13, May 20-22 | 2× 3-day | PTO |
| Hannah Wang | Apr 9-16 | 8 days | PTO |
| Kaela Gallagher | Apr 23-24, Jun 11-12 | 2× 2-day | PTO |
| Mustafa Raja | Apr 1-10 | 10 days | PTO |
| Pranav Narahari | Apr 17-24 | 8 days | PTO |
| Rico Rejoso | Apr 10 | 1 day | PTO |
Client: Time off (ID 36052)
Project: Time off (ID 81533)
Status: ✅ Correct — These are legitimate forward-looking PTO bookings and should remain unchanged.
API Command Used
API_KEY=$(op read "op://Brainforge AI Team/Operating.app API Key/password")
# Update each allocation
curl -s -X PATCH "https://api.operating.app/v1/allocations/{id}" \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{"through": "2026-03-31"}'Verification
# Check remaining allocations past March 31
curl -s "https://api.operating.app/v1/allocations" \
-H "Authorization: Bearer $API_KEY" | jq -r '
.data[] | select(.archivedAt == null and .through > "2026-03-31") |
"\(.id): Through \(.through) (Position: \(.positionId))"
'Date: March 25, 2026
Executed by: API automation
Status: 32 updated, 8 pending (future start dates)