Complete feature list

Everything Duxor does, in one list.

Not a highlight reel. This is the full working surface of the product, grouped the way the console is grouped, with a sentence on each so you can tell what it actually does. If something here is not clear, ask us and we will show you the screen.

This is Duxor v1. Anything we deliberately do not do is listed at the bottom, because knowing where a product stops is worth as much as knowing where it starts.

Book a walkthrough See it on screen

AThe job record

A1Projects: their own job number, work type, contract value, and dates.
A2Jobsites: kept separate from the project, with a map pin, so presence and access notes attach to the place while budget and schedule attach to the work.
A3Lifecycle: planned to active, on hold, and complete, with only the legal next moves offered.
A4Scope of work: plain language, with every revision kept on the job's own history.
A5Project team: project manager, superintendent, and foreman by role, and who held each before.
A6Project timeline: everything that has happened on the job, in the order it happened, written as sentences rather than log lines.
A7Job Book: every module's slice of one job on a single screen, so a job review is one page.
A8Closeout readiness: what is still open before the job can be closed.
A9Milestones: target and actual dates, visible to the customer.
A10Permits: applied to issued to closed, carrying the jurisdiction's own number.
A11Inspections: scheduled, passed, or failed. A failed inspection keeps its record and the re-inspection is a new one.
A12Daily logs: one per job per day, corrected as new versions rather than overwritten.
A13Safety log: toolbox talks, incidents, and near misses.
A14Custom fields: your own fields on projects, people, vendors, and leads.
A15Task templates at project birth: a standard startup checklist or punch list that lands when a job is created, the sibling of estimate and shift templates.
A16Warranty period: stamped automatically when a job completes.

BScheduling

B1Shifts: real start and end times, or all day, and any number of people on one shift.
B2Arrival windows: the crew and the customer both know it is a 7:30 to 8:00 job.
B3Crews: save a roster, put the whole crew on a job as one shift, and move it as one thing.
B4Shift templates: save a standard week and apply it to any week.
B5Double-booking detection: warns and never blocks, because crews double-book on purpose but should never do it unknowingly.
B6Leave-aware scheduling: approved time off shows on the board and warns when you schedule over it.
B7Publish and acknowledge: the office knows the crew has actually seen the week.
B8Decline with a reason: it reaches the office three ways rather than sitting on a board nobody reads.
B9Unacknowledged-change alerting: work that moved and nobody has re-confirmed.
B10Work dependencies: a shift can wait on another shift, an inspection, a milestone, a task, an RFI, or a submittal.
B11Ripple view: if this moves, what else moves.
B12Gantt: read only, for looking at the shape of a job.
B13Weather days: recorded against the schedule.
B14Calendar feed: per person, to subscribe in Google, Outlook, or Apple Calendar.
B15Arrival prediction from the truck: a setting, off unless you turn it on. Company vehicles report their position, Duxor routes it against the jobsite, and you know who is running late, with nothing installed on anyone's phone. Phone-based arrival is its own setting, and the crew is always told what is on.

CThe field

C1Today: the phone screen with the day's work, the crew on it, and what needs acknowledging.
C2Presence: on my way, arrived, leaving site, as deliberate taps rather than tracking.
C3Crew check-in from one phone: a real crew is one person with the app and several without, and the record always says who spoke for whom.
C4Office check-in: for the day a phone dies, always visible as an override.
C5Photos: straight from the camera onto the job.
C6Access needs: gate code, dog, lockbox, and whether somebody has to be home, on the day's card.
C7Spoken briefing: the day read aloud, for hands that are full.
C8Installable phone app: on the home screen, with push notifications.
C9Offline: the day opens with no signal, and check-ins, clock punches, and acknowledgements queue and send themselves when it returns. Photos need a connection.
C10Geofence evidence: recorded on the punch, with nothing tracked between punches.
C11Press to talk: the crew speaks instead of typing.
C12Wrong-site detection: a punch at a different active jobsite, flagged from evidence already captured.

DTime, pay, and the workforce

