The field, on the record.
Equipment in classrooms, cables in ceilings, technicians on ferries — Crest keeps all of it accountable: serialized stock, a movement ledger that never forgets, visit reports that submit atomically, and budgets that carry their own approval history.
crest / portal / visitsTechnical visit · SPCM
Preventive maintenance — registrar's office, new SHS building
Aug 19 · 07:40 → 14:30
Replaced three failed patch runs to the SHS wing, deployed a spare access point from stock, and confirmed tapping stations at the registrar. Outcome: resolved on site. Follow-up: schedule senior-high server check before term 2.
Stock movements · submitted atomically
UTP Cat6 patch cable×3
SN-4821-4823Access point (deployed)×1
SN-AP-0142Client acknowledgement — “Received and verified.” — Registrar
reviewed · SecretaryA visit report that holds up.
Technical visits are evidence: what was done, what it consumed, who acknowledged it. Drafts touch nothing; submission applies every stock movement in one transaction.
- Context
- Date, type, school, on-site contact, travel & arrival/departure times
- Narrative
- Work done, outcome, follow-up — the report a reviewer can act on
- Proof
- Photos follow the same private, permission-checked document model
- Stock lines
- Parts consumed, equipment deployed or retrieved — scanned by serial
- Acknowledgement
- Client sign-off recorded on the visit
- Review
- Owner, Administrator, or Secretary reviews; technicians manage their own
Inventory that counts itself.
For serialized items, quantity on hand equals the serials physically in stock — scanned by barcode wand, typed, or read with the device camera. Every movement writes the ledger.
crest / inventory / stockStock · movement ledger
serialized · scanned
Access point · dual-band
NET-AP-01 · serialized · 12 deployed
7 on hand
UTP Cat6 cable · 305 m box
NET-CBL-06 · reorder point 3
low stock2 on hand
42″ display · SHS classrooms
AV-DISP-42 · serialized · 34 deployed
9 on hand
Serialized items count themselves: quantity on hand equals the serials in stock. Deploy, consume, or write off — every movement scans the physical unit it touches.
Deployments are a state, and a history.
What's at which school today is one view; how it got there is the immutable ledger underneath. Retrievals and decommissions return equipment through the same audited movements.
Deploy with serials
Assign equipment to a client site with quantity, serial, actor, and timestamp.
Derive site visibility
Technician portals show client sites derived from currently deployed assets.
Purchase → expense
A stock purchase can create its linked expense in one motion.
Field money, governed.
Activity budgets for travel, training, implementations, and school visits preserve their authorization as relational history — not a note in a chat thread.
01
Authorization
A budget is created with its original approval — travel, training, school visits, errands.
02
Field spend
Sales & Marketing team members report expenses against it, including genuine over-budget spending.
03
Requests
Additional funds are requested and partially approved — each a recorded decision.
04
Reconciliation
Releases and final reconciliation close the loop; rejected items never move balances.
Authorized equals the original budget plus approved additions. Sales & Marketing team members can report genuine over-budget spending and request funds — but never approve their own requests, record releases, or reconcile. Those boundaries are enforced server-side. Next: the focused portals your field team works in.
See your fleet, serialized.
We'll load a sample of your stock items and deployed units, then run a visit submission end to end — draft, scan, submit, ledger.
Invitation-only · Onboarding guided by the team that built it