Subsidiary revenue for 2025 is set out below, with the Shanghai office broken out from the other offices. The same revenue line is carried into the Q3 operating review and the October finance workbook.…
Subsidiary revenue is reconciled back to the annual report, with the October inventory worksheet tagged as one of the sources. Rounded disclosure figures must still tie to monthly operating data before sign-off.…
Performance is compared across operating entities. Inventory turnover is the one finance metric still awaiting follow-up before the next executive review, and the delivery-linked entities are flagged for a second read.…
The 2025 annual report draws on the ERP export and the finance tables listed here. Reviewer note: subsidiary revenue must match the disclosure table before the PDF is released.…
Subsidiary revenue by month and branch, including the October roll-up used in finance review. Column headers follow the disclosure schedule, and the branch codes match the entity list used in the board packet.…
This section summarizes 2025 revenue by subsidiary and explains the operating items that require follow-up in Q3 and October finance reviews.
| Subsidiary | Revenue | Net Profit | Inventory Turnover | Follow-up |
|---|---|---|---|---|
| Shanghai Office | 184.20m | 56.43m | 4.1x | Inventory review |
| North Region | 142.80m | 41.06m | 4.7x | Customer delivery |
| South Region | 116.35m | 33.72m | 5.0x | Renewal pipeline |
| Online Channel | 88.64m | 21.38m | 6.3x | Margin mix |
Subsidiary revenue for 2025 is set out below, with the Shanghai office broken out from the other offices. The same revenue line is carried into the Q3 operating review and the October finance workbook. Finance notes that the same revenue line is used in the Q3 operating review and October operating metrics workbook.
| Check | Evidence | Result |
|---|---|---|
| Revenue table | Ties to finance workbook | Matched |
| Inventory note | October metric source | Open follow-up |
| Review owner | Finance Operations | Approved |
| Item | Detail | Status |
|---|---|---|
| Source file | October workbook | Cross-checked |
| Review basis | Rounded disclosure | For report use |
| Downstream use | Q3 deck | Consistent |
| Status | Ready to cite | Tracked |
The schedule below reconciles management reporting to the annual-report disclosure table. Rounding differences are reviewed by Finance before publication.
| Month | Shanghai | North | South | Online | Total |
|---|---|---|---|---|---|
| May | 14.80m | 11.62m | 9.04m | 6.85m | 42.31m |
| Jun | 15.42m | 11.88m | 9.51m | 7.10m | 43.91m |
| Jul | 15.76m | 12.14m | 9.82m | 7.22m | 44.94m |
| Aug | 16.18m | 12.30m | 9.96m | 7.31m | 45.75m |
| Sep | 16.35m | 12.47m | 10.11m | 7.42m | 46.35m |
| Oct | 16.90m | 12.73m | 10.28m | 7.64m | 47.55m |
Customer feedback comments mention delivery delay in seven accounts, and the support team marks it as priority 1 for the next operating review. Owner and promised response date are recorded in the decision table below.…
Delivery delay is the top customer feedback theme this cycle: 7 accounts, priority P1, owned by Operations. Revised dates go out before Friday. Owner: Operations · Due: Friday 12:00 · Review: Next ops meeting…
Across the free-text customer feedback in this cycle, delivery delay and status visibility draw the most comments. Delivery delay is carried at the highest priority; the quotes below are grouped by account segment.…
Priority Tracker · June 2026 — Delivery delay · Accounts 7 · Priority P1 · Owner Operations · Status In progress · Next step Confirm revised dates Friday · Reply language · Accounts 6 · Priority P1 · Owner Support · Status Drafting · Next step Use one template…
Confirming the follow-up owner and response date for the affected accounts. Operations — please close out the delivery delay note before the next review. I will add the revised dates to the tracker as soon as they are confirmed.…
The October review groups feedback from support tickets, renewal calls, and post-delivery surveys. The most frequent theme is delivery delay, mentioned by seven accounts in the last three weeks.
| Theme | Accounts | Priority | Owner |
|---|---|---|---|
| Delivery delay | 7 | P1 | Operations |
| Invoice setup questions | 4 | P2 | Finance Ops |
| Renewal timing | 3 | P2 | Customer Success |
Customers are asking for status visibility before expected delivery dates change. Support recommends a Friday update to impacted accounts.
| Signal | Where found | Follow-up |
|---|---|---|
| Support tickets | Seven accounts | Friday update |
| Renewal calls | Date visibility | CS owner |
| Survey text | Status concern | Tracker note |
The table lists accounts that mentioned delivery timing in tickets or renewal calls. Names are grouped for follow-up rather than revenue ranking.
| Account Group | Signal | Requested Response | Owner |
|---|---|---|---|
| Priority Retail | Shipment slipped twice | Firm date and weekly update | CS Lead |
| North Renewal Pool | Status not visible | Delivery dashboard link | Support |
| Online Channel | Unclear handoff | Single owner for updates | Operations |
| Enterprise Pilot | Phase-one date at risk | Escalation call | Ops Manager |
“We can handle a late delivery if we see the status early.” Another account asked whether the new promised date had been confirmed by warehouse operations.
| Account group | Next message | Internal owner |
|---|---|---|
| Priority Retail | New date confirmed | CS Lead |
| North Renewal Pool | Dashboard link | Support |
| Enterprise Pilot | Escalation call | Ops Manager |
Customer feedback comments mention delivery delay in seven accounts, and the support team marks it as priority 1 for the next operating review. Owner and promised response date are recorded in the decision table below.
| Decision | Reason | Next Step |
|---|---|---|
| Set delivery delay to P1 | Seven accounts, renewal exposure | Operations plan due before weekly review |
| Keep invoice setup at P2 | Common but not revenue-blocking | Add FAQ link to onboarding |
| Watch renewal timing | Three accounts asked for date clarity | CS to update account notes |
Support will update the tracker after each account receives a response. The next monthly review will compare open items against the operating action list.
| Theme | Why priority | Review path |
|---|---|---|
| Delivery delay | Renewal exposure | Operating review |
| Invoice setup | FAQ can solve | Onboarding guide |
| Renewal timing | Small count | Account notes |
The team agreed that customer-facing updates should go out before the next operating review. Operations will provide dates; Customer Success will send account-specific responses.
| Action | Owner | Due | Status |
|---|---|---|---|
| Confirm revised delivery dates | Operations | Friday 12:00 | Open |
| Draft customer email | Customer Success | Friday 15:00 | In progress |
| Update feedback tracker | Support | Friday 17:00 | Open |
| Add topic to operating review | Ops PM | Monday | Scheduled |
| Task | Proof | Owner |
|---|---|---|
| Confirm dates | Warehouse note | Operations |
| Send responses | Email log | CS |
| Update tracker | Feedback sheet | Support |
문서를 실제 모습 그대로 표시
내 PC에서 바로 실행되는 더 스마트하고 빠른 검색. 로컬 실행으로 더 안전합니다.
0.01초 만에 결과 확인
유형, 크기, 날짜별 맞춤 검색
단어를 넘어 문맥으로 검색
이미지를 바로 미리보기
원하는 문단으로 즉시 이동
Each service area in the responsibility matrix below is assigned a daily owner and an exception owner: Operations, Facilities Support, and the vendor on-site team. The loading dock requires immediate response.…
Service coverage is set out in Schedule A. Disputes over a service area are resolved against the responsibility table before escalation, and only the contract owner may escalate beyond the operations manager.…
Weekend coverage for the loading dock and customer lobby is updated as follows, using the responsibility matrix in Schedule A. All other service areas keep the response rules recorded in the executed agreement.…
Filed with the contract records: the vendor team holds several on-site obligations, and insurance evidence is retained with the schedule for the full term. Renewal is due before the next weekend coverage window opens.…
Open question: should the loading-dock owner in the responsibility matrix be updated after the latest customer feedback review? Delivery handoffs were late twice in the same week, both during the vendor on-site shift.…
This schedule is issued with the master services agreement to identify each service area, the daily owner, exception owner, response frequency, and the evidence that must be kept in the contract folder.
| Service area | Daily owner | Exception owner | Response rule |
|---|---|---|---|
| Main entrance | Operations desk | Duty lead | Hourly checks during visitor hours |
| Storage zone | Facilities support | Facilities supervisor | 30-minute rounds during peak inventory movement |
| Loading dock | Vendor on-site team | Operations manager | Immediate response when handoff is delayed |
| Customer lobby | Customer Success | Support lead | Daily status note before close of business |
| Returns desk | Operations desk | Project owner | Same-day confirmation for unresolved cases |
| Escalation cue | Owner to notify | Evidence kept with schedule |
|---|---|---|
| Delay affects customer appointment | Operations manager | Dock log and customer feedback summary |
| Repeated misses in the same week | Project owner | Weekly exception report |
| Vendor responsibility unclear | Contract owner | Master agreement clause cross-reference |
Each service area in the responsibility matrix below is assigned a daily owner and an exception owner: Operations, Facilities Support, and the vendor on-site team. The loading dock requires immediate response.
| Zone | Response window | Evidence retained | Review |
|---|---|---|---|
| Loading dock | Immediate | Dock log and handoff photo | Weekly |
| Storage zone | 30 minutes at peak | Inventory movement sheet | Weekly |
| Main entrance | Hourly during visitor hours | Visitor register | Monthly |
| Customer lobby | Same day | Status note filed before close | Monthly |
| Returns desk | Same day | Case confirmation record | Monthly |
AI는 인터넷의 방대한 정보를 알지만, Gety는 여러분의 업무를 이해하게 돕습니다. 백그라운드에서 파일을 검색 하고 관련 맥락을 자동으로 제공합니다.
Claude, ChatGPT, OpenClaw, Cursor 등 무엇이든 가능합니다. Gety는 MCP, API, CLI를 통해 모든 AI와 연결됩니다.
Review Document to be Shared with ClaudePlease review the content below before continuing.
…Q4 plan assumes $2.4M in enterprise ARR and $3.1M in first-year bookings. Average implementation: 78–104 hours per account…
…SSO setup target under 4 hours. Admin satisfaction score: 40+. 2 design partners live by September 30, 2026…
검색과 인덱싱은 오직 로컬에서만 이루어집니다. 사용자가 승인한 스니펫만 AI와 공유되므로 안심할 수 있습니다.
Gety로 검색8개 파일 발견
Approval memo.docxRisk register.pdfProject Aurora brief.docx