D1Time punches: never edited. A correction supersedes the old one and both are kept.
D2Work sessions: clock in to clock out, with breaks, one open session per person.
D3Geofence posture: off, warn, or block, per company, with the distance named.
D4Weekly timesheets: review and approval, person by person.
D5Labor posting: approving the week posts each session to job costing exactly once, and resumes safely if interrupted.
D6Overtime classification: weekly, daily, double time, and the seventh-day rule, so hours reach payroll already split. Only the timesheet knows which hours were past a threshold.
D7Cost rate basis: tell Duxor whether the rate you type is blended or a base rate.
D8Overtime premium allocation: put the premium on a job, spread it across the week, or keep it out of job costing.
D9Payroll CSV: the approved week, permission-gated and audited.
D10Timecards: hours the office enters, with rates.
D11Trades and default cost rates: per person, per company.
D12Time off: policies, requests, approvals, and a balance ledger that is added to rather than overwritten.
D13Certifications: expiry tracking, with warnings before somebody is put on work that requires one.
D14Workforce groups: cohorts that are not crews.
D15Roster: invite, assign roles, suspend, photos, emergency contact, hire date.

ECommunication

E1One room per audience, per job: the crew's room, the client's room, and one for each subcontractor. A candid remark about pricing cannot reach the customer.
E2Account conversations: discuss a customer across every job they have.
E3Group conversations: rooms you create, for exactly the people you add.
E4Direct messages: one to one, between staff. A customer's questions belong in their job's own room.
E5Record conversations: a discussion attached to any record, whether a task, a change order, a bill, an RFI, or a vendor.
E6Subject references: a message can be about an invoice, and the card resolves per reader, so a number never leaks to somebody who should not see it.
E7Mentions: reach the person named and nobody else.
E8Read state and receipts: who has seen what, staff side.
E9Unanswered-message alerting: somebody outside the company has written and nobody has opened it.
E10Translation: everyone reads in their own language and their own words are preserved, with the source language labeled and the translating model recorded for audit.
E11Company announcements: broadcast to every employee, with acknowledgement.
E12Turn a message into work: a task, an RFI, or a change order, without losing the conversation.
E13Text message replies: a customer's text lands in their job's client room, as them.
E14Durable inbox: plus push, so a worker whose phone was off still finds the message.
E15Email replies: land in the right room too, the way text messages already do, so somebody who will never install anything still takes part.
E16Impact from a message: one tap runs the impact view against what somebody just told you.

FSales and estimating

F1Leads: a pipeline board, from first call to won.
F2Activity log: calls, texts, emails, meetings, and notes, per lead.
F3Follow-up dates: with alerting when a lead is going cold.
F4Lead routing and ownership: every lead has one owner, so nobody assumes somebody else called back.
F5Public quote-request form: publish it on your own website and submissions land as leads.
F6Customer accounts: a named party with a contact rolodex, so repeat business stays connected.
F7Appointments: site visits, sales meetings, and estimate appointments, each with an outcome.
F8Estimates: lines, sections, unit cost, and margin.
F9Markup-driven pricing: enter the cost and the markup and Duxor prices it.
F10Cost catalog: reusable priced items.
F11Assemblies: reusable bundles that can nest inside each other.
F12Estimate templates: a catalog-linked line re-prices from today's catalog rather than going stale.
F13Options and alternates: resolved when the customer accepts, so the declined ones drop out of the contract.
F14Allowances: budgeted amounts for what has not been chosen yet.
F15Proposal with e-signature: signed by name on a link, with an expiry date.
F16Acceptance seeds the job: the project, its budget, and its allowances, in one move.
F17Overhead: a burden rate over a bid's own cost, so the margin you see is what is actually left after running the business.
F18Win rate and conversion: how many estimates become jobs, reported over time.
F19Sales commissions: accrued automatically when a job is won.

GBilling and getting paid

G1Invoices: line items, or a single amount for a deposit or draw.
G2Progress billing: deposits, draws, and finals against the job.
G3Retainage: held on each draw and released at completion.
G4AIA-style progress billing: a schedule of values, where the continuation sheet is derived from the invoices rather than typed twice.
G5Payment ledger: partial payments, with the balance always computed from what was actually received.
G6Bill a person: rather than a job, so receivables age by who owes them.
G7Customer statements: across all their jobs, printable.
G8AR aging: by party, current through 90 plus.
G9Printable documents: the invoice itself, and a certificate for an AIA application.
G10Online payment: card and bank, from the customer's own portal.
G11Overdue alerting: chases what is still owed rather than the face amount.
G12A billing plan at acceptance: the draw schedule generated from the estimate you just won, the same way the schedule of values already is.

HCosts and paying others

H1Job costing: actual, committed, and projected, with margin.
H2Cost codes: mapped to categories, so a code and its kind can never disagree.
H3Budgets: snapshotted from the accepted estimate and revised as versions.
H4Purchase orders: vendor links and promised delivery dates.
H5Receiving: when the material actually arrived, recorded separately from when the bill lands.
H6Late-delivery alerting: only for orders that carry a promised date, so it never cries wolf.
H7Vendor bills: a real lifecycle, where approving posts the cost and closes the purchase order it fulfills.
H8Bid requests: invite, compare, and award, and the award cuts the purchase order.
H9Back charges: the cost of fixing a sub's work, raised against them and tracked until settled.
H10Approval chains: above an amount you set, Approve becomes a request and named people sign in order.
H11Work orders: printable for the trade doing the work.
H12QuickBooks export pack: your own chart of accounts, with a ledger of what has already been exported so nothing posts twice.

JContract administration

J1Change orders: approving moves the contract value and the completion date together.
J2Customer approval in the portal: the customer approves their own change orders, which is where the decision belongs.
J3RFIs: the question and the answer of record kept as separate facts, numbered, and chased when they go past the promised date.
J4Submittals: tracked through their review cycle, and work can wait on approval.
J5Lien waivers: the four standard forms, sent as a link and signed by name, with the signature and time captured.
J6Selections and allowances: the variance becomes a change order in one click.
J7Impact view: given something that just changed, what work, which people, what paperwork, and what money it reaches. It describes, it never acts.

KEquipment, materials, and vendors

K1Fleet and equipment register: who has each machine, on which job, and what state it is in.
K2Forward reservations: equipment booked ahead, with double-bookings flagged.
K3Vehicle GPS: a setting, off by default. Turn it on and you see where every truck is, which feeds arrival times, utilization, and a flag when a vehicle is sitting at a jobsite it was not sent to.
K4Maintenance: schedules, service history, and recurring intervals.
K5Meter-based service: hours or miles instead of dates, so the machine that is earning gets serviced and the idle one is not.
K6Rentals: the rate, the term, and the return date, flagged when a rented machine is still on site past it.
K7Insurance and registration expiry: tracked, so nothing lapses quietly.
K8Materials: on-hand quantities, reorder points, and movement history.
K9Consuming material to a job: writes a real cost against it.
K10Vendors and subcontractors: certificate-of-insurance tracking, with expiry warnings before they are on site.
K11Vendor records: contacts, payment terms, tax ID, and 1099 flag.
K12Camera registry: which cameras exist, which job each watches, who may look, whether it is still reporting, and a link to the live view. Snapshots and time-lapse need a camera vendor.

LDocuments and photos

L1Photos and files: on the job, filed into folders.
L2Versions: a new revision supersedes the old one and keeps it.
L3Notes on files: a permit condition lives with the permit.
L4Photo tags: with filtering, for finding the framing shots.
L5Capture provenance: who took it, when, and where.
L6Internal-only marking: honored on every customer-facing read.
L7CompanyCam connector: for contractors already using it, photos flow in with their capture time, place, and photographer.
L8Signatures and approvals on documents: reusing the e-signature that already runs proposals and lien waivers, and the approval chains that already run bills.

MWhat the customer gets

M1Their own portal: per job, by explicit grant, under your name.
M2Their project's story: photos, the documents you allow, milestones, invoices, and service tickets.
M3Change orders and selections: they approve and confirm themselves, from the portal.
M4Warranty reports with a photo: from their phone, landing as a real ticket in your service queue.
M5Questions, answered: is anyone coming tomorrow, what do I still owe. Anything Duxor should not answer reaches you instead, in their room, rather than being refused.
M6Arrival notices: who is coming, from which company, when, and why.
M7End-of-day summaries: what happened, and when somebody is next expected.
M8Schedule change and cancellation notices: nobody stays home for nothing.
M9What the job is waiting on: phrased so it never carries internal blame.
M10Their own preferences: which channel, how much detail, and quiet hours on their own clock. Bills and decisions always reach them; the day-to-day chatter is theirs to decline.
M11Co-branding: by default, with full white-label on the Enterprise plan.

NWhat subcontractors and vendors get

N1Their own portal: scoped to the jobs you grant them, free.
N2Purchase orders: sent to them to acknowledge, so acceptance is on the record.
N3Bid requests: to price or decline, without needing to be on the job yet.
N4Submit a bill: it lands as a draft your office approves. No money moves without review.
N5Their own insurance dates: kept current by them, so chasing certificates stops being your job.
N6Their schedule: the published shifts for their crew on each granted job.
N7Their own bills: each one visible with its progress, draft to approved to paid.
N8One home across every contractor: a sub works for several, and sees all of them in one place.

PKnowing what needs you

P1Attention rules: 33 of them, each landing on the screen that fixes it. When one rule fires many times, it collapses into a single line with the count, so a bad import cannot bury the real warning.
P2Morning brief: is today normal, and what changed.
P3Weekly digest: the week in numbers, every Monday.
P4Ask Duxor: questions about your own company's data, by voice or typing, answered from what you are already entitled to see.
P5Prepared actions: say what you want and Duxor turns it into proposals. Anything financial, contractual, outward-facing, or hard to undo waits for a person to confirm it.
P6Relationship risk: the customer who is quietly going wrong, from signals rather than guesswork.
P7Automation: when this happens, do that. A won job can create its kickoff task and notify the right people.
P8Reports: job profitability, AR aging, estimate versus actual, period comparison, conversion, and win rate.
P9Search: every record type, including by number.
P10More by voice: book an appointment, move an inspection, capture a note, tell everyone on a job, and have Duxor write today's daily report from the work, the photos, and who was on site.

QYour data, and the platform

Q1Export: 29 lists as spreadsheets, or the whole account as one file. Your data is yours and leaving is not punished.
Q2Import: vendors, catalog, materials, and leads, with a preview before anything is created.
Q3Migration: 43 loaders from your current system, a row-by-row record of what came in and what did not, and a durable map back to the source.
Q4Archive: history worth keeping but not worth merging.
Q5Public API: keys you issue and revoke yourself, scoped by family.
Q6Webhooks: events pushed to your own systems, with signed deliveries.
Q7One login across companies: every company you belong to, with a switcher.
Q8Magic-link sign-in: a link in the email signs you in, alongside passwords.
Q9Roles and permissions: a matrix that shows what is actually enforced rather than what was intended.
Q10Self-serve signup: create your company yourself, with a first-run setup wizard.
Q11Live updates: what changes on a phone appears on the office screen in about a second.
Q12Four languages: messages between people translate across English, Spanish, Polish, and Ukrainian, each reader in their own.
Q13Audit history: every business action on an append-only record.
Q14Two-factor sign-in: because a magic link is only as safe as the inbox it lands in.
Q15Encryption at rest: alongside the encryption in transit that is already in place.

ZWhat Duxor deliberately does not do

Every product has a boundary. Being straight about ours saves you a demo.

Z1It is not your accounting system. Duxor runs the operational money and hands clean numbers to QuickBooks. There is no general ledger here.
Z2It does not run payroll. It classifies hours, including overtime, and exports them. Rates, deductions, and filings belong to a payroll provider.
Z3It is not a critical-path scheduling engine. Duxor records what work waits on what and flags what is at risk. It will not level resources, and it will never silently move five crews because one inspection failed.
Z4It is not BIM, and it does not do model coordination or clash detection.
Z5It does not track anyone by default, and never outside a scheduled shift. Presence is the crew's own taps plus geofence evidence at the punch. Arrival prediction is coming as a setting, off unless you turn it on, because some companies require the app and most do not.
Z6It does not read the mood of your messages. The signals it acts on are countable things: schedule changes, unanswered messages, portal visits.
Z7It is not a hardware company. Duxor connects to cameras and equipment you already own.

Ask us about anything on this page